• Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: component-soap
    • Labels:



      Brain I did not found any thread for reporting SOAP Binding issues, Switchyard SOAP project is not getting deployed, because of following issues, I guess:

      Deployment fails to call Web Service in the same JBoss instance at deployment time in JBoss EAP 6.4. I have a deployment which calls our Switchyard-soap-binding (JAXWS Web Service) to get configuration at startup. It is is getting a 404 trying to access the URL, yet we can use SOAPUI or wget and are able to connect to the Switchyard-soap-binding. Why is our application running in the same JBoss instance unable to connect yet SOAPUI and other tools are?

      server console traces :

      16:07:30,912 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1

      16:07:33,045 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

      16:07:33,486 INFO [] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting

      16:07:44,820 INFO [] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

      16:07:44,860 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.13.GA-redhat-1

      16:07:44,901 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.13.GA-redhat-1

      16:07:45,245 INFO [] (ServerService Thread Pool – 31) JBAS010280: Activating Infinispan subsystem.

      16:07:45,250 INFO [] (ServerService Thread Pool – 44) JBAS013371: Activating Security Subsystem

      16:07:45,278 INFO [] (ServerService Thread Pool – 39) JBAS011800: Activating Naming Subsystem

      16:07:45,278 INFO [] (ServerService Thread Pool – 48) JBAS015537: Activating WebServices Extension

      16:07:45,247 WARN [] (ServerService Thread Pool – 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

      16:07:45,984 INFO [] (ServerService Thread Pool – 37) JBAS012615: Activated the following JSF Implementations: [main, 1.2]

      16:07:46,206 INFO [] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1)

      16:07:46,854 INFO [] (MSC service thread 1-3) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1

      16:07:48,146 INFO [] (ServerService Thread Pool – 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      16:07:49,405 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.3.4.Final-redhat-1

      16:07:49,745 INFO [] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      16:07:50,293 INFO [] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

      16:07:50,948 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/

      16:07:51,052 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/

      16:07:51,540 INFO [] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      16:07:53,099 INFO [] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory D:\Users\nitin-kuma\jbdevstudio\runtimes\jboss-eap\standalone\deployments

      16:07:53,107 INFO [] (MSC service thread 1-1) JBAS015876: Starting deployment of "switchyard-soap-binding.jar" (runtime-name: "switchyard-soap-binding.jar")

      16:07:53,175 INFO [] (MSC service thread 1-1) JBAS017100: Listening on

      16:07:53,178 INFO [] (MSC service thread 1-4) JBAS017100: Listening on

      16:07:55,454 INFO [] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1

      16:07:56,014 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment switchyard-soap-binding.jar

      16:07:56,197 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: switchyard-soap-binding.jar

      16:07:56,424 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.28 (redhat)

      16:07:56,542 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment switchyard-soap-binding.jar

      16:07:59,098 INFO [] (Remoting "lp-1cc1debc5521:MANAGEMENT" task-1) JBAS012119: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]

      16:07:59,097 INFO [] (Remoting "lp-1cc1debc5521:MANAGEMENT" read-1) JBAS012119: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]

      16:08:00,076 INFO [] (ServerService Thread Pool – 28) JBAS015859: Deployed "switchyard-soap-binding.jar" (runtime-name : "switchyard-soap-binding.jar")

      16:08:00,297 INFO [] (Controller Boot Thread) JBAS015961: Http management interface listening on

      16:08:00,301 INFO [] (Controller Boot Thread) JBAS015951: Admin console listening on

      16:08:00,304 INFO [] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 32515ms - Started 191 of 228 services (59 services are lazy, passive or on-demand)

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  tcunning Thomas Cunningham
                  rajuadityapur2012 nitin kumar
                • Votes:
                  0 Vote for this issue
                  3 Start watching this issue


                  • Created: