| Author |
Message
|
| ardi |
 Posted: Mon Dec 05, 2016 3:35 am Post subject: IIB 10 - SOAPRequest node cant handle larger CDATA |
 |
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
Hi,
I have some issue with SOAPRequest node, my goal is a put some soap request to backend system with SOAP XML request embed with CDATA XML.
While i testing with larger XML embed with CDATA(Content:length = 68222 and size 61KB) request it throws error. The success request only happen when CDATA is smaller in length and size.
Update:
- Found that testing with SOAPUI working.
- SOAPRequest node is now suspect for cannot handle the larger length.
- set the maxPostSize to 2MB seems doesnt work.
Have anyone encounter with this error. Thanks.
| Code: |
(CHARACTER)
)
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'F:\build\S1000_slot1\S1000_P\src\WebServices\WSLibrary\ImbWSRequest.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 470 (INTEGER)
(0x03000000:NameValue):Function = 'ImbWSRequest::makeWSRequest' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 3152 (INTEGER)
(0x03000000:NameValue):Text = 'A Web Service request has detected a SOCKET error whilst invoking a web service located at host &1, on port &2, on path &3.' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'dev-sungl621' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 2 (INTEGER)
(0x03000000:NameValue):Text = '8080' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = '/connect/soap/ComponentExecutor' (CHARACTER)
)
(0x01000000:Name ):SocketTimeoutException = (
(0x03000000:NameValue):File = 'F:\build\S1000_slot1\S1000_P\src\CommonServices\ImbBasicSocket.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 938 (INTEGER)
(0x03000000:NameValue):Function = 'ImbBasicSocket::sendTimeout' (CHARACTER)
(0x03000000:NameValue):Type = '' (CHARACTER)
(0x03000000:NameValue):Name = '' (CHARACTER)
(0x03000000:NameValue):Label = '' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPmsgs' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 3150 (INTEGER)
(0x03000000:NameValue):Text = 'An occurred whilst performing a socket operation' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = '::send' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 2 (INTEGER)
(0x03000000:NameValue):Text = '0' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'An established connection was aborted by the software in your host machine.
' (CHARACTER)
)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 2 (INTEGER)
(0x03000000:NameValue):Text = '119990' (CHARACTER)
)
)
)
)
)
)
)
|
_________________
Indonesian WMQ & WMB User |
|
| Back to top |
|
 |
| ardi |
| Posted: Mon Dec 05, 2016 10:23 am Post subject: |
|
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
Update :
- Using compression deflate seems working, but i cannot get the SOAP response body.
_________________
Indonesian WMQ & WMB User |
|
| Back to top |
|
|
| timber |
| Posted: Mon Dec 05, 2016 3:04 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| SOAPRequest node is now suspect for cannot handle the larger length. |
The SOAPRequest node does have a maximum size that it can handle. For most users, that max size will be a *lot* larger than 61Kb. I don't know what setting you need to change to fix this, but somebody else might know.
Have you taken a user trace (using command-line programs mqsichangetrace, mqsireadlog, mqsiformatlog) to see whether there are other errors happening at the same time? |
|
| Back to top |
|
|
| ardi |
| Posted: Mon Dec 05, 2016 9:12 pm Post subject: |
|
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
Update the user trace :
| Code: |
2016-12-06 11:47:35.904076 4036 UserTrace BIP3633I: Node 'SF_Transform_JI_to_SUN_Rq.Post Journal' sending HTTP data to URL '/connect/soap/ComponentExecutor' at host 'dev-sungl621' (port 8080).
The integration node is sending data via HTTP to a remote server at host 'dev-sungl621' (port 8080) using URL '/connect/soap/ComponentExecutor'. See subsequent messages for success or failure messages relating to this request.
No action required.
2016-12-06 11:47:35.906012 4036 UserTrace BIP2231E: Error detected whilst processing a message in node 'Request.JI_SUNGL_Rq.SF_Transform_JI_to_SUN_Rq.Post Journal'.
The integration node detected an error whilst processing a message in node 'Request.JI_SUNGL_Rq.SF_Transform_JI_to_SUN_Rq.Post Journal'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2016-12-06 11:47:35.906048 4036 RecoverableException BIP3754E: The SOAP Request Node or SOAP Async Request Node Request.JI_SUNGL_Rq.SF_Transform_JI_to_SUN_Rq.Post Journal encountered an error while processing the outbound SOAP request.
An error occurred while processing the SOAP Request.
See previous error messages for an indication to the cause of the errors.
2016-12-06 11:47:35.906680 4036 RecoverableException BIP3162S: An HTTP error occurred. The HTTP Request-Line was: ''POST /connect/soap/ComponentExecutor HTTP/1.1 |
| Code: |
The HTTP Reply Header bitstream (if any) received from the server was: ''''. The HTTP Reply Message Body bitstream (if any) received from the server was: ''''. Ensure that the HTTP data is valid.
See the following messages for information pertaining to this error.
2016-12-06 11:47:35.906708 4036 RecoverableException BIP3152S: Socket error detected whilst invoking Web service located at host 'dev-sungl621', port 8080, path '/connect/soap/ComponentExecutor'.
This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number.
Check that the hostname and port number are valid, and point to a functioning Web service.
2016-12-06 11:47:35.906712 4036 SocketTimeoutException BIP3150S: A socket error occurred. Operation: '::send'. Error Code: 0. Error Text: 'An established connection was aborted by the software in your host machine.
'.
An error occurred whilst performing a TCP/IP socket operation. This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname or port number.
See the following messages for information pertaining to this error.
|
Again, we tested with simple message below 60Kb its works.
_________________
Indonesian WMQ & WMB User |
|
| Back to top |
|
|
| ardi |
| Posted: Tue Dec 06, 2016 4:43 am Post subject: |
|
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
Update :
Error only happen in Windows Environment, deploy msgflow to Linux works like magic
_________________
Indonesian WMQ & WMB User |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 06, 2016 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ardi wrote: |
Update :
Error only happen in Windows Environment, deploy msgflow to Linux works like magic |
Windoze claims another victim....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| timber |
| Posted: Tue Dec 06, 2016 7:14 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| Error only happen in Windows Environment, deploy msgflow to Linux works like magic |
As I suspected. This is probably not an IIB restriction, but an environment config issue. |
|
| Back to top |
|
|
|
|
