8 Replies Latest reply on Nov 23, 2013 12:11 AM by Akaine Harga

    Web Service endpoint already registered.

    Bruno Cardoso Newbie

      Anyone have any idea what is this error, already tried a lot and found no light on how to solve it.

      in Jboss 7.0.1.Final its run but in i am using now Jboss AS  7.1.0.final and run deploy....ERROR

       

       

      10:22:06,097 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."snaLight.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."snaLight.war".PARSE: Failed to process phase PARSE of deployment "snaLight.war"

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]

                at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]

      Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint com.sun.xml.ws.tx.webservice.member.coord.ActivationRequesterPortTypeImpl with URL pattern /Coordinator is already registered. Web service endpoint com.sun.xml.ws.tx.webservice.member.coord.RegistrationRequesterPortTypeImpl is requesting the same URL pattern.

                at org.jboss.as.webservices.metadata.model.AbstractDeployment.addEndpoint(AbstractDeployment.java:60)

                at org.jboss.as.webservices.metadata.model.JAXWSDeployment.addEndpoint(JAXWSDeployment.java:27)

                at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_POJO.processAnnotation(WSIntegrationProcessorJAXWS_POJO.java:94)

                at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:87)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                ... 5 more

       

       

      10:22:06,112 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "snaLight.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"snaLight.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"snaLight.war\".PARSE: Failed to process phase PARSE of deployment \"snaLight.war\""}}

      10:22:07,021 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment snaLight.war in 884ms

      10:22:07,021 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.deployment.unit."snaLight.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."snaLight.war".PARSE: Failed to process phase PARSE of deployment "snaLight.war"

       

       

      10:22:07,021 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"snaLight.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"snaLight.war\".PARSE: Failed to process phase PARSE of deployment \"snaLight.war\""}}}}

        • 1. Re: Web Service endpoint already registered.
          Syed Jawahar Newbie

          Hi Brundo,

           

          i am facing the same error when i deploy the war file which contains webservice_rt.jar file in the lib folder, worked in jboss-eap-5.1 got an error in jboss-as-7.1.0.final

           

          Caused by: java.lang.IllegalArgumentException: JBAS015533: Web Service endpoint
          com.sun.xml.ws.tx.coord.v11.endpoint.RegistrationPortImpl with URL pattern /Regi
          strationService_V11 is already registered. Web service endpoint com.sun.xml.ws.t
          x.coord.v11.endpoint.RegistrationRequesterPortImpl is requesting the same URL pa
          ttern.

           

          14:20:45,225 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS
          7.1.0.Final "Thunder" started (with errors) in 3407ms - Started 137 of 209 servi
          ces (1 services failed or missing dependencies, 70 services are passive or on-de
          mand)
          14:20:45,225 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015
          870: Deploy of deployment "amadeus.war" was rolled back with failure message {"J
          BAS014671: Failed services" => {"jboss.deployment.unit.\"amadeus.war\".PARSE" =>
          "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"amadeu
          s.war\".PARSE: Failed to process phase PARSE of deployment \"amadeus.war\""}}
          14:20:45,318 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBA
          S015877: Stopped deployment amadeus.war in 93ms

           

           

          Do you have an solution/fix  for the above error,

           

          Thanks & Regards

          Jawahar      

          • 2. Re: Web Service endpoint already registered.
            Bruno Cardoso Newbie

            I have not found solution yet to this problem, with jboss 7.0.2 application works. 7.1.0 only the error occurs.

            • 3. Re: Web Service endpoint already registered.
              Syed Jawahar Newbie

              Thanks Brundo, tried with 7.0.2-final it works fine. Problem with 7.1.0 still exists.

              • 4. Re: Web Service endpoint already registered.
                Antonio Bruno Newbie

                Hi,
                same error occurs when deploying a war with jboss 7.1.1.Final.
                Instead it works with jboss 7.0.2.Final.

                Still no news on this bug?

                 

                Regards

                Ing. Antonio Bruno

                • 5. Re: Web Service endpoint already registered.
                  NIranjan Nanda Apprentice

                  This is happening because JBoss 7.1 already starts a web service service. Open $JBOSS_HOME/standalone/configuration/standalone.xml and look for below blocks/lines and comment those:

                   

                  <extension module="org.jboss.as.webservices"/>

                   

                  <subsystem xmlns="urn:jboss:domain:webservices:1.1">

                              <modify-wsdl-address>true</modify-wsdl-address>

                              <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>

                              <endpoint-config name="Standard-Endpoint-Config"/>

                              <endpoint-config name="Recording-Endpoint-Config">

                                  <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

                                      <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>

                                  </pre-handler-chain>

                              </endpoint-config>

                          </subsystem>

                   

                   

                  Your app should deploy now.

                   

                  Although JBoss 7.1 is modular, but its embracing to JAX-WS really frustrates. I am still pondering why JBoss 7.1 includes a JAX-WS service and starts it. It just restricts developers to use their own flavor of technology stack.

                   

                  Thanks,

                  Niranjan

                  • 6. Re: Web Service endpoint already registered.
                    Stephen Coy Master

                    NIranjan Nanda wrote:

                     

                    ...

                     

                    Although JBoss 7.1 is modular, but its embracing to JAX-WS really frustrates. I am still pondering why JBoss 7.1 includes a JAX-WS service and starts it. It just restricts developers to use their own flavor of technology stack.

                     

                     

                    Because every Enterprise Java Specification since J2EE 1.4 has required it to do this.

                    (Although technically J2EE 1.4 was JAX-RPC only, JAX-WS was introduced in Java EE 5).

                     

                    Personally, I've *never* needed to use a particular WS tech stack. Sticking to the standards has meant that my applications have always worked on every vendor's enterprise java server implementation.

                    • 7. Re: Web Service endpoint already registered.
                      NIranjan Nanda Apprentice

                      Well Stephen,

                       

                      I am also in favor of standards, and I always try adhering to standards. In this case, I am using Sun Metro, which is also a standard product, but my point was, why JBoss starts the service.

                       

                      Anyways, this could be a separate discussion. I have another question related to JBoss 7 and Sun Metro. Could you please check the below link and see if you have any clue?

                       

                      http://stackoverflow.com/questions/13045885/jboss-7-1-with-spring-3-1-2-and-sun-metro-2-1-1-peculiar-issue

                       

                      Thanks and Regards,

                      Niranjan

                      • 8. Re: Web Service endpoint already registered.
                        Akaine Harga Novice

                        Just remove the web service related libraries from the application you're deploying.