[jboss-dev-forums] [JBoss ESB Development] - esb soapui can not debug

[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&containerType=14&container=2032]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20100720/e1452d1c/attachment.html