Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

I also have been playing with automatic client reconnection using version 7.1.0.0. I got it to work pretty well with the MQSERVER environment variable and the amqsputc/amqsgetc sample programs. But, when I tried using it from JMS, I ran into a show stopper. Apparently, automatic client reconnection will ONLY work for persistent connections in JMS. It must be able to connect to the first queue manager in the list. I thought it would work the same as non- JMS connections where it would try the first host(port) and if that didn't work, try the next host(port) in the connectionnamelist. It doesn't work that way at all, you get an error "can not create connection factory", when the call fails on the first server. Here is some information from the ticket that I opened with IBM: (Sorry the extract from the manual did not format very well) From: Goldstein, Barry A Sent: Sunday, June 24, 2012 7:25 AM To: 'websphere_support-5Nx6oC45glHMbYB6QlFGEg@public.gmane.org' Cc: DL EA TEAM Subject: RE: 76233 122 000: Automatic JMS client reconnection fails This is only usable for persistent connections then. I am disappointed. My first test was using the MQSERVER variable with the sample programs (amqsputc, amqsgetc). That worked exactly like I wanted it to, when the first connection could not be established, it made connection with the second one. Would a JNDI connection or a CCDT connection work more like my first test using the MQSERVER environment variable? Thank you, Barry From: websphere_support-5Nx6oC45glHMbYB6QlFGEg@public.gmane.org [mailto:websphere_support-5Nx6oC45glHMbYB6QlFGEg@public.gmane.org] Sent: Friday, June 22, 2012 3:43 PM To: Goldstein, Barry A Subject: Re: 76233 122 000: Automatic JMS client reconnection fails Hello, In your error it seems that the client does not initially connect to the QM: /* SHUTDOWN SQLX1ESB1 */ javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'goblxdvesb1:*'. This is the first QM in the cf.setConnectionNameList("goblxdvesb1 (1464),goblxdvesb2(1464)"); Per the documentation for reconnectable JMS clients: "Automatically reconnectable client connections only become reconnectable once the connection has been established." Automatic client reconnection Configure your JMS client to reconnect automatically following a network, queue manager, or server failure. Use the CONNECTIONNAMELIST and CLIENTRECONNECTOPTIONS properties of the MQClientConnectionFactory class to configure a client connection to automatically reconnect following a connection failure or an administrative request to reconnect client applications after stopping a queue manager. The full list of connection names in a ConnectionNameList is only accessible to the set/getConnectionNameList methods that can handle a list of connection names. Methods such as get/setHostname that do not handle lists of names, access the first name in the list. Automatically reconnectable client connections only become reconnectable once the connection has been established. Whether an application continues to work correctly after being reconnected automatically depends on its design. Read the related topics to understand how to design reconnectable clients. Some existing clients might work correctly without modification following automatic reconnection. Let me know if you have additional questions. Jim Simmons WMQ support. Thank you for using IBM products and support. http://www.ibm.com/support

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com