I am using jboss 4, Diameter Client and I have 8 Diameter Servers connected, with 4 as Active and 4 as Backup, so whenever there is a connection reset done on DIameter Server then the Thread keeps on waiting, here the complete flow
- In Diameter Client we are establishing all the Active and Backup connections to all four sites while starting the JBOSS.
- From Diameter Client we are sending the CCR to Diameter Server using the below logic
a. Diameter Client will send the AVP messages with a event listener object on Diameter Stack
b. Then event listener object will wait for response from diameter server.
c. Once diameter client receives the response, event listener object will be notified to release the wait lock.
d. Then the event listener will send the response to Charging Manager and the process flows.
3. In this above logic we are able identify some abnormal scenarios as follows.
a) Diameter Client will send the AVP messages with a event listener object on Diameter Stack.
b) Then event listener object will wait for response from diameter server.
c) Diameter Client got disconnected due to RESET command sent from Diameter Server.
d) Diameter Client resend the same request to Backup server for charging.
e) Now previously created event listener object are in WAITING state and are not cleared from JBOSS.
f) This kind of scenario keeps on following and the WAITNG state keeps on growing in JBOSS. At one point of time JBOSS was not able to handle the huge load and starts responding slowly.
But here as the number of Threads increases in WAITING block RMI suddenly crashes without stopping the Jboss, so can you please help in resolving this issue, since we are unable to see the Traps comming since Jboss is not down only RMI is down.
Kindly respond ASAP.