Error sending messages after upgrade to version 4.1.0

[umuser2020]

Hi,

I have upgraded from OpenAS2 v2.14 to v4.1.0, managed to migrate all configurations and partnership configurations without much problems and it is working without any issues communicating with four partners but I still couldn't manage to make it work for two of them, this is where I need some help.

For those two partners, when trying to send a message using v4.1.0, I'm getting two different errors:

• for partner 1 it fails with the following error:

INFO  org.openas2.processor.receiver.AS2MDNReceiverHandler - DISPOSITION MIC ALG: sha1   IMPORTANCE: optional
INFO  org.openas2.processor.sender.AS2SenderModule - Connecting to: https://as2.***** [<20250311151024-87d4aa0d-a574-4062-9256-2cd81cdfa756@MYAS2_PARTNER1AS2>]
WARN  org.openas2.util.HTTPUtil - SSL factory building using:
overrideSslChecks: false
isTrustSelfSignedCNHandling: false
isExtendedSelfsignedTrustCheck: false
org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: cookiesession1=********;Expires=Wed, 11 Mar 2026 15:10:25 GMT;Path=/;HttpOnly". Invalid 'expires' attribute: Wed, 11 Mar 2026 15:10:25 GMT
ERROR org.openas2.processor.sender.AS2SenderModule - Error sending message. URL: https://as2.***** ::: Response Code: 412 Erro Interno - REC13 - Arithmetic operation resulted in an overflow. ::: Response Message: [B@71500ce4

• for partner 2 it fails with the following error:

17:17:52.011 [AS2DirectoryPollingModule] ERROR org.openas2.util.AS2Util - Disposition exception processing MDN: This MDN response message is for:\r
From:          MYAS2\r
[<20250305171751-2036f449-0fcd-49ba-b0de-102d158f4f29@MYAS2_PARTNER2AS2>]
Message id:    <20250305171751-2036f449-0fcd-49ba-b0de-102d158f4f29@MYAS2_PARTNER2AS2>\r
Date received: Wed, 05 Mar 2025 17:17:51 GMT\r

17:17:52.009 [AS2DirectoryPollingModule] WARN  org.openas2.util.AS2Util - Disposition error detected in MDN. Received disposition: automatic-action/MDN-sent-automatically; processed/error: unexpected-processing-error [<20250305171751-2036f449-0fcd-49ba-b0de-102d158f4f29@MYAS2_PARTNER2AS2>]

The partnership configurations:

<partner name="myas2" as2_id="MYAS2" x509_alias="myas2" email="my@as2" />

<partner name="partner1" as2_id="PARTNER1AS2" x509_alias="partner1" email="partner1@as2" />
<partnership name="partner1-incoming">
    <sender name="partner1" />
    <receiver name="myas2" />
    <attribute name="store_received_file_to" value="$properties.storageBaseDir$/inbox/messages/$msg.sender.as2_id$-$msg.receiver.as2_id$/$msg.content-disposition.filename$-$msg.headers.message-id$" />
    <attribute name="reject_unsigned_messages" value="true" />
</partnership>
<partnership name="partner1-outgoing">
    <sender name="myas2" />
    <receiver name="partner1" />
    <pollerConfig enabled="true" />
    <attribute name="protocol" value="as2" />
    <attribute name="content_transfer_encoding" value="binary" />
    <attribute name="compression_type" value="NONE" />
    <attribute name="subject" value="File $attributes.filename$ sent from $sender.name$ to $receiver.name$" />
    <attribute name="as2_url" value="https://as2.*****" />
    <attribute name="as2_mdn_to" value="my@as2" />
    <attribute name="as2_mdn_options" value="signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, $attribute.sign$" />
    <attribute name="encrypt" value="3des" />
    <attribute name="sign" value="sha1" />
    <attribute name="resend_max_retries" value="24" />
    <attribute name="prevent_canonicalization_for_mic" value="false" />
    <attribute name="rename_digest_to_old_name" value="false" />
    <attribute name="remove_cms_algorithm_protection_attrib" value="false" />
    <attribute name="no_chunked_max_size" value="15728640" />
