[JBoss Messaging] - Failed to download and/or install client side AOP stack / Co
by pdestrais
Hi,
I just installed the latest JBoss messaging 1.2 as a replacement to JBossMQ.
In our application, in the processing of an MDB, we are creating a acknowledgement message that we submit on a queue.
When the message is created on the queue (through Spring's JMSTemplate), we get this error :
2007-03-02 15:36:46,290 ERROR [org.jboss.jms.client.JBossConnectionFactory] Failed to download and/or install client side AOP stack
org.jboss.jms.util.MessagingNetworkFailureException: Failed to connect client
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createClient(ClientConnectionFactoryDelegate.java:288)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$getClientAOPStack$aop(ClientConnectionFactoryDelegate.java:222)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPStack(ClientConnectionFactoryDelegate.java)
at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:67)
at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:199)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:88)
at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:83)
at org.springframework.jms.core.JmsTemplate.createConnection(JmsTemplate.java:760)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:420)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:477)
at com.notary.app.taxsocnot.notice.jms.XmlSenderImpl.send(XmlSenderImpl.java:42)
at com.notary.app.taxsocnot.notice.jms.XmlSenderImpl.send(XmlSenderImpl.java:37)
at com.notary.app.taxsocnot.notice.service.NoticeManagerImpl.sendNotificationAck(NoticeManagerImpl.java:608)
at com.notary.app.taxsocnot.notice.service.NoticeManagerImpl.receiveNotification(NoticeManagerImpl.java:544)
at com.notary.app.taxsocnot.notice.service.NoticeManagerImpl$$FastClassByCGLIB$$7e317016.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:685)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:623)
at com.notary.app.taxsocnot.notice.service.NoticeManagerImpl$$EnhancerByCGLIB$$d5118cf3.receiveNotification()
at com.notary.app.taxsocnot.notice.service.impl.NoticeFacadeImpl.processNotification(NoticeFacadeImpl.java:95)
at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:287)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy65.processNotification(Unknown Source)
at com.notary.app.taxsocnot.notice.service.ejb.ReceivePRNOTIFBean.onMessage(ReceivePRNOTIFBean.java:72)
at sun.reflect.GeneratedMethodAccessor286.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:495)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:116)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:109)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:402)
at org.jboss.ejb.Container.invoke(Container.java:954)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:987)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1287)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:266)
at org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:153)
at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:791)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14.invoke(SessionAspect14.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.run(JBossSession.java:211)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Couldn't find valid client invoker class for transport 'bisocket'
at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:333)
at org.jboss.remoting.Client.(Client.java:178)
at org.jboss.remoting.Client.(Client.java:157)
at org.jboss.remoting.Client.(Client.java:126)
at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createClient(ClientConnectionFactoryDelegate.java:282)
... 68 more
Being new to Jboss messaging, I'm wondering if this could be a configuration problem (and if yes, what it could be) or if this is an issue.
Thanks for your help.
Philippe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024660#4024660
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024660
19Â years, 1Â month
[JBoss Seam] - Back button after logout - solved through Seam?
by hamtho2
Hi,
I just included the Seam Security into my application and I´m really thrilled about the very easy and effective solution to all the security issues. I like the "redirect-to-protected-pages-through-login-page"-feature especially. It´s always a common problem and it´s so easy this way.
This is really the first really good webbased security system, I´ve seen so far. Congratulations to this.
But I come to another standard web-application-problem: pressing the back button after logout. Is there an elegant way through the seam security feature to prevent users from seeing protected pages with pressing the back-button?
I know, that there are some options for preventing the browser from caching (e.g. through jsp:scriptlet), as the usual meta-tags aren´t enough in most cases, but I think this is not a very elegant solution and I´d prefer to set these header-information through something like the SeamServlet or the FacesServlet.
Is there already anything included in Seam? If not, wouldn´t that be anything, that should be included?
Thanks for your answers
Thomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024655#4024655
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024655
19Â years, 1Â month
[JBoss jBPM] - Swimlane asssignment
by gscheibel
Hi all! I having the following problem:
When I have two tasks in diferents task nodes using the same swimlane, jbpm is not invoking the assign handler from swimlane when it reaches the second task.
here is my jpdl:
| <process-definition xmlns="urn:jbpm.org:jpdl-3.1" name="webtest">
| <swimlane name="swim1">
| <assignment class="swim.Swim1"/>
| </swimlane>
| <start-state name="start">
| <transition name="ok" to="task1" />
| </start-state>
| <end-state name="end1" />
| <task-node name="task1">
| <task name="task1" swimlane="swim1"/>
| <transition name="t1" to="end1" />
| <transition name="tr2" to="task2" />
| <event type="node-enter">
| <action name="action1" class="action.Action1" />
| </event>
| <event type="node-leave">
| <action name="action2" class="action.Action2" />
| </event>
| </task-node>
| <task-node name="task2">
| <task name="task2" swimlane="swim1"/>
| <transition name="ok" to="end1" />
| </task-node>
| </process-definition>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024654#4024654
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024654
19Â years, 1Â month