Bookshelf Home | Contents | Index | PDF     

Siebel Store-and-Forward Messaging Guide for Handheld > Installation and Configuration of Siebel Store-and-Forward Messaging > Troubleshooting Store-and-Forward Messaging Setup and Configuration >

Siebel Store-and-Forward Messaging Server-Side Common Error Messages

Some common server-side error messages, and their solutions, are described in Table 8.

Table 8. Server-Side Common Error Messages
Symptom or Error Message
Diagnostic Steps or Cause
Solution

MQe Internal Error: RemoveMsg: Message inside of Inbound Queue is not deleted successfully.

Error Code: 121

Error Code 121 means there is no matching message in the queue.

Multiple Receivers or Tasks may be trying to process or dispatch from the same queue at the same time.

Check srvrmgr to find out how many SMQReceivers are running in the server.

Reconfigure as needed to make sure that there is only one SMQReceiver for each application.

ObjMgrBusServiceLog  Error  1  
000008e0440515c0:0  2006-03-02 00:05:23  (srmsyncsv.cpp (1214)) SBL-SRQ-00103: Unable to find definition for component WfProcMgr

This error may appear in the SMQReceiver log file.

The server components may not be synchronized to the internal table.

To synchronize the server components to the internal table, perform the following steps:

  1. In the Administration - Server Configuration > Synchronize screen, click Synchronize.
  2. Restart the SMQReceiver component.

JVM Init Exception: Can't load JVM dll: libjvm

This error may appear in the SMQReceiver log file on Solaris and Linux systems.

There may be an incorrect value in LD_LIBRARY_PATH.

Check the value of LD_LIBRARY_PATH by running one of the following commands:

  • env
  • echo $LD_LIBRARY_PATH

On AIX, check $LIBPATH.

Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode) IBM WebSphere MQ Everyplace 2.0.2.4 Created session for subsys SmqReceiverSubsys GetClientNames: com.ibm.mqe.MQeException: Message not found[ServerQM 27] (code=121) atcom.ibm.mqe.MQeTransporter._remoteExecute(DashoA8173) at com.ibm.mqe.MQeTransporter.remoteExecute(DashoA8173) at com.ibm.mqe.MQeTransporter.getMessage(DashoA8173) at com.ibm.mqe.MQeRemoteQueue._synchronousGetMessage(DashoA8173) at com.ibm.mqe.MQeRemoteQueue.getMessage(DashoA8173) at com.ibm.mqe.MQeQueueControlBlock.getMessage(DashoA8173) at com.ibm.mqe.MQeQueueManager.waitForMessage(DashoA8173) at com.ibm.mqe.MQeQueueManager.waitForMessage(DashoA8173) at com.siebel.smq.session.MQeBaseSession.executeAdmin(MQeBaseSession.java:279) at com.siebel.smq.session.MQeServerSession.getClientNames(MQeServerSession.java:255)

This error may appear in the SMQReceiver Logoff.

System clocks on different hosts may not be synchronized.

Synchronize the clocks on the host machines for WfProcMgr, SMQReceiver, and the Tomcat server.

    
Siebel Store-and-Forward Messaging Guide for Handheld Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.