managed servers are getting thrown out of cluster
recieved the below error messages
<BEA-010026> <Exception occurred during commit of transaction
Caused by: weblogic.transaction.internal.TimedOutException: Transaction has timed out when making request to XAResource
<BEA-000144> <Managed server WLS1D has been suspended or shutdown.>
<BEA-000115> <Lost 2 multicast message(s).>
<BEA-000111> <Adding WLS1D with ID 5716223036452484921S:WLS1:[8371,8371,-1,-1,-1,-1,-1]:CMS:WLS1D to cluster: cmsCluster view.>
<BEA-000128> <Updating 5716223036452484921S:WLS1:[8371,8371,-1,-1,-1,-1,-1]:CMS:WLS1D in the cluster.>
<BEA-000112> <Removing WLS1C jvmid:-943465781735899304S:WLS1:[8271,8271,-1,-1,-1,-1,-1]:CMS:WLS1C from cluster view due to timeout.>
I see that many transactions are being rolled back and those exceptions are causing the memory to get filled frequently, and so the garbage collection takes time causing the multicast messages to miss.
change the value of your JTA in config.xml and restart to check if we still get the same problems.
stop the domain
take backup of config.xml
change <jta>
<timeout-seconds>90</timeout-seconds>
<security-interop-mode>default</security-interop-mode>
</jta>
from 90 to 600 and start the servers.
Fixed
recieved the below error messages
<BEA-010026> <Exception occurred during commit of transaction
Caused by: weblogic.transaction.internal.TimedOutException: Transaction has timed out when making request to XAResource
<BEA-000144> <Managed server WLS1D has been suspended or shutdown.>
<BEA-000115> <Lost 2 multicast message(s).>
<BEA-000111> <Adding WLS1D with ID 5716223036452484921S:WLS1:[8371,8371,-1,-1,-1,-1,-1]:CMS:WLS1D to cluster: cmsCluster view.>
<BEA-000128> <Updating 5716223036452484921S:WLS1:[8371,8371,-1,-1,-1,-1,-1]:CMS:WLS1D in the cluster.>
<BEA-000112> <Removing WLS1C jvmid:-943465781735899304S:WLS1:[8271,8271,-1,-1,-1,-1,-1]:CMS:WLS1C from cluster view due to timeout.>
I see that many transactions are being rolled back and those exceptions are causing the memory to get filled frequently, and so the garbage collection takes time causing the multicast messages to miss.
change the value of your JTA in config.xml and restart to check if we still get the same problems.
stop the domain
take backup of config.xml
change <jta>
<timeout-seconds>90</timeout-seconds>
<security-interop-mode>default</security-interop-mode>
</jta>
from 90 to 600 and start the servers.
Fixed
1 comment:
Hi I do not have th setting specified and i only get the four mesges at every 15 minutes interval
#### <> <> <> <1300113794530>
#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1300113794558>
#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1300113833776>
#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1300113833777>
Post a Comment