MQSeries.net :: View topic - StandAlone Java App on Solaris using Oracle XA

fdouek · Posted: Tue Jul 23, 2002 5:26 am Post subject:

Hi,
I have a very big problem.
I develop a simple application to get an message and insert on Oracle database, using Two Phase Commit. MQ are the coordinator.

SO: Solaris 2.7
API: MA88
Database: Oracle 8.1.7
MQ Version: 5.2

When I run one instance of process (on solaris), works fine.
When I start an second instance (on solaris), occur an error described bellow.
PS: If I start two instances on windows 2000 works fine.

My code
=====
import com.ibm.mq.*;
import java.util.*;
import java.sql.*;
import oracle.jdbc.xa.client.*;

public class Test {
public static void main(String[] args) {
Test mt = new Test();
mt.execute();

}

public void execute() {
MQQueueManager mm=null;
try {
System.out.println("inicia");
//teste para ver se carrega as classes:
Class mag = Class.forName("com.ibm.mq.MQQueueManager").getClassLoader().loadClass("com.ibm.mq.MQQueueManager");
Class magm = Class.forName("com.ibm.mq.MQSESSION").getClassLoader().loadClass("com.ibm.mq.MQSESSION");
System.out.println("fim " + mag);
System.out.println("fim " + magm);
//teste para ver se faz a conexao:
MQEnvironment.channel = "SYSTEM.DEF.SVRCONN";
Hashtable ht = new Hashtable();
ht.put("MQC.TRANSPORT_PROPERTY", "MQC.TRANSPORT_MQSERIES_BINDINGS"); //"MQC.TRANSPORT_MQSERIES_CLIENT");
ht.put("MQC.PASSWORD_PROPERTY", "mqmpassword");
ht.put("MQC.USER_ID_PROPERTY", "mqmuser");

mm = new MQQueueManager("QM_TEST", ht);
OracleXADataSource oxa = new OracleXADataSource();
oxa.setURL("jdbc:oracle:thin:@10.10.10.1:1521:orcl");
oxa.setUser("username");
oxa.setPassword("password");
oxa.setDatabaseName("10.10.10.1:1521:orcl");
java.sql.Connection cAux = mm.getJDBCConnection(oxa);

System.out.println("end " + cAux);
System.out.println("end " + mm);

int options = MQC.MQOO_INPUT_SHARED | MQC.MQOO_OUTPUT;
MQQueue queue = mm.accessQueue("MYQUEUE",
options,
"QM_TEST",
null,
null);

MQGetMessageOptions gmo = new MQGetMessageOptions();
gmo.waitInterval = MQC.MQWI_UNLIMITED;
gmo.options = MQC.MQGMO_SYNCPOINT | MQC.MQGMO_WAIT;
MQMessage retrievedMessage = new MQMessage();

while (true) {
mm.begin();
retrievedMessage.clearMessage();
retrievedMessage.correlationId = MQC.MQCI_NONE;
retrievedMessage.messageId=MQC.MQMI_NONE;

System.out.println("Aguardando msg");
queue.get(retrievedMessage, gmo);
String msgText = retrievedMessage.readString(retrievedMessage.getMessageLength());
System.out.println("the message: " + msgText);

System.out.println("the end of the get");

Statement stt = cAux.createStatement();
String query = "insert into testefabio values('" + msgText + "')";
int i = stt.executeUpdate(query);
System.out.println();
mm.commit();
}
} catch(Exception e) {
try {
mm.backout();
}
catch (Exception ex) {
System.out.println("Erro no rollback" + ex.getMessage());
}
e.printStackTrace();
}
}

}

Error on client
=========
MQJE001: Completion Code 2, Reason 2195
MQJE001: Completion Code 2, Reason 2009
Erro no rollbackMQJE001: Completion Code 2, Reason 2009
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2195
at com.ibm.mq.MQQueueManager.commit(MQQueueManager.java:905)
at Test.execute(Test.java:74)
at Test.main(Test.java:9)

Error on MQ server (log)
================

07/17/02 22:47:48
AMQ7605: The XA resource manager smstar has returned an unexpected return code
-3, when called for xa_prepare.

EXPLANATION:
MQSeries received an unexpected return code when calling XA resource manager
smstar at its xa_prepare entry point. This indicates an internal error, either
within MQSeries or the resource manager.
ACTION:
Try to determine the source of the error. A trace of the failure could be used
to look at the XA flows between MQSeries and the resource manager. MQSeries
has allocated an RMId of 1 to this resource manager. This will be useful when
isolating the flows associated with the resource manager concerned. If the
error occurs on an xa_commit or xa_rollback request, the queue manager will not
attempt to redeliver the commit or rollback instruction for this transaction,
until after the queue manager has been restarted. The transaction indoubt is
identified by the following XID of
X'004D514D0000000E000000043D360B1800032012514D5F534D5300000001'. If you think
that the error lies within the queue manager, contact your IBM support center.
Do not discard any information describing the problem until after the problem
has been resolved.
-------------------------------------------------------------------------------
07/17/02 22:47:48
AMQ6184: An internal MQSeries error has occurred on queue manager QM_SMS.

EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 22317.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
_________________
Fabio Douek