Error in Server log

, ,
1

Hi All,

am using wM8.0 version, today am getting below error in server log

[900]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[899]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[898]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[897]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[896]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[895]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[894]2010-04-19 12:22:13 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows
[893]2010-04-19 12:22:13 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[892]2010-04-19 12:22:13 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[891]2010-04-19 12:22:12 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows
[890]2010-04-19 12:22:12 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[889]2010-04-19 12:22:12 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[888]2010-04-19 12:22:11 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[887]2010-04-19 12:22:11 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[886]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[885]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[884]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[883]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[882]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[881]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[880]2010-04-19 12:22:06 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[879]2010-04-19 12:22:06 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[878]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[877]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[876]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[875]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[874]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[873]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[872]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[871]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[870]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[869]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[868]2010-04-19 12:22:01 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows
[867]2010-04-19 12:22:01 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
[866]2010-04-19 12:22:01 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.

Regards,
Anil Kumar E

2

Did you have a DB outage?

Thats a problem with JDBC thread pool, I would contact support for that one.

3

Hi Anil,

I am seeing the same exact error. Were you able to find a resolution for this?

Thanks,
Tiff

4

Hi Anil/Tiff,

Did either of you find a resolution to this problem? I have this same problem, except we’re using Oracle… same exact errors though.

Thanks,
Ryan

5

Ryan,

No, i haven’t been able to find a firm solution for this issue yet. Right now, the only solution is to restart Integration Server. It maybe a bug for webMethods 8.0 version, unless someone know of a solution where we don’t need to restart Integration Server, everytime the database is shutdown and restart.

6

I was told this would be fixed in IS_8.0_SP1_Core_Fix5.

What to do meanwhile?

1- Restart IS any time you get the error.
2- Contact support and ask for the temp fix, if you are lucky :smiley:
3- Wait for the final fix. (When will be public available? should be by the end of this month).

Regards.

7

Thank you!

8

Hi,

The latest fixes for IS_8.0_SP1_Core_Fix is up to Fix 3 dated on 12 May 2010 according to the Empower product fix page. The Fix will resolve the issues as followed:

WDP-964
Removing inner classes from a Java service does not delete the class files.
When saving a Java service that contains inner, Developer generates a class file for the inner classes. When the inner class is removed from the Java service and the Java service is then saved, Developer should delete the class file that corresponds to the inner class from the file system, but does not.

Resolved

PIE-14370
Integration Server throws a NullPointerException when executing a flow service for which results are cached.

If Integration Server caches results for a flow service and the cache expires, Integration Server throws a NullPointerException while attempting to write to the cache.

This issue is now resolved. Integration Server no longer throws a NullPointerException when attempting to write to the cache.

Note: This update contains server files required for enhancement
PIE-14370, which is contained in IS_8.0_SP1_CL_Fix3.
For more information about this enhancement, see the readme for
IS_8.0_SP1_CL_Fix3(or the readme for the latest fix that
supersedes IS_8.0_SP1_CL_Fix3).

PIE-14187
SOAP fault does not contain fault details when provider Web service descriptor was created from WSDL document.

When invoking a service in a WSDL first provider Web service descriptor results in a SOAP fault, Integration Server returns a SOAP response containing a SOAP fault that is missing fault details.

This issue is now resolved. Integration Server now includes the fault details in the SOAP fault.

PIE-14683
After applying the IS_7.1.2_WebSvcsXML_Fix12 fix, the pub.soap.handler:removeHeaderElement service returns a SOAP fault that contains a ClassCastException.

Prior to installing IS_7.1.2_WebSvcsXML_Fix12, the pub.soap.handler:removeHeaderElement service executed successfully. After installing IS_7.1.2_WebSvcsXML_Fix12 , the service returns a SOAP fault that contains the following erroneous exception in the fault detail:

java.lang.ClassCastException: com.wm.lang.xml.TextNode

This issue is now resolved.

PIE-14581
Security log contains messages stating that the Process Engine JDBC connection pool alias has been modified even though it has not been modified.

Integration Server intermittently writes an extraneous message to the error log indicating that the JDBC connection pool alias for Process Engine has been modified. The message is similar to this:

local/Administrator JDBC POOLS Modified JDBC Connection pool alias ProcessEngine.

Integration Server no longer writes this extraneous message to the security log.

PIE-14792
Services that require a Session ID throw an error when they are resubmitted from My webMethods Server.

Sometimes SAP adapter services throw the error "[SAP.103.9110] WmSAP Adapter: No session ID given, cannot release locked connection " when the service is resubmitted from My webMethods Server. This problem can occur for any service that requires a valid Session ID. The same service runs without problems when invoked directly from Developer.

This problem is resolved. Integration Server always provides a valid session ID for all services during resubmission.

PIE-13932
Integration Server not deleting expired tasks.

Integration Server is not deleting scheduled tasks that have expired. Instead, the tasks remain listed on the Server > Scheduler screen. The tasks are eventually deleted when Integration Server is restarted.

This issue is resolved. In addition, a new configuration parameter, watt.server.scheduler.deleteCompletedTasks, has been added.

watt.server.scheduler.deleteCompletedTasks
Specifies whether or not scheduled tasks that have expired should be automatically deleted. By default (true) Integration Server deletes expired tasks. If you do not want Integration Server to delete expired tasks until the next server restart, set this parameter to false.

PIE-13941
Integration Server throws a NullPointerException when creating a SOAP response.

If the output signature of an IS service acting as a Web service contains a document list and a child element in the document list contains an invalid QName, Integration Server throws a NullPointerException when attempting to encode the SOAP response.

Now, Integration Server encodes an invalid QName in document list correctly.

PIE-13722
The service pub.soap.handler:getSOAPMessage fails when the incoming SOAP message contains Latin script characters.

When the incoming SOAP message contains Latin script characters (for example Spanish accented characters), then invoking pub.soap.handler:getSOAPMessage results in a SOAPException “[ISS.0088.9155] this SOAPMessage does not contain a valid Envelope object.”

This issue is resolved. Integration Server now handles the Spanish characters correctly and no exception is thrown.

Please refer to the readme file of the fix.

Thanks

Best Regards,
William

9

Anil/Tiff,

Not sure if you’re aware, but I received the following news from Software AG regarding this problem…

This issue has been identified and a fix will be available soon. The fix that will contain the solution is IS_8.0_SP1_Core_Fix5.

This fix has been built and should be available in the next week or two.

:slight_smile:

10

Yes, i did. Thank you!

11

hmm, I thought we are not allowed to post anything licensed (documentation or fixes or fix readmes) in this forum!

Cheers,
Akshith

12

sorry for late reply, i have updated my environment with IS_8.0_SP1_Core_Fix5 in wM8SP1, got resolved.

13

Hi,
We’ve have patch IS_8.0_SP1_Core_Fix18 installed and we are still getting the same error:

“2012-04-26 08:18:50 EST [CommonLib.MWS.0002W] DB Server disconnected. Will try to reconnect
[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.java.sql.SQLException: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.”

The strange thing is that this happens at roughly the same time every day, and only once or twice a day.

14

Hi,
We’ve have patch IS_8.0_SP1_Core_Fix18 installed and we are still getting the same error:

“2012-04-26 08:18:50 EST [CommonLib.MWS.0002W] DB Server disconnected. Will try to reconnect
[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.java.sql.SQLException: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.”

The strange thing is that this happens at roughly the same time every day, and only once or twice a day.

15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.