This section contains descriptions of known issues in this release.
65445. eXchange does not support the ability to create and send multiple Functional Groups within the interchange.
Although multiple transactions per Functional Group are supported, transactions within a Functional Group must be of the same type.
77187. eXchange does not support message payloads that contain a "Return" (CRLF) character and messages fail during parsing.
The following error message (from X12, where parsing fails at the SE or GE) is typical:
. . TokenStreamException: Unable to assign segment data with tag [GE] to any Token Type
Before sending any message payload, you must trim the CRLF or any extra spaces before wrapping the Outbound envelope. After trimming, make sure that the ending segment delimiter exists. Absence of this delimiter can also cause parsing errors.
82049. In ePM, do not use the apostrophe character in the Sender ID and Receiver ID fields.
If either of these fields contains an apostrophe, attempting to use Message Tracker to view messages under that name results in an Error on page message and there is no display of the original message or any acknowledgments to it.
82053. Release characters are shown “as is” when you view a message via Message Tracker.
eXchange does not expect an explicit escape character in the sender ID in ePM, where escape is automatic. Transaction IDs that contain escape characters also cause errors in Message Tracker, due to inconsistencies with ePM. Delimiters are not supported.
85935. In ebXML, ACK is improperly updated with error generation date in Message Tracker.
95722. If you update existing private keys with the same name, they disappear from the list in ePM.
Each time you change a key to an existing name, it accepts the change and the original name disappears from the list.
98704. In ebXML, ePM is not validating the “Host/Partner Role in Transaction” fields.
101800. eXchange cannot handle messages that contain characters that conflict with those used in XML.
For example, if an X12 message contains characters such as & (ampersand) , > (greater than), or < (less than) as delimiters or in the text components, parsing fails and an error message is generated.
105778. When running a sample X12 scenario on top of Java CAPS 5.1.2, the following error message is generated:
Unable to Register Response, Correlation failed Stack
If you do not receive a response, you can set the resendCount and resendInterval to 0. (In this case, if you do get a response, you also get an exception) If you want to receive a response, then you must set both resendCount and resendInterval to greater than 0. This means you have to reconfigure for at least one resend if you expect to receive a response.
109553. When you send a 270 message as a request and receive 271 and 278 messages as the response, you get the following error message:
Unable to Register Response, Correlation failed Stack
The error is false because two separate responses are actually registered; however, they cannot be correlated when they are registered. Thus, the resend service does not know that more than one response is expected.
6577891. Cannot use existing eXchange Partner Manager profiles from SRE.
A conversion tool is needed for migrating SRE eXchange Trading Partners into eXchange 5.1.1.
6589277. Usability problems occur when you re-import keys and/or certificates via the ePM GUI.
When you attempt to re-import a certificate and/or key via the ePM system and the certificate or key already exists, an error condition is thrown. This requires you to remove the LDAP entries.
6591068. In AS2, ProcError shows Nonmeaningful Error-description when the Berlin TP encryption certificate is expired.
Apply ESR 6613784 to correct this problem.
6591131. In AS2, negative MDN is not able to correlate when Berlin TP encryption certificate is invalid.
When Atlanta sends an AS2 message with encrypted data to Berlin, and Berlin sends a negative MDN with signature, Atlanta fails to verify the signature, and the negative MDN does not correlate the original message. Apply ESR 6613784 to correct this problem.
6591552. AS2 Message Headers are not visible in Message Tracker when SME options are ON.
When SME options are set to ON , the Message Tracker does not display the AS2 Message Headers; however, the Headers are displayed when SME options are set to OFF. The Message Tracker does not support multiple tracks. Attributes are shown in the Attributes tab.
6593890. Incorrect configuration of database users can result in runtime database error.
When sending messages with a batch size greater than 1, the following Oracle errors were generated to the server's log file:
SQL Error: 1461, SQLState: 72000
ORA-01461: can bind a LONG value only for insert into a LONG column
This problem was caused by different users being assigned to the Oracle eWay and the B2BServiceConfiguration in Enterprise Designer; for example, the Oracle eWay's user is set to ex_adminA and the B2BServiceConfiguration Oracle user is set to ex_admin. The Sun B2B Suite does not support using two different database users for the same environment setup. To correct this error, you would set the B2BServiceConfiguration Oracle user to ex_adminA, then rebuild and redeploy the eXchange deployment.
6594363. When you attempt to delete a key using the ePM GUI, the password box is displayed, but you are not required to provide a password.
6599180. A negative MDN is not generated when the Message Encoding field is mismatched between two Trading Partners.
AS2 Protocol Manager uses this encoding only to sign or encrypt, not to verify. The message is verified based on the format in which it is received. A positive MDN is received even though the Message Encoding field is mismatched.
6605895. In AS2, unable to post messages of 10 MB or more from Atlanta to Berlin.
To work around this problem, do the following:
In the domain.xml file for each affected logical host, set the value for jvm-options to 1024, for example:
Shut down your logicalhost.
Delete any existing *.dbs files from your stcms/instance1 directory.
Update your stcms.default.properties to increase the segment size.
Restart your logicalhost.
For more information, see the Sun SeeBeyond eGate Integrator JMS Reference.
6608672. Inbound message with an erroneous GS01 causes a dead letter.
If an inbound message's G01 (FUNC_ID_CODE) does not match the corresponding information for the Trading Partner as specified in ePM, the Sun B2B Suite will create a dead letter. The deadletter (and server.log) will contain the following message: Could not retrieve ExStdEvent.
Check to see if any of the following values do not match the expected values set in ePM (where var = value):
ISA_SENDER_QUAL = 01|ISA_SENDER_ID = AtlantaIID|ISA_RECEIVER_QUAL = 01|ISA_RECEIVER_ID = BerlinIID|ISA_VERSION = 00401|ST_TRANS_ID = 270|FUNC_ID_CODE = HA|GS_SENDER_ID = AtlantaAcd|GS_RECEIVER_ID = BerlinAcd|GS_VERSION = 004010|( Note that the names listed in the message are not an exact match to what is shown in ePM.)
Example log message: ePM GS01 set to HS and inbound sent with GS01 = HA
6611611. RedHat Linux LDAP Server is not currently certified to work with the Sun B2B Suite.
6612855. In AS2, you are unable to save the Private Keys in the ePM Hosts with Open LDAP setup.
When trying to execute an AS2 SME–related baseline scenario with Open LDAP setup, you cannot save private keys in the host. When you attempt to do so, an exception is thrown.
6617828. Some ebXML default attributes do not appear on the pull-down list of values.
In ePM Trading Partner Transaction Profile under Outbound ToPartner⇒Overrides⇒Delivery Batch ⇒ Outbound ToPartner, the default value for SignatureAlgorithm shows as DSA-SHA1, but this value does not appear as one of the values on the pull-down list . The default value for EncryptionAlgorithm shows as DSA-SHA1 while the pull-down shows one value: DES3.
6618383. ebXML messages signed with the dsa-sha1 () algorithm fail. Only RSA is supported in 5.1.1.
6618474. ExStdEvent is not returned when using an external attribute key (getExStdEventByExtAttrs).
Standard getExStdEvent works when using the lookup with the four standard attributes.
6620248. In HIPAA with Foresight, a negative 997 is not generated for a duplicate SE segment.
The code validates the message and attempts to generate a response. The validation code receives proper errors, but the error codes for the response generator records in the detail file are mismatched.
6621344. In SME, with a signed payload, but without a signed envelope or encryption, the expected signed acknowledgement fails and the following XML exception is raised:
SOAP Header was not found in the envelope.
6621889. Unsigned encrypted payload message with signed AckRequested is not supported in ebXML.
Unsigned encrypted message with AckRequested fails to return an acknowledgment. Instead, it generates ProcError with error code 1000 and error description: EXCHANGESERVICE SELECTOR HANDLER SYSTEM FAILURE.
6623986. Envelope MIME parameters defined in ePM are ignored.
6625072. When you delete or rename an existing Trading Partner profile, and then re-import it with the same Trading Partner name, it is imported successfully, except that the certificate under the Trading Partner profile tree is missing.
The Certificate is missing from the TP profile tree because the refKeyStoreConfiguration attribute is missing from the newly imported TP in LDAP. Importing the original certificate fails because the certificate already exists in the keystore.
To work around this problem, do the following:
Import the same certificate with a different alias.
If keeping the same name is critical, bring up LDAP and change the alias name to the original.
If you need to import certificates, then you need to set the system property before importing starts and the keystore being referenced by the Trading Partner must have all of the aliases.
6625177 Encryption Flag set inconsistently on both TP1 and TP2, but doesn't return inconsistent ProcError.
With inconsistency in the ePM configuration on both the Trading Partners, TP2 is expected to return an inconsistent ProcError. For example. with TP1 Payload1 EncryptFlag set to Yes and Inbound TP2 Payload1 EncryptFlag set to No, TP2 fails to return an inconsistent ProcError. Instead, it returns an Unsigned ACK as configured in the ePM.
6625495. In ebXML, TP1 sends encrypted message even when Encryption algorithm is set to “none”.
With Encryption algorithm set to none, the Outbound message should fail to send an encrypted message, instead it should return a ProcError. However, with TP1 Payload1 EncryptFlag set to Yes , Delivery-use Encryption set to yes, and Encryption Algorithm set to none, the outbound payload is still encrypted.
6625828. When Protocol Validation Handler is set to None, a ProcError is not generated.
The system generates neither a ProcError nor a written exception in the server log file; rather, after posting the message to Ex_FromTP, the system stops processing the message. The ePM GUI should have a parameter relationship validation that enforces selection of a Validation Handler. ebXML Protocol Manager does not have this validation mechanism. Documentation should reflect that a Validation Handler must be selected.
6625845. Instead of showing < >" ", the system shows <, >, " (XML entity references) in Message Tracker.
6628903. An Inbound message in asynchronous mode containing a SOAP fault (invalid type=text) fails to generate a ProcError.
A ProcError regarding the SOAP fault should be returned via a separate HTTP Host. The ProcError is not returned.
6630706. In ebXML, when an unsupported message is received, a MessageError with NotSupported is not returned to the Trading Partner.
6632403. Need to use the same CPAId within the same ebXML trading partner.
The current ebXML sample project uses different sets of CPAId for different transaction profiles within the same trading partner. Currently , however, only one CPAId is supported for all the transaction profiles within the same trading partner, thus, the same CPAId should be used between two partners.
6632421. ebXML does not use some fields in ePM that look like they should be used.
In ePM transaction profile Overrides at the TP level:
On Delivery Protocol⇒Inbound FromPartner the following fields are not being used by ebXML although they look like they should be:
Use Decryption Delivery
Verify Signature Delivery
Use Decompression Delivery
Message Encoding Delivery
The only two fields within the group that have been used by ebXML are the following:
Duplication Checking Delivery
On the Delivery Protocol⇒Outbound ToPartner, there are also similar fields that are not used. All the acknowledgments on the Overrides such as ACK - Delivery Protocol and ACK - Delivery Batch are not used whether inbound or outbound because ebXML only uses the ebXMLAcknowledgment defined as signal message in the transaction profile.
6635799. ebXML fails to parse namespaces with HL7.
6635915. In ebXML, unable to send 20 MB message from Atlanta to Berlin.
When processing the X12 payload, the system throws a TransactionRolledBackException in the server log file. To process payloads of up to 15 MB, do the following for each logical host:
Edit the domain.xml file and change the Java heap size from 512 to 1024 .
Edit the stcms.default.properties file and change the segment size from 16 MB to 25 MB.
Delete the *.dbs files under \stcms\instance1.
6637590. In ebXML, when the selected outbound encryption algorithm is DES3, the message is encrypted with the default algorithm, AES128.
The sample projects shipped with ebXML Protocol Manager use hard-coded hostnames (“domain1” for the Atlanta host and “domain2” for the Berlin host), but the documentation presumes a single local host (“localhost”) throughout.
To use the ebXML sample, do one (and only one) of the following:
To use two different machines to simulate the Atlanta and Berlin hosts, globally change the string “domain1” to the actual hostname of the machine you are using to simulate the Atlanta host, and globally change the string “domain2” to the actual hostname of the machine you are using to simulate the Berlin host.
To use a single machine to simulate both the Atlanta and Berlin hosts, add aliases for “domain1” and “domain2” to the machine's etc/hosts file (on Windows, this file is %SYSTEMROOT%\system32\drivers\etc\hosts), as highlighted in the following fictitious example:
127.0.0.1 localhost # (optional comment)255.255.255.255 mymachine.myenterprise.com 111.333.555.777 machine1 # (optional comment) 222.444.666.888 machine2.theirenterprise2.com[...]255.255.255.255 domain1 # aliasing domain1 to mymachine <-- 255.255.255.255 domain2 # aliasing domain2 to mymachine <-- [...]