</partnership>

<partner name="partner2" as2_id="PARTNER2AS2" x509_alias="partner2" email="partner2@as2" />
<partnership name="partner2-incoming">
    <sender name="partner2" />
    <receiver name="myas2" />
    <attribute name="store_received_file_to" value="$properties.storageBaseDir$/inbox/messages/$msg.sender.as2_id$-$msg.receiver.as2_id$/$msg.content-disposition.filename$-$msg.headers.message-id$" />
    <attribute name="reject_unsigned_messages" value="true" />
</partnership>
<partnership name="partner2-outgoing">
    <sender name="myas2" />
    <receiver name="partner2" />
    <pollerConfig enabled="true" />
    <attribute name="protocol" value="as2" />
    <attribute name="content_transfer_encoding" value="binary" />
    <attribute name="compression_type" value="ZLIB" />
    <attribute name="subject" value="File $attributes.filename$ sent from $sender.name$ to $receiver.name$" />
    <attribute name="as2_url" value="https://*****" />
    <attribute name="as2_mdn_to" value="my@as2" />
    <attribute name="as2_mdn_options" value="signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, $attribute.sign$" />
    <attribute name="encrypt" value="3des" />
    <attribute name="sign" value="sha256" />
    <attribute name="resend_max_retries" value="24" />
    <attribute name="prevent_canonicalization_for_mic" value="false" />
    <attribute name="rename_digest_to_old_name" value="false" />
    <attribute name="remove_cms_algorithm_protection_attrib" value="false" />
    <attribute name="no_chunked_max_size" value="0" />
</partnership>

With the same configurations it works in OpenAS2 v2.14 but not with version 4.1.0, does anyone have a hint on what could be the issue?

Thanks

[uhurusurfa]

For both issues the logging is fairly cryptic and it would be best if you enabled TRACE level logging and uploadededthat with more of the preceding and succeeding log entries as there may be clues in there.

For partner 1 it seems odd that there are cookie errors since cookies are not used in AS2 but that entry is just a WARN level log so is not the problem. The MDN your partner sent back reports some sort of arithmetic overflow which may mean it cannot do CHUNKED encoding transfers.

For partner2 the MDN respoinse is more cryptic but possibly caused by the same underl;ying issue.

The most likely solution is to prevent chunking for those parterns.
See the section "Content Length Versus Chunked" in the OpenAS2HowTo.pdf for how to prevent using chunking mode for specific partners.

[umuser2020]

Hi @uhurusurfa,

Thanks for the fast reply.

For partner 1, it uses the config no_chunked_max_size=15728640, I've tested adding also prevent_chunking=true but with no success.

Note that with the same configurations shared above for partner 1 and 2 it works for OpenAS2 v2.14 but not for v4.1.0, I'm still trying to do some debug, it seems that it could be related with something in the MDN validation.

I going to enable TRACE for logging and will share it here.

Thanks

[uhurusurfa]

The main change in 4.x was to use CHUNKED mode by default for sending.
The error is actually happening on your partner side (search for this string: processed/error) which is why they are returning an MDN with a failure message - there has been no change to the actual processing of the MDN in a very long time so I am highly doubtful that it will be anything to do with processsing the MDN anyway)
It will probably help a lot if you can ask your partners for more details on exactly what the error is on their side - it could be any number of problems from decrypting, signature verification or simply some HTTP processwing error.

[umuser2020]

I think it might have been some mistake on my side 😅 I've add back the prevent_chunking=true to that particular partnership and prevent_chunking=false to all others, rebuild the image and it worked, it is now sending the messages with success.

Thank you again for helping and pointing to the right direction.
Cheers.

[uhurusurfa]

Thanks for reporting back. Hope you enjoy the software.