Troubleshooting Message Service Runtime Errors

Problem: Runtime errors received in a message service.

Solution: Use the following sequence to troubleshoot message service runtime errors:

Use external utilities and methods for examining data on queues, files, or Email servers.

Open the Message Service Editor and choose from these options:

Option	Description
Message service with email endpoint	Verify that property values exist for the From and To properties. Verify that all other property values are valid against the email RFC. If there is connection timeout or similar error, test whether the server is accessible via SMTP over the specified port, using telnet `<SMTP host name> <SMTP port number, default is 25>`.
Message service with JMS endpoint	Create the endpoint from connection profile to make sure the configuration properties are correctly. If third party JMS queues are used (TIBCO, OpenJMS, or WSMQ) extract the third party driver classes and copy the DLL files before deploying the service package. If a JMS connection profile is used, verify that the Initial Context Factory and Queue Connection Factory properties are correct for your JMS provider type and site implementation. Some JMS providers allow multiple names for these properties.

Option

Description

Message service with email endpoint

Verify that property values exist for the From and To properties.
Verify that all other property values are valid against the email RFC.
If there is connection timeout or similar error, test whether the server is accessible via SMTP over the specified port, using telnet <SMTP host name> <SMTP port number, default is 25>.

Message service with JMS endpoint

Create the endpoint from connection profile to make sure the configuration properties are correctly.
If third party JMS queues are used (TIBCO, OpenJMS, or WSMQ) extract the third party driver classes and copy the DLL files before deploying the service package.
If a JMS connection profile is used, verify that the Initial Context Factory and Queue Connection Factory properties are correct for your JMS provider type and site implementation.

Some JMS providers allow multiple names for these properties.

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.