Error when attempting to Publish On Albpm Projects From Ant Scripts.

(Doc ID 1086168.1)

Last updated on JULY 06, 2012

Applies to:

Oracle Business Process Management Suite - Version 6.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jul-2012***

Symptoms

The following error occurs when the ant task attempts to notify the engine when running the publish Ant task with a J2EE engine.

[fuego:publish] Could not notify deployment changes to engine 'xxxxxxxxxxxxxxxx'. Engine seems to be stopped. [notification:type='4', processId='/xxxxxxxxxxxx#Default-1.1']
[fuego:publish] Details :
[fuego:publish] fuego.papi.impl.EngineNotAvailableException: Cannot reach engine 'xxxxxxxxxxx' at URL: 'null'.
[fuego:publish] Cannot reach engine 'xxxxxxxxxxx' at URL: 'null'.
[fuego:publish] Caused by: java.io.IOException
[fuego:publish] Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
[fuego:publish] java.io.StreamCorruptedException: invalid type code: 31]
[fuego:publish] Caused by: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
[fuego:publish] java.io.StreamCorruptedException: invalid type code: 31
[fuego:publish] Caused by: invalid type code: 31
[fuego:publish]

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms