Hide Forgot
Date of First Response: 2010-01-13 05:14:15 project_key: SOA See linked issue for details.
Link: Added: This issue related JBESB-3083
A fix for JBESB-3083 has been committed to jbossesb/branches/JBESB_4_7_CP.
Didn't make ER7
Wise SOAPClient action now invokes Oneway methods correctly, but I am getting *Fatal Error :-1:-1: Premature end of file* after invocation. See console output in this comment, I also attached server.log file. Don't see any relevant exceptions in the log, so I am not sure what exactly is causing this Fatal Error message. 17:15:16,823 INFO [STDOUT] Message structure: 17:15:16,823 INFO [STDOUT] [ message: [ JBOSS_XML ] header: [ To: JMSEpr [ PortReference < <wsa:Address jms:localhost#queue/wise_oneway_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/wise_oneway_esb/>, <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/> > ] MessageID: 1e086d11-f5fa-4167-b815-a6badc6a2e64 RelatesTo: jms:correlationID#1e086d11-f5fa-4167-b815-a6badc6a2e64 ] context: {} body: [ objects: {request-content=Deferred serialized value: 6e7ce201} ] fault: [ ] attachments: [ Named:{}, Unnamed:[] ] properties: [ {org.jboss.soa.esb.message.transport.type=Deferred serialized value: 5a2384db, org.jboss.soa.esb.message.byte.size=2495, javax.jms.message.redelivered=false, org.jboss.soa.esb.message.source=Deferred serialized value: 51e77418} ] ] 17:15:16,825 INFO [STDOUT] Outbound message: 17:15:16,825 INFO [STDOUT] <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns1:sendOneWay xmlns:ns1="http://oneway_wise/helloworld"/></env:Body></env:Envelope> 17:15:16,830 INFO [STDOUT] @@@@ Hello world from OneWay! @@@@ 17:15:16,832 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file. 17:15:16,832 INFO [MessagePayloadProxy] Null data found in message location(s): [org.jboss.soa.esb.message.defaultEntry] 17:15:16,832 INFO [STDOUT] Message structure: 17:15:16,832 INFO [STDOUT] [ message: [ JBOSS_XML ] header: [ To: JMSEpr [ PortReference < <wsa:Address jms:localhost#queue/wise_oneway_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/wise_oneway_esb/>, <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/> > ] MessageID: 1e086d11-f5fa-4167-b815-a6badc6a2e64 RelatesTo: jms:correlationID#1e086d11-f5fa-4167-b815-a6badc6a2e64 ] context: {} body: [ objects: {response-content={result=null}, request-content={webMethodName=sendOneWay}, response-content-set-stack=java.lang.Exception: setPayload stack trace for 'response-content'.} ] fault: [ ] attachments: [ Named:{}, Unnamed:[] ] properties: [ {org.jboss.soa.esb.message.transport.type=Deferred serialized value: 5a2384db, org.jboss.soa.esb.message.byte.size=2495, jboss.esb:category=MessageCounter,deployment=Wise-One-Way.esb,service-category=WiseWebServices,service-name=OnewayTime=9051292, javax.jms.message.redelivered=false, org.jboss.soa.esb.message.source=Deferred serialized value: 51e77418} ] ]
Attachment: Added: server.log.bz2
Looks like SOAPClient never handled null responses (request/response) so now fails on OneWay.
So what is the resolution for this JIRA? Will there be some additional fixes for SOAPClient? If yes, this JIRA should be reopen.
I will shortly be creating a new bug to cover this, and will link it here.
The premature end of file originates in the JBossWS codebase, before it gets back to wise.
Attachment: Added: stacktrace.log
Stacktrace from CP1 server
Attachment: Added: stacktrace.cp1.log
Link: Added: This issue related SOA-1945
Verified in CR1. WISE SOAPClient is now able to invoke Oneway methods on WS endpoints. (For premature end of file issue see SOA-1945).