NAESB inbound message failing in BusinessConnect
Article ID: KB0080073
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | 6.X |
Description
Inbound NAESB message from trading partner fails with the following error :
<<<
ERROR PACKAGE_RECEIPT NAESB message received but failed to be unpackaged. Packaged error receipt for null, returning HTTP 500 Missing start boundary.
>>>
The bad message has some MIME boundaries that are not correct: i.e.
<<<
....
boundary2--20020511
Content-Type: application/pgp-encrypted
Version: 1
boundary2--20020511
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
....
>>>
<<<
ERROR PACKAGE_RECEIPT NAESB message received but failed to be unpackaged. Packaged error receipt for null, returning HTTP 500 Missing start boundary.
>>>
The bad message has some MIME boundaries that are not correct: i.e.
<<<
....
boundary2--20020511
Content-Type: application/pgp-encrypted
Version: 1
boundary2--20020511
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
....
>>>
Issue/Introduction
Correct the incoming message
Environment
Linux: Red Hat 8.0
Resolution
The obvious reason is that the message is malformed at the MIME header level, so you need to correct the incoming message.
MIME boundaries must always start with two hyphens like :
<<<
...
--20020511
Content-Type: application/pgp-encrypted
Version: 1
--20020511
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
...
>>>
MIME boundaries must always start with two hyphens like :
<<<
...
--20020511
Content-Type: application/pgp-encrypted
Version: 1
--20020511
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
...
>>>
Additional Information
NAESB, MIME, unpackage, malformed
Feedback
Yes
No
Powered by
