| Author |
Message
|
| 2ndjuly |
 Posted: Wed Dec 12, 2012 11:48 am Post subject: HTTPS- SOAPRequest abruptly terminated |
 |
|
Newbie
Joined: 12 Dec 2012
Posts: 5
|
HTTPInput-->compute-->SOAPRequest (HTTPS-SSL)-->compute-->HTTPreply
The thread is abruptly getting terminated aftter the call of SOAP Request. It is not giving any error message.
It is HTTPS URL
I have imported certificate chain into "C:\IBM\MQSI\8.0.0.1\jre16\lib\security\cacerts" and 'C:\IBM\MQSI\8.0.0.1\certificates-carters\MB8BROKER.jks'
more info:
C:\IBM\MQSI\8.0.0.1>mqsireportproperties MB8BROKER -o BrokerRegistry -r
BrokerRegistry
uuid='BrokerRegistry'
brokerKeystoreType='JKS'
brokerKeystoreFile=''
brokerKeystorePass='brokerKeystore::password'
brokerTruststoreType='JKS'
brokerTruststoreFile='C:\IBM\MQSI\8.0.0.1\certificates-carters\MB8BROKER.jks'
brokerTruststorePass='brokerTruststore::changeit'
httpConnectorPortRange=''
httpsConnectorPortRange=''
modeExtensions=''
operationMode='advanced'
shortDesc=''
longDesc='' |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Dec 12, 2012 12:01 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| fatherjack |
| Posted: Wed Dec 12, 2012 12:09 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| Quote: |
The thread is abruptly getting terminated aftter the call of SOAP Request. It is not giving any error message.
|
I doubt it. Have you got your catch terminals wired up so you can 'catch' the exception that is being thrown?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| 2ndjuly |
| Posted: Wed Dec 12, 2012 12:10 pm Post subject: |
|
|
Newbie
Joined: 12 Dec 2012
Posts: 5
|
I have trace node connected to both Failure and Fault terminal of SOAP request. It is still not writting the trace log
File path: C:\temp\11111UserTrace.txt
Pattern: Trace at ${CURRENT_TIMESTAMP} Root=${Root} |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 12, 2012 12:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And when you ran the user trace (as distinct from inserting Trace nodes) the reason it gave for the error was.....?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Wed Dec 12, 2012 12:24 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| Quote: |
I have trace node connected to both Failure and Fault terminal of SOAP request. It is still not writting the trace log
File path: C:\temp\11111UserTrace.txt
Pattern: Trace at ${CURRENT_TIMESTAMP} Root=${Root} |
And even if it was writing the trace log this would tell you what the exception was?
| Quote: |
| And when you ran the user trace (as distinct from inserting Trace nodes) the reason it gave for the error was.....? |
Apparently....
| Quote: |
It is not giving any error message.
|
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 12, 2012 12:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fatherjack wrote: |
Apparently....
| Quote: |
It is not giving any error message.
|
|
My interpretation is that the OP has put some Trace nodes in, does not see anything coming out in the file path specified and has concluded there's no error message.
I would assert that, even if this is the case, running a user trace would be probative in that there could be an error message indicating why the highly implausible scenario of the thread being terminated is coming about. Especially given one important detail the OP doesn't mention setting.
I suspect that the thread is "abruptly terminating" because there's an error, the Trace node is not configured as posted, no output is being produced where the OP is looking because of the configuration error and no error is being logged because the terminals are connected to a flow that worked. All of this would be reported in a user trace including, I suspect, the Trace node output......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| 2ndjuly |
| Posted: Wed Dec 12, 2012 8:33 pm Post subject: |
|
|
Newbie
Joined: 12 Dec 2012
Posts: 5
|
| thanks all. It trace node output was not connected. Issue is closed. |
|
| Back to top |
|
|
|
|
