Hi All,
Application team is getting below error and they wanted to check if there is an issue from the database end.
We didn't find anything from the database end. Nothing in the sql errorlogs nor we see any blocking.
Is it really a database error or generic error? did anyone come across this error? how to go about troubleshooting such issues to narrow down if it is SQL server issue or any app server issue?
org.activebpel.rt.bpel.AeBusinessProcessException
at org.activebpel.rt.bpel.server.engine.AePersistentProcessManager.createBusinessProcess(AePersistentProcessManager.java:280)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:388)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.setAutoCommit(SQLServerConnection.java:1883)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:906)
at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1923)
at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:452)
... 32 more
Thanks,
Sam
June 27, 2024 at 8:38 pm
just trying to understand if these turn out to be real database issue or app server issue which might throw a generic issue.
how to narrow down such issues?
Is this a web app? HTTP 500 is strange - https://blog.hubspot.com/marketing/http-500-internal-server-error
Ultimately, you need some tracing of what's happening. This might be in the app, with some sort of tool that traces through code, or you just log out each step. Your app ought to have logging, and at different levels, so you can get deep logging of everything.
With the db, I'd need to go back and look at my monitoring when this returned and try to determine what was happening.
June 27, 2024 at 10:14 pm
Is this a web app? HTTP 500 is strange - https://blog.hubspot.com/marketing/http-500-internal-server-error
Ultimately, you need some tracing of what's happening. This might be in the app, with some sort of tool that traces through code, or you just log out each step. Your app ought to have logging, and at different levels, so you can get deep logging of everything.
With the db, I'd need to go back and look at my monitoring when this returned and try to determine what was happening.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply