ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP request failure

Post new topic  Reply to topic
 SOAP request failure « View previous topic :: View next topic » 
Author Message
cc
PostPosted: Thu Sep 20, 2012 7:56 pm    Post subject: SOAP request failure Reply with quote

Novice

Joined: 28 May 2008
Posts: 19
I am getting an Exception out of the SOAP Request Failure Terminal. We are running WMB V8.0.0.0 on Linux s390x.

The Exception looks like this:

ExceptionList
RecoverableException
File:CHARACTER:F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1129
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ImbRequestTemplateNode
Name:CHARACTER:TestGroups#FCMComposite_1_3
Label:CHARACTER:TestGroups.SOAP Request
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestNode.cpp
Line:INTEGER:797
Function:CHARACTER:ImbSOAPRequestNode::requestData
Type:CHARACTER:ImbRequestTemplateNode
Name:CHARACTER:TestGroups#FCMComposite_1_3
Label:CHARACTER:TestGroups.SOAP Request
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3754
Text:CHARACTER:Error occurred in ImbSOAPRequestHelper::makeSOAPRequest()
RecoverableException
File:CHARACTER:F:\build\S000_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp
Line:INTEGER:1852
Function:CHARACTER:ImbSOAPRequestHelper::makeSOAPRequest
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3701
Text:CHARACTER:Error Making SOAP JNI Call: Axis2Requester_processRequestMessageNonSoap
Insert
Type:INTEGER:5
Text:CHARACTER:Axis2Requester_processRequestMessageNonSoap
Insert
Type:INTEGER:5
Text:CHARACTER:java.lang.NullPointerException
Insert
Type:INTEGER:5
Text:CHARACTER:Frame : 0 java.lang.NullPointerException: null
@: com.ibm.xml.xlxp2.scan.util.SymbolMap.copyObjectsFromParent(SymbolMap.java:453)
@: com.ibm.xml.xlxp2.scan.util.SymbolMap.addSymbolSubstring(SymbolMap.java:437)
@: com.ibm.xml.xlxp2.scan.util.Symbol.setQNameValues(Symbol.java:135)
@: com.ibm.xml.xlxp2.scan.util.SymbolMap.getQNameSymbol(SymbolMap.java:299)
@: com.ibm.xml.xlxp2.scan.util.SymbolTable.getQNameSymbol(SymbolTable.java:119)
@: com.ibm.xml.xlxp2.scan.DocumentScanner.scanQName(DocumentScanner.java:3821)
@: com.ibm.xml.xlxp2.scan.DocumentScanner.scanElementType(DocumentScanner.java:4460)
@: com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElementCommon(DocumentScanner.java:2283)
@: com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElement(DocumentScanner.java:2253)
@: com.ibm.xml.xlxp2.scan.DocumentScanner.nextEvent(DocumentScanner.java:1294)
@: com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:579)
@: com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxyImpl.next(XMLInputFactoryImpl.java:183)
@: com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderProxy.next(WSSXMLInputFactory.java:55)
@: org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:622)
@: org.apache.axiom.om.impl.builder.StAXOMBuilder.lookahead(StAXOMBuilder.java:634)
@: org.apache.axiom.soap.impl.llom.SOAPBodyImpl.hasLookahead(SOAPBodyImpl.java:191)
@: org.apache.axiom.soap.impl.llom.SOAPBodyImpl.getFirstElementLocalName(SOAPBodyImpl.java:217)
@: org.apache.axiom.soap.impl.llom.SOAPBodyImpl.hasFault(SOAPBodyImpl.java:99)
@: com.ibm.broker.axis2.SoapUtilities.wrapDataInSoapEnvelopeIfRequiredAvoidingAxis2(SoapUtilities.java:1789)
@: com.ibm.broker.axis2.Axis2Requester.processRequestMessageNonSoap(Axis2Requester.java:1045)


The message being sent into the SOAP Request Node looks like this:

Message
Properties
MessageSet:CHARACTER:
MessageType:CHARACTER:
MessageFormat:CHARACTER:
Encoding:INTEGER:546
CodedCharSetId:INTEGER:437
Transactional:BOOLEAN:true
Persistence:BOOLEAN:false
CreationTime:TIMESTAMP:java.util.GregorianCalendar[time=1348212225500,areFieldsSet=true,areAllFieldsSet=false,lenient=true,zone=sun.util.calendar.ZoneInfo[id="America/New_York",offset=-18000000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=America/New_York,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=?,YEAR=2012,MONTH=8,WEEK_OF_YEAR=?,WEEK_OF_MONTH=?,DAY_OF_MONTH=21,DAY_OF_YEAR=?,DAY_OF_WEEK=?,DAY_OF_WEEK_IN_MONTH=?,AM_PM=0,HOUR=3,HOUR_OF_DAY=3,MINUTE=23,SECOND=45,MILLISECOND=500,ZONE_OFFSET=?,DST_OFFSET=?]
ExpirationTime:INTEGER:-1
Priority:INTEGER:0
ReplyIdentifier:BLOB:[B@7bb27bb2
ReplyProtocol:CHARACTER:MQ
Topic:UNKNOWN:null
ContentType:CHARACTER:
IdentitySourceType:CHARACTER:
IdentitySourceToken:CHARACTER:
IdentitySourcePassword:CHARACTER:
IdentitySourceIssuedBy:CHARACTER:
IdentityMappedType:CHARACTER:
IdentityMappedToken:CHARACTER:
IdentityMappedPassword:CHARACTER:
IdentityMappedIssuedBy:CHARACTER:
XMLNSC
Envelope
xsi:CHARACTER:http://www.w3.org/2001/XMLSchema-instance
xsd:CHARACTER:http://www.w3.org/2001/XMLSchema
soapenv:CHARACTER:http://schemas.xmlsoap.org/soap/envelope/
urnMobile:CHARACTER:urn:mobile_payment
Body
log_et_tracking
urn:CHARACTER:urn:log_et_tracking
encodingStyle:CHARACTER:http://schemas.xmlsoap.org/soap/encoding/
issue_text:CHARACTER:Record: 338
event_name:CHARACTER:PLAN CHANGE
bill_lvl_cim:CHARACTER:1
bill_lvl_case_number:CHARACTER:000000
carrier:CHARACTER:FB


The ESQL Code to generate this Message looks like this:

ESQL:
SET OutputRoot.Properties = InputProperties;
SET OutputRoot.XMLNSC.soapenv:Envelope.(XMLNSC.NamespaceDecl)xmlns:xsi=xsi;
SET OutputRoot.XMLNSC.soapenv:Envelope.(XMLNSC.NamespaceDecl)xmlns:xsd=xsd;
SET OutputRoot.XMLNSC.soapenv:Envelope.(XMLNSC.NamespaceDecl)xmlns:soapenv=soapenv;
SET OutputRoot.XMLNSC.soapenv:Envelope.(XMLNSC.NamespaceDecl)xmlns:urnMobile=urnMobile;
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.(XMLNSC.NamespaceDecl)xmlns:urn=urnlog;
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.(XMLNSC.Attribute)soapenv:encodingStyle = 'http://schemas.xmlsoap.org/soap/encoding/';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.issue_text='Record: ' || CAST(NUMREC AS CHARACTER);
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.event_name = 'PLAN CHANGE';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.bill_lvl_cim = rGroup.groupCim;
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.bill_lvl_cim = '1';
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.bill_lvl_case_number = rGroup.groupCaseNum;
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.urnlog:log_et_tracking.carrier = 'FB';

I have tried pointing the URL in the SOAP Request Node at the localhost with the TCP/IP Monitor running and the call never gets there.

Any thoughts or ideas would be greatly appreciated.
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Thu Sep 20, 2012 8:17 pm    Post subject: Re: SOAP request failure Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany
java.lang.NullPointerException: Some (mandatory) element/field is not set.

The (underlying) Java will throw a null-exception, if an (unchecked, meaning nobody else: e.g. the compiler or toolkit requested/insisted on you to fill it out) empty value is passed, which (implicitly) is mandatory.

Unfortunately Java likely/often isn't kind enough to tell you the name of the property.

Check what might be / is missing and fill it in.
Back to top
View user's profile Send private message
mgk
PostPosted: Thu Sep 20, 2012 11:32 pm    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1647
I'm not sure what is causing the exception, but I do not think it is anything you have done so you should raise a PMR for this. However, as you are using the SOAPRequest node and are building the message yourself you should be using the SOAP parser in this case. The SOAP parser is recomended for use with the SOAP nodes, and simplifies building SOAP messages, and I suspect would not give you the exception you are seeing.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Sep 21, 2012 5:08 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
You will get a null pointer exception if you try to send a SOAP request with a Request-Reply in which the Reply has no return elements. Make sure your WSDL/XSD defines at least one element in the Response message and that it gets populated. A Reply message with no elements causes the SOAPRequest node to error out with an NPE.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP request failure
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.