-
30. Re: Trouble with jms-topic
Hi,
I tried patching my version with the jars you mentioned.
When I start up the server now, I get the following Exception:15:54:40,625 INFO [DatabaseInitializer] java:/juddiDB datasource is already initialized 15:54:40,625 INFO [JuddiRMIService] starting juddi RMI service 15:54:40,656 WARN [ServiceController] Problem starting service jboss.esb:service=JuddiRMI java.lang.NullPointerException at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:89) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy27.start(Unknown Source) at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:356) at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595)
After that allot of stuff is waiting for the deployment of other stuff, like:.... org.jboss.deployment.DeploymentInfo@25c1c62b { url=file:/C:/jbossesb-server-4.2GA/server/default/deploy/soap.esb/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jbossesb-server-4.2GA/server/default/deploy/soap.esb/ altDD: null lastDeployed: 1204815287046 lastModified: 1188964694000 mbeans: org.jboss.deployment.DeploymentInfo@376b8469 { url=file:/C:/jbossesb-server-4.2GA/server/default/deploy/spring.esb/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jbossesb-server-4.2GA/server/default/deploy/spring.esb/ altDD: null lastDeployed: 1204815287046 lastModified: 1188964694000 mbeans: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:service=JuddiRMI State: FAILED Reason: java.lang.NullPointerException I Depend On: jboss.jca:service=DataSourceBinding,name=juddiDB Depends On Me: jboss.esb:service=ESBDeployer --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:service=JuddiRMI State: FAILED Reason: java.lang.NullPointerException I Depend On: jboss.jca:service=DataSourceBinding,name=juddiDB Depends On Me: jboss.esb:service=ESBDeployer
Do I need to update any more libs? Or is it even possible to patch my version?
I would really like to test this with my version, until I know whether I can change versions.
Regards
Andreas -
31. Re: Trouble with jms-topic
I'll try patching a 4.2GA a little later on today and see what is needed.
If you like could you try adding esb.juddi.xml to the jbossesb.sar directory.
Thanks,
Daniel -
32. Re: Trouble with jms-topic
This is what I did to patch 4.2GA:
Replaced the following jars in jbossesb.sar/lib:jbossesb-rosetta.jar jbossesb-config-model.jar
Added the following files to jbossesb.sar:actionArtifactMap.properties esb.juddi.xml
To run the helloworld_topic_notifier quickstart from the trunk, but against your 4.2GA server, update samples/quickstarts.properites and set org.jboss.esb.server.home.
You will also need to copy the following files from your 4.2GA server to trunk/product/build/jbossesb-server-4.2.1GA (for JBM and JBR):server/default/lib/jboss-messaging.jar server/default/lib/jboss-remoting.jar client/jboss-messaging-client.jar client/jbossall-client.jar
This worked for me. Can you give that a try?
Regards,
Daniel -
33. Re: Trouble with jms-topic
Hi,
I tried it with the files you said.
When I start up the server now, I get this message over and over again,
until I kill the server.18:32:51,343 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,359 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,375 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,468 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,500 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,515 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f 18:32:51,578 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b69f6e5c-a251-4c24-a3de-9b3ed8235f3f RelatesTo: jms:correlationID#b69f6e5c-a251-4c24-a3de-9b3ed8235f3f
Any thoughts?
Regards
Andreas -
34. Re: Trouble with jms-topic
Ok, this is clearly not working.
I'll add the patch to my checked out 4.2GA and build that.
If you email me I'll send you a pathed jbossesb-rosetta.jar.
I've tested this locally and it works.
Just klick on my user name and use that email adrress.
Regards,
Daniel -
35. Re: Trouble with jms-topic
Hi,
since I tried migrating to the new esb versions the last few days,
I hadn't tried that patch until today (I really hoped I wouldn't need too).
Sadly I have to move back to 4.2GA now, because I have a Client application,
that just can't be persuaded to receive jms-messages from the 4.2.1 version.
I think it's because of the new JBM version, but can't be sure about that.
After I tried running the 4.2.1 version with diffrent versions of JBM (1.3, 1.4GA, 1.4SP3),
and juggling with loads of other libs (like jboss-remoting), I finally had to give up.
Because I get next to no output from the client application, and no errors from the esb
I just can't figure out what goes wrong, besides the client don't getting the messages from the jms-queue.
So I had to go back to 4.2GA (I know it worked there) an try that patch.
Im using the checked out 4.2GA version from the repository.
I wasn't really sure whether I had to replace all the files mentioned,
or just rosetta, so I started just replacing rosetta.jar in jbossesb.sar/lib & soapui-client.sar.
The esb starts that way, but when I deploy the service that publishes on the topic,
I get a class-cast exception.org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:176) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:160) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:79) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:79) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.jboss.soa.esb.ConfigurationException: Unexpected exception while instantiating action instance at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:348) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:329) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:140) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:171) ... 51 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:344) ... 54 more Caused by: org.jboss.soa.esb.ConfigurationException: Failed to configure JMS Queue for routing. at org.jboss.soa.esb.actions.routing.JMSRouter.createQueueSetup(JMSRouter.java:280) at org.jboss.soa.esb.actions.routing.JMSRouter.<init>(JMSRouter.java:133) at org.jboss.soa.esb.actions.routing.JMSRouter.<init>(JMSRouter.java:113) ... 59 more Caused by: java.lang.ClassCastException: org.jboss.jms.destination.JBossTopic cannot be cast to javax.jms.Queue at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.<init>(JMSRouter.java:306) at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.<init>(JMSRouter.java:284) at org.jboss.soa.esb.actions.routing.JMSRouter.createQueueSetup(JMSRouter.java:278) ... 61 more 20:13:21,417 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
So I tried replacing jbossesb-config-model-1.0.1.jar in jbossesb.sar/lib &
adding actionArtifactMap.properties & esb.juddi.xml to jbossesb.sar.
As soon, as I replace jbossesb-config-model-1.0.1.jar I get the following error, while starting the esb:20:48:59,511 WARN [ServiceController] Problem starting service jboss.esb:deployment=jbossesb.esb java.lang.NoClassDefFoundError: org/jboss/soa/esb/listeners/config/xbeanmodel/JmsProviderDocument$JmsProvider at org.jboss.soa.esb.listeners.config.mappers.JmsListenerMapper.map(JmsListenerMapper.java:63) at org.jboss.soa.esb.listeners.config.ESBAwareGenerator.addESBAwareConfig(ESBAwareGenerator.java:103) at org.jboss.soa.esb.listeners.config.ESBAwareGenerator.generate(ESBAwareGenerator.java:85) at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:147) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:98) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:78) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy30.start(Unknown Source) at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.soa.esb.listeners.config.xbeanmodel.JmsProviderDocument$JmsProvider at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 119 more
Did I do something wrong, or do I need to update more files?
Do I only have to replace roserra.jar or the other files too?
Sorry I have to dig this up again,
but I really just want this to work now,
and just can't figure out whats going wrong.
Thanks for the help!
Regards
Andreas -
36. Re: Trouble with jms-topic
Hi Andreas,
the client application that could not receive messages. Did the client sort of just hang...no errors or exceptions?
This can happen if the client has not updated it's jboss-remoting.jar and jboss-messaging-client.jar.
So if you have existing JBM clients those will need to update their jars.
Regards,
Daniel -
37. Re: Trouble with jms-topic
Hi,
yea I read about that.
I tried switching versions like described here
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126373
always using a set of jboss-messsaging.jar, jboss-messaging-client.jar & jboss-remoting.jar
for client and server.
Mostly I tried using JBM 1.4SP3 messaging.jars, and 2.2.2.SP5 I think for remoting. But I also tried using other libs. Nothing really worked.
Thats why I wanted to patch the 4.2GA version now as a last resort.
Regards
Andreas -
38. Re: Trouble with jms-topic
..ah, and yes, no errors and exceptions,
but I don't know whether or not the client really 'hang'.
Since I heard about that I really thought I cold get it to work,
but no go.
Regards
Andreas -
39. Re: Trouble with jms-topic
The first error you are seeing is because you have a JMSRouter configured to use a Topic. This is not supported in the version you are running. This available in the version in the main trunk.
Can you try starting over with a newly built ESB server?
To help troubleshoot the JBM client issue could you post the following information about the versions of both the client side and server side libs:
Client:java -jar jboss-remoting.jar jar xvf jboss-messaging.jar VERSION
Server$JBOSS_HOME/client jar xvf jboss-messaging-client.jar VERSION $JBOSS_HOME/server/default/lib java -jar jboss-remoting.jar jar xvf jboss-messaging.jar VERSION
Thanks,
Daniel -
40. Re: Trouble with jms-topic
Hi,
is there any other way to use a topic in 4.2GA than with the JMSRouter?
I thought that was the way to go, after we tried so many things last time.
To the libs:
I have no jboss-messaging.jar on the client side,
but jboss-messaging-client.jar has:jboss.messaging.jmsVersion=1.1 jboss.messaging.jmsMajorVersion=1 jboss.messaging.jmsMinorVersion=1 jboss.messaging.jmsProviderName=JBoss Messaging jboss.messaging.providerVersion=1.4.0.SP3 jboss.messaging.providerMajorVersion=1 jboss.messaging.providerMinorVersion=4 jboss.messaging.providerIncrementingVersion=21
jboss-remoting.jar:JBossRemoting Version 2.2.2.SP5 (Bluto)
I never changed jboss-messaging-client.jar in $JBOSS_HOME/client,
because I thought it's not being used. Do I have to change that too?
The other libs on the server side are:
jboss-remoting.jar:JBossRemoting Version 2.2.2.SP5 (Bluto)
jboss-messaging.jar:jboss.messaging.jmsVersion=1.1 jboss.messaging.jmsMajorVersion=1 jboss.messaging.jmsMinorVersion=1 jboss.messaging.jmsProviderName=JBoss Messaging jboss.messaging.providerVersion=1.4.0.SP3 jboss.messaging.providerMajorVersion=1 jboss.messaging.providerMinorVersion=4 jboss.messaging.providerIncrementingVersion=21
At least that was the last setup I tried.
I would be glad when I just had messed up the lib config,
and don't have to patch the old version.
I now have a setup where I can switch versions fairly easy,
so I am very grateful for all tips on that.
Thanks
Andreas -
41. Re: Trouble with jms-topic
Hi Andreas,
and you are running JBossESB server 4.2GA?
Those version don't match the versions of the jars shipped with 4.2GA.
Messaging should be 1.3.0.GA and remoting 2.2.0 SP4 (Bluto).
But as long as you have the same versions on both client and server you might be ok anyway.
Can you try writing a client that sends a message to a queue on the server. This is just to verify that the messaging libs are correct and working.
If you can send a messgage but not receive can you check the client code if there has been any change to it. Could be that the connection has not been started.
This is a long shot but perhaps worth a check anyway so we can rule it out.
Regards,
Daniel -
42. Re: Trouble with jms-topic
To use be able to send to a topic you can copy the JMSRouter from the main trunk. Change the package name of that class and package it in your .esb archive.
Don't forget to update the package name in the action aswell so the correct version is used.
Regards,
Daniel -
43. Re: Trouble with jms-topic
Hiya Andreas.
The other thing to check on your client classpath is the location of jbossall-client.jar as this contains a copy of the remoting classes. If you do include this jar then please make sure that the jboss-remoting jar precedes it.
Kev -
44. Re: Trouble with jms-topic
Hi,
no the described setup is the 4.2.1 trunk version, but with updated libs for messaging & remoting.
Its a different setup than the one I tried to patch with the rosetta libs.
Am I replacing all the right libs here , or did I forget some (e.g. messaging-client on server side).
I'll try writing that test-client right away, and get back to you with the results.
Client code hasn't changed though, because its a 3rd party app & I can't change it.
I can only configure things like the queue names & the JMS provider.
Thanks for the tip with the JMSRouter, I'll try that too.
To the classpath thing:
I'm actually using jbossall-client.jar, and I read about remoting.jar having to precede that.
The thing is, my client app is deployed on a Tomcat server,
and I don't have that much ways (that I know of) to tell Tomcat about the order of the libs.
I read that when I put a lib into "Tomcat\common\endorsed\" its treated with higher priority, but thats about all I can do.
I can't really tell if it's working though.
Here are the libs I currently use on the client side (all but messaging & remoting original 4.2.1 trunk) taken from ESBServer/client (except remoting):
- trove.jar
- log4j.jar
- jboss-messaging-client.jar (updated)
- jboss-jaxws.jar
- jboss-aop-jdk50-client.jar
- jbossall-client.jar
- javassist.jar
- jboss-remoting.jar (in "common\endorsed", updated)
Regards
Andreas