I upgraded my previous MQ V6.0 to MQ 7.0 a few days ago. But once upgrade completed, MQ Explorer can not display local QMGR in the Queue Manages. I have to add local QMGR through "Add Remote Queue Manager" and it works fine.
I just wonder why that local QMGR cannot be shown in the MQ Explorer.
Thanks in advance
Open a Command Prompt and run the following command:
strmqcfg -c
I think the problem you describe is documented here. Are you at the latest fixpack of MQ v701 or v7.1?
Related
I am trying to move one .NET framework 4.5 Windows console app to Windows Container. That app is using IBM MQ client 9.0.0.6. The application is working fine local Machine/VDI where I have installed IBM MQ 9.0.0.6 Client successfully.
What will be the best approach to move this app to Windows Container ?
I have followed below options but it's not working.
Install the whole IBM MQ 9.0.0.6 Client in Windows Container using silent installation. But I can see the logs saying it's installed successfully but my application is not working fine. During connecting to QManager, I am getting below error.
{"The type initializer for 'IBM.WMQ.Nmqi.UnmanagedNmqiMQ' threw an exception."}
Silent Installation Command in Windows Container: msiexec /i "c:\temp\Windows\MSI\IBM MQ.msi" /l*v c:\temp\install.log /q TRANSFORMS="1033.mst" AGREETOLICENSE="yes" ADDLOCAL="Client"
Second Option, I am trying to use the removal of IBM MQ client dependencies and only take the required dlls in my Application but it's also not working.
Also, tried to explore IBM MQ Redistributable client but seems it's not working.
But somehow I knew that any one of these options should be working. Can you please help me out on this ?
Thanks,
koushik
I had installed redis-3.0.504. Followed the installation instructions and now redis-server is running in the port
I had also installed redis in Windows services, but that is not running. I'm also not able to manually start the service. Getting the below error.
Any ideas to start the service?
Right-click in the service in Window Services and go to Properties.
Then go to Log On tab and select Local System account.
Click on the Ok button and start the service.
If you installed this via chocolatey, you need to add the following folder to allow the supplied redis.windows-service.conf to work:
C:\ProgramData\chocolatey\lib\redis-64\Logs
If you didn't install via chocolatey, a missing log folder is still likely to be the culprit.
The Redis port for Windows you are using has been deprecated.
As the last commit in that project suggests you can check out Memurai.
Memurai is a production grade software, actively maintained and freely available for development.
I am completely new to MQ world and need help understanding the install.
I have downladed 9.2.0.1-IBM-MQFA-Redist-LinuxX64.tar.gz redistrible package . Now i can see under bin folder there is set of FTE* commands.
Requirements:
Need to transfer files from linux server to queue (File to Queue)
Questions:
Do i need to run FTEcreateagent in my linux host or MQ server?
If i run FTEcreateagent in my linux host, does the agent will be visible automatically in windows server?
You have downloaded is the Redistributable version of IBM MQ Managed File Transfer product. It can be simply unpackaged anywhere on a file system. But you need to have a MQ v9 or above queue manager running somewhere as MQ is a prerequisite for MFT.
The redistributable package contains binaries and commands for for setting up agents to run transfers. It does not contain MQExplorer.
You need to start by running fteCreateEnvironment command and then call fteSetupCoordination, fteSetupCommands and then fteCreateAgent. This is the best place to start learning about configuring MFT using the redistributable package.
I'm running Eclipse Java EE (Mars) / Websphere Liberty (8.5.5.8) / Websphere Liberty Developer Tools Plugin (8.5.5) on IBM SDK 8.0 64 Bits for Windows.
When launching the server at localhost, the server starts normally and the console writes "server is ready" but the Eclipse launch delegate still tells the server status is "starting". After timeout period, Eclipse says the server was unable to start and kills it.
I know this is a recurring issue : i change connection settings in eclipse to direct, add localhost to etc/host, add -Djava.net.preferIPv4Stack=true to eclipse.ini but couldn't resolve it ...
There are some known limitations if you have changed the logging settings, see the Developer Tools known issues and restrictions.
The tools look for this exact message id in the eclipse Console view: CWWKF0011I. If that message id is not detected the tools think the server did not start. Do you see that message id in the eclipse Console view?
I am using websphere 9.0 traditional in eclipse 2019-09 having the same issue. Probably because some session is running background.
Resolved by:
1) Go to console->Right click-> terminate/disconnect all. Then agin right click remove all terminated button.
2)If still the problem there remove all the cache in temp files both in application and profiles.
Java 7 prevents FTP transfers on Windows Vista and 7.
In FTP, before a file is transferred a PORT or a PASV command must be sent. As soon as one of the commands is sent the Windows Firewall closes the socket that sent it. This only happens if the firewall is on and an exception for java.exe is absent. I suspect this problem is related to Java 7 using the new Vista IP stack.
Does anyone have any ideas how to fix or work around this problem? We're distributing a Java FTP library so we obviously can't add exceptions ourselves.
Exception:
java.net.SocketException: Permission denied: recv failed
JRE version info:
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
FOLLOW-UP 1 (14 November 2011):
Oracle has analysed the problem and have found that it seems to be a bug in Windows Firewall and/or the IPv6 stack. They managed to replicate the problem with a native C (i.e. non-Java) app, so this is strong evidence that the bug is not in Java. They have informed Microsoft, so the ball is in their court now. More details can be found at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7077696
FOLLOW-UP 2 (27 July 2012):
A (very helpful) contact at Oracle has told me that the issue has now been escalated at Microsoft. We're hoping to see some results soon.
FOLLOW-UP 3 (15 August 2012):
Our contact at Oracle has told us that Microsoft has accepted the bug and is in the process of prioritizing it.
FOLLOW-UP 4 (21 September 2012):
Microsoft has produced a patch that is currently being tested by Oracle. No word on a release date.
FOLLOW-UP 5 (11 October 2012):
Success at last! Microsoft has publicly released a hotfix. They imply that the fix will be included in a general software update in the future:
"if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix."
The problem is caused by the stateful FTP filter of the firewall. As a workaround you can disable it by executing netsh advfirewall set global StatefulFTP disable with administrator rights.
Another workaround is to start the JVM with:
-Djava.net.preferIPv4Stack=true
We tested the Windows hotfix http://support.microsoft.com/kb/2754804 and confirmed that it did resolve the problem.
I've submitted a bug report to Oracle, see bugs.sun.com/bugdatabase/view_bug.do?bug_id=7077696
They've marked the priority as low, which makes me think that they don't quite understand the magnitude of the problem, i.e. that FTP is broken on Java/Windows. I forgot to state that explicitly in the bug report. If anyone else feels like it should have a higher priority please add a comment to the Oracle bug report.
I just noticed that you can also 'vote' for the bug, so please give it a vote if you agree it's significant.
This problem can be demonstrated without JDK7, it's the firewall in Windows 7 blocking the ftp protocol when the application is using IPv6-mapped IPv4 addresses. See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7077696 for more details and workarounds.
Blogged about the issue here:
http://podzemski.com/2011/09/12/java-7-prevents-ftp-transfers-on-windows-when-firewall-is-on/
Maybe it'll cause some additional awareness of the problem.
Actually TFTP under JDK7 on windows 7 also have the same problem, the MS hotfix does resolve FTP issue, but still not works for TFTP. Seems Oracle should report the same problem to MS and get another hotfix to resolve TFTP issue as well.
The same bug was reported here with a test case:
Java 7 Socket Exception Bug forum.
Its an issue with Java 7
I had the same problem using IDE Eclipse Neon, JAVA 7 and Windows 7 Professional. Trying to upload a PDF file to an FTP server. I solved it by running the following command in CMD as administrator:
C: \ Users \ pc01> netsh advfirewall set global StatefulFTP disable