Last updated on JUNE 29, 2017
Applies to:Oracle WebCenter Sites - Version 7.6.2 and later
Information in this document applies to any platform.
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 sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms