|
Hi
David,
yes, the -db.xml files are definately nicer :-) Okay, I made 2 changes from the default configuration. 1) Changed the hsqldb-ds.xml file so that the jndiname tag is as follows: <jndi-name>xpetstoreDS</jndi-name> 2) Changed the jbossmq-destinations-service.xml file to contain queues pertaining to the xpetstore app. <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=order"> <attribute name="JNDIName">queue/order</attribute> <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationMan ager</depends> </mbean> <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=mail"> <attribute name="JNDIName">queue/mail</attribute> <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationMan ager</depends> </mbean> So JBoss boots fine, unfortunately however once I deploy my xpetstore.ear I get the error. The stack trace is below. thanks very much, Brian 17:27:56,781 ERROR [DLQHandler] Initialization failed javax.naming.NameNotFoundException: XAConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) at org.jnp.server.NamingServer.getObject(NamingServer.java:509) at org.jnp.server.NamingServer.lookup(NamingServer.java:282) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:136) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:168) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoke r.java:394) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvok er.java:553) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:197) at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.jav a:193) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:197) at org.jboss.ejb.Container.invoke(Container.java:729) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:957) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:388) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy30.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:444) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:197) 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:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:957) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:388) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy20.start(Unknown Source) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:470) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:816) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:636) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:600) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:404) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:545) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan( AbstractDeploymentScanner.java:19 5) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Ab stractDeploymentScanner.java:206) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abs tractDeploymentScanner.java:185) 17:27:57,265 ERROR [JMSContainerInvoker] Starting failed javax.naming.NameNotFoundException: XAConnectionFactory not bound ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 28, 2003 5:07 PM Subject: Re: [JBoss-user] Re: [Xpetstore-devel] Re: xpetstore note > jboss is definitely going towards the *-ds.xml files, they are possible > to understand :-) > > I don't understand how you could get the quoted error from > hsqldb-ds.xml. Could you post what is giving the error and more stack > trace? > > thanks > david jencks > On Tuesday, January 28, 2003, at 11:49 AM, Brian McSweeney wrote: > > > Hi everyone, > > trying to update the xpetstore app to run on jboss3.2.0RC1 > > First thing I encountered was that in server/default/deploy there now > > seems to be a file > > > > - hsqldb-ds.xml > > > > whereas I used to use > > > > hsqldb-service.xml > > > > I see that they are still in the examples, but is JBoss going away from > > these? > > > > So I copied the structure of hsqldb-ds.xml and configured it for the > > xpetstore > > datasource - I got rid of an exception saying that the referenced DS > > was not > > found. > > Good. > > > > Unfortunately I got an error saying the following: > > > > INFO [DLQHandler] Creating > > ERROR [DLQHandler] Initialization failed > > javax.naming.NameNotFoundException: XAConnectionFactory not bound > > > > Any ideas? > > > > Also, I'm still quite new to JBoss, but I'd love to know if there's > > anywhere > > where I can > > get information on any changes that are being made to the jboss > > structure of > > files to > > deploy. For example, if the file format IS going to change to > > hsqldb-ds.xml, > > then I'd love > > to be able to see that somewhere. > > thanks for any replies, > > Brian |
