You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2009/05/22 19:45:46 UTC
[jira] Commented: (TUSCANY-3057) binding.jms fails to lookup
ConnectionFactory
[ https://issues.apache.org/jira/browse/TUSCANY-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712181#action_12712181 ]
ant elder commented on TUSCANY-3057:
------------------------------------
Attempt at a fix in 1.x r777627 and 1.5 branch r777632
> binding.jms fails to lookup ConnectionFactory
> ---------------------------------------------
>
> Key: TUSCANY-3057
> URL: https://issues.apache.org/jira/browse/TUSCANY-3057
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.5
> Environment: Linux x86_64 Websphere 6.1 FP 17 or Weblogic 9.2 SP3
> Reporter: Dave Sowerby
> Assignee: ant elder
>
> Using a previously functional webapp using a binding.jms element of "<binding.jms uri="jms:RequestQueue" />" on 1.5 initialisation fails with the following errors:
> Websphere:
> [22/05/09 17:04:22:384 BST] 000000ad javaURLContex E NMSV0310E: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the op
> eration's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application re
> quest. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does
> not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. Exception stack trace:
> javax.naming.ConfigurationException [Root exception is javax.naming.NameNotFoundException: Name "comp/env/ConnectionFactory" not found in context "java:".]
> at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:411)
> at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:388)
> at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:204)
> at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:363)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.jndiLookUp(JMSResourceFactoryImpl.java:214)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.createConnection(JMSResourceFactoryImpl.java:122)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.getConnection(JMSResourceFactoryImpl.java:75)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.getResponseConnection(JMSResourceFactoryImpl.java:242)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.createResponseSession(JMSResourceFactoryImpl.java:229)
> at org.apache.tuscany.sca.binding.jms.context.JMSBindingContext.getJmsResponseSession(JMSBindingContext.java:81)
> at org.apache.tuscany.sca.binding.jms.transport.TransportServiceInterceptor.invoke(TransportServiceInterceptor.java:81)
> at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:149)
> at org.apache.tuscany.sca.host.jms.asf.ServiceInvoker.invokeService(ServiceInvoker.java:94)
> at org.apache.tuscany.sca.host.jms.asf.ServiceInvoker.onMessage(ServiceInvoker.java:70)
> at org.apache.tuscany.sca.host.jms.asf.ASFListener$1$1.run(ASFListener.java:129) at org.apache.tuscany.sca.core.work.Work.run(Work.java:63)
> at org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:215)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:797)
> Caused by: javax.naming.NameNotFoundException: Name "comp/env/ConnectionFactory" not found in context "java:".
> at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1095)
> at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:991)
> at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1263)
> at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:384)
> ... 19 more
> Weblogic:
> <22-May-2009 17:37:05 o'clock BST> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1243010223665' for task '1'. Error is: 'weblogic.application.ModuleException: '
> weblogic.application.ModuleException:
> at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
> at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
> at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
> at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
> Truncated. see log file for complete stacktrace
> org.apache.tuscany.sca.binding.jms.impl.JMSBindingException: connection factory not found: ConnectionFactory
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.createConnection(JMSResourceFactoryImpl.java:124)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.getConnection(JMSResourceFactoryImpl.java:75)
> at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactoryImpl.createSession(JMSResourceFactoryImpl.java:86)
> at org.apache.tuscany.sca.host.jms.asf.ASFListener.registerListerner(ASFListener.java:99)
> at org.apache.tuscany.sca.host.jms.asf.ASFListener.start(ASFListener.java:76)
> Truncated. see log file for complete stacktrace
> I've triple checked the resource references, and JNDI name mappings within the deployment descriptors - all seem fine.
> Dave.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.