Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HTTP Tunneling - detecting transport failure in weblogic.rjvm.http.HTTPClientJVMConnection

96 views
Skip to first unread message

Anthony warden

unread,
Jan 17, 2002, 8:38:30 AM1/17/02
to

I've been using JMS via HTTP tunneling in WLS6.1.

To examine the resillience of the setup, I interjected a proxy between JMS Client
(which is the weblogic example 'QueueReceive') and the WLServer.

If I break the link by killing my proxy, I get the trace attached at the botom
on standard out.

I have tried enclosing the whole example in a try catch - and get no exception
when the link is broken.

Please tell me:

1)How to configure the clint HTTP tunneling to set options for auto re-connect.
(does WL 6.1 have the concept of resillience in HTTP tunneling?)

or

2)How to best detect this kind of failure and re-establish the link.


I hope the BEA JMS implementation w.r.t. HTTP tunneling is enterprise grade and
I don't have to buy a specialist JMS like SonicMQ to get basic durability features........

<Jan 17, 2002 12:19:34 PM GMT> <Warning> <HttpClient> <Couldn't open connection
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpURLConnection.getHttpClient(HttpURLConnection.java:119)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:311)
at weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:390)
at weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConnection.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Jan 17, 2002 12:19:35 PM GMT> <Error> <HTTPClientJVMConnection> <
java.net.ConnectException: Tried all: '1' addresses, but could not connect over
HTTP to server: 'lonwebhost18.lehman.com', port: '8522'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpURLConnection.getHttpClient(HttpURLConnection.java:119)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:311)
at weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:390)
at weblogic.rjvm.http.HTTPClientJVMConnection.execute(HTTPClientJVMConnection.java:296)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Zach

unread,
Jan 17, 2002, 9:29:24 AM1/17/02
to
JMS throws an exception when you make an actual call using the connection
(or its sessions, producers, consumers, ...). If you want an asynchronous
notification of a problem with the connection, then you must set up an
ExceptionListener for the connection.

_sjz.

"Anthony warden" <awa...@lehman.com> wrote in message
news:3c46d3d6$1...@newsgroups.bea.com...

0 new messages