| Author |
Message
|
| issac |
 Posted: Sat Apr 24, 2010 12:40 am Post subject: AMQ9915 After Upgrading to MQ 6.0.2.8 |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hey, guys
After upgrading from 6.0.2.5 to MQ 6.0.2.8 on SUSE, I got AMQ9915 in /var/mqm/errors/AMQERR01.LOG when trying to amqscnxc on my QMGR's host.
mqm@VIRTUALSUSE:~> amqscnxc -x '127.0.0.1(7001)' -c SYSTEM.DEF.SVRCONN MQBUTT
Sample AMQSCNXC start
Connecting to queue manager MQBUTT
using the server connection channel SYSTEM.DEF.SVRCONN
on connection name 127.0.0.1(7001).
MQCONNX ended with reason code 2059
----- amqccita.c : 564 --------------------------------------------------------
04/24/2010 04:33:48 PM - Process(11096.1) User(mqm) Program(amqscnxc)
AMQ9915: The IP protocol 'IPv4/IPv6' is not available on the system.
EXPLANATION:
An attempt to use an IP protocol that is not available on the system has been
made.
ACTION:
Install the required IP protocol or use an IP protocol that is available on the
system. This error can also occur if the system is short of memory or other
system resources.
I try to connect with a java applications which worked before, it still works. The QMGR is connected smoothly. But amqscnxc and amqsputc would not. No more log is found elsewhere. I made no IPV6-specific setting.
So why? Thanks!
_________________
Bazinga! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Apr 24, 2010 5:42 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
04/24/2010 04:33:48 PM - Process(11096.1) User(mqm) Program(amqscnxc)
AMQ9915: The IP protocol 'IPv4/IPv6' is not available on the system.
EXPLANATION:
An attempt to use an IP protocol that is not available on the system has been
made.
ACTION:
Install the required IP protocol or use an IP protocol that is available on the
system. This error can also occur if the system is short of memory or other
system resources.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| issac |
| Posted: Sat Apr 24, 2010 5:49 am Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Mmmm.. thanks to highlight the log. But... does it mean my SUSE isn't supporting IPV6? Why is the QMGR going for IPV6? Is there any config relevant to the behavior?
I made no change to QMGR since 6.0.2.5. The message suddenly begin to appear after my ugprade...
_________________
Bazinga! |
|
| Back to top |
|
|
| zpat |
| Posted: Sat Apr 24, 2010 5:56 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The error refers to IPV4/IPV6 - not to IPV6.
Do the usual diagnostics for a MQRC 2059. Check the MQ listener is running. |
|
| Back to top |
|
|
| issac |
| Posted: Sat Apr 24, 2010 7:10 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
MQ Listener is running. Java applications can connect to QMGR well, so can another QMGR by SDR CHL. But amqscnxc still doesn't work.
Anyone has a clue why I'm supposed to be using the IPV4/IPV6 protocol? I'm definitely using IPV4.
_________________
Bazinga! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Apr 25, 2010 9:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Try using the public ip address of the machine and not the loopback. Maybe the loopback is configured oddly. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Apr 25, 2010 10:45 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| mqm@VIRTUALSUSE:~> amqscnxc -x '127.0.0.1(7001)' -c SYSTEM.DEF.SVRCONN MQBUTT |
Did you do this on the same platform (LPAR) where client and server exist?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| issac |
| Posted: Mon Apr 26, 2010 5:03 am Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Yes, I'm connecting to 127.0.0.1, thus it's got to be the same platform . 
But it was the same when I tried connecting with amqsputc from a windows platform.
The good news is, the problem got solved after my re-upgrade to 6.0.2.9  Not sure about the reason. Perhaps I didn't upgrade well. I've persuaded my customers to switch to 6.0.2.9, the recommended fix level by IBM. 
_________________
Bazinga! |
|
| Back to top |
|
|
|
|
