Re: MQ Java problem on AIX
could be missing the item beneath in ur startup script QueueManager: Name=XXX Prefix=/var/mqm IPCCBaseAddress=12 Regards Low Jit Khoon Software Engineer Lido AeroNet Pte Ltd 80 Raffles Place #47-01 UOB Plaza1 Singapore 048624 Tel: 3790144 Fax:3790150 |-+--- | | Chris A. Dahl | | | [EMAIL PROTECTED]| | | TATE.MN.US | | | Sent by: MQSeries List | | | [EMAIL PROTECTED]| | | | | | | | | | | | 10/04/02 02:56 AM | | | Please respond to | | | MQSeries List | | | | |-+--- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: MQ Java problem on AIX | ---| Christian, I have extracted this from the readme.txt file under /usr/mqm/java/doc/en_us. It may be that you are running into the AIX shared memory conflict if you are using server bindings mode. 6. On AIX, the use of the bindings transport (C via JNI) in JDK 1.2.2 and 1.3.0 requires some additional configuration to avoid a conflict with shared memory segments. The problem presents as a failure to create a new instance of MQQueueManager with reason code 2059, as well as the generation of FDCs in the var/mqm/errors directory. For the latest information on how to resolve this problem, please refer to http://www.ibm.com/software/ts/mqseries/support/summary/jvreadme.html For convenience, the relevant section is reproduced below, but you are advised to check the above url to ensure that this information is still current: MQSeries V5.1 and below --- AIX 4.3.3 supports an environment variable (LDR_CNTRL) which can be used to fix this problem. Before starting the JVM, use the following command: export LDR_CNTRL=MAXDATA=0x3000 This will change the way that processes use memory segments, so it is recommended that this environment be used solely for running JVMs that need to be run on the same machine as MQ queue managers. In particular, MQSeries commands (such as strmqm) will not work under these conditions. MQSeries V5.2 and above --- An extra parameter for the mqs.ini file is now supported by MQSeries V5.2. The parameter is IPCCBaseAddress and is set on a per queue manager basis. By default this parameter is set to the value 8, but we recommend setting this to the value 12. The following is an example of an altered QueueManager stanza in an mqs.ini file: QueueManager: Name=MQJavaTest Prefix=/var/mqm IPCCBaseAddress=12 Allowable values for this parameter are 4, 5, 8, 9, 10, 11 or 12; see the MQSeries V5.2 documentation for more information. - Hope that's your problem, Chris Saar, Andrew [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Sent by: Subject: Re: MQ Java problem on AIX MQSeries List MQSERIES@AKH-WI EN.AC.AT 10/03/02 01:10 PM Please respond to MQSeries List Your code looks correct and I've duplicated the same thing here. Are you sure that your spelling of the QM name is correct? I hate to ask such a simple question but often times it's the little things that slip under the radar. 2059s are common when you have a misspelling and a little hard to track since your code is
Re: Help required for MQSeries Java Client on Solaris
Hi There should be abt 7 jar file that u need to reference to in your classpath com.ibm.mq.iiop.jar com.ibm.mq.jar com.ibm.mqbind.jar com.mqjms.jar jms.jar providerutil.jar fscontext.jar Regards Low Jit Khoon Software Engineer Lido AeroNet Pte Ltd 80 Raffles Place #47-01 UOB Plaza1 Singapore 048624 Tel: 3790144 Fax:3790150 Joshi, A (Anant) [EMAIL PROTECTED]To: [EMAIL PROTECTED] BOBANK.COMcc: Sent by: MQSeries Subject: Help required for MQSeries Java Client on Solaris List MQSERIES@AKH-WIEN. AC.AT 09/19/02 04:15 AM Please respond to MQSeries List Hi, We have installed MA88 support pack on Solaris. The JDK version is 1.3.1 The sample application MQIVP returns following error after entering Queue Manager name: Failure: Missing software, may be MQSeries, or VBROKER_ADM variable java.lang.NoClassDefFoundError: javax/resource/ResourceException When we run our own Java class, the error NoClassDefFoundError is thrown for line qm1= new com.ibm.mq.MQQueueManager(qmname); Following is output of lines to verify version and classpath: === java version: 1.3.1_04 CLASSPATH: .:/usr/java/lib/tools.jar:/usr/java/lib/dt.jar:/usr/j2sdkee1.3.1/j2ee.jar:/o pt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqbind.jar:/opt/mqm /java/lib/jta.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar Any suggestions to fix this will be greatly appreciated. TIA == De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. == The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail. == Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: was qcf
Hi Maybe WS not started Regards Low Jit Khoon Software Engineer Lido AeroNet Pte Ltd 80 Raffles Place #47-01 UOB Plaza1 Singapore 048624 Tel: 3790144 Fax:3790150 |-+- | | Graham Lekota | | | graham.lekota@LIB| | | ERTY.CO.ZA | | | Sent by: MQSeries | | | List | | | MQSERIES@AKH-WIEN| | | .AC.AT | | | | | | | | | 07/09/02 07:10 PM | | | Please respond to | | | MQSeries List | | | | |-+- -| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: was qcf | -| Hi, i am trying to create wsqcf connection factory from JMSAdmin command and i get Unable to create a Websphere specific class. I can create a q object and a context. I am running : ma88 5.2, mqseries 5.2, was 4.0.2, ibm http server 3.2, solaris 5.8. PATH=/usr/sbin:/usr/bin:/usr/ucb:/etc:/usr/dt/bin:/usr/openwin/bin:/bin:/usr /ucb:/usr/opt/SUNWmd/sbin:/opt/mqm/java/lib/:/app/WebSphere/AppServer/bin:/o pt/mqm/bin:/opt/mqm/java/bin:/app/WebSphere/AppServer/java/jre/bin:. CLASSPATH=/usr/java1.1/lib/classes.zip:/opt/mqm/java/lib/com.ibm.mq.jar:/opt /mqm/java/lib/com.ibm.mqbind.jar:/opt/mqm/java/lib/connector.jar:/opt/mqm/ja va/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/jms.jar:/opt/mqm/java/lib/jndi.ja r:/opt/mqm/java/lib/jta.jar:/opt/mqm/java/lib/ldap.jar:/opt/mqm/java/lib/pro viderutil.jar:/opt/mqm/java/lib/com.ibm.mqbind.jar:/opt/mqm/java/samples/bas e:/opt/mqm/java/lib:/opt/mqm/java/lib/com.ibm.fscontext.jar/app/WebSphere/Ap pServer/lib/ns.jar:/app/WebSphere/AppServer/lib/j2ee.jar Thanks Maditsi --- Graham Lekota(Liberty Group) IBM Certified Specialist, WebsphereMQ +27 83 327 3619 / +27 11 408 4683 [EMAIL PROTECTED] *** Wheresoever you go, go with all your heart. --Confucius ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** *** This message may contain information which is confidential and subject to legal privilege. If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message. *** Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Duplicate Queue Manager Names
Hi Jason U should design your program in such a way that, resource parameters such as Queue or QueueManager could be configurable. A program designed in such a way will have little or no change required when there is a need to port the program to another system with a different resource naming. It is advisable to use a configuration file where during a start of the program the setting will be read in by running program. I feel that using a duplicate name is not a good idea, it create confusion in the first place, and shall be extremely diffcult to troubleshoot if problem arise. My 2 cents... Regards Low Jit Khoon Software Engineer Lido AeroNet Pte Ltd 80 Raffles Place #47-01 UOB Plaza1 Singapore 048624 Tel: 3790144 Fax:3790150 Jason Cornell Jason_Cornell@LATo: [EMAIL PROTECTED] BCORP.COM cc: Sent by: MQSeriesSubject: Duplicate Queue Manager Names List MQSERIES@AKH-WIE N.AC.AT 06/28/02 01:14 AM Please respond to MQSeries List Currently, our developers are concerned that having queue managers named differently according to environment (i.e. test, qa, prod) will cause issues when migrating to the next level in the promotion model. While I agree slight application modifications will be required I was under the impression having duplicate queue manager names on the same network was highly discouraged. Any suggestions on how to deal with this issue? Any assistance would be appreciated. Thanks Jason Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Orphaned client channel connections using JMS/MQ
Hi David your problem seem very interesting to me. could you share a little bit more on your use of the client channel connection. I used JMS application but has never hook it up with the qmanager vie the client channel connection. Never have I define a client connection to support the JMS application. Maybe I have miss out something in the past. Thanks Regards Low Jit Khoon Software Engineer Lido AeroNet Pte Ltd 80 Raffles Place #47-01 UOB Plaza1 Singapore 048624 Tel: 3790144 Fax:3790150 Dave Corbett david.corbett@USTo: [EMAIL PROTECTED] BANK.COMcc: Sent by: MQSeriesSubject: Re: Orphaned client channel connections using JMS/MQ List MQSERIES@AKH-WIE N.AC.AT 06/28/02 06:04 AM Please respond to MQSeries List Danny, Thank you very much for the info on TCP keep alive, MQ Heartbeat and disconnect intervals. It is always very helpful to have that type of documentation handy. Even though most of the document specifically mentions QM sender/receiver channels, it still has meaning for the client channels. Thanks, David Corbett Work: 651-205-2714 Pager: 651-610-3842 Gorse, Darry Darry_Gorse@AFTo: [EMAIL PROTECTED] CC.COMcc: Sent by: Subject: Re: Orphaned client channel connections using JMS/MQ MQSeries List MQSERIES@AKH-W ien.AC.AT 06/27/2002 11:10 AM Please respond to MQSeries List Dave, Do you have TCP KeepAlive set up on your server and implemented on your Queue Managers? If I remember this was discussed some time ago on the list. Cheers, Darry Gorse IBM Certified Specialist - WebSphere MQ Systems Infrastructure Operations -Original Message- From: Dave Corbett [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 8:47 AM To: [EMAIL PROTECTED] Subject:Orphaned client channel connections using JMS/MQ I have an application that has two W2k boxes talking to each other. One is a QM and the other runs a websphere application that uses JMS to do MQ calls. The websphere app makes client connections across a wan to the QM. We are having network issues and the client channel connections end up orphaned on the QM. The client automatically reconnects when it detects connection failure. This has the result of the maxChannels parameter being eventually exceeded. I have set the parameter to 300, but this just delays the inevitable. We are continually trying to resolve the network issues, but as a short term fix we should be able to use MQSeries explorer to control the client connections. The issue is that when checking the status of the server connection where all instances of the client connections are displayed, there is no way to stop a specific instance. By right clicking on the serverconn, we can stop all client instances, but this has the result of causing timeouts to end users. And, when we issue a stop command, the channels go into a stopping mode, but I believe they are still included in the max channels count. Does anybody know of a way to kill and delete these orphaned client connections? Our site is having many network issues and we are looking for a faster way of restarting things without rebooting the QM. Thanks, David Corbett MQSeries Certified Solutions Expert Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
