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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Using Document form varable results in failed unmarshalling message


Level 5


  I'm on LiveCycle ES 8.2. For PDF submit forms from workspace, I assigned the servername for submit as URL:


We are using Document Form variable for this process. The reason is the forms will be digitally signed at each stage and we dont want to loose their signatures if forms go next stage.

This works perfect when I submit the form.

Now, we will be moving all the existing instances to new server and I want this URL to be server independent.

I take off this URL and kept it blank and try to submit from workspace. Nothing happens if I click submit and the form stays at the same place.

I see the following error in the log file:

2012-03-29 15:07:17,541 ERROR [org.jgroups.protocols.UDP] failed unmarshalling message

          at Source)

          at org.jgroups.Message.readFrom(

          at org.jgroups.protocols.TP.bufferToMessage(

          at org.jgroups.protocols.TP.handleIncomingPacket(

          at org.jgroups.protocols.TP.access$400(

          at org.jgroups.protocols.TP$

          at Source)

I have to avoid using this URL in the form as I will be moving my system to new domain & DNS and for any existing process instances, if they try to submit the form, that will error out as the URL is pointing to another server.

Your help is highly appreciated.



3 Replies


Level 6

Is this form served from LiveCycle or a static form? If served from LiveCycle, try adding the Form Bridge to your form and not setting the URL at all.


Level 5


  It's served from LiveCycle. Form Bridge already exists for the form which runs good when we are in 8.2. Problem occurs only on ES2.

Is it a must to include the URL for forms rendered with Document form variables?


Level 6

I don't think I read your first post thoroughly. I see now you are setting the URL to prevent the form from appearing altered. I don't use digital signatures, but can see the potential problem. My first thought was to put JavaScript in the form to set the URL, but that would likely cause the same problem. I probably can't be of much help with no experience using the digital signatures. Our forms are considered 'Signed' if a logged in user clicks approve. Have you deleted the Form Bridge and readded? There may be differences with the one in ES2.

I think you are also saying you can't set the URL server side before rendering the form because processes will launch under one domain then get changed later.

If you were able to use JavaScript to determine which URL to submit to, you could put that code in the Form Bridge code and I would think that would submit. The form is not being altered by the code. This is assuming the code snippet I copied out of the form bridge is really what is called.

/** Invoke the standard Submit action */

function submitAction(doc, url, type) {

    if ( BRIDGE_SUBMIT_URL  != null ) url  = BRIDGE_SUBMIT_URL;

    if ( BRIDGE_SUBMIT_TYPE != null ) type = BRIDGE_SUBMIT_TYPE;

    if ( type == null ) type = "PDF";

    if (url != null) {

        setFocus(null);  // force current field focus out in 8.1 + readers (null op in previous versions)

//      doc.submitForm({cURL: url, bEmpty: true, cSubmitAs: type, cCharset: "utf-8"});   

        doc.submitForm({cURL: url, cSubmitAs: type});