Queue manager ended unexpectedly - ibm-mq

We are using MQ 9.0.0.1 version on linux machine and it is active/passive configuration.
We have faced issue in production server issue is "queue manager ended unexpectedly" around 10:30 AM IST, we have taken queue manager restart manually post restart everything is normal issue got resolved.
From the Queue manager logs we have observed below error stacks. Request to all,
please provide your analysis from the below queue manager logs why the queue manager ended unexpectedly?
-------------------------------------------------------------------------------
03/07/2019 07:21:10 AM - Process(5082.15855) User(tsg) Program(amqzlaa0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ7234: 20000 messages from queue 'NEFT_SMS_INQUIRY' loaded on queue manager
'QMGR_NEFT'.
EXPLANATION:
20000 messages from queue NEFT_SMS_INQUIRY have been loaded on queue manager
QMGR_NEFT.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5003.1) User(tsg) Program(amqzxma0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5008: An essential IBM MQ process 5016 (zllCRIT) cannot be found and is
assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
IBM MQ will stop all MQ processes. Inform your systems administrator. When
the problem is rectified IBM MQ can be restarted.
----- amqzxmb0.c : 10095 ------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5080.1) User(tsg) Program(amqpcsea)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ8506: Command server MQGET failed with reason code 2009.
EXPLANATION:
An MQGET request by the command server, for the IBM MQ queue
SYSTEM.ADMIN.COMMAND.QUEUE , failed with reason code 2009.
ACTION:
None.
----- amqphrea.c : 86 ---------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5069.1) User(tsg) Program(amqzmgr0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5025: The command server has ended. ProcessId(5080).
EXPLANATION:
The command server process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5051.1) User(tsg) Program(amqrrmfa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrrmfa.c : 3011 -------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5051.1) User(tsg) Program(amqrrmfa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9411: Repository manager ended normally.
EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5047.9) User(tsg) Program(amqzmuf0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5976: 'IBM MQ Distributed Pub/Sub Command Task' has ended.
EXPLANATION:
'IBM MQ Distributed Pub/Sub Command Task' has ended.
ACTION:
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5047.10) User(tsg) Program(amqzmuf0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5976: 'IBM MQ Distributed Pub/Sub Publish Task' has ended.
EXPLANATION:
'IBM MQ Distributed Pub/Sub Publish Task' has ended.
ACTION:
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5047.8) User(tsg) Program(amqzmuf0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5976: 'IBM MQ Distributed Pub/Sub Fan Out Task' has ended.
EXPLANATION:
'IBM MQ Distributed Pub/Sub Fan Out Task' has ended.
ACTION:
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5047.7) User(tsg) Program(amqzmuf0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5976: 'IBM MQ Distributed Pub/Sub Controller' has ended.
EXPLANATION:
'IBM MQ Distributed Pub/Sub Controller' has ended.
ACTION:
-------------------------------------------------------------------------------
03/07/2019 10:30:15 AM - Process(31712.199) User(tsg) Program(amqrmppa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QMGR_NEFT' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- cmqxrmsa.c : 6146 -------------------------------------------------------
03/07/2019 10:30:15 AM - Process(31712.199) User(tsg) Program(amqrmppa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9772: MQCTL failed with MQRC=2009.
EXPLANATION:
The indicated IBM MQ API call failed for the specified reason code.
ACTION:
Refer to the Application Programming Reference manual for information about
Reason Code 2009.
----- cmqxrstf.c : 2663 -------------------------------------------------------
03/07/2019 10:30:15 AM - Process(31712.199) User(tsg) Program(amqrmppa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9999: Channel 'GPSSVRCONN' to host 'XXXXXX' ended abnormally.
EXPLANATION:
The channel program running under process ID 31712 for channel 'GPSSVRCONN'
ended abnormally. The host name is 'XXXXXX'; in some cases the host name
cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5081.5) User(tsg) Program(runmqlsr)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'QMGR_NEFT' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- cmqxrmsa.c : 471 --------------------------------------------------------
03/07/2019 10:30:15 AM - Process(5081.5) User(tsg) Program(runmqlsr)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9999: Channel 'GPSSVRCONN' to host 'XXXXXX' ended abnormally.
EXPLANATION:
The channel program running under process ID 5081 for channel 'GPSSVRCONN''
ended abnormally. The host name is 'XXXXXX'; in some cases the host name
cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
03/07/2019 10:30:17 AM - Process(5078.1) User(tsg) Program(runmqchi)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9510: Messages cannot be retrieved from a queue.
EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CHANNEL.INITQ' on queue manager
'QMGR_NEFT' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
----- amqrimna.c : 1085 -------------------------------------------------------
03/07/2019 10:30:18 AM - Process(5069.1) User(tsg) Program(amqzmgr0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5023: The channel initiator has ended. ProcessId(5078).
EXPLANATION:
The channel initiator process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:24 AM - Process(31712.192) User(tsg) Program(amqrmppa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9540: Commit failed.
EXPLANATION:
The program ended because return code 2009 was received when an attempt was
made to commit change to the resource managers. The commit ID was
'AMQRMRSASFMS.TO.IPAYNEFT XXXXXX E怜͇'.
ACTION:
Tell the systems administrator.
----- amqrmrca.c : 2977 -------------------------------------------------------
03/07/2019 10:30:24 AM - Process(31712.192) User(tsg) Program(amqrmppa)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ9999: Channel 'SFMS.TO.IPAYNEFT' to host 'XXXXXX' ended abnormally.
EXPLANATION:
The channel program running under process ID 31712 for channel
'SFMS.TO.IPAYNEFT' ended abnormally. The host name is 'XXXXXX'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
03/07/2019 10:30:24 AM - Process(5071.1) User(tsg) Program(amqfqpub)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5807: Queued Publish/Subscribe Daemon for queue manager QMGR_NEFT ended.
EXPLANATION:
The Queued Publish/Subscribe Daemon on queue manager QMGR_NEFT has ended.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:24 AM - Process(5003.1) User(tsg) Program(amqzxma0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5050: An essential IBM MQ process 5071 (amqfqpub) cannot be found and is
assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created. 3) MQ has encountered an unexpected
error. Check for possible errors reported in the MQ error logs and for any
FFSTs that have been generated.
ACTION:
IBM MQ will attempt to restart the terminated process.
----- amqzxmb0.c : 10095 ------------------------------------------------------
03/07/2019 10:30:24 AM - Process(5003.1) User(tsg) Program(amqzxma0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ8004: IBM MQ queue manager 'QMGR_NEFT' ended.
EXPLANATION:
IBM MQ queue manager 'QMGR_NEFT' ended.
ACTION:
None.
-------------------------------------------------------------------------------
03/07/2019 10:30:25 AM - Process(5069.1) User(tsg) Program(amqzmgr0)
Host(xxxxxxx) Installation(Installation1)
VRMF(9.0.0.1) QMgr(QMGR_NEFT)
AMQ5027: The listener 'LISTENER.TCP' has ended. ProcessId(5081).
EXPLANATION:
The listener process has ended.
ACTION:
None.
-------------------------------------------------------------------------------

Related

Docker : Unable to access the IBM MQ web management console

I followed the article - https://github.com/nuviosoftware/custom-ibm-mq and deployed the container using the below commands in my windows laptop using docker for desktop
docker build -t nuviosoftware-mq-local .
docker volume create qm1data
and executed
docker run --env LICENSE=accept --env MQ_QMGR_NAME=QM1 --volume qm1data:/mnt/mqm --publish 1414:1414 --publish 9443:9443 --env MQ_APP_PASSWORD=passw0rd nuviosoftware-mq-local
below is the container log
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (windows/amd64) and no specific platform was requested
2021-07-15T08:58:20.659Z CPU architecture: amd64
2021-07-15T08:58:20.659Z Linux kernel version: 4.19.27-linuxkit
2021-07-15T08:58:20.661Z Base image: Red Hat Enterprise Linux 8.3 (Ootpa)
2021-07-15T08:58:20.661Z Running as user ID 0 with primary group 0
2021-07-15T08:58:20.661Z Capabilities (bounding set): chown,dac_override,fowner,fsetid,kill,setgid,setuid,setpcap,net_bind_service,net_raw,sys_chroot,mknod,audit_write,setfcap
2021-07-15T08:58:20.661Z seccomp enforcing mode: disabled
2021-07-15T08:58:20.661Z Process security attributes: none
2021-07-15T08:58:20.661Z Detected '9p' volume mounted to /mnt/mqm
2021-07-15T08:58:25.540Z Using queue manager name: QM1
2021-07-15T08:58:27.316Z Created directory structure under /var/mqm
2021-07-15T08:58:27.316Z Image created: 2021-03-12T09:57:54+00:00
2021-07-15T08:58:27.316Z Image tag: ibm-mqadvanced-server-dev:9.2.2.0-r1.20210312094918.14987c1-amd64
2021-07-15T08:58:27.794Z MQ version: 9.2.2.0
2021-07-15T08:58:27.794Z MQ level: p922-L210310.DE
2021-07-15T08:58:27.794Z MQ license: Developer
2021-07-15T08:58:29.405Z Creating queue manager QM1
2021-07-15T08:58:29.405Z Starting web server
2021-07-15T08:58:29.652Z Detected existing queue manager QM1
2021-07-15T08:58:29.675Z Error 126 starting web server: AMQ5061E: Program 'strmqweb' cannot be run with root privileges.
2021-07-15T08:58:29.675Z Error starting web server: exit status 126
2021-07-15T08:58:29.982Z Removing existing ServiceComponent configuration
2021-07-15T08:58:29.991Z Starting queue manager
2021-07-15T08:58:31.031Z AMQ5657W: The system resource RLIMIT_NOFILE is set at an unusually low level for IBM MQ. [ArithInsert1(1024), ArithInsert2(10240), CommentInsert1(RLIMIT_NOFILE)]
2021-07-15T08:58:31.216Z AMQ5657W: The system resource RLIMIT_NPROC is set at an unusually low level for IBM MQ. [ArithInsert1(3844), ArithInsert2(4096), CommentInsert1(RLIMIT_NPROC)]
2021-07-15T08:58:31.962Z AMQ5775I: Successfully applied automatic configuration INI definitions. [CommentInsert1(INI)]
2021-07-15T08:58:36.368Z Initializing MQ Advanced for Developers custom authentication service
2021-07-15T08:58:39.939Z AMQ5051I: The queue manager task 'LOGGER-IO' has started. [ArithInsert2(1), CommentInsert1(LOGGER-IO)]
2021-07-15T08:58:42.052Z AMQ7229I: 6 log records accessed on queue manager 'QM1' during the log replay phase. [ArithInsert1(6), CommentInsert1(QM1)]
2021-07-15T08:58:42.104Z AMQ7230I: Log replay for queue manager 'QM1' complete. [ArithInsert1(6), CommentInsert1(QM1)]
2021-07-15T08:58:42.244Z AMQ5051I: The queue manager task 'CHECKPOINT' has started. [ArithInsert2(1), CommentInsert1(CHECKPOINT)]
2021-07-15T08:58:42.359Z AMQ7231I: 0 log records accessed on queue manager 'QM1' during the recovery phase. [CommentInsert1(QM1)]
2021-07-15T08:58:42.405Z AMQ7232I: Transaction manager state recovered for queue manager 'QM1'. [CommentInsert1(QM1)]
2021-07-15T08:58:42.542Z AMQ7233I: 0 out of 0 in-flight transactions resolved for queue manager 'QM1'. [CommentInsert1(QM1)]
2021-07-15T08:58:43.559Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(1), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.603Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(2), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.643Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(3), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.689Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(4), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.731Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(5), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.793Z AMQ5037I: The queue manager task 'ERROR-LOG' has started. [ArithInsert2(1), CommentInsert1(ERROR-LOG)]
2021-07-15T08:58:43.822Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(6), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.849Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(7), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:43.896Z AMQ5037I: The queue manager task 'APP-SIGNAL' has started. [ArithInsert2(8), CommentInsert1(APP-SIGNAL)]
2021-07-15T08:58:45.037Z AMQ8003I: IBM MQ queue manager 'QM1' started using V9.2.2.0. [CommentInsert1(9.2.2.0), CommentInsert3(QM1)]
2021-07-15T08:58:45.551Z AMQ5051I: The queue manager task 'DUR-SUBS-MGR' has started. [ArithInsert2(1), CommentInsert1(DUR-SUBS-MGR)]
2021-07-15T08:58:45.559Z AMQ9410I: Repository manager started.
2021-07-15T08:58:45.643Z AMQ5051I: The queue manager task 'TOPIC-TREE' has started. [ArithInsert2(1), CommentInsert1(TOPIC-TREE)]
2021-07-15T08:58:45.689Z AMQ5024I: The command server has started. ProcessId(135). [ArithInsert1(135), CommentInsert1(SYSTEM.CMDSERVER.1)]
2021-07-15T08:58:45.758Z AMQ5022I: The channel initiator has started. ProcessId(137). [ArithInsert1(137), CommentInsert1(SYSTEM.CHANNEL.INITQ)]
2021-07-15T08:58:45.802Z AMQ5051I: The queue manager task 'AUTOCONFIG' has started. [ArithInsert2(1), CommentInsert1(AUTOCONFIG)]
2021-07-15T08:58:45.838Z AMQ5051I: The queue manager task 'IQM-COMMS-MANAGER' has started. [ArithInsert2(1), CommentInsert1(IQM-COMMS-MANAGER)]
2021-07-15T08:58:46.262Z AMQ8942I: Starting to process automatic MQSC configuration script.
2021-07-15T08:58:46.291Z AMQ8024I: IBM MQ channel initiator started. [CommentInsert1(SYSTEM.CHANNEL.INITQ)]
2021-07-15T08:58:59.758Z AMQ8939I: Automatic MQSC configuration script has completed, and contained 24 command(s), of which 0 had errors. [ArithInsert1(24), CommentInsert1(0)]
2021-07-15T08:58:59.809Z AMQ5051I: The queue manager task 'ACTVTRC' has started. [ArithInsert2(1), CommentInsert1(ACTVTRC)]
2021-07-15T08:58:59.818Z AMQ5037I: The queue manager task 'DEFERRED_DELIVERY' has started. [ArithInsert2(1), CommentInsert1(DEFERRED_DELIVERY)]
2021-07-15T08:58:59.831Z AMQ5052I: The queue manager task 'QPUBSUB-CTRLR' has started. [ArithInsert2(1), CommentInsert1(QPUBSUB-CTRLR)]
2021-07-15T08:58:59.840Z AMQ5051I: The queue manager task 'EXPIRER' has started. [ArithInsert2(1), CommentInsert1(EXPIRER)]
2021-07-15T08:58:59.846Z AMQ5037I: The queue manager task 'DEFERRED-MSG' has started. [ArithInsert2(1), CommentInsert1(DEFERRED-MSG)]
2021-07-15T08:58:59.859Z AMQ5052I: The queue manager task 'QPUBSUB-SUBPT-NLCACHE' has started. [ArithInsert2(1), CommentInsert1(QPUBSUB-SUBPT-NLCACHE)]
2021-07-15T08:58:59.867Z AMQ5051I: The queue manager task 'Q-DELETION' has started. [ArithInsert2(1), CommentInsert1(Q-DELETION)]
2021-07-15T08:58:59.879Z AMQ5052I: The queue manager task 'QPUBSUB-QUEUE-NLCACHE' has started. [ArithInsert2(1), CommentInsert1(QPUBSUB-QUEUE-NLCACHE)]
2021-07-15T08:58:59.882Z AMQ5037I: The queue manager task 'STATISTICS' has started. [ArithInsert2(1), CommentInsert1(STATISTICS)]
2021-07-15T08:58:59.892Z AMQ5051I: The queue manager task 'ASYNCQ' has started. [ArithInsert2(1), CommentInsert1(ASYNCQ)]
2021-07-15T08:58:59.915Z AMQ5051I: The queue manager task 'RESOURCE_MONITOR' has started. [ArithInsert2(1), CommentInsert1(RESOURCE_MONITOR)]
2021-07-15T08:58:59.918Z AMQ5037I: The queue manager task 'MARKINTSCAN' has started. [ArithInsert2(1), CommentInsert1(MARKINTSCAN)]
2021-07-15T08:58:59.930Z AMQ5052I: The queue manager task 'PUBSUB-DAEMON' has started. [ArithInsert2(1), CommentInsert1(PUBSUB-DAEMON)]
2021-07-15T08:58:59.930Z AMQ5975I: 'IBM MQ Distributed Pub/Sub Controller' has started. [CommentInsert1(IBM MQ Distributed Pub/Sub Controller)]
2021-07-15T08:58:59.966Z AMQ5026I: The listener 'SYSTEM.LISTENER.TCP.1' has started. ProcessId(174). [ArithInsert1(174), CommentInsert1(SYSTEM.LISTENER.TCP.1)]
2021-07-15T08:58:59.984Z AMQ5051I: The queue manager task 'PRESERVED-Q' has started. [ArithInsert2(1), CommentInsert1(PRESERVED-Q)]
2021-07-15T08:59:00.011Z AMQ5051I: The queue manager task 'MULTICAST' has started. [ArithInsert2(1), CommentInsert1(MULTICAST)]
2021-07-15T08:59:00.142Z Started queue manager
2021-07-15T08:59:00.142Z Metrics are disabled
2021-07-15T08:59:00.225Z AMQ5975I: 'IBM MQ Distributed Pub/Sub Command Task' has started. [CommentInsert1(IBM MQ Distributed Pub/Sub Command Task)]
2021-07-15T08:59:00.279Z AMQ5975I: 'IBM MQ Distributed Pub/Sub Publish Task' has started. [CommentInsert1(IBM MQ Distributed Pub/Sub Publish Task)]
2021-07-15T08:59:00.294Z AMQ5975I: 'IBM MQ Distributed Pub/Sub Fan Out Task' has started. [CommentInsert1(IBM MQ Distributed Pub/Sub Fan Out Task)]
2021-07-15T08:59:00.498Z AMQ5806I: Queued Publish/Subscribe Daemon started for queue manager QM1. [CommentInsert1(QM1)]
2021-07-15T08:59:07.843Z AMQ5041I: The queue manager task 'AUTOCONFIG' has ended. [CommentInsert1(AUTOCONFIG)]
however I could access the web management console
as well as I could not connect with the MQ from the client application
2021-07-15 14:31:40.922 ERROR 4884 --- [enerContainer-1] o.s.j.l.DefaultMessageListenerContainer : Could not refresh JMS Connection for destination 'ORDER.RESPONSE' - retrying using FixedBackOff{interval=5000, currentAttempts=0, maxAttempts=unlimited}. Cause: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'QM1' with connection mode 'Client' and host name 'localhost(1414)'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
2021-07-15 14:31:47.368 ERROR 4884 --- [enerContainer-1] o.s.j.l.DefaultMessageListenerContainer : Could not refresh JMS Connection for destination 'ORDER.RESPONSE' - retrying using FixedBackOff{interval=5000, currentAttempts=1, maxAttempts=unlimited}. Cause: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'QM1' with connection mode 'Client' and host name 'localhost(1414)'.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')
try to access it through with https:
https://localhost:9443/ibmmq/console
I was using the windows mode and switched to Linux mod, it worked.

Setting up a RocketMQ cluster: slave not visible & not replicating

I'm trying to set up a RocketMQ cluster, with a single name server, 1 master and 2 slaves. But, I'm running into some problems.
The version I'm running is downloaded from github/rocketmq-all-4.1.0-incubating.zip.
The brokers are run using mqbroker -c broker.conf, where broker.conf
differs for master and slave. For the master I have:
listenPort=10911
brokerName=mybroker
brokerClusterName=mybrokercluster
brokerId=0
deleteWhen=04
fileReservedTime=48
brokerRole=SYNC_MASTER
flushDiskType=ASYNC_FLUSH
And for slaves:
listenPort=10911
brokerName=mybroker
brokerClusterName=mybrokercluster
brokerId=1
deleteWhen=04
fileReservedTime=48
brokerRole=SLAVE
flushDiskType=ASYNC_FLUSH
The second slave has brokerId=2.
Brokers start up fine, some parts of the logs for a slave:
2017-10-02 20:31:35 INFO main - brokerRole=ASYNC_MASTER
2017-10-02 20:31:35 INFO main - flushDiskType=ASYNC_FLUSH
(...)
2017-10-02 20:31:35 INFO main - Replace, key: brokerId, value: 0 -> 1
2017-10-02 20:31:35 INFO main - Replace, key: brokerRole, value:
ASYNC_MASTER -> SLAVE
(...)
2017-10-02 20:31:37 INFO main - Set user specified name server address:
172.22.1.38:9876
2017-10-02 20:31:37 INFO ShutdownHook - Shutdown hook was invoked, 1
2017-10-02 20:31:37 INFO ShutdownHook - shutdown thread
PullRequestHoldService interrupt false
2017-10-02 20:31:37 INFO ShutdownHook - join thread PullRequestHoldService
eclipse time(ms) 0 90000
2017-10-02 20:31:37 WARN ShutdownHook - unregisterBroker Exception,
172.22.1.38:9876
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to
<172.22.1.38:9876> failed
at
org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:359)
~[rocketmq-remoting-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.out.BrokerOuterAPI.unregisterBroker(BrokerOuterAPI.java:221)
~[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.out.BrokerOuterAPI.unregisterBrokerAll(BrokerOuterAPI.java:198)
~[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.BrokerController.unregisterBrokerAll(BrokerController.java:623)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.BrokerController.shutdown(BrokerController.java:589)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at org.apache.rocketmq.broker.BrokerStartup$1.run(BrokerStartup.java:218)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_141]
2017-10-02 20:31:37 INFO ShutdownHook - Shutdown hook over, consuming total
time(ms): 25
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - dispatch behind
commit log 0 bytes
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - Slave fall
behind master: 0 bytes
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - register broker
to name server 172.22.1.38:9876 OK
2017-10-02 20:32:15 INFO BrokerControllerScheduledThread1 - register broker
to name server 172.22.1.38:9876 OK
As I suspect the broker is trying to connect to the name server, which
isn't running initially, so it retries and eventually succeeds?
However, later when trying clusterList I only see one broker listed, which happens to be a slave (172.22.1.17) and has brokerId=2 in the configuration (although here it's listed as 0):
$ ./mqadmin clusterList -n 172.22.1.38:9876
#Cluster Name #Broker Name #BID #Addr
#Version #InTPS(LOAD) #OutTPS(LOAD) #PCWait(ms) #Hour
#SPACE
mybrokercluster mybroker 0 172.22.1.17:10911
V4_1_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0
418597.80 -1.0000
Moreover, when sending messages to the master, I get SLAVE_NOT_AVAILABLE.
Why is that? Are the brokers configured properly? If so, wy does
clusterList report them incorrectly?
you should change slave port,as you know 10911 has been used by anthoer process(master node),slave should be use different tcp port(eg.10921/10931 and so on)
tips:my cluster deploy on one machine,so i changed tcp port and startup successful,if you master&slave deploy on different machine and startup failed,you should visit rocketmq error log for more information.
notice:one master which have more than one slave,brokerId should be different

AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

Im using Qpid JMS 0.8.0 library in order to implement a standalone java AMQP client. Because the underlying transport connection tends to break every couple of hours I have set the reconnection using following configuration:
failover:(amqps://someurl:5671)?failover.reconnectDelay=2000&failover.warnAfterReconnectAttempts=1
In accordance with Qpid client configuration explanation page I expect my client to keep trying to reconnect increasing the attempt delays for factor 2 (starting with 2 seconds). Instead, according to the log file, only two attempts to reconnect have been performed when a connection failure was detected and at the end the whole client application has been terminated, what I definitively would like to avoid! Here is the log file:
2016-03-22 14:29:40 INFO AmqpProvider:1190 - IdleTimeoutCheck closed the transport due to the peer exceeding our requested idle-timeout.
2016-03-22 14:29:40 DEBUG FailoverProvider:761 - Failover: the provider reports failure: Transport closed due to the peer exceeding our requested idle-timeout
2016-03-22 14:29:40 DEBUG FailoverProvider:519 - handling Provider failure: Transport closed due to the peer exceeding our requested idle-timeout
2016-03-22 14:29:40 DEBUG FailoverProvider:653 - Connection attempt:[1] to: amqps://publish.preops.nm.eurocontrol.int:5671 in-progress
2016-03-22 14:29:40 INFO FailoverProvider:659 - Connection attempt:[1] to: amqps://publish.preops.nm.eurocontrol.int:5671 failed
2016-03-22 14:29:40 WARN FailoverProvider:686 - Failed to connect after: 1 attempt(s) continuing to retry.
2016-03-22 14:29:42 DEBUG FailoverProvider:653 - Connection attempt:[2] to: amqps://publish.preops.nm.eurocontrol.int:5671 in-progress
2016-03-22 14:29:42 INFO FailoverProvider:659 - Connection attempt:[2] to: amqps://publish.preops.nm.eurocontrol.int:5671 failed
2016-03-22 14:29:42 WARN FailoverProvider:686 - Failed to connect after: 2 attempt(s) continuing to retry.
2016-03-22 14:29:43 DEBUG ThreadPoolUtils:156 - Shutdown of ExecutorService: java.util.concurrent.ThreadPoolExecutor#778970af[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] is shutdown: true and terminated: true took: 0.000 seconds.
2016-03-22 14:29:45 DEBUG ThreadPoolUtils:192 - Waited 2.004 seconds for ExecutorService: java.util.concurrent.ScheduledThreadPoolExecutor#877a470[Shutting down, pool size = 1, active threads = 0, queued tasks = 1, completed tasks = 3] to terminate...
2016-03-22 14:29:46 DEBUG ThreadPoolUtils:156 - Shutdown of ExecutorService: java.util.concurrent.ScheduledThreadPoolExecutor#877a470[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 4] is shutdown: true and terminated: true took: 2.889 seconds.
Any idea, what I’m doing wrong here? Basically, what I'm looking for to achieve is a client which is capable to detect transport connection failure and try to reconnect every 5-10 seconds.
Many thanks!

SonarQube not running on CentOS

I'm currently trying to install sonarqube on my VM which runs CentOS.
I'm just running ./sonar.sh start or ./sonar.sh console but I get the following error:
Spawning intermediate process...
Spawning daemon process...
--> Wrapper Started as Daemon
Using tick timer.
server listening on port 32000.
Command[0] : /usr/java/jdk1.8.0_40/bin/java
Command[1] : -Djava.awt.headless=true
Command[2] : -Xms3m
Command[3] : -Xmx32m
Command[4] : -Djava.library.path=./lib
Command[5] : -classpath
Command[6] : ../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-5.1.1.jar
Command[7] : -Dwrapper.key=YJaZZIwuLc49FoZw
Command[8] : -Dwrapper.port=32000
Command[9] : -Dwrapper.jvm.port.min=31000
Command[10] : -Dwrapper.jvm.port.max=31999
Command[11] : -Dwrapper.debug=TRUE
Command[12] : -Dwrapper.pid=8925
Command[13] : -Dwrapper.version=3.2.3
Command[14] : -Dwrapper.native_library=wrapper
Command[15] : -Dwrapper.service=TRUE
Command[16] : -Dwrapper.cpu.timeout=10
Command[17] : -Dwrapper.jvmid=1
Command[18] : org.tanukisoftware.wrapper.WrapperSimpleApp
Command[19] : org.sonar.application.App
Launching a JVM...
WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader#4e25154f
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
Wrapper Manager: JVM #1
Running a 64-bit JVM.
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Load native library. One or more attempts may fail if platform specific libraries do not exist.
Loading native library failed: libwrapper-linux-x86-64.so Cause: java.lang.UnsatisfiedLinkError: no wrapper-linux-x86-64 in java.library.path
Loaded native library: libwrapper.so
Calling native initialization method.
Inside native WrapperManager initialization method
Java Version : 1.8.0_40-b25 Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor : Oracle Corporation
Control event monitor thread started.
Startup runner thread started.
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp#4a574795, args[]) called by thread: main
Communications runner thread started.
Open socket to wrapper...Wrapper-Connection
Opened Socket from 31000 to 32000
Send a packet KEY : YJaZZIwuLc49FoZw
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
accepted a socket from 127.0.0.1 on port 31000
read a packet KEY : YJaZZIwuLc49FoZw
Got key from JVM: YJaZZIwuLc49FoZw
send a packet LOW_LOG_LEVEL : 0
send a packet PING_TIMEOUT : 0
send a packet PROPERTIES : (Property Values)
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 0
Wrapper Manager: LowLogLevel from Wrapper is 0
Received a packet PING_TIMEOUT : 0
PingTimeout from Wrapper is 0
Received a packet PROPERTIES : (Property Values)
Received a packet START : start
calling WrapperListener.start()
Waiting for WrapperListener.start runner thread to complete.
WrapperListener.start runner thread started.
WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
WrapperSimpleApp: invoking main method
Wrapper Manager: ShutdownHook started
WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
Send a packet STOP : 0
Startup runner thread stopped.
read a packet STOP : 0
JVM requested a shutdown. (0)
wrapperStopProcess(0) called.
Sending stop signal to JVM
send a packet STOP : NULL
Send a packet START_PENDING : 5000
read a packet START_PENDING : 5000
JVM signalled a start pending with waitHint of 5000 millis.
Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
Send a packet STOPPED : 0
read a packet STOPPED : 0
JVM signalled that it was stopped.
Closing socket.
socket read no code (closed?).
server listening on port 32001.
JVM exited normally.
Signal trapped. Details:
signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
Wrapper Manager: ShutdownHook complete
Send a packet START_PENDING : 5000
WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null
WrapperListener.start runner thread stopped.
returned from WrapperListener.start()
Send a packet STARTED :
Server daemon shut down
<-- Wrapper Stopped
Spawning intermediate process...
Spawning daemon process...
--> Wrapper Started as Daemon
Using tick timer.
server listening on port 32000.
Command[0] : /usr/java/jdk1.8.0_40/bin/java
Command[1] : -Djava.awt.headless=true
Command[2] : -Xms3m
Command[3] : -Xmx32m
Command[4] : -Djava.library.path=./lib
Command[5] : -classpath
Command[6] : ../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-5.1.1.jar
Command[7] : -Dwrapper.key=M_r8LVkidRlWI7_b
Command[8] : -Dwrapper.port=32000
Command[9] : -Dwrapper.jvm.port.min=31000
Command[10] : -Dwrapper.jvm.port.max=31999
Command[11] : -Dwrapper.debug=TRUE
Command[12] : -Dwrapper.pid=9032
Command[13] : -Dwrapper.version=3.2.3
Command[14] : -Dwrapper.native_library=wrapper
Command[15] : -Dwrapper.service=TRUE
Command[16] : -Dwrapper.cpu.timeout=10
Command[17] : -Dwrapper.jvmid=1
Command[18] : org.tanukisoftware.wrapper.WrapperSimpleApp
Command[19] : org.sonar.application.App
Launching a JVM...
WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader#4e25154f
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
Wrapper Manager: JVM #1
Running a 64-bit JVM.
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Load native library. One or more attempts may fail if platform specific libraries do not exist.
Loading native library failed: libwrapper-linux-x86-64.so Cause: java.lang.UnsatisfiedLinkError: no wrapper-linux-x86-64 in java.library.path
Loaded native library: libwrapper.so
Calling native initialization method.
Inside native WrapperManager initialization method
Java Version : 1.8.0_40-b25 Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor : Oracle Corporation
Control event monitor thread started.
Startup runner thread started.
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp#4a574795, args[]) called by thread: main
Communications runner thread started.
Open socket to wrapper...Wrapper-Connection
Opened Socket from 31000 to 32000
Send a packet KEY : M_r8LVkidRlWI7_b
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
accepted a socket from 127.0.0.1 on port 31000
read a packet KEY : M_r8LVkidRlWI7_b
Got key from JVM: M_r8LVkidRlWI7_b
send a packet LOW_LOG_LEVEL : 0
send a packet PING_TIMEOUT : 0
send a packet PROPERTIES : (Property Values)
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 0
Wrapper Manager: LowLogLevel from Wrapper is 0
Received a packet PING_TIMEOUT : 0
PingTimeout from Wrapper is 0
Received a packet PROPERTIES : (Property Values)
Received a packet START : start
calling WrapperListener.start()
Waiting for WrapperListener.start runner thread to complete.
WrapperListener.start runner thread started.
WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
WrapperSimpleApp: invoking main method
Wrapper Manager: ShutdownHook started
WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
Send a packet STOP : 0
Startup runner thread stopped.
read a packet STOP : 0
JVM requested a shutdown. (0)
wrapperStopProcess(0) called.
Sending stop signal to JVM
send a packet STOP : NULL
Send a packet START_PENDING : 5000
read a packet START_PENDING : 5000
JVM signalled a start pending with waitHint of 5000 millis.
Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
Send a packet STOPPED : 0
read a packet STOPPED : 0
JVM signalled that it was stopped.
Closing socket.
socket read no code (closed?).
server listening on port 32001.
JVM exited normally.
Signal trapped. Details:
signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
Wrapper Manager: ShutdownHook complete
Send a packet START_PENDING : 5000
WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null
WrapperListener.start runner thread stopped.
returned from WrapperListener.start()
Send a packet STARTED :
Server daemon shut down
<-- Wrapper Stopped
Spawning intermediate process...
Spawning daemon process...
--> Wrapper Started as Daemon
Using tick timer.
server listening on port 32000.
Command[0] : /usr/java/jdk1.8.0_40/bin/java
Command[1] : -Djava.awt.headless=true
Command[2] : -Xms3m
Command[3] : -Xmx32m
Command[4] : -Djava.library.path=./lib
Command[5] : -classpath
Command[6] : ../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-5.1.1.jar
Command[7] : -Dwrapper.key=90kxlGkfiFFf0qJi
Command[8] : -Dwrapper.port=32000
Command[9] : -Dwrapper.jvm.port.min=31000
Command[10] : -Dwrapper.jvm.port.max=31999
Command[11] : -Dwrapper.debug=TRUE
Command[12] : -Dwrapper.pid=10211
Command[13] : -Dwrapper.version=3.2.3
Command[14] : -Dwrapper.native_library=wrapper
Command[15] : -Dwrapper.service=TRUE
Command[16] : -Dwrapper.cpu.timeout=10
Command[17] : -Dwrapper.jvmid=1
Command[18] : org.tanukisoftware.wrapper.WrapperSimpleApp
Command[19] : org.sonar.application.App
Launching a JVM...
Unable to start JVM: No such file or directory (2)
Signal trapped. Details:
signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 1, setting the wrapper exit code to 1.
JVM exited while loading the application.
JVM Restarts disabled. Shutting down.
<-- Wrapper Stopped
--> Wrapper Started as Console
Using tick timer.
server listening on port 32000.
Command[0] : /usr/java/jdk1.8.0_40/bin/java
Command[1] : -Djava.awt.headless=true
Command[2] : -Xms3m
Command[3] : -Xmx32m
Command[4] : -Djava.library.path=./lib
Command[5] : -classpath
Command[6] : ../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-5.1.1.jar
Command[7] : -Dwrapper.key=pQGEkNJknvC5D5wq
Command[8] : -Dwrapper.port=32000
Command[9] : -Dwrapper.jvm.port.min=31000
Command[10] : -Dwrapper.jvm.port.max=31999
Command[11] : -Dwrapper.debug=TRUE
Command[12] : -Dwrapper.pid=10259
Command[13] : -Dwrapper.version=3.2.3
Command[14] : -Dwrapper.native_library=wrapper
Command[15] : -Dwrapper.cpu.timeout=10
Command[16] : -Dwrapper.jvmid=1
Command[17] : org.tanukisoftware.wrapper.WrapperSimpleApp
Command[18] : org.sonar.application.App
Launching a JVM...
Unable to start JVM: No such file or directory (2)
Signal trapped. Details:
signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 1, setting the wrapper exit code to 1.
JVM exited while loading the application.
wrapper | Unable to start JVM: No such file or directory (2)
JVM Restarts disabled. Shutting down.
<-- Wrapper Stopped
Any suggestions on what may be my problem?
I'll post my sonar.properties and wrapper.conf files below:
# This file must contain only ISO 8859-1 characters.
# See http://docs.oracle.com/javase/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream)
#
# Property values can:
# - reference an environment variable, for example sonar.jdbc.url= ${env:SONAR_JDBC_URL}
# - be encrypted. See http://redirect.sonarsource.com/doc/settings-encryption.html
#--------------------------------------------------------------------------------------------------
# DATABASE
#
# IMPORTANT: the embedded H2 database is used by default. It is recommended for tests but not for
# production use. Supported databases are MySQL, Oracle, PostgreSQL and Microsoft SQLServer.
# User credentials.
# Permissions to create tables, indices and triggers must be granted to JDBC user.
# The schema must be created first.
sonar.jdbc.username=root
sonar.jdbc.password=
#----- Embedded Database (default)
# It does not accept connections from remote hosts, so the
# server and the analyzers must be executed on the same host.
sonar.jdbc.url=jdbc:h2:tcp://localhost:9092/sonar
# H2 embedded database server listening port, defaults to 9092
sonar.embeddedDatabase.port=9092
#----- MySQL 5.x
# Only InnoDB storage engine is supported (not myISAM).
# Only the bundled driver is supported.
#sonar.jdbc.driverClassName=net.sourceforge.jtds.jdbc.Driver
#sonar.jdbc.url=jdbc:mysql://localhost:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance
#----- Oracle 10g/11g
# - Only thin client is supported
# - Only versions 11.2.* of Oracle JDBC driver are supported, even if connecting to lower Oracle versions.
# - The JDBC driver must be copied into the directory extensions/jdbc-driver/oracle/
# - If you need to set the schema, please refer to http://jira.codehaus.org/browse/SONAR-5000
#sonar.jdbc.url=jdbc:oracle:thin:#localhost/XE
#----- PostgreSQL 8.x/9.x
# If you don't use the schema named "public", please refer to http://jira.codehaus.org/browse/SONAR-5000
#sonar.jdbc.url=jdbc:postgresql://localhost/sonar
#----- Microsoft SQLServer 2008/2012
# Only the bundled jTDS driver is supported.
# Collation must be case-sensitive (CS) and accent-sensitive (AS).
#sonar.jdbc.url=jdbc:jtds:sqlserver://localhost/sonar;SelectMethod=Cursor
#----- Connection pool settings
# The maximum number of active connections that can be allocated
# at the same time, or negative for no limit.
sonar.jdbc.maxActive=50
# The maximum number of connections that can remain idle in the
# pool, without extra ones being released, or negative for no limit.
sonar.jdbc.maxIdle=5
# The minimum number of connections that can remain idle in the pool,
# without extra ones being created, or zero to create none.
sonar.jdbc.minIdle=2
# The maximum number of milliseconds that the pool will wait (when there
# are no available connections) for a connection to be returned before
# throwing an exception, or <= 0 to wait indefinitely.
sonar.jdbc.maxWait=5000
sonar.jdbc.minEvictableIdleTimeMillis=600000
sonar.jdbc.timeBetweenEvictionRunsMillis=30000
#--------------------------------------------------------------------------------------------------
# WEB SERVER
# Web server is executed in a dedicated Java process. By default heap size is 768Mb.
# Use the following property to customize JVM options.
# Recommendations:
#
# The HotSpot Server VM is recommended. The property -server should be added if server mode
# is not enabled by default on your environment: http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html
#
# Set min and max memory (respectively -Xms and -Xmx) to the same value to prevent heap
# from resizing at runtime.
#
sonar.web.javaOpts=-Xmx768m -XX:MaxPermSize=160m -XX:+HeapDumpOnOutOfMemoryError -server
# Same as previous property, but allows to not repeat all other settings like -Xmx
#sonar.web.javaAdditionalOpts=
# Binding IP address. For servers with more than one IP address, this property specifies which
# address will be used for listening on the specified ports.
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=127.0.0.1
# Web context. When set, it must start with forward slash (for example /sonarqube).
# The default value is root context (empty value).
sonar.web.context=/sonarqube
# TCP port for incoming HTTP connections. Disabled when value is -1.
sonar.web.port=9000
# The maximum number of connections that the server will accept and process at any given time.
# When this number has been reached, the server will not accept any more connections until
# the number of connections falls below this value. The operating system may still accept connections
# based on the sonar.web.connections.acceptCount property. The default value is 50 for each
# enabled connector.
sonar.web.http.maxThreads=50
#sonar.web.https.maxThreads=50
# The minimum number of threads always kept running. The default value is 5 for each
# enabled connector.
sonar.web.http.minThreads=5
#sonar.web.https.minThreads=5
# The maximum queue length for incoming connection requests when all possible request processing
# threads are in use. Any requests received when the queue is full will be refused.
# The default value is 25 for each enabled connector.
sonar.web.http.acceptCount=25
#sonar.web.https.acceptCount=25
# TCP port for incoming AJP connections. Disabled if value is -1. Disabled by default.
sonar.ajp.port=9000
#--------------------------------------------------------------------------------------------------
# ELASTICSEARCH
# Elasticsearch is used to facilitate fast and accurate information retrieval.
# It is executed in a dedicated Java process.
# JVM options of Elasticsearch process
# Recommendations:
#
# Use HotSpot Server VM. The property -server should be added if server mode
# is not enabled by default on your environment: http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server-class.html
#
# Set min and max memory (respectively -Xms and -Xmx) to the same value to prevent heap
# from resizing at runtime.
#
sonar.search.javaOpts=-Xmx1G -Xms256m -Xss256k -Djava.net.preferIPv4Stack=true \
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 \
-XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
# Same as previous property, but allows to not repeat all other settings like -Xmx
#sonar.search.javaAdditionalOpts=
# Elasticsearch port. Default is 9001. Use 0 to get a free port.
# This port must be private and must not be exposed to the Internet.
sonar.search.port=9001
#--------------------------------------------------------------------------------------------------
# UPDATE CENTER
# Update Center requires an internet connection to request http://update.sonarsource.org
# It is enabled by default.
sonar.updatecenter.activate=true
# HTTP proxy (default none)
#http.proxyHost=
#http.proxyPort=
# NT domain name if NTLM proxy is used
#http.auth.ntlm.domain=
# SOCKS proxy (default none)
#socksProxyHost=
#socksProxyPort=
# proxy authentication. The 2 following properties are used for HTTP and SOCKS proxies.
#http.proxyUser=
#http.proxyPassword=
#--------------------------------------------------------------------------------------------------
# LOGGING
# Level of logs. Supported values are INFO, DEBUG and TRACE
sonar.log.level=TRACE
# Path to log files. Can be absolute or relative to installation directory.
# Default is <installation home>/logs
sonar.path.logs=logs
# Rolling policy of log files
# - based on time if value starts with "time:", for example by day ("time:yyyy-MM-dd")
# or by month ("time:yyyy-MM")
# - based on size if value starts with "size:", for example "size:10MB"
# - disabled if value is "none". That needs logs to be managed by an external system like logrotate.
sonar.log.rollingPolicy=time:yyyy-MM-dd
# Maximum number of files to keep if a rolling policy is enabled.
# - maximum value is 20 on size rolling policy
# - unlimited on time rolling policy. Set to zero to disable old file purging.
sonar.log.maxFiles=20
# Access log is the list of all the HTTP requests received by server. If enabled, it is stored
# in the file {sonar.path.logs}/access.log. This file follows the same rolling policy as for
# sonar.log (see sonar.log.rollingPolicy and sonar.log.maxFiles).
sonar.web.accessLogs.enable=true
# Format of access log. It is ignored if sonar.web.accessLogs.enable=false. Value is:
# - "common" is the Common Log Format (shortcut for: %h %l %u %user %date "%r" %s %b)
# - "combined" is another format widely recognized (shortcut for: %h %l %u [%t] "%r" %s %b "%i{Referer}" "%i{User-Agent}")
# - else a custom pattern. See http://logback.qos.ch/manual/layouts.html#AccessPatternLayout
sonar.web.accessLogs.pattern=combined
#--------------------------------------------------------------------------------------------------
# OTHERS
# Delay in seconds between processing of notification queue. Default is 60 seconds.
sonar.notifications.delay=60
# Paths to persistent data files (embedded database and search index) and temporary files.
# Can be absolute or relative to installation directory.
# Defaults are respectively <installation home>/data and <installation home>/temp
sonar.path.data=data
sonar.path.temp=temp
#--------------------------------------------------------------------------------------------------
# DEVELOPMENT - only for developers
# The following properties MUST NOT be used in production environments.
# Dev mode allows to reload web sources on changes and to restart server when new versions
# of plugins are deployed.
sonar.web.dev=true
# Path to webapp sources for hot-reloading of Ruby on Rails, JS and CSS (only core,
# plugins not supported).
sonar.web.dev.sources=/path/to/server/sonar-web/src/main/webapp
# Uncomment to enable the Elasticsearch HTTP connector, so that ES can be directly requested through
# http://lmenezes.com/elasticsearch-kopf/?location=http://localhost:9010
sonar.search.httpPort=9010
And the wrapper.conf file:
# Path to JVM executable. By default it must be available in PATH.
# Can be an absolute path, for example:
#wrapper.java.command=/path/to/my/jdk/bin/java
#wrapper.java.command=java
wrapper.java.command=/usr/java/jdk1.8.0_40/bin/java
#
# DO NOT EDIT THE FOLLOWING SECTIONS
#
#********************************************************************
# Wrapper Java
#********************************************************************
wrapper.java.additional.1=-Djava.awt.headless=true
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=../../lib/jsw/*.jar
wrapper.java.classpath.2=../../lib/*.jar
wrapper.java.library.path.1=./lib
wrapper.app.parameter.1=org.sonar.application.App
wrapper.java.initmemory=3
# Xmx can't be set to a lower value because of compatibility with Java 6
wrapper.java.maxmemory=32
#********************************************************************
# Wrapper Logs
#********************************************************************
wrapper.console.format=PM
wrapper.console.loglevel=TRACE
wrapper.logfile=../../logs/sonar.log
wrapper.logfile.format=M
wrapper.logfile.loglevel=TRACE
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=10m
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=10
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=DEBUG
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=SonarQube
# Disallow start of multiple instances of an application at the same time on Windows
wrapper.single_invocation=true
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=SonarQube
# Display name of the service
wrapper.ntservice.displayname=SonarQube
# Description of the service
wrapper.ntservice.description=SonarQube
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
#********************************************************************
# Forking Properties
#********************************************************************
wrapper.disable_restarts=TRUE
wrapper.ping.timeout=0
wrapper.shutdown.timeout=3000
wrapper.jvm_exit.timeout=3000
The error log "Unable to start JVM: No such file or directory (2)" means that the path to java executable does not exist. Please check that /usr/java/jdk1.8.0_40/bin/java, as you configured in wrapper.conf, is correctly installed.

Can't start a new Queue-Manager on MQ Explorer

After creating a new Queue-Manager using the MQ Explorer, it's fails to be started properly and provide the following message:
Command: "C:\Program Files (x86)\IBM\WebSphere MQ\bin\crtmqm" -sa test_qm
WebSphere MQ queue manager created.
Directory 'C:\Program Files (x86)\IBM\WebSphere MQ\qmgrs\test_qm'
created.
The queue manager is associated with installation 'WMQ75Install'.
exitvalue = 2059
I couldn't figure out how to solve it from the logs and tried to start it manually from the MQ Explorer and from the command-line shell as well, but without any success - it just not started.
HERE IS MY AMQERR01.LOG TEXT:
21/01/2015 14:18:46 - Process(7960.3) User(johnsmith) Program(amqzmuc0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ6287: WebSphere MQ V7.5.0.2 (p750-002-131001_DE).
EXPLANATION:
WebSphere MQ system information:
Host Info :- Windows 7 Enterprise x64 Edition, Build 7601: SP1 (MQ
Windows 32-bit)
Installation :- C:\Program Files (x86)\IBM\WebSphere MQ (WMQ75Install)
Version :- 7.5.0.2 (p750-002-131001_DE)
ACTION:
None.
21/01/2015 14:18:46 - Process(7960.3) User(johnsmith) Program(amqzmuc0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
21/01/2015 14:18:46 - Process(7960.1) User(johnsmith) Program(amqzmuc0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5041: The queue manager task 'LOGGER-IO' has ended.
EXPLANATION:
The queue manager task LOGGER-IO has ended.
ACTION:
None.
21/01/2015 14:18:49 - Process(7528.3) User(johnsmith) Program(amqzmuc0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5051: The queue manager task 'LOGGER-IO' has started.
EXPLANATION:
The critical utility task manager has started the LOGGER-IO task. This task has
now started 1 times.
ACTION:
None.
21/01/2015 14:18:49 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ7229: 4 log records accessed on queue manager 'test_qm' during the log
replay phase.
EXPLANATION:
4 log records have been accessed so far on queue manager test_qm during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
21/01/2015 14:18:49 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ7230: Log replay for queue manager 'test_qm' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager test_qm.
ACTION:
None.
21/01/2015 14:18:49 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ7231: 0 log records accessed on queue manager 'test_qm' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager test_qm during the
recovery phase of the transactions manager state.
ACTION:
None.
21/01/2015 14:18:49 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ7232: Transaction manager state recovered for queue manager 'test_qm'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager test_qm.
ACTION:
None.
21/01/2015 14:18:49 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager
'test_qm'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager test_qm ended have
been resolved.
ACTION:
None.
21/01/2015 14:18:49 - Process(7528.4) User(johnsmith) Program(amqzmuc0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5051: The queue manager task 'CHECKPOINT' has started.
EXPLANATION:
The critical utility task manager has started the CHECKPOINT task. This task
has now started 1 times.
ACTION:
None.
21/01/2015 14:18:51 - Process(9796.3) User(johnsmith) Program(amqzmur0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5037: The queue manager task 'ERROR-LOG' has started.
EXPLANATION:
The restartable utility task manager has started the ERROR-LOG task. This task
has now started 1 times.
ACTION:
None.
21/01/2015 14:18:51 - Process(9796.4) User(johnsmith) Program(amqzmur0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 1 times.
ACTION:
None.
21/01/2015 14:18:51 - Process(9796.5) User(johnsmith) Program(amqzmur0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 2 times.
ACTION:
None.
21/01/2015 14:18:51 - Process(9796.7) User(johnsmith) Program(amqzmur0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 4 times.
ACTION:
None.
21/01/2015 14:18:51 - Process(9796.6) User(johnsmith) Program(amqzmur0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5037: The queue manager task 'APP-SIGNAL' has started.
EXPLANATION:
The restartable utility task manager has started the APP-SIGNAL task. This task
has now started 3 times.
ACTION:
None.
21/01/2015 14:18:52 - Process(10328.1) User(johnsmith) Program(amqzfuma.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ8077: Entity 'johnsmith#intranet' has insufficient authority to access object
'test_qm'.
EXPLANATION:
The specified entity is not authorized to access the required object. The
following requested permissions are unauthorized: connect/system
ACTION:
Ensure that the correct level of authority has been set for this entity against
the required object, or ensure that the entity is a member of a privileged
group.
----- amqzfubn.c : 515 --------------------------------------------------------
21/01/2015 14:18:52 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5525: The WebSphere MQ Object Authority Manager has failed.
EXPLANATION:
The Object Authority Manager has failed to complete an MQ request.
ACTION:
Check the queue manager error logs for messages explaining the failure and try
to correct the problem accordingly.
----- amqzxma0.c : 3825 -------------------------------------------------------
21/01/2015 14:18:52 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ8003: WebSphere MQ queue manager 'test_qm' started using V7.5.0.2.
EXPLANATION:
WebSphere MQ queue manager 'test_qm' started using V7.5.0.2.
ACTION:
None.
21/01/2015 14:18:52 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5008: An essential WebSphere MQ process 10328 (amqzfuma.exe) cannot be found
and is assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
----- amqzxmb0.c : 9956 -------------------------------------------------------
21/01/2015 14:18:52 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ5050: An essential WebSphere MQ process 9188 (zllPUBSUB) cannot be found and
is assumed to be terminated.
EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created. 3) MQ has encountered an unexpected
error. Check for possible errors reported in the MQ error logs and for any
FFSTs that have been generated.
ACTION:
WebSphere MQ will attempt to restart the terminated process.
----- amqzxmb0.c : 9679 -------------------------------------------------------
21/01/2015 14:18:53 - Process(9760.1) User(johnsmith) Program(amqzxma0.exe)
Host(NY0035546) Installation(WMQ75Install)
VRMF(7.5.0.2) QMgr(test_qm)
AMQ8004: WebSphere MQ queue manager 'test_qm' ended.
EXPLANATION:
WebSphere MQ queue manager 'test_qm' ended.
ACTION:
None.
At a guess, is johnsmith a domain id? Is this a domain workstation (what is 'johnsmith#intranet')? My suspicion is you have a machine in a domain but you have not configured MQ to run on a machine in a domain. I think the issue is that at startup MQ is trying to determine what groups the userid 'johnsmith#intranet' is a member of, and hence fails. Its possible, adding johnsmith to the local mqm group may get you futher although my suspicion is you need to do the domain configuration. See another answer for details of what to do:
Issue with permission grant to domain users in IBM web sphere queue manager
First, make sure your UserID is part of the 'mqm' group and second reboot your PC (wonderful things happen when you reboot Windows!).

Resources