Q: Where does the 5000ms timeout come from when I get “process(Lweblogic.cluster.messaging.internal.ClusterMessage;) timed out after: 5000ms..”?


And we said:

The 5000ms is the currently default value for DatabaseLessLeasingBasisMBean.MessageDeliveryTimeout mbean propety.

This is the stack trace generated by a weblogic managed server leader in a cluster defined with consensus migration in wich another cluster node probably died (or was very busy):

Apr 25, 2016 10:47:42 AM CEST> <Warning> <RJVM> <BEA-000573> <RequestTimeout for 
message id 71,049 with message: RJVM response from 'weblogic.rjvm.RJVMImpl@4d7a17a8 
- id: '2862061204926831748S:172.16.78.135:[7003,-1,-1,-1,-1,-1,-1]:PRENOMAD:
prenomad2' connect time: 'Mon Apr 25 09:30:02 CEST 2016'' for 'process
(Lweblogic.cluster.messaging.internal.ClusterMessage;)' timed out after: 5000ms..> 
 weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception 
 at weblogic.cluster.messaging.internal.RMIClusterMessageEndPointImpl_12130_WLStub.
process(Unknown Source) 
 at weblogic.cluster.messaging.internal.RMIClusterMessageSenderImpl.send
(RMIClusterMessageSenderImpl.java:115) 
 at weblogic.cluster.messaging.internal.RMIClusterMessageSenderImpl.send
(RMIClusterMessageSenderImpl.java:93) 
 at weblogic.cluster.messaging.internal.RMIClusterMessageSenderImpl.send
(RMIClusterMessageSenderImpl.java:88) 
 at weblogic.cluster.messaging.internal.ClusterMessageSenderWrapper.send
(ClusterMessageSenderWrapper.java:56) 
 at weblogic.cluster.leasing.databaseless.ServerFailureDetectorImpl$PingTimer.
timerExpired(ServerFailureDetectorImpl.java:309) 
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:304) 
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run
(SelfTuningWorkManagerImpl.java:548) 
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) 
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) 
 Caused by: weblogic.rmi.extensions.RequestTimeoutException: RJVM response from 
'weblogic.rjvm.RJVMImpl@4d7a17a8 - id: '2862061204926831748S:172.16.78.135:
[7003,-1,-1,-1,-1,-1,-1]:PRENOMAD:prenomad2' connect time: 'Mon Apr 25 09:30:02 
CEST2016'' for 'process(Lweblogic.cluster.messaging.internal.ClusterMessage;)' 
timed out after: 5000ms. 
 at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:255) 
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:304) 
 ... 10 more

Enjoy 😉

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.