7 Replies Latest reply on May 3, 2006 4:29 PM by Nicholas Capito

    BPEL Process Deploy problem (JNDI Connection Factory problem

    Nicholas Capito Newbie

      Very quick background. I basically am doing my own tutorial and am using the hello example delivered with the BPEL Extension as a guide. Here is where i got stuck.


      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear -> C:\Nicks_temp\jboss-4.0.2\server\all\tmp\deploy\tmp8514fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.EARDeployer@a8e586
      2006-05-02 16:01:36,140 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/MANIFEST.MF
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/application.xml
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: fusion-client.jar
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: fusion-web.war
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Deployment Info: org.jboss.deployment.DeploymentInfo@1e3e762a { url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war }
      deployer: null
      status: null
      state: CONSTRUCTED
      watch: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      altDD: null
      lastDeployed: 0
      lastModified: 0
      mbeans:
      , isDirectory: false
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.EARDeployer] Deployment Info: org.jboss.deployment.DeploymentInfo@d834fbf2 { url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar }
      deployer: null
      status: null
      state: CONSTRUCTED
      watch: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      altDD: null
      lastDeployed: 0
      lastModified: 0
      mbeans:
      , isDirectory: false
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@1c74f37, cl=org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=0}
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@1c74f37, cl=org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=0}
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=0}
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg:
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] found 2 subpackages of file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.ClientDeployer] Found a META-INF/application-client.xml file, di: org.jboss.deployment.DeploymentInfo@d834fbf2 { url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar }
      deployer: null
      status: null
      state: CONSTRUCTED
      watch: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      altDD: null
      lastDeployed: 0
      lastModified: 0
      mbeans:

      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.ClientDeployer@14aa2db
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.ClientDeployer] looking for nested deployments in : file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      2006-05-02 16:01:36,140 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=52}
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      2006-05-02 16:01:36,140 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.web.tomcat.tc5.Tomcat5@baa573
      2006-05-02 16:01:36,140 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Begin init
      2006-05-02 16:01:36,140 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Unpacking war to: C:\Nicks_temp\jboss-4.0.2\server\all\tmp\deploy\tmp8514fusion-application.ear-contents\fusion-web-exp.war
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Replaced war with unpacked contents
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] webContext: /fusion
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] warURL: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web-exp.war/
      2006-05-02 16:01:36,187 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.init,fusion-web.war
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] End init
      2006-05-02 16:01:36,187 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web-exp.war/, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=52}
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying fusion-client.jar
      2006-05-02 16:01:36,187 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      2006-05-02 16:01:36,187 DEBUG [org.jboss.system.ServiceController] Creating service jboss.web.deployment:war=fusion-web.war,id=507409962
      2006-05-02 16:01:36,187 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: []
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.WebModule] Creating jboss.web.deployment:war=fusion-web.war,id=507409962
      2006-05-02 16:01:36,187 DEBUG [org.jboss.web.WebModule] Created jboss.web.deployment:war=fusion-web.war,id=507409962
      2006-05-02 16:01:36,187 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.web.deployment:war=fusion-web.war,id=507409962 dependents are: []
      2006-05-02 16:01:36,187 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.create,fusion-web.war
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying fusion-web.war
      2006-05-02 16:01:36,218 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EARDeployment,url='fusion-application.ear'
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.EARDeployment] Creating jboss.j2ee:service=EARDeployment,url='fusion-application.ear'
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.EARDeployment] Created jboss.j2ee:service=EARDeployment,url='fusion-application.ear'
      2006-05-02 16:01:36,218 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EARDeployment,url='fusion-application.ear' dependents are: []
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying fusion-application.ear
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      2006-05-02 16:01:36,218 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-client.jar
      2006-05-02 16:01:36,234 DEBUG [org.jboss.deployment.ClientDeployer] Creating client ENC binding under: fusion-client
      2006-05-02 16:01:36,234 DEBUG [org.jboss.webservice.ServiceClientDeployer] Webservice binding: java:comp/env/service/Fusion
      2006-05-02 16:01:36,234 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: fusion-client.jar
      2006-05-02 16:01:36,234 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      2006-05-02 16:01:36,234 DEBUG [org.jboss.system.ServiceController] starting service jboss.web.deployment:war=fusion-web.war,id=507409962
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.WebModule] Starting jboss.web.deployment:war=fusion-web.war,id=507409962
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] webContext: /fusion
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] warURL: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web-exp.war/
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] webAppParser: org.jboss.web.AbstractWebDeployer$DescriptorParser@5e3ad0
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
      2006-05-02 16:01:36,234 INFO [org.jboss.web.tomcat.tc5.TomcatDeployer] deploy, ctxPath=/fusion, warUrl=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web-exp.war/
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] AbstractWebContainer.parseWebAppDescriptors, Begin
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Creating ENC using ClassLoader: java.net.FactoryURLClassLoader@67467e
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..org.jboss.mx.loading.UnifiedClassLoader3@771eeb{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear ,addedOrder=52}
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..org.jboss.system.server.NoAnnotationURLClassLoader@ab95e6
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..sun.misc.Launcher$AppClassLoader@e39a3e
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..sun.misc.Launcher$ExtClassLoader@a39137
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Bound java:comp/ORB
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Linked java:comp/UserTransaction to JNDI name: UserTransaction
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] addEnvEntries
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkResourceEnvRefs
      2006-05-02 16:01:36,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkResourceRefs
      2006-05-02 16:01:36,234 ERROR [org.jboss.web.WebModule] Starting failed jboss.web.deployment:war=fusion-web.war,id=507409962
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)
      at org.jboss.web.WebModule.startModule(WebModule.java:68)
      at org.jboss.web.WebModule.startService(WebModule.java:46)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:418)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy41.start(Unknown Source)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.GeneratedMethodAccessor16.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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
      Caused by: javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.
      at org.jboss.web.AbstractWebDeployer.linkResourceRefs(AbstractWebDeployer.java:596)
      at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:494)
      at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:851)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:143)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
      ... 49 more
      2006-05-02 16:01:36,250 WARN [org.jboss.system.ServiceController] Problem starting service jboss.web.deployment:war=fusion-web.war,id=507409962
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)
      at org.jboss.web.WebModule.startModule(WebModule.java:68)
      at org.jboss.web.WebModule.startService(WebModule.java:46)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:418)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy41.start(Unknown Source)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.GeneratedMethodAccessor16.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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
      Caused by: javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.
      at org.jboss.web.AbstractWebDeployer.linkResourceRefs(AbstractWebDeployer.java:596)
      at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:494)
      at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:851)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:143)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
      ... 49 more
      2006-05-02 16:01:36,250 ERROR [org.jboss.deployment.MainDeployer] could not start deployment: file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp8514fusion-application.ear-contents/fusion-web.war
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)
      at org.jboss.web.WebModule.startModule(WebModule.java:68)
      at org.jboss.web.WebModule.startService(WebModule.java:46)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:418)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy41.start(Unknown Source)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.GeneratedMethodAccessor16.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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
      Caused by: javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.
      at org.jboss.web.AbstractWebDeployer.linkResourceRefs(AbstractWebDeployer.java:596)
      at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:494)
      at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:851)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:143)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
      ... 49 more
      2006-05-02 16:01:36,250 ERROR [org.jboss.deployment.MainDeployer] could not start deployment: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)
      at org.jboss.web.WebModule.startModule(WebModule.java:68)
      at org.jboss.web.WebModule.startService(WebModule.java:46)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:418)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy41.start(Unknown Source)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.GeneratedMethodAccessor16.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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
      Caused by: javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.
      at org.jboss.web.AbstractWebDeployer.linkResourceRefs(AbstractWebDeployer.java:596)
      at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:494)
      at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:851)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:143)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
      ... 49 more
      2006-05-02 16:01:36,250 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@6d58bf2f{ url=file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear, deployedLastModified=0 }
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)
      at org.jboss.web.WebModule.startModule(WebModule.java:68)
      at org.jboss.web.WebModule.startService(WebModule.java:46)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:418)
      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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy41.start(Unknown Source)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
      at sun.reflect.GeneratedMethodAccessor16.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:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy8.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
      Caused by: javax.naming.NamingException: resource-ref: jms/ConnectionFactory has no valid JNDI binding. Check the jboss-web/resource-ref.
      at org.jboss.web.AbstractWebDeployer.linkResourceRefs(AbstractWebDeployer.java:596)
      at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:494)
      at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:851)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:143)
      at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
      ... 49 more
      2006-05-02 16:01:36,250 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear -> file:/C:/Nicks_temp/jboss-4.0.2/server/all//deploy/fusion-application.ear



      I am sure this is just a configuration/server issue. It is complaining about my ConnectionFactory not being bound correctly in my jboss-web:

      <?xml version="1.0" encoding="UTF-8" ?>
      <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN"
       "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
      <jboss-web>
      
       <message-destination-ref>
       <message-destination-ref-name>jms/callerQueue</message-destination-ref-name>
       <jndi-name>queue/testQueue</jndi-name>
       </message-destination-ref>
      
       <resource-ref>
       <res-ref-name>jms/ConnectionFactory</res-ref-name>
       <jndi-name>java:ConnectionFactory</jndi-name>
       </resource-ref>
      
      
      
      </jboss-web>


      The tutorial does not mention how to set up the server. But i believe it should be configured this way as delivered. Any suggesions? If you need more info let me know.




        • 1. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
          Alejandro Guizar Master

          The tutorial does mention it ;-) Check out section 6.4 of the hello world tutorial.

          6.4 Binding references to actual resources

          We proceed to bind the destination and connection factory references to resources that exist in the operational environment. This task is specific to the target application server. For JBoss we write a jboss-web.xml descriptor and place it in directory web.


          <jboss-web>
          
           <message-destination-ref>
           <!-- destination reference (in web.xml) -->
           <message-destination-ref-name>jms/callerQueue</message-destination-ref-name>
           <!-- actual resource in the global JNDI context -->
           <jndi-name>queue/testQueue</jndi-name>
           </message-destination-ref>
          
           <resource-ref>
           <!-- connection factory reference (in web.xml) -->
           <res-ref-name>jms/ConnectionFactory</res-ref-name>
           <!-- actual resource in the java JNDI context -->
           <jndi-name>java:ConnectionFactory</jndi-name>
           </resource-ref>
          
          </jboss-web>


          • 2. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
            Nicholas Capito Newbie

             

            proceed to bind the destination and connection factory references to resources that exist in the operational environment.


            I agree it mentions it. And i have the jboss-web file and it does not recognize the connection factory. I am using the 4.0.2 all setup. I am going to try to plug it into the 4.03 setup and if that works my JMS must not be installed/configured right. Which is what i was trying to get to. I am not quite sure what i have to do to bind the JNDI to the JMS Connection Factory.


            Sorry for the confusion i am new to all this.

            • 3. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
              Alejandro Guizar Master

              Let me know what you find. By the way, I only tested alpha 4 against the default configuration, so you might want to start there first and then move to the all configuration.

              • 4. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
                Nicholas Capito Newbie

                Using 4.0.3SP1 did not work. Same error as before. I am going to try and use the default config, if it works I will let you know. I also attached the web.xml file that i am using.

                JMS comes configured?

                My Jboss-web is at the begining of the thread and here is my web.xml.

                <?xml version="1.0" encoding="UTF-8"?>
                <web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
                 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
                
                 <servlet>
                 <servlet-name>callerServlet</servlet-name>
                 <!-- service implementation bean class -->
                 <servlet-class>webservice.fusion.FusionCaller_Impl</servlet-class>
                 </servlet>
                
                 <servlet>
                 <servlet-name>messagerServlet</servlet-name>
                 <servlet-class>org.jbpm.bpel.service.messager.MessagerServlet</servlet-class>
                 <load-on-startup>1</load-on-startup>
                 </servlet>
                
                
                 <servlet-mapping>
                 <servlet-name>messagerServlet</servlet-name>
                 <url-pattern>/messager</url-pattern>
                 </servlet-mapping>
                
                
                
                 <servlet-mapping>
                 <servlet-name>callerServlet</servlet-name>
                 <url-pattern>/caller</url-pattern>
                 </servlet-mapping>
                
                
                
                
                 <resource-ref>
                 <res-ref-name>jms/ConnectionFactory</res-ref-name>
                 <res-type>javax.jms.ConnectionFactory</res-type>
                 <res-auth>Container</res-auth>
                 <res-sharing-scope>Shareable</res-sharing-scope>
                 </resource-ref>
                
                 <message-destination-ref>
                 <message-destination-ref-name>jms/callerQueue</message-destination-ref-name>
                 <message-destination-type>javax.jms.Queue</message-destination-type>
                 <message-destination-usage>ConsumesProduces</message-destination-usage>
                 </message-destination-ref>
                
                
                
                
                </web-app>


                • 5. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
                  Nicholas Capito Newbie

                  Using the default server did not work. Same error.

                  • 6. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
                    Alejandro Guizar Master

                    The JMS objects references in the provided jboss-web.xml come preconfigured in a typical JBoss installation. With that said, I can think of two causes:
                    The JMS objects were not installed. To verify this, go to the JBoss management console, look for the JNDIView service under the jboss section, invoke the list operation and look for these entries:
                    java: Namespace
                    +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)

                    Global JNDI Namespace
                    +- queue (class: org.jnp.interfaces.NamingContext)
                    | +- testQueue (class: org.jboss.mq.SpyQueue)
                    You packaged the wrong jboss-web.xml file. Make sure the right file is packaged in the WEB-INF directory within your WAR.

                    • 7. Re: BPEL Process Deploy problem (JNDI Connection Factory pro
                      Nicholas Capito Newbie

                      I thank you for your help my war file was not finding my jboss-web.xml.


                      Thanks, again.



                      Nick