| Summary: | CP01 (helloworld quickstart) is failing with Tibco EMS as the JMS provider | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> | ||||||||||
| Component: | JBossESB | Assignee: | Len DiMaggio <ldimaggi> | ||||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 4.2 CP01 | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | 4.2 CP02 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-557 | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: |
SOA-P CP01
TIBCO Enterprise Message Service - Version 4.4.1 V2 2/21/2007
|
|||||||||||
| Last Closed: | 2008-06-10 17:08:19 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
Attachment: Added: helloworld.tar Attachment: Added: server.log.43GA.zip Attachment: Added: server.log.CP01.zip Notes on getting tibco + ESB + helloworld running. Attachment: Added: Tibco-EMS.txt The Tibco jar appears to throw that exception on every invocation of list(). Changing the createContext method to call lookup() instead of list() should result in the same test being executed. CORRECTION - this is also failing with ESB - it had been working due to an inadvertent change to:
rosetta/src/org/jboss/soa/esb/helpers/NamingContextPool.java
Where this test was removed:
context.list("__dummy2@#$%") ;
I removed the test as a workaround to: http://jira.jboss.com/jira/browse/SOA-535
And neglected to put it back.
Changing the method call to .lookup solved the problem for Tibco EMS.
Link: Added: This issue is a dependency of JBESB-1773 Verified resolved in CR1 build for CP02.
<jms-provider
name="TibcoEMS"
jndi-URL="tcp://localhost:7222"
jndi-context-factory="com.tibco.tibjms.naming.TibjmsInitialContextFactory"
connection-factory="QueueConnectionFactory" >
And Tibco EMS:
TIBCO Enterprise Message Service.
Copyright 2003-2007 by TIBCO Software Inc.
All rights reserved.
Version 4.4.1 V2 2/21/2007
And the changed version of helloworld referenced here:
http://jira.jboss.com/jira/browse/JBQA-1595
|
Date of First Response: 2008-05-27 09:32:49 project_key: SOA CP01 (helloworld quickstart) is failing with Tibco EMS as the JMS provider. The same test is passing with ESB 4.3GA (from trunk - revision 20143). With CP01 - I'm seeing this exception at deployment: Caused by: javax.naming.OperationNotSupportedException: Not supported at com.tibco.tibjms.naming.TibjmsContext.list(TibjmsContext.java:1004) at com.tibco.tibjms.naming.TibjmsContext.list(TibjmsContext.java:482) at javax.naming.InitialContext.list(InitialContext.java:395) at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:341) ... 56 more Notes on modifications to helloworld to run with Tibco: http://jira.jboss.com/jira/browse/JBQA-1595#action_12414082 See the attached file for a copy of the modified quickstart. Also - this posting shows the same problem - which is odd - as the quickstart is running with ESB from trunk: http://eai.ittoolbox.com/groups/technical-functional/tibco-l/ems-list-all-topicsqueues-programatically-2053980 Stack trace: 13:08:45,997 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_helloworld.esb org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected naming context exception from prepareMessageReceiver at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:125) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:150) at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:69) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:83) 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: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 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.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.GeneratedMethodAccessor23.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$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.jboss.soa.esb.helpers.NamingContextException: Failed to create Naming Context at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:356) at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:295) at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:150) at org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(NamingContextPool.java:400) at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:371) at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:109) ... 51 more Caused by: javax.naming.OperationNotSupportedException: Not supported at com.tibco.tibjms.naming.TibjmsContext.list(TibjmsContext.java:1004) at com.tibco.tibjms.naming.TibjmsContext.list(TibjmsContext.java:482) at javax.naming.InitialContext.list(InitialContext.java:395) at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:341) ... 56 more 13:08:46,026 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected naming context exception from prepareMessageReceiver I Depend On: jboss.esb:deployment=jbossesb.esb jboss.esb.quickstart.destination:service=Queue,name=jbossQ --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected naming context exception from prepareMessageReceiver I Depend On: jboss.esb:deployment=jbossesb.esb jboss.esb.quickstart.destination:service=Queue,name=jbossQ