1 2 Previous Next 16 Replies Latest reply on Mar 2, 2009 9:37 AM by Martin Murphy

    Fuse ESB 3.3.1.13 wsdl-first sample won't run

    nicolas duminil Newbie

      Greetings,

       

      After I have installed FuseESB 3.3.1.13 I tried to run the wsdl-first sample by launching mvn install, mvn install jbi:projectDeploy and got the following error message:

       

      Build Error

      Unable to deploy project

      Error accessing ServiceMix administration

      non JRMP remote endpoint

       

      Looking on google I have seen that lots of people have got this same problems but none didn't seem to got a solution. Please help !

       

      Kind reagrds,

       

      Nicolas

        • 1. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
          Martin Murphy Novice

          This works fine for me on 3.3.1.13. Here is my build log:

           

          -


          Deployment Analysis -


          ServiceMix :: Samples :: WSDL first :: SA has 3 child dependencies

            - jbi-service-assembly : C:\Documents and Settings\mmurphy\.m2\repository\org\apache\servicemix\samples\cxf-wsdl-first\wsdl-first-cxf-sa\3.3.1.13-fuse\wsdl-first-cxf-sa-3.3.1.13-fuse.zip

            - jbi-component : C:\Documents and Settings\mmurphy\.m2\repository\org\apache\servicemix\servicemix-cxf-se\3.3.1.13-fuse\servicemix-cxf-se-3.3.1.13-fuse-installer.zip

            - jbi-component : C:\Documents and Settings\mmurphy\.m2\repository\org\apache\servicemix\servicemix-cxf-bc\3.3.1.13-fuse\servicemix-cxf-bc-3.3.1.13-fuse-installer.zip

            - jbi-shared-library : C:\Documents and Settings\mmurphy\.m2\repository\org\apache\servicemix\servicemix-shared\3.3.1.13-fuse\servicemix-shared-3.3.1.13-fuse-installer.zip

          -


          servicemix-shared is deployed

          servicemix-cxf-bc is deployed

          servicemix-cxf-se is deployed

          wsdl-first-cxf-sa is not deployed

          Deploying jbi-service-assembly from C:\Documents and Settings\mmurphy\.m2\repository\org\apache\servicemix\samples\cxf-wsdl-first\wsdl-first-cxf-sa\3.3.1.13-fuse\wsdl-first-cxf-sa-3.3.1.13-fuse.zip

          -


          Reactor Summary:

          -


          ServiceMix :: Samples :: CXF WSDL first ............... SUCCESS

          ServiceMix :: Samples :: WSDL first :: CXF SE ......... SUCCESS

          ServiceMix :: Samples :: WSDL first :: CXF BC ......... SUCCESS

          ServiceMix :: Samples :: WSDL first :: SA ............. SUCCESS

          -


          -


          BUILD SUCCESSFUL

          -


          Total time: 1 minute 52 seconds

          Finished at: Wed Feb 25 16:00:31 GMT 2009

          Final Memory: 32M/58M

          -


           

           

          On the FUSE ESB side I can see it deploying:

           

          INFO  - ServerImpl                     - Setting the server's publish address to be http://localhost:8092/PersonService/

          INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: wsdl-first-cxf-sa

          INFO  - ServiceUnitLifeCycle           - Initializing service unit: wsdl-first-cxfse-su

          INFO  - ServiceUnitLifeCycle           - Initializing service unit: wsdl-first-cxfbc-su

          INFO  - ServiceUnitLifeCycle           - Starting service unit: wsdl-first-cxfse-su

          INFO  - ReflectionServiceFactoryBean   - Creating Service PersonService from class org.apache.servicemix.samples.wsdl_first.Person

          INFO  - ConfigurerImpl                 - Could not determine bean name for instance of class org.apache.cxf.transport.jbi.JBIDestination.

          INFO  - ServerImpl                     - Setting the server's publish address to be jbi://ID-10-5-1-15-11fae2821d3-4-0

          INFO  - ServiceUnitLifeCycle           - Starting service unit: wsdl-first-cxfbc-su 25-Feb-2009 16:00:31 sun.reflect.NativeMethodAccessorImpl invoke0

          INFO: Logging to org.slf4j.impl.JDK14LoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog

          25-Feb-2009 16:00:31 sun.reflect.NativeMethodAccessorImpl invoke0

          INFO: jetty-6.1.12

          25-Feb-2009 16:00:31 sun.reflect.NativeMethodAccessorImpl invoke0

          INFO: Started SelectChannelConnector@0.0.0.0:8092

           

           

          I'm using Maven 2.0.9 and JDK 1.5. Also I cleared the hotdeploy directory to only contain the CXF-BC CXF-SE and shared components.

          • 2. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
            Martin Murphy Novice

            I've just realised that you may be attempting to use the wsdl-first demo and not the cxf-wsdl-first demo

            I've updated my hotdeploy just to have the jsr-181, http and shared components and restarted. I then deployed the wsdl first demo and that is working fine as well.

             

            INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: wsdl-first-sa

            INFO  - ServiceUnitLifeCycle           - Initializing service unit: wsdl-first-jsr181-su

            INFO  - ServiceUnitLifeCycle           - Initializing service unit: wsdl-first-http-su

            INFO  - ServiceUnitLifeCycle           - Starting service unit: wsdl-first-jsr181-su

            INFO  - ServiceUnitLifeCycle           - Starting service unit: wsdl-first-http-su

            INFO  - jetty                          - jetty-6.1.12

            INFO  - jetty                          - Started SelectChannelConnector@0.0.0.0:8192

             

             

            • 3. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
              nicolas duminil Newbie

              Martin,

               

              I'm very glad to know that it's working for you. I probably forgot to mention that I'm deploying servicemix war in JBoss 5 and, consequently, I'm using the JDK 1.6 and have to keep with it. I know that in the simplest case it's probably working but, as soon as one tries to use it in a slightly different context from the one in the manual ... Any clou on that ?

               

              Many thanks in advance,

               

              Nicolas

              • 4. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                nicolas duminil Newbie

                Some more details: running FuseESB 3.3.1.13 on SLES 10. While running with Java 5 the command mvn install jbi:projectDeploy raises:

                 

                ..................................

                jbi:projectDeploy

                Attempting to build MavenProject instance for Artifact (org.apache.ws.commons:XmlSchema:1.1) of type: jar; constructing POM artifact instead.

                -


                Deployment Analysis -


                ServiceMix :: Samples :: WSDL first :: SA has 3 child dependencies

                  - jbi-service-assembly : /home/nicolas/.m2/repository/org/apache/servicemix/samples/wsdl-first/wsdl-first-sa/3.3.1.13-fuse/wsdl-first-sa-3.3.1.13-fuse.zip

                  - jbi-component : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-jsr181/3.3.1.13-fuse/servicemix-jsr181-3.3.1.13-fuse-installer.zip

                  - jbi-component : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-http/3.3.1.13-fuse/servicemix-http-3.3.1.13-fuse-installer.zip

                  - jbi-shared-library : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-shared/3.3.1.13-fuse/servicemix-shared-3.3.1.13-fuse-installer.zip

                -


                -


                BUILD ERROR

                -


                Unable to deploy project, Error accessing ServiceMix administration

                 

                Connection refused

                 

                 

                While running with Java 6, the error is:

                 

                 

                jbi:projectDeploy

                Attempting to build MavenProject instance for Artifact (org.apache.ws.commons:XmlSchema:1.1) of type: jar; constructing POM artifact instead.

                -


                Deployment Analysis -


                ServiceMix :: Samples :: WSDL first :: SA has 3 child dependencies

                  - jbi-service-assembly : /home/nicolas/.m2/repository/org/apache/servicemix/samples/wsdl-first/wsdl-first-sa/3.3.1.13-fuse/wsdl-first-sa-3.3.1.13-fuse.zip

                  - jbi-component : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-jsr181/3.3.1.13-fuse/servicemix-jsr181-3.3.1.13-fuse-installer.zip

                  - jbi-component : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-http/3.3.1.13-fuse/servicemix-http-3.3.1.13-fuse-installer.zip

                  - jbi-shared-library : /home/nicolas/.m2/repository/org/apache/servicemix/servicemix-shared/3.3.1.13-fuse/servicemix-shared-3.3.1.13-fuse-installer.zip

                -


                -


                BUILD ERROR

                -


                Unable to deploy project, Error accessing ServiceMix administration

                 

                non-JRMP server at remote endpoint

                 

                In both cases, FuseESB 3.3.1.13 doesn't run in stand-alone mode on SLES 10.3. Could anyone please help ?

                 

                Many thanks in adavance,

                 

                Nicolas

                • 5. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                  nicolas duminil Newbie

                  Does anybody feel concerned ?

                  • 6. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                    nicolas duminil Newbie

                    Does anybodt feel concerned ?

                    • 7. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                      Martin Murphy Novice

                      I wonder if jconsole can connect? My guess is it can't either. This would lead me to question if servicemix has been deployed correctly into JBoss. Can you check with jconsole and then have a look in your JBoss logs/admin to see if it has deployed correctly.

                       

                      Also, note that we haven't certified on SLES 10 yet, but there is an open requirement for this. Note this doesn't mean it won't work, just that we haven't added this platform to our release cycle yet for FUSE ESB.

                       

                      Finally out of interest, can you test this standalone and confirm it is working on the platform for you.

                      • 8. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                        nicolas duminil Newbie

                        Yes, jconsole can connect. And no, servicemix is not deployed in JBoss in the scenario I'm speaking about. This is really the most basic case when one starts servicemix in standalone mode and tries to run a sample in order to test the installation.

                         

                        I don't beleive I did any mistake during the install as I only downloaded the binary for Linux 64 bits, I started the install script and, once it finished announcing that the install was successfull, I started servicemix, which started correctly, without any error. This has happened three days ago and since I'm trying to get a sample running. The most surprizing is that nobody seems to be ever heard about such a behaviour, however I don't see any raeson that this happens only in my case, as I didn't do anything of special.

                         

                        Anyway ...

                        • 9. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                          Martin Murphy Novice

                          This is very strange, the only thing I can think of is that it could be a problem with SUSE 10.

                          Can you attach the servicemix.log file?

                          • 10. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                            nicolas duminil Newbie

                            Of course, here you are. This servicemix.xml file is exactly the same as the one I use on Windows XP and in this install the "mvn install jbi:projectDeploy" succeeds.

                             

                            Does it mean that FuseESB 3.1.1.13 isn't supported on SLES ? And, ss we have to use SLES, does it mean that we need to reconsider our ESB choice ? Please advice.

                             

                            Many thanks in advance,

                             

                            Nicolas DUMINIL

                            • 11. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                              nicolas duminil Newbie

                              And here is the servicemix.log file

                              • 12. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                                Martin Murphy Novice

                                I notice in the logs that your jmx connector is started on 2099:

                                 

                                JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:2099/jmxrmi

                                 

                                The default port is 1099, so I'm guessing you have updated your servicemix.properties file to change this port.

                                 

                                Here is what the default setting looks like:

                                 

                                rmi.port                   = 1099

                                rmi.host                   = localhost

                                jmx.url                    = service:jmx:rmi:///jndi/rmi://${rmi.host}:${rmi.port}/jmxrmi

                                 

                                 

                                Could you try switching back to 1099 to see if that solves the problem?

                                I notice from the logs that ServiceMix was shutdown. I presume that was intentional.

                                 

                                Finally, you can still deploy your Service Assemblies by copying them to the hotdeploy folder.

                                • 13. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                                  nicolas duminil Newbie

                                  Martin,

                                   

                                  Yes, this is correct, I modified the TCP port number of servicemix to be 2099 as 1099 was busy. I stoped the service currently working on 1099, I modified the servicemix.properties file in order to configure it back to 1099 and the deploy command worked this time. Obviously, servicemix is not able to run on any other TCP port than 1099, at least on SLES.

                                   

                                  This is certainly not a solution as we cannot use a product whose TCP port number couldn't be modified. This is also the goal of servicemix.properties file: to configure the settings, i.e to run the service on a different port than the default one.

                                   

                                  Also, deploying by copy is not reasonable at the Eclipse/maven era or, if you prefer, it's as reasonable as using Notepad as a software development tool and copy commands as SCM.

                                   

                                  Many thanks for your help,

                                   

                                  Nicolas

                                  • 14. Re: Fuse ESB 3.3.1.13 wsdl-first sample won't run
                                    Ulhas Bhole Novice
                                    nicolas-duminil wrote:

                                    Martin,

                                     

                                    Yes, this is correct, I modified the TCP port number of servicemix to be 2099 as 1099 was busy. I stoped the service currently working on 1099, I modified the servicemix.properties file in order to configure it back to 1099 and the deploy command worked this time. Obviously, servicemix is not able to run on any other TCP port than 1099, at least on SLES.

                                     

                                    Hi Nicolas,

                                    Simple solution is to add -Dport=<your-rmi-port> in mvn jbi:projectDeploy command. e..g. mvn -Dport=2099 jbi:projectDeploy

                                    1 2 Previous Next