I am testing a deployment of MQ 9.0.1 using Docker, and trying to administer this instance using the Web console. However I am receiving a warning when attaching widgets stating the "Queue manager unavailable".
Warning messages
In the console I can see my Queues are running and have created local queues and can run commands against them.
Also if I try to modify the Queue security records I get another error:
Failed to get authority recordsWMQWB0003E: The request could not be completed due to an internal web application server error.
Any thoughts or suggestions around this issue?
There is no definitive fix for MQ9.0.1 but upgrading to use MQ9.0.2 will resolve issues with hosting MQ Console on linux.
Related
I've just installed the demo version of this but fail to connect to the default queue manager. The error in the logs shows me that configuration is not correct for the mq dlls
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: Error: MQJE001: Completion Code '2', Reason '2495'.
2022/09/29 17:12:49 MQCmdServer: isCmdServerRunning: getCause()=com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
I've tried everything I can to set the path and java.library.path correctly but it all fails. They appear in the visual edit logs as being set but it makes no difference to the outcome.
Visual edit log also tells me that it should have the mq jars in its install directory:
C:\Capitalware\MQVE3\com.ibm.mq.commonservices.jar;
but these are not there and are nowhere to be seen. So, I'm mystified as to what version of the client it's using and therefore what help I can give it. I'm wondering if it's using a different version of the client from the one I have installed and so the dll and mq java lib have a mismatch? Or, if it's using the client I have installed then how is it finding it - because it's not in the paths that I've got in the visual edit logs !
Any thoughts anyone? What can I do to investigate further?
thank you !
Background: There are 2 ways an MQ client application can connect to a queue manager:
(1) Bindings mode means that the MQ client application is connecting to a local (i.e. on the same server) queue manager
(2) Client mode means that the MQ client application will connect to a remote queue manager by specifying the hostname/IP address, port # and channel name
CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd64' was not found. For a client installation this is expected. [3=mqjbnd64]
This error mean that you are trying to connect to a local queue manager (in bindings mode) but there is no local queue manager. MQ client library uses the 'mqjbnd64' DLL to handle the connection to the local queue manager. But clearly, the queue manager is remote to where MQ Visual Edit is running.
Go back to the Queue Manager Access Profile, click on the Remote icon, then fill in the channel name, hostname/IP address and port # of the remote queue manager, save the information then you should be able to the remote queue manager.
I published a simple .NET 6.0 web app with user authentication on my IIS 10.0 web server hosted on Azure.
The application read and write data from a SQL Server 2017 database hosted on another machine on the same virtual network of the web server.
Everything works fine but after a while, even though nobody is using the app, it stop working and send Http Error 503 Service Unavailable and I have to restart it every time from the application pool.
I enabled tracing on the event log, but I don't receive any message explaining this.
These are the application settings:
IIS application settings
I tried to follow these advices but none of them worked:
IIS HTTP Error 503. The service is unavailable
503 “Service Unavailable” error for all apps after installing .NET Core 2.2 Runtime & Hosting Bundle for Windows
.Net core Service Unavailable after Publish to IIS
On the same web server I have other applications but this problem appears only on this one. None of the other apps is using .NET 6, most use .NET Framework 4.7/4.8 and another couple .NET Core 3.1.
I also tried to publish the application on Azure WebApp service and it has the same problem.
1. If you're deploying on IIS, we can install DebugDiag Tools and then use the DebugDiag collection to crawl the dump logs.
2. If you are using the azure app service, it is recommended to get dump in the azure portal.
My Suggestion
Enable Failed Request Tracing, and find which request will cause the Http 503.
Maybe this 503 is not a problem with the code, and it is possible to find some useful information in the log.
Check the EventViewer, try to find the useful info about the application.
Download the DebugDiag Tools, use debugdiag collection to collect the dump file when the issue occured, and use the debugdiag analysis to analyze the dump file and check the stacktrace.
My suggestion can't tell you the root cause directly, but it will help you to find it. You are also welcome to update the useful stacktrace information in the future, and there will be more people to help you.
I'm currently having the issue but using MySQL on a remote server.
Azure WebApp, Azure VM (IIS 10) and AWS EC2.
Http Error 503 Service Unavailable when the database connection timesout or fails to connect and the AppPool failed to restart.
No crashes when debugging in VS via console app.
I changed the hosting model to out-of-process and this solved the issue.
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="outofprocess">
I have BizTalk running on a virtual box, that hits my server. It can post messages to the MQ queues without any problem. The issue is when I run BizTalk, which is installed on the same server as MQ, the MQSAgent throws this error:
The adapter has encountered an 'Access Denied' error while attempting to contact the COM+ object on the MQSeries server. Ensure the BizTalk account is added to the Role on the MQSAgent COM+ application*
The virtual box, uses the same MQSAgent as the server. Just to be sure I checked to make sure everything is set up, ie User is added to the COM group and has the role of creater/owner.
I haven't found anything on line where a developer is having the same issue.
Anyone got any ideas?
I never faced this issue but it seems to be a known issue by Microsoft. please check the following Known Issues with the MQSeries Adapter (learn.microsoft.com)
Web API has GlobalConfiguration.Configuration.IncludeErrorDetailPolicy
= IncludeErrorDetailPolicy.Always; to turn on remote errors. (Allowing them to see them in a browser even if you are not browsing on the local machine.
But, near as I can tell, Service Fabric, running Web Api, does not support GlobalConfiguration.
Is there a way to configure things so I don't have to log into one of my Service Fabric server machines each time I want to see what a services error message is?
I recommend you don't show error details to everyone.
It's a security risk.
Consider moving your error logs out of your cluster. For instance, by using OMS, ELK or Application Insights.
I have installed MQ server on HP Nonstop and client version 8 on windows server. When i am trying to access MQ server via websphere MQ explorer on windows i am getting Access not permitted,You are not authorized to perform this operation (AMQ4036) error. Can you guys help me here?
If you look in the AMQERR01.LOG on the queue manager it will tell you the reason you were rejected access. There are several different possibilities for security failures, but the exact nature of your failure will always be found in the error log. If you are not sure of the meaning of what you find in the error log, update your question with more information and I will update this answer with more information too.