Thread "WebContainer : 33" (00000195) has been active for 729801 milliseconds and may be hung.  There is/are 20 thread(s) in total in the server that may be hung.

              at java.net.SocketInputStream.socketRead0(Native Method)

Transaction (Process ID 124) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[3/30/20 9:01:02:605 EDT] 00002eeb SystemErr     R        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

• Are you using any IID sourced parts in your solution, or is this all BPMN models?  
• Have you checked the code for the existence of Multi-Instance Loops?  
• Have you checked the Event Manger to see if there is a backlog there (which will be an indicator of the MIL problem)?
• Does this happen at a regular time each day, or randomly?
• What else is the system doing before this occurs?  Have you checked for resource leaks etc?

Thread "WebContainer : 33" (00000195) has been active for 729801 milliseconds and may be hung.  There is/are 20 thread(s) in total in the server that may be hung.

              at java.net.SocketInputStream.socketRead0(Native Method)

Transaction (Process ID 124) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[3/30/20 9:01:02:605 EDT] 00002eeb SystemErr     R        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

Thread "WebContainer : 33" (00000195) has been active for 729801 milliseconds and may be hung.  There is/are 20 thread(s) in total in the server that may be hung.

              at java.net.SocketInputStream.socketRead0(Native Method)

Transaction (Process ID 124) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[3/30/20 9:01:02:605 EDT] 00002eeb SystemErr     R        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)

Hi Rameshkumar,

There is a good description of java.net.SocketInputStream.socketRead0 in this article https://dzone.com/articles/threads-stuck-in-javanetsocketinputstreamsocketrea. But basically BPM is waiting for a reply from an external source, mostly likely in my experience a web services call or a database call. Some years ago when I was heavily involved in BPM we did from time to time experience DB locking issues. With help from the DBAs we could get logs and traces from DB2 and diagnose the problem. From the second part of the message you posted it looks like you may have a database issue. My suggestion would be to work with the DBAs to see if they cannot throw some light on the issue. No real experience with SQLServer so cannot be more helpful. There are also some BPM specific traces that can be enabled in WebSphere which may also give insight on the issue. Unfortunately I cannot provide more help at this stage as my focus for the last couple of years has been anything other than BPM.

Thread "WebContainer : 33" (00000195) has been active for 729801 milliseconds and may be hung.  There is/are 20 thread(s) in total in the server that may be hung.

              at java.net.SocketInputStream.socketRead0(Native Method)

Transaction (Process ID 124) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

[3/30/20 9:01:02:605 EDT] 00002eeb SystemErr     R        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)