1 2 Previous Next 24 Replies Latest reply on Jan 11, 2008 10:13 AM by kabirkhan

    NPE booting Embedded JBoss from trunk

    pmuir

      When I try to boot embedded from trunk I get an NPE from JMS. I suspect this is some configuration problem with our xml, but as the error message isn't helpful :p I'm not sure

      [testng] WARN [org.jboss.mx.loading.UnifiedLoaderRepository3] Tried to add non-URLClassLoader. Ignored
       [testng] WARN [org.jboss.aop.deployment.AspectManagerService] Could not find base-aspects.xml file in the resources of sun.misc.Launcher$AppClassLoader@a39137
       [testng] INFO [org.jboss.aop.deployers.AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@f26c81 for sun.misc.Launcher$AppClassLoader@a39137
       [testng] INFO [org.jboss.resource.deployers.RARDeployment] Required license terms exist, view vfsfile:/Users/pmuir/workspace/jboss-seam/bootstrap-new/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
       [testng] INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
       [testng] INFO [org.jboss.resource.deployers.RARDeployment] Required license terms exist, view vfsfile:/Users/pmuir/workspace/jboss-seam/bootstrap-new/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
       [testng] INFO [org.jboss.resource.deployers.RARDeployment] Required license terms exist, view vfsfile:/Users/pmuir/workspace/jboss-seam/bootstrap-new/deploy/jms-ra.rar/META-INF/ra.xml
       [testng] WARN [org.jboss.jms.server.security.SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
       [testng] INFO [org.jboss.jms.server.ServerPeer] JBoss Messaging 1.4.0.SP1 server [0] started
       [testng] INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] Connector bisocket://capercaillie.local:4457 has leasing enabled, lease period 10000 milliseconds
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@9c62bb started
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] Connector bisocket://capercaillie.local:4457 has leasing enabled, lease period 10000 milliseconds
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@394344 started
       [testng] INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
       [testng] WARN [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
       [testng] WARN [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] Connector bisocket://capercaillie.local:4457 has leasing enabled, lease period 10000 milliseconds
       [testng] INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@ce2a00 started
       [testng] INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
       [testng] INFO [org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer] Found persistence units [org.jboss.ejb3.metadata.jpa.spec.PersistenceUnitMetaData@5ff3aa{name=integration}]
       [testng] WARN [org.jboss.xb.builder.runtime.CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] installing bean: persistence.units:jar=test-build.jar,unitName=integration with dependencies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] and supplies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] installing bean: jboss.j2ee:jar=test-build,name=TestQueueListener,service=EJB3 with dependencies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] and supplies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] Class:javax.jms.MessageListener
       [testng] INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.jboss.seam.test.integration.MessagingTest$TestQueueListener ejbName: TestQueueListener
       [testng] WARN [org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] installing bean: jboss.j2ee:jar=test-build,name=TestTopicListener,service=EJB3 with dependencies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] and supplies:
       [testng] INFO [org.jboss.ejb3.MCKernelAbstraction] Class:javax.jms.MessageListener
       [testng] INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.jboss.seam.test.integration.MessagingTest$TestTopicListener ejbName: TestTopicListener
       [testng] WARN [org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED
       [testng] INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=integrationDatasource' to JNDI name 'java:integrationDatasource'
       [testng] INFO [org.jboss.ejb3.entity.PersistenceUnitDeployment] Starting persistence unit persistence.units:jar=test-build.jar,unitName=integration
       [testng] WARN [jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@133ffe(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@ddcf85 destination=queue/testQueue isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
       [testng] java.lang.NullPointerException
       [testng] at org.jboss.jms.client.container.ConnectionAspect.getConnectionState(ConnectionAspect.java:254)
       [testng] at org.jboss.jms.client.container.ConnectionAspect.handleSetExceptionListener(ConnectionAspect.java:118)
       [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       [testng] at java.lang.reflect.Method.invoke(Method.java:585)
       [testng] at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:119)
       [testng] at org.jboss.jms.client.delegate.ClientConnectionDelegate$setExceptionListener_8089029433030319178.invokeNext(ClientConnectionDelegate$setExceptionListener_8089029433030319178.java)
       [testng] at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
       [testng] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
       [testng] at org.jboss.jms.client.delegate.ClientConnectionDelegate$setExceptionListener_8089029433030319178.invokeNext(ClientConnectionDelegate$setExceptionListener_8089029433030319178.java)
       [testng] at org.jboss.jms.client.delegate.ClientConnectionDelegate.setExceptionListener(ClientConnectionDelegate.java)
       [testng] at org.jboss.jms.client.JBossConnection.setExceptionListener(JBossConnection.java:116)
       [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:142)
       [testng] at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
       [testng] at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
       [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:401)
       [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:339)
       [testng] at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:692)
       [testng] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
       [testng] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
       [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       [testng] at java.lang.Thread.run(Thread.java:613)


      This doesn't seem to cause any great problem when running (except when using JMS ;)

      Here is our xml (messaging folder and jms-ra.jar are a copy from server/default/deploy on trunk):

      http://fisheye.jboss.com/browse/JBoss/jboss-seam/bootstrap-new

      and the jars we use to build

      http://fisheye.jboss.com/browse/JBossAS/trunk/embedded/build.xml?r=67802#l343

        • 1. Re: NPE booting Embedded JBoss from trunk
          anil.saldhana
          • 2. Re: NPE booting Embedded JBoss from trunk
            timfox

             

            "anil.saldhana@jboss.com" wrote:

            You have to ask Mr.Fox.


            Best to ask Clebert - he has been handling the AS5 integration :)

            • 3. Re: NPE booting Embedded JBoss from trunk
              clebert.suconic

               

              "pete.muir@jboss.org" wrote:
              When I try to boot embedded from trunk I get an NPE from JMS. I suspect this is some configuration problem with our xml, but as the error message isn't helpful :p I'm not sure



              Being honest to you, I don't know how to run embedded....
              If you give me some instructions I will try to replicate it here.

              Probably there is some problems on the ordering of startup when you're running embedded. I will try to work around if you give me some instructions.

              • 4. Re: NPE booting Embedded JBoss from trunk
                pmuir

                It's probably easiest to replicate by running from the Seam testsuite

                You need current Seam CVS.

                cvs -d:ext:USERNAME@cvs.forge.jboss.com:/cvsroot/jboss co jboss-seam
                cd jboss-seam/src/test/integration
                ant testclass -DclassName=MessagingTest


                The tests are in jboss-seam/src/test/integration/src/org.jboss.seam.test.integration.MessagingTest

                If you want to look at the xml's (including log4j configuration) they are in jboss-seam/bootstrap.



                • 5. Re: NPE booting Embedded JBoss from trunk
                  starksm64

                  I'll take a look at it and try to get it resolved by monday as I need to do a release of jbm for other jbossas issues.

                  • 6. Re: NPE booting Embedded JBoss from trunk
                    clebert.suconic

                    I just updated JBM to 1.4.0.SP3 on jboss5.

                    (BTW I have created a JIRA for this: http://jira.jboss.org/jira/browse/JBAS-5104)


                    I have done some tests on my local box and I don't foresee any major problems. I'll start a run on hudson in few minutes and I will follow up results.

                    • 7. Re: NPE booting Embedded JBoss from trunk
                      pmuir

                      I did the update to 1.4.0.SP3 locally (and updated the xmls) and I still get the same exception when I try to boot embedded.

                      • 8. Re: NPE booting Embedded JBoss from trunk
                        timfox

                        Can someone explain what this "embedded configuration" is?

                        The only JBM configurations I am aware of that we need to support are: JBAS 4.3 and JBAS 5.0.....

                        Is this a new requirement? If so, I know nothing about it :)

                        • 9. Re: NPE booting Embedded JBoss from trunk
                          clebert.suconic

                           

                          Can someone explain what this "embedded configuration" is?


                          +1

                          There is something starting up services out of order on this configuration you or someone created. I/We don't have much information about that... so I don't know much how to help there.

                          • 10. Re: NPE booting Embedded JBoss from trunk
                            pmuir

                             

                            "timfox" wrote:
                            Can someone explain what this "embedded configuration" is?


                            http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedJBoss

                            We use it in Seam for

                            1) allowing deployment of EJB3 apps to Tomcat
                            2) Integration testing environment

                            timfox wrote:
                            The only JBM configurations I am aware of that we need to support are: JBAS 4.3 and JBAS 5.0.....

                            Is this a new requirement? If so, I know nothing about it :)


                            Well currently JMS stuff doesn't work in Embedded JBoss beta3 snapshots (it does in beta2). Whilst JMS support isn't critical from my (Seam team's) perspective, it certainly would be better if it worked ;) Much more important from my perspective is to get a beta3 release out there so that we can release the next Seam version.

                            clebert.suconic@jboss.com wrote:
                            There is something starting up services out of order on this configuration you or someone created. I/We don't have much information about that... so I don't know much how to help there.


                            Ok, so what information are you after? Tell me what information Ales or I can provide and we will try to help.

                            I'm pretty much shooting in the dark here, so even a hint about *what* service isn't started which is needed would probably get us further down the road to success.

                            As this is probably more AS integration than messaging perhaps Scott is able to help more :)

                            • 11. Re: NPE booting Embedded JBoss from trunk
                              clebert.suconic

                              Actually I think I was wrong regarding the order of those services...


                              Re-reading this whole thread, looking at your original problem... you couldn't get a state set...


                              It looks like you don't have our aspects being deployed on the client side.


                              We have aspects on client side, and on the server side. The client side will download the aspects from server side. Probably you have some classLoading issues with loading aop-messaging-client.xml and aop-messaging-server.xml.

                              Take a look if you see anything obvious in regard to the classpath on that.

                              • 12. Re: NPE booting Embedded JBoss from trunk
                                starksm64

                                I'm debugging this. I'm working on the JBMESSAGING-1189 changes I need in for jbossas.

                                • 13. Re: NPE booting Embedded JBoss from trunk
                                  starksm64

                                  I'm not getting far enough because of jaxb version conflicts:

                                   [testng] java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/home/cvs/Seam/jboss-seam/lib/test/thirdparty-all.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
                                   [testng] at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
                                  ...
                                   [testng] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
                                   [testng] at org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer.create(ManagedConnectionFactoryParserDeployer.java:88)
                                  

                                  I can't seem to find where the endorsed jars are coming from. I'm currently trying to use the jboss-seam cvs trunk and running the test target from the jboss-seam/src/test/integration directory.


                                  • 14. Re: NPE booting Embedded JBoss from trunk
                                    starksm64

                                    I see the same problem is I just try to run the -DclassName=MessagingTest testclass target. The eclipse project settings seemed messed up. After importing the jboss-seam/.project/.classpath the build path was still screwed up. How do you normally setup eclipse for a new checkout?

                                    1 2 Previous Next