MQSeries.net :: View topic

vadivel · Posted: Tue Mar 04, 2003 3:26 am Post subject: AMQ 6109

Hi,

I have installed MQSeries 5.2 on Sun Solaris as per the installation script provided. I have defined 4 queue managers on the system. While I was trying to start one of the queue managers, I am getting the error : AMQ6109: An internal MQSeries error has occurred.

The explanation of the error is as followed:

AMQ6109 An internal MQSeries error has
occurred.
Explanation: An error has been detected, and the
MQSeries error recording routine has been called.
User Response: 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.

MA88 Support Pac is also installed. When I run a Java program to access the MQ QM we get the following error:

SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x0]

stackpointer=F68FEEC8
"MQBindingsQMThread1024" (TID:0x7402b8, sys_thread_t:0x7401f0, state:R, thread_t
: t@1036, threadID:0xf6901d70, stack_bottom:0xf6901d70, stack_size:0x1fd70) prio
=5 *current thread*

[1] com.ibm.mq.server.MQSESSION._MQCONN(Native Method)
[2] com.ibm.mq.server.MQThread.run(MQThread.java:1341)
[3] java.lang.Thread.run(Thread.java:478)
-------------------
"Thread-4" (TID:0x688560, sys_thread_t:0x688498, state:MW, thread_t: t@11, threa
dID:0xfb641d70, stack_bottom:0xfb641d70, stack_size:0x1fd70) prio=5

[1] com.ibm.mq.server.MQThread.waitForCompletion(MQThread.java:1303)
[2] com.ibm.mq.server.MQThread.MQCONN(MQThread.java:329)
[3] com.ibm.mq.server.MQSESSION.MQCONN(MQSESSION.java:1033)
[4] com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:126)
[5] com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQ
BindingsManagedConnectionFactoryJ11.java:115)
[6] com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnection(MQB
indingsManagedConnectionFactoryJ11.java:157)
[7] com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:72)
[8] com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionMa
nager.java:115)
[9] com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:640)
[10] com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:591)
[11] com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:388)
[12] com.citibank.zbank.messaging.mq.MQHelper.openConnection(MQHelper.java:234)
[13] com.citibank.zbank.messaging.process.InMessageDispatcherTask.process(InMess
ageDispatcherTask.java:261)
[14] com.citibank.zbank.messaging.process.InMessageDispatcherTask.run(InMessageD
ispatcherTask.java:226)
[15] java.lang.Thread.run(Thread.java:479)
-------------------
"Thread-3" (TID:0x642910, sys_thread_t:0x642848, state:CW, thread_t: t@10, threa
dID:0xfb671d70, stack_bottom:0xfb671d70, stack_size:0x1fd70) prio=5

[1] java.lang.Thread.sleep(Native Method)
[2] com.citibank.zbank.messaging.utils.TimerHelper.sleep(TimerHelper.java:52)
[3] com.citibank.zbank.messaging.process.CacheRefresher.process(CacheRefresher.j
ava:166)
[4] com.citibank.zbank.messaging.process.CacheRefresher.run(CacheRefresher.java:
336)
[5] java.lang.Thread.run(Thread.java:479)
-------------------
"Thread-2" (TID:0x631568, sys_thread_t:0x6314a0, state:CW, thread_t: t@9, thread
ID:0xfb7f1d70, stack_bottom:0xfb7f1d70, stack_size:0x1fd70) prio=5

[1] java.lang.Object.wait(Object.java:424)
[2] com.citibank.zbank.core.log.LogQueue.put(LogQueue.java:79)
[3] com.citibank.zbank.core.log.LogQueue.get(LogQueue.java:173)
[4] com.citibank.zbank.core.log.LogWriterThread.run(LogWriterThread.java:147)
-------------------
"Thread-1" (TID:0x5911a0, sys_thread_t:0x5910d8, state:CW, thread_t: t@8, thread
ID:0xfde71d70, stack_bottom:0xfde71d70, stack_size:0x1fd70) prio=5

[1] java.lang.Thread.sleep(Native Method)
[2] com.citibank.zbank.core.db.DbConnectionPool.run(DbConnectionPool.java:157)
[3] java.lang.Thread.run(Thread.java:479)
-------------------

Exiting Thread (sys_thread_t:0xfefcfdb0) : no stack
"Finalizer" (TID:0x1556a8, sys_thread_t:0x1555e0, state:CW, thread_t: t@6, threa
dID:0xfe871d70, stack_bottom:0xfe871d70, stack_size:0x1fd70) prio=8

[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3] java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
24)
-------------------
"Reference Handler" (TID:0x27188, sys_thread_t:0x270c0, state:CW, thread_t: t@5,
threadID:0xfebf1d70, stack_bottom:0xfebf1d70, stack_size:0x1fd70) prio=10

[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:136)
-------------------
"Signal dispatcher" (TID:0x120210, sys_thread_t:0x120148, state:MW, thread_t: t@
4, threadID:0xff051d70, stack_bottom:0xff051d70, stack_size:0x1fd70) prio=10

-------------------
"main" (TID:0x39588, sys_thread_t:0x394c0, state:CW, thread_t: t@1, threadID:0x2
5228, stack_bottom:0xffbf0000, stack_size:0x800000) prio=5

[1] java.lang.Thread.sleep(Native Method)
[2] com.citibank.zbank.messaging.utils.TimerHelper.sleep(TimerHelper.java:52)
[3] com.citibank.zbank.messaging.process.TaskManager.monitorTasks(TaskManager.ja
va:464)
[4] com.citibank.zbank.messaging.process.TaskManager.main(TaskManager.java:181)

I am able to start all the other queue managers. Can anybody throw any light on to this problem? Is there any settings that I need to do in the system?

Regards,

Sajith