[JBoss Web Services Development] - Not able to deploy Jaxws webservices - Incompletely deployed packages
by Rajesh Kumar
Rajesh Kumar [http://community.jboss.org/people/rajzzh] created the discussion
"Not able to deploy Jaxws webservices - Incompletely deployed packages"
To view the discussion, visit: http://community.jboss.org/message/553397#553397
--------------------------------------------------------------
In web.xml, i have the following,
<listener
>
<listener-class>
com.sun.xml.ws.transport.http.servlet.WSServletContextListener
</listener-class
>
</listener
>
<servlet
>
<servlet-name>jaxws</servlet-name
>
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class
>
</servlet
>
<servlet-mapping
>
<servlet-name>jaxws</servlet-name
>
<url-pattern>/BillPayService</url-pattern
>
</servlet-mapping
>
When I start the Jboss 4.3 server, i get the below error, not able to deploy the webservice.
10:41:46,421 ERROR [STDERR] Jul 19, 2010 10:41:46 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
10:41:48,955 ERROR [STDERR] Jul 19, 2010 10:41:48 AM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/BillPayInboundWs-BillPayService-BillPayServicePort
10:41:49,225 ERROR [STDERR] Jul 19, 2010 10:41:49 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
10:41:49,265 INFO [EARDeployer] Started J2EE application: file:/C:/Documents and Settings/e005934.MASTERCARD/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_EAP_4.3_Server/deploy/BillPayInboundWsApp.ear/
10:41:49,265 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@8d0a4c0f { url=file:/C:/Documents and Settings/e005934.MASTERCARD/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_EAP_4.3_Server/deploy/BillPayInboundService.wsdl }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/Documents and Settings/e005934.MASTERCARD/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_EAP_4.3_Server/deploy/BillPayInboundService.wsdl
altDD: null
lastDeployed: 1279554109265
lastModified: 1279554109265
mbeans:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@8d0a4c0f { url=file:/C:/Documents and Settings/e005934.MASTERCARD/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_EAP_4.3_Server/deploy/BillPayInboundService.wsdl }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/Documents and Settings/e005934.MASTERCARD/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_EAP_4.3_Server/deploy/BillPayInboundService.wsdl
altDD: null
lastDeployed: 1279554109265
lastModified: 1279554109265
mbeans:
Any help would greatly be appreciated...
Thanks,
Rajesh
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/553397#553397]
Start a new discussion in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
[JBoss ESB Development] - esb soapui can not debug
by yapeng zhao
yapeng zhao [http://community.jboss.org/people/yapeng] created the discussion
"esb soapui can not debug"
To view the discussion, visit: http://community.jboss.org/message/553386#553386
--------------------------------------------------------------
hello everyone ,i use org.jboss.soa.esb.actions.soap.SOAPClient as webService client to create soap request to the webService ,
i use jbossmq as the message bus, and i create my actions then create a Map instance set on the default body location (Message.getBody().add(Map)) ,
i use ServiceInvoker to send a message to invoke the actions,
in the jboss console print the errors :
11:39:25,345 INFO [STDOUT] Progress: 1 - Loading definition from cache
11:39:25,454 INFO [STDOUT] Retrieving document at ' http://192.168.123.21:8180/axis2/services/OrderService?wsdl http://192.168.123.21:8180/axis2/services/OrderService?wsdl'.
11:39:25,658 INFO [SchemaUtils] Loading schema types from [ http://192.168.123.21:8180/axis2/services/OrderService?wsdl http://192.168.123.21:8180/axis2/services/OrderService?wsdl]
11:39:25,658 INFO [SchemaUtils] Getting schema http://192.168.123.21:8180/axis2/services/OrderService?wsdl http://192.168.123.21:8180/axis2/services/OrderService?wsdl
11:39:25,798 INFO [SchemaUtils] schema for [ http://www.wxxr.com/vgop/serviceorder/v1_0/common http://www.wxxr.com/vgop/serviceorder/v1_0/common] contained [{}] namespaces
11:39:25,798 INFO [SchemaUtils] schema for [ http://www.wxxr.com/vgop/serviceorder/v1_0 http://www.wxxr.com/vgop/serviceorder/v1_0] contained [{}] namespaces
11:39:26,204 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: InVMEpr [ PortReference < <wsa:Address invm://5375627363726962655365727669636543617465676f727924242424242424242424242473756273637269626553657276696365436f6e73756d6572/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] MessageID: fe0ec823-2766-47bd-b2eb-96a52526c1cc
11:39:26,298 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms:172.16.21.34:1199#queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 172.16.21.34:1199/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: InVMEpr [ PortRef
erence < <wsa:Address invm://5375627363726962655365727669636543617465676f727924242424242424242424242473756273637269626553657276696365436f6e73756d6572/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] MessageID: fe0ec823-2766-47bd-b2eb-96a52526c1cc ]
11:39:26,329 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms:172.16.21.34:1199#queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 172.16.21.34:1199/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: InVMEpr [ PortRef
erence < <wsa:Address invm://5375627363726962655365727669636543617465676f727924242424242424242424242473756273637269626553657276696365436f6e73756d6572/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] MessageID: fe0ec823-2766-47bd-b2eb-96a52526c1cc ]
11:39:26,329 WARN [ActionProcessingPipeline] Failed to send response failure to DLQ service
11:39:27,626 INFO [MessageAwareListener] State reached : false
and i debug the java project ,
in my project the esb file dependes soapui-1.7.1.jar,
then i download the soapui source files 1.7.1 version,
and i find the jboss esb used soapui-1.7.1.jar is not the same version with my downloaded . whice version is the right ?
and they have some Inconsistent ?
and about the errors i find some Solution,
eg:
http://community.jboss.org/thread/105853 http://community.jboss.org/thread/105853
this issue is solved by changing jms connection pool size in jbossesb-properties.xml as below
<property name="org.jboss.soa.esb.jms.connectionPool" value="40"/>
and it still does not work well
i am a new user to jbossesb. anybody can help me ?
thank you .
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/553386#553386]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month