Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Who Me Too'd this topic

Not applicable

hey guys,

Not sure if any one of you have similar experience. We are running Livecyle.ES 8.2.1 and so far we use this for signing PDF files only for a government agency.We use EJB endpoint.

Our application is a custom webapp which use Livecycle Java AIP. The problem we see is on and off, we see this exception during sign PDF.

2009-04-04 10:37:50,420 ERROR [STDERR] Apr 4, 2009 10:37:50 AM com.adobe.idp.DocumentManagerClient requestRemotePassivation
SEVERE: DOCS001: Unexpected exception. See the stack trace for details.
org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
    at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectionAbort(ORBUtilSystemException.java:2372)

And this error is raised from,

com.adobe.idp.DocumentError: org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 completed: Maybe
    at com.adobe.idp.DocumentManagerClient.requestRemotePassivation(DocumentManagerClient.java:329)
    at com.adobe.idp.Document.passivate(Document.java:1069)
    at com.adobe.idp.Document.passivate(Document.java:1012)
    at com.adobe.idp.Document.getInputStream(Document.java:1524)


The interesting this about this error is, documents get signed before and after this error, are just fine. This problem used to last about 1 minute and gone. And this happens only in our PROD env . I dont see this in my DEV or TEST. The tricky thing is, in PROD, we connect to a hardware signature profile, rather than a normal scenario, not sure if related.

My guessing is that the document do get signed on the server side, and then somehow when client request it, it is gone or something.

Well, i am stomped. Really appreciate if anyone of you can share some insight.

Thanks.

-ying

Who Me Too'd this topic