Receive publishing failed email for publishing session that was completed successfully (Doc ID 1547924.1)

Last updated on NOVEMBER 18, 2024

Applies to:

Symptoms

Scheduled publishes send publishing failure messages but on inspection of the publishing history, the publish sessions were successful.

Issue occurs in a cluster environment only.

A publishing session id can be found in multiple cluster members, e.g.:

"

[2013-03-19 10:30:42,959] [logging.cs.xcelerate.publish] In buildSession method of PubSessionManager : PubSession id 1251688888754 is found to be running but the batch host is not found.
[2013-03-19 10:30:42,965] [logging.cs.xcelerate.publish] In buildSession method of PubSessionManager : Verifying again that the PubSession id 1251688888754 is still running before marking it failed
[2013-03-19 10:30:42,965] [logging.cs.xcelerate.publish] In buildSession method of PubSessionManager : After quick check PubSession id 1251688888754 was still found to be runnig so marking it failed
[2013-03-19 10:30:43,083] [logging.cs.xcelerate.publish] Failed session 1251688888754 at java.lang.Exception
       at com.openmarket.xcelerate.publish.SessionTable.failSession(y:1877)
       at com.openmarket.xcelerate.publish.PubSessionManager.failSession(y:748)
       at com.openmarket.xcelerate.publish.PubSessionManager.buildSession(y:1021)
       at com.openmarket.xcelerate.publish.PubSessionManager.getSessions(y:3212)
       at com.openmarket.xcelerate.publish.PubSessionManager.getSessions(y:1473)
       at com.openmarket.xcelerate.publish.PubSessionManager.getActiveSessions(y:2057)
       at com.openmarket.xcelerate.commands.PubSessionManagerDispatcher.GetAllActive(y:3451)
       at sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)

"

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.