November 27, 2009 at 7:41 pm
Symptom
JMS adapter does not provide a message dump feature.
Such a feature would be valuable in verifying if JMS adapter is responsible for any character conversions while interoperating with third party JMS providers.
Other terms
JMS adapter, character conversion, Websphere MQ
Reason and Prerequisites
While interoperating with third party JMS providers (most notably Websphere MQ), many cases of [...]
November 7, 2009 at 8:23 pm
Symptom
Your J2EE Engine is stuck. XI/PI Message flow through the Adapter Framework has stopped. On 6.40 and 7.0 systems logon to the Visual Administrator isn’t possible any longer, in 7.1 systems SAP NetWeaver Administrator hangs. System startup failes, hangs or takes very long.
Other terms
Application Thread Manager, Max Thread Count, Messaging System, [...]
August 5, 2009 at 1:19 am
Symptom
The parameter “clusterSyncMode” setting was only available for Advanced mode table and not available as service property in Visual administrator.
Other terms
FTP adapter, File Adapter, Advance mode parameter, service property
Reason and Prerequisites
Special development
Solution
From SP21(Patch 20) onwards, the parameter ‘clusterSyncMode’ can also be set as Service level property in Visual administrator. Prior to this SP, [...]
July 13, 2009 at 9:25 pm
Symptom
The timeout value used by the standard trasnport handler such as HTTPSender or CommonsHTTPSender is obtained by the timeout
value set in the Axis MessageContext object. The MessageContext object has method getTimeout() and setTimeout(int timeout) to get and set the timeout value.
However, this value was previously not accessible directly in the adapter’s channel/handler configuration [...]
July 10, 2009 at 5:56 am
Symptom
FAQ XI 3.0 RFC Adapter, PI 7.0 RFC Adapter, PI 7.1 RFC Adapter
Other terms
XI 3.0, PI 7.0 RFC Adapter, PI 7.1 RFC Adapter, RFC Adapter, RFC Adapter, J2EE, J2SE Plain Adapter Engine, Adapter Engine, Adapter Framework, SAP XI Adapter: RFC
Reason and Prerequisites
This note serves as Frequently Asked Questions on the topic
XI 3.0 RFC Adapter, [...]
July 10, 2009 at 3:59 am
Symptom
You are experiencing problems with the SAP XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter and/or need further detailed information about its operation and configuration.
Other terms
Exchange Infrastructure, XI 3.0 / PI 7.0 / PI 7.1, Adapter Framework, Frequently Asked Questions, HOWTO
Reason and Prerequisites
This note serves as FAQ document for the SAP XI [...]
June 30, 2009 at 9:12 am
Symptom
You notice that the J2EE Engine restarts frequently, due to an Out Of Memory Error(OOM) (i.e., “java.lang.OutOfMemoryError” ). Traces and thread dumps will exhibit, the following error message: “java.lang.OutOfMemoryError. The JVM(Java Virtual Machine) will exit with an exit code of 666″
Other terms
JDBC, JDBC Adapter, OutOfMemoryError, OOM , Message Size Limit, Limit Number of [...]
June 30, 2009 at 9:09 am
Symptom
You are using JDBC adapter in your scenarios with QoS(Quality of Service) as Synchronous(Best Effort/BE). However, messages report a “MessageExpiredException”.
Other terms
JDBC, JDBC Adapter, Dummy Query, timeout, dummySQLQueryTimeout, timeout, synchronous, best effort
Reason and Prerequisites
Any delay in the response to a blocking synchronous request, results in the above exception. In this case, the delay is [...]
June 25, 2009 at 4:00 am
Symptom
A new feature has been introduced in the JMS adapter (receiver channel) to help reduce the number of open TCP/IP connections to IBM Websphere MQ JMS provider.
Other terms
JMS Adapter, On Demand Connection, Connection on Demand, CONNECTION_TEST_POLL
Reason and Prerequisites
When connecting to IBM Websphere MQ using PI JMS adapter, each channel creates a TCP/IP connection.
Since Websphere [...]
June 25, 2009 at 3:51 am
Symptom
During the processing of JDBC receiver communication channels, too many open connections are noticed in the DB2 logs, which in turn lead to performance problems.
Other terms
JDBC, DB2, open connections, JDBC Adapter
Reason and Prerequisites
This issue occured due to a programmatic error.
Solution
The issue has been solved by changes in the code. The archives and the
support package [...]