|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
SOAPInput node with Apache Server |
« View previous topic :: View next topic » |
Author |
Message
|
vishBroker |
Posted: Fri Sep 09, 2016 9:58 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010 Posts: 135
|
Could you run this command and check the details for the URI you are hitting?
C:\Program Files\IBM\IIB\10.0.0.5>mqsireportproperties nodeName -e default -o HTTPConnector -r
deecee wrote: |
..
Quote: |
A quick way is to have a dummy flow - just to rule out network issue. |
Can you explain what you mean by this? |
I was thinking, you could just create a sample IntegrationService and deploy it.
But on a second thought - your flow, as you mentioned is simple one as well.
Anyhow,
could you do following -
1. As HTTPInput node flow is successful - capture the HTTP headers that are being sent to the IIB. - you can do it in debug mode.
2. Inspect/share the HTTP headers
I am guessing...there is some problematic HTTP header that SOAP node is rejecting. |
|
Back to top |
|
 |
deecee |
Posted: Mon Sep 12, 2016 12:24 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2014 Posts: 51
|
Hi,
Values from mqsireportproperties
Quote: |
HTTPConnector
uuid='HTTPConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='0'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
Connector
port='7080'
type='Broker'
URLRegistration
url='/PROXYSERVLET'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
flowLabel='soap'
BIP8071I: Successful command completion. |
values of the HTTP headers taken from debug:
Quote: |
HTTPInputHeader
accept-encoding:CHARACTER:gzip,deflate
content-type:CHARACTER:application/xml
content-length:CHARACTER:5280
host:CHARACTER:localhost:8080
connection:CHARACTER:Keep-Alive
user-agent:CHARACTER:Apache-HttpClient/4.1.1 (java 1.5)
X-WBIMB-Servlet-Remote-Host:CHARACTER:127.0.0.1
X-Remote-Addr:CHARACTER:127.0.0.1
X-Remote-Host:CHARACTER:127.0.0.1
X-Server-Name:CHARACTER:localhost
X-Server-Port:CHARACTER:8080
X-Scheme:CHARACTER:http
X-Original-HTTP-Command:CHARACTER:POST http://localhost:8080/PROXYSERVLET HTTP/1.1 |
|
|
Back to top |
|
 |
vishBroker |
Posted: Mon Sep 12, 2016 7:38 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010 Posts: 135
|
I guess, This is the header when you are hitting HTTP input node.
Can you compare this against the HTTP header when you are hitting SOAP input node.
On a side note -
1. If possible, create a new flow where you are listening on embedded port and not on the broker port.
2. See - whether it is working as expected.
Can you share the Apache logs and userTrace on IIB.
From your apache log -which you shared in first post - it seems, you are doing some MQ operations. Is that related to your SOAP input node flow? |
|
Back to top |
|
 |
deecee |
Posted: Wed Sep 14, 2016 2:36 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2014 Posts: 51
|
This is the HTTP header when I hit the SOAPNode directly, there seem to be last two lines added. But everything else looks the same.
Quote: |
HTTPInputHeader
X-Original-HTTP-Command:CHARACTER:POST http://localhost:7080/PROXYSERVLET HTTP/1.1
Accept-Encoding:CHARACTER:gzip,deflate
Content-Type:CHARACTER:application/xml
Content-Length:CHARACTER:5280
Host:CHARACTER:localhost:7080
Connection:CHARACTER:Keep-Alive
User-Agent:CHARACTER:Apache-HttpClient/4.1.1 (java 1.5)
X-Remote-Addr:CHARACTER:127.0.0.1
X-Remote-Host:CHARACTER:127.0.0.1
X-Server-Name:CHARACTER:localhost
X-Server-Port:CHARACTER:7080
X-Scheme:CHARACTER:http
X-Server-Name:CHARACTER:localhost
X-Server-Port:CHARACTER:7080 |
Apache log is what i shared, the MQ is the apache server trying to connect with the IIB flows using the system queues.
The user trace gives the same error of stringoutofboundexception which i pasted earlier and this MQ error similar to apache logs
Quote: |
BIP2657I: MQGetNode ''MQ'' has completed its MQGET() call. The returned MQ codes are: MQCC=2, MQRC=2033.
MQGetNode ''MQ'' has made 0 attempt(s) at calling MQGET() to read queue ''SYSTEM.BROKER.WS.INPUT'' of queue manager ''BROKERQM''. The last call returned with MQ completion code 2 and reason code 2033 |
|
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Sep 14, 2016 2:50 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Is the flow timing out?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|
|
|
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
|
|
|
|