Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JMS does not connect #522

Open
geekosphere-net opened this issue Apr 21, 2023 · 2 comments
Open

JMS does not connect #522

geekosphere-net opened this issue Apr 21, 2023 · 2 comments

Comments

@geekosphere-net
Copy link

When running the latest 9.3.2 container I can only connect to the QMGR via admin on DEV.ADMIN.SVRCONN in MQ Explorer, JMSToolBox does not connect.

  • MQ Explorer: admin on DEV.ADMIN.SVRCONN works
  • MQ Explorer: app on DEV.APP.SVRCONN error
    • AMQ8077W: Entity 'app' has insufficient authority to access object SYSTEM.MQEXPLORER.REPLY.MODEL [queue]. [CommentInsert1(app), CommentInsert2(SYSTEM.MQEXPLORER.REPLY.MODEL [queue]), CommentInsert3(inq)]
  • JMSToolBox: admin on DEV.ADMIN.SVRCONN error
    • AMQ8077W: Entity 'admin' has insufficient authority to access object QM1 [qmgr]. [CommentInsert1(admin), CommentInsert2(QM1 [qmgr]), CommentInsert3(connect)]
    • AMQ9557E: Queue Manager User ID initialization failed for 'mqm'. [ArithInsert1(2), ArithInsert2(2035), CommentInsert1(mqm), CommentInsert2(admin), CommentInsert3(admin)]
  • JMSToolBox: app on DEV.APP.SVRCONN error:
    • AMQ8077W: Entity 'app' has insufficient authority to access object SYSTEM.ADMIN.COMMAND.QUEUE [queue]. [CommentInsert1(app), CommentInsert2(SYSTEM.ADMIN.COMMAND.QUEUE [queue]), CommentInsert3(put/inq)]

As admin on MQ Explorer worked, I would have expected the JMSToolBox to connect as well.
It would also be nice to be able to browse messages as app

Image:
icr.io/ibm-messaging/mq latest 6ba79f4584cc
"Image": "sha256:6ba79f4584cc612937fefbfb144745196e26828a9048489f41a301acef36fa38"

Docker run:

docker run -itd                                                                         \
        --rm                                                                            \
        --name mq                                                                       \
        --privileged                                                                    \
        -v /mnt/d/docker/mq/MQDATA:/mnt/mqm                                             \
        -p 1414:1414                                                                    \
        -p 9443:9443                                                                    \
        -e LICENSE=accept                                                               \
        -e MQ_QMGR_NAME=QM1                                                             \
        -e MQ_ADMIN_PASSWORD=xxxxx                                                      \
        -e MQ_APP_PASSWORD=xxxxx                                                        \
        icr.io/ibm-messaging/mq:latest

If I use our script to grant full access then both tools work for both users.

My questions/issues:

  1. Why do I get an error when connecting as admin with JMSToolBox when MQExplorer works?
  2. Should the app use be allowed to connect by default to help developers?

Thanks in advance

@andreysaksonov
Copy link

andreysaksonov commented May 17, 2023

I experience the same issue, posted question on SO https://stackoverflow.com/questions/76260819/how-to-connect-to-local-ibm-mq-container-using-jmstoolbox @arthurbarr could you take a look? Looks like "admin" user in the image lacks some permissions?
Could it be workarounded via some addtional lines in config.mqsc?

@vgavinash
Copy link
Contributor

MQ Explorer: app on DEV.APP.SVRCONN error
AMQ8077W: Entity 'app' has insufficient authority to access object SYSTEM.MQEXPLORER.REPLY.MODEL [queue]. [CommentInsert1(app), CommentInsert2(SYSTEM.MQEXPLORER.REPLY.MODEL [queue]), CommentInsert3(inq)]

The below link may resolve your issue, please give it a try -

https://www.ibm.com/support/pages/mq-rc-2035-mqrcnotauthorized-or-amq4036-or-jmswmq2013-when-using-client-connection-mq-administrator-chlauth-channel-authentication-records

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants