1 2 Previous Next 19 Replies Latest reply on Jul 13, 2007 6:35 AM by toby saville

    Quickstart webservice_jbossws_adapter_01 question

    toby saville Novice

      Hello,

      i am running into an issue with the above quickstart.

      before i start on the main issue, can you explain why the readme tells you to remove jbossesb.esb/jbm-queue-service.xml file? When i started the AS (after following the steps in the readme) it complained and didnt start the esb archive. thanks! :)

      With that last paragraph in mind, i am running the quickstart with the jbm-queue-service.xml file in place (maybe this is the cause of my problem, but i doubt it)

      I am following the quickstart's readme, which contains a different svn repo url to previous versions (http://anonsvn.jboss.org/repos/jbossws/branches/jbossws-2.0) can you confirm this is the correct one? The reason I ask is due to some confusion in my mind raised by reading this post:http://www.jboss.org/index.html?module=bb&op=viewtopic&t=111480

      I should also say that i have recently updated from both ESB & WS repositories before posting this.

      When i start up the AS after following the quickstart, i get the following error:

      ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.0.GA/server/messaging/tmp/deploy/tmp25903Quickstart_webservice_jbossws_adapter_01.esb-contents/Quickstart_webservice_jbossws_adapter_01.war
      java.lang.NullPointerException
       at org.jboss.wsf.container.jboss42.WebMetaDataAdapter.buildUnifiedWebMetaData(WebMetaDataAdapter.java:64)
       at org.jboss.wsf.container.jboss42.DeploymentInfoAdapter.buildMetaData(DeploymentInfoAdapter.java:117)
       at org.jboss.wsf.container.jboss42.DeploymentInfoAdapter.buildDeploymentInfo(DeploymentInfoAdapter.java:86)
       at org.jboss.wsf.container.jboss42.UnifiedDeploymentInfoDeployer.create(UnifiedDeploymentInfoDeployer.java:64)
       at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:69)
       at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
       at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
       at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
       at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
       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 $Proxy46.create(Unknown Source)
       at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
       at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
       at sun.reflect.GeneratedMethodAccessor22.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.startService(AbstractDeploymentScanner.java:336)
       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 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.deploy(MainDeployer.java:819)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
       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: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 $Proxy5.deploy(Unknown Source)
       at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
       at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
       at org.jboss.Main.boot(Main.java:200)
       at org.jboss.Main$1.run(Main.java:508)
       at java.lang.Thread.run(Thread.java:595)
      


      most of this code is in the JBossWS project, so let me know if you i should redirect this question to their forum.

      i had a dig around, and its trying to load the field called modules of type org.jboss.deployment.J2eeModuleMetaData from a property of type org.jboss.deployment.J2eeApplicationMetaData from an object of type org.jboss.deployment.DeploymentInfo. From what i gathered from the source, this modules field is:
      The application.xml modules in definition order
      

      Does this mean its trying to load info from a file with this name?

      the code snippet from org.jboss.wsf.container.jboss42.WebMetaDataAdapter is:
      ...
      import org.jboss.deployment.DeploymentInfo;
      import org.jboss.deployment.J2eeApplicationMetaData;
      import org.jboss.deployment.J2eeModuleMetaData;
      import org.jboss.metadata.WebMetaData;
      ...
      
      public class WebMetaDataAdapter
      {
       public UnifiedWebMetaData buildUnifiedWebMetaData(Deployment dep, UnifiedDeploymentInfo udi, DeploymentInfo di)
       {
       String contextRoot = null;
      
       WebMetaData wmd = (WebMetaData)di.metaData;
       dep.getContext().addAttachment(WebMetaData.class, wmd);
      
       if (di.parent != null)
       {
       J2eeApplicationMetaData appmd = (J2eeApplicationMetaData)di.parent.metaData;
       Iterator it = appmd.getModules(); // FAILS ON THIS LINE
       while (it.hasNext())
       {
       J2eeModuleMetaData module = (J2eeModuleMetaData)it.next();
       if (module.getFileName().equals(udi.simpleName))
       contextRoot = module.getWebContext();
       }
       }
      ...
      


      thanks for any help you can provide.

      toby

        • 1. Re: Quickstart webservice_jbossws_adapter_01 question
          Tom Fennelly Master

          Phew... Toby, that was some post ;-)

          Anyway...

          I am following the quickstart's readme
          Accept for one very important part... you're not removing jbossesb.esb/jbm-queue-service.xml.

          This file needs to be removed if you're using JBoss AS 4.2GA out-of-the-box. JBoss AS 4.2GA ships with JMossMQ and not JBoss Messaging. jbossesb.esb/jbm-queue-service.xml is only required if you've removed JBossMQ from your AS and patched it with JBoss Messaging. Have you done this? If so, then you need to remove jbossesb.esb/jbmq-queue-service.xml. Only one of these files (jbm-queue-service.xml or jbmq-queue-service.xml) can be present.

          Can you try this and report back please?

          • 2. Re: Quickstart webservice_jbossws_adapter_01 question
            Tom Fennelly Master

            Toby, can you also take a look at this thread please and see how it matches up with the issue as you see it:
            http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113048.

            Sort out the 2 JMS deployment descriptors first though please.

            • 3. Re: Quickstart webservice_jbossws_adapter_01 question
              toby saville Novice

              Hello,

              yeah, sorry for the length, its a pity that after all that, i omitted the fact that i have indeed patched my AS with JBossMessaging 1.3.0GA, so now my jbossesb.esb dir only contains jbm-queue-service.xml (and no jbmq-queue-service.xml file).

              ill check out the thread you linked to and report back again after that.

              thanks for the swift follow up!

              - tobes

              • 4. Re: Quickstart webservice_jbossws_adapter_01 question
                toby saville Novice

                yeah, looks like the same issue - the stack traces are very similar (if not the same, only compared the first 5 lines)

                I also removed the tmp, data & work folders, restarted and came across the same problem

                thanks again,
                - tobes

                • 5. Re: Quickstart webservice_jbossws_adapter_01 question
                  Kevin Conner Master

                   

                  "tfennelly" wrote:
                  This file needs to be removed if you're using JBoss AS 4.2GA out-of-the-box. JBoss AS 4.2GA ships with JMossMQ and not JBoss Messaging. jbossesb.esb/jbm-queue-service.xml is only required if you've removed JBossMQ from your AS and patched it with JBoss Messaging.


                  Sorry, but can you explain *why* this is in the instructions? The installation already installs the correct version of the messaging services into jbossesb.esb.


                  • 6. Re: Quickstart webservice_jbossws_adapter_01 question
                    Tom Fennelly Master

                     

                    "tobysaville" wrote:
                    yeah, sorry for the length


                    Don't mind me Toby, I'm just kidding :-) Lots of information is good!

                    "tobysaville" wrote:
                    i have indeed patched my AS with JBossMessaging 1.3.0GA, so now my jbossesb.esb dir only contains jbm-queue-service.xml (and no jbmq-queue-service.xml file).
                    - tobes


                    OK, so that's not the issue then (hopefully).

                    "tobysaville" wrote:
                    yeah, looks like the same issue - the stack traces are very similar (if not the same, only compared the first 5 lines)


                    OK, well since then I tried out these quickstart and found that they deployed fine in my env. The only difference I can tell right now (from your env) is the fact that I was using JBossMQ.

                    I'll try these again here with JBoss Messaging + the GA release of JBossWS 2.0.0 (just out) and see what I get.

                    "Kevin.Conner@jboss.com" wrote:
                    "tfennelly" wrote:
                    This file needs to be removed if you're using JBoss AS 4.2GA out-of-the-box. JBoss AS 4.2GA ships with JMossMQ and not JBoss Messaging. jbossesb.esb/jbm-queue-service.xml is only required if you've removed JBossMQ from your AS and patched it with JBoss Messaging.


                    Sorry, but can you explain *why* this is in the instructions? The installation already installs the correct version of the messaging services into jbossesb.esb.


                    If jbossesb.esb is just copied in Vs installed via the install script, then one of those files needs to be removed manually. I'll update the readme to highlight that that doesn't need to be done if installed via the installer. Thanks Kev.

                    • 7. Re: Quickstart webservice_jbossws_adapter_01 question
                      Kevin Conner Master

                       

                      "tfennelly" wrote:
                      If jbossesb.esb is just copied in Vs installed via the install script, then one of those files needs to be removed manually. I'll update the readme to highlight that that doesn't need to be done if installed via the installer. Thanks Kev.


                      Just leave it Tom, this is one of my tasks for today in any case :)

                      We should be asking people to install via the installation script though, not copying the esbs around. Then we know what configuration they are using.

                      • 8. Re: Quickstart webservice_jbossws_adapter_01 question
                        Tom Fennelly Master

                         

                        "Kevin.Conner@jboss.com" wrote:
                        We should be asking people to install via the installation script though, not copying the esbs around. Then we know what configuration they are using.


                        I agree, but I'd still like to make it clear, just in case someone did copy them manually. All this type of info should probably go in a top level readme anyway (in the root of the quickstarts, not conf), with each individual QS readme referring to it.

                        • 9. Re: Quickstart webservice_jbossws_adapter_01 question
                          Kevin Conner Master

                           

                          "tfennelly" wrote:
                          I agree, but I'd still like to make it clear, just in case someone did copy them manually. All this type of info should probably go in a top level readme anyway (in the root of the quickstarts, not conf), with each individual QS readme referring to it.

                          We should not be giving any instructions for doing it manually, especially with the quickstarts. The prerequisite for running those should be that they have installed the ESB using the install script.


                          • 10. Re: Quickstart webservice_jbossws_adapter_01 question
                            Tom Fennelly Master

                            Ok guys, I'm after getting to the bottom of this. Unfortunately the goalposts have moved on us re JBossWS 2.0. Changes were made there since this SOAPProcessor work was done and prior to JBossWS 2.0.0GA being released. These changes are breaking us, causing this error that Toby and Andy are seeing :-(

                            I'll be back in a bit when I've a better idea what our options are on this.

                            • 11. Re: Quickstart webservice_jbossws_adapter_01 question
                              toby saville Novice

                              I just tried running the quickstart against a fresh install of the ESB into my AS server config that uses JBossMQ. I got a very similar stack trace:

                              java.lang.NullPointerException
                               at org.jboss.wsf.container.jboss42.WebMetaDataAdapter.buildUnifiedWebMetaData(WebMetaDataAdapter.java:64)
                               at org.jboss.wsf.container.jboss42.DeploymentInfoAdapter.buildMetaData(DeploymentInfoAdapter.java:117)
                               at org.jboss.wsf.container.jboss42.DeploymentInfoAdapter.buildDeploymentInfo(DeploymentInfoAdapter.java:86)
                               at org.jboss.wsf.container.jboss42.UnifiedDeploymentInfoDeployer.create(UnifiedDeploymentInfoDeployer.java:64)
                               at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:69)
                               at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
                               at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
                               at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
                               at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
                               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 $Proxy46.create(Unknown Source)
                               at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
                               at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
                               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
                               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
                               at sun.reflect.GeneratedMethodAccessor18.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)
                              


                              while im here, could i be so bold as to suggest an addition to the readme for this quickstart. Step 5.b) - deploy using the deploy-jboss42 target. It might be helpful to specify that its the ant script in the jbossws-core folder. It took me a wee while to find the target referred to.



                              • 12. Re: Quickstart webservice_jbossws_adapter_01 question
                                Tom Fennelly Master

                                 

                                "tobysaville" wrote:
                                I just tried running the quickstart against a fresh install of the ESB into my AS server config that uses JBossMQ. I got a very similar stack trace


                                Yep, JBossWS 2.0.0GA is breaking us. I'm working a patch for this.

                                "tobysaville" wrote:
                                while im here, could i be so bold as to suggest an addition to the readme for this quickstart. Step 5.b) - deploy using the deploy-jboss42 target. It might be helpful to specify that its the ant script in the jbossws-core folder. It took me a wee while to find the target referred to.


                                I've actually updated the readmes with instructions to install JBossWS 2.0.0GA. It comes with a set of install instructions that are fine.

                                • 13. Re: Quickstart webservice_jbossws_adapter_01 question
                                  Mark Little Master

                                   

                                  "tfennelly" wrote:

                                  Yep, JBossWS 2.0.0GA is breaking us. I'm working a patch for this.


                                  Let me know if I need to go talk to someone ;-)

                                  • 14. Re: Quickstart webservice_jbossws_adapter_01 question
                                    toby saville Novice

                                     


                                    Yep, JBossWS 2.0.0GA is breaking us. I'm working a patch for this.


                                    Thanks a lot Tom, i eagerly await your patching gold :)

                                    1 2 Previous Next