MQSeries.net :: View topic - MQ Internet Passthrough (MQIPT ) Not able to communicate ove

madhurd · Posted: Wed Apr 24, 2002 9:07 pm Post subject:

Hi

I have observed that MQIPT(s) work fine in a scenario wherein
it ( they ) have to communicate to a MQ server or MQIPT directly .
The moment a proxy server is introduced in between it refuses to work

I have however successfully tested and made MQIPT to work over an HTTP
proxy as well as Socks Proxy ( AnalogX Proxy ) (http://www.analogx.com)

However I have been facing a problem using MS Proxy and other Proxy servers
for the same configuration .

Is there a published list of Supported Proxy servers for MQIPT ?
Has any of you guys managed to make MQIPT to work over a HTTP proxy ?

after analyzing the tracefiles I have noticed the following errors in
case of MS proxy 2 on NT 4

Time: 2002.04.11 17:19:58.923
Class: com.ibm.mq.ipt.ConnectionThread
Method: getHTTPHeader
Thread ID: ConnThd for Route 1414-4
Logger: TraceLogger 1414
/1.0 501 Not Supported
Content-Type: text/html

Time: 2002.04.11 17:19:58.923
Class: com.ibm.mq.ipt.ConnectionThread
Method: responderToCaller
Thread ID: ConnThd for Route 1414-4
Logger: TraceLogger 1414
Received HTTP non-chunking

---> com.ibm.mq.ipt.ConnectionThread.readTshEyecatcher (ConnThd for
Route 1414-4) 2002.04.11 17:19:58.923

Time: 2002.04.11 17:19:58.923
Class: com.ibm.mq.ipt.ConnectionThread
Method: validateTSHEyecatcher
Thread ID: ConnThd for Route 1414-4
Logger: TraceLogger 1414
Unknown eyecatcher received: 3c626f64

In the above example I have used HTTP chunking for two MQIPTs to talk
to each other over a MS proxy Link .

In the meantime I also did the similar test on Winproxy HTTP proxy
and found it to gave exactly the same error .

If it helps , I have analyzed and observed that in case of ANALOGX
Http proxy server , which is working fine with MQIPT
over HTTP link ,we have got the following entries 9 times during
one transaction , unlike MS proxy which has given only 1 such entry
during a MQ transaction

Time: 2002.04.11 14:58:03.368
Class: com.ibm.mq.ipt.ConnectionThread
Method: getHTTPHeader
Thread ID: ConnThd for Route 1414-4
Logger: TraceLogger 1414
/1.1 200 OK
Date: Thu, 11 Apr 2002 09:23:35 GMT
Connection: Keep-Alive
Proxy-Connection: Keep-Alive
Cache-Control: no-cache, no-transform
Server: MQSeries internet pass-thru
Content-Type: application/octet-stream
Content-Length: 44

I also get the following Traces in case of MS Proxy

Time: 2002.04.11 14:59:19.477 Class:
com.ibm.mq.ipt.ConnectionThread Method: responderToCaller Thread ID:
ConnThd for Route 1414-4 Logger: TraceLogger 1414 Waiting for next
message from responder... Time: 2002.04.11 15:04:12.008 Class:
com.ibm.mq.ipt.ThreadManager Method: run Thread ID: Vulture Logger:
TraceLogger 1414 Vulture thread looking for carcasses... Time:
2002.04.11 15:09:12.019 Class: com.ibm.mq.ipt.ThreadManager Method:
run Thread ID: Vulture Logger: TraceLogger 1414 Vulture thread
looking for carcasses...

The wierd( Funny ) "vulture thread looking for carcasses..." entry is
not present in the trace incase of ANALOGX proxy

Any help or suggestion would be highly appreciated

thanks
Madhur D'silva