Topic
  • 3 replies
  • Latest Post - ‏2012-10-14T03:18:50Z by fjb_saper
SystemAdmin
SystemAdmin
8523 Posts

Pinned topic Issue when I try to create new QM

‏2012-09-18T11:45:33Z |
Hello,

I am currently using IBM Websphere MQ7. The issue I am facing is related to the creation and the start of new QMs. In fact, when I create a new Queue Manager I got the following error:

bash$ crtmqm TEST_CREATION
WebSphere MQ queue manager created.
Creating or replacing default objects for TEST_CREATION.
AMQ6109: An internal WebSphere MQ error has occurred.

And after that, when I try to start the new QM I got :

bash$ strmqm TEST_CREATION
WebSphere MQ queue manager 'TEST_CREATION' starting.
264 log records accessed on queue manager 'TEST_CREATION' during the log replay phase.
Log replay for queue manager 'TEST_CREATION' complete.
Transaction manager state recovered for queue manager 'TEST_CREATION'.
WebSphere MQ queue manager 'TEST_CREATION' started.

But the QM passes from the two following status:

bash$ dspmq
QMNAME(TEST_CREATION) STATUS(Ending preemptively)

bash$ dspmq
QMNAME(TEST_CREATION) STATUS(Ended unexpectedly)

Can anyone help me to solve this issue?

Regards,
Achraf
Updated on 2012-10-14T03:18:50Z at 2012-10-14T03:18:50Z by fjb_saper
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: Issue when I try to create new QM

    ‏2012-09-24T17:56:46Z  
    Hello,

    Do anyone have an idea to solve this issue?

    Regards,
    Achraf
  • Madhes
    Madhes
    13 Posts

    Re: Issue when I try to create new QM

    ‏2012-10-09T10:06:12Z  
    Hello,

    Do anyone have an idea to solve this issue?

    Regards,
    Achraf
    It looks like user doesn't have enought permission, add that user into local mqm group and give a try.
  • fjb_saper
    fjb_saper
    175 Posts

    Re: Issue when I try to create new QM

    ‏2012-10-14T03:18:50Z  
    • Madhes
    • ‏2012-10-09T10:06:12Z
    It looks like user doesn't have enought permission, add that user into local mqm group and give a try.
    There should be an FDC created.
    Check the content of the FDC (1st page).
    You may lack permission or resources...
    The FDC should clarify why the qmgr is shutting down.