PeerGoneException

Question

Hi,
We are using weblogic application server ver 5.1. In our application
we are using T3Client.isConnected() to verify wether connection is live
to App server from webserver side. Earlier we were using T3Connection
since it was deprecated, changed it to T3Client. We are getting
reference to Remote factory object and caching in webserver side. If
application is idle for some time, connection is lost to appserver and
Remote referense is no more valid. I am setting
T3Client.DISCONNECT_TIMEOUT_NEVER., why it is dicconnecting?. Is am i
missing something here?Is there is work around for this. See the
following code
private boolean setShipmentFactory(){
boolean connected = true;
try
// Call the application (Tengah) server.
sf = (ShipmentFactory) Naming.lookup( shipmentFactoryAddress );
ScreenHelper.setShipmentFactory(sf);
catch( RemoteException re )
printline( "setShipmentFactory()", "ERROR: RemoteException: " +
re.getMessage() );
catch( NotBoundException nbe )
printline( "setShipmentFactory()", "ERROR: NotBoundException: " +
nbe.getMessage() );
catch( MalformedURLException mURLe )
printline( "setShipmentFactory()", "ERROR: MalformedURLException: "
+ mURLe.getMessage() );
try
String url = "t3://" + ConfigProperties.getProperty( "jwsTENGAHHOST"
t3Client = new T3Client(url);
t3Client.connect();
t3Client.setSoftDisconnectTimeoutMins(T3Client.DISCONNECT_TIMEOUT_NEVER);
t3Client.setHardDisconnectTimeoutMins(T3Client.DISCONNECT_TIMEOUT_NEVER);
connected = t3Client.isConnected();
System.out.println("Connected:"+connected);
// catch( T3Exception t3e )
// printline( "setShipmentFactory()", "ERROR: T3Exception: " +
t3e.getMessage() );
catch( IOException ioe )
printline( "setShipmentFactory()", "ERROR: IOException: " +
ioe.getMessage() );
catch( Exception e )
printline( "setShipmentFactory()", "ERROR: Exception: " +
e.getMessage() );
return connected;
Console StackTrace
weblogic.rjvm.PeerGoneException: no message was received for 240 seconds
at
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
ava:76)
at
fmweb.ntframework.ERWLabelManager_WLStub.getUnitLabelData(ERWLabelMan
ager_WLStub.java:216)
at LabelServlet.importData(LabelServlet.java:186)
at LabelServlet.createReport(LabelServlet.java:104)
at LabelServlet.service(LabelServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRun
ner.java:462)
Thanks&Regards
Venky

Answer 1

Where is the reply? Could not find it on misc group.
thanks,
Edwin
"Wei Guan" <[email protected]> wrote in message
news:[email protected]...
Refer to my reply on misc. Please do not cross-post.
Cheers - Wei
Venkateswaran Karuppanan <[email protected]> wrote in message
news:[email protected]...
Hi,
We are using weblogic application server ver 5.1. In our application
we are using T3Client.isConnected() to verify wether connection is live
to App server from webserver side. Earlier we were using T3Connection
since it was deprecated, changed it to T3Client. We are getting
reference to Remote factory object and caching in webserver side. If
application is idle for some time, connection is lost to appserver and
Remote referense is no more valid. I am setting
T3Client.DISCONNECT_TIMEOUT_NEVER., why it is dicconnecting?. Is am i
missing something here?Is there is work around for this. See the
following code
private boolean setShipmentFactory(){
boolean connected = true;
try
// Call the application (Tengah) server.
sf = (ShipmentFactory) Naming.lookup( shipmentFactoryAddress );
ScreenHelper.setShipmentFactory(sf);
catch( RemoteException re )
printline( "setShipmentFactory()", "ERROR: RemoteException: " +
re.getMessage() );
catch( NotBoundException nbe )
printline( "setShipmentFactory()", "ERROR: NotBoundException: " +
nbe.getMessage() );
catch( MalformedURLException mURLe )
printline( "setShipmentFactory()", "ERROR: MalformedURLException: "
+ mURLe.getMessage() );
try
String url = "t3://" + ConfigProperties.getProperty( "jwsTENGAHHOST"
t3Client = new T3Client(url);
t3Client.connect();
t3Client.setSoftDisconnectTimeoutMins(T3Client.DISCONNECT_TIMEOUT_NEVER);
>>
>>
>>
t3Client.setHardDisconnectTimeoutMins(T3Client.DISCONNECT_TIMEOUT_NEVER);
>>
connected = t3Client.isConnected();
System.out.println("Connected:"+connected);
// catch( T3Exception t3e )
// printline( "setShipmentFactory()", "ERROR: T3Exception: " +
t3e.getMessage() );
catch( IOException ioe )
printline( "setShipmentFactory()", "ERROR: IOException: " +
ioe.getMessage() );
catch( Exception e )
printline( "setShipmentFactory()", "ERROR: Exception: " +
e.getMessage() );
return connected;
Console StackTrace
weblogic.rjvm.PeerGoneException: no message was received for 240 seconds
at
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.j
ava:76)
at
fmweb.ntframework.ERWLabelManager_WLStub.getUnitLabelData(ERWLabelMan
ager_WLStub.java:216)
at LabelServlet.importData(LabelServlet.java:186)
at LabelServlet.createReport(LabelServlet.java:104)
at LabelServlet.service(LabelServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRun
ner.java:462)
Thanks&Regards
Venky