| Author |
Message
|
| sebastia |
 Posted: Wed Aug 06, 2008 8:46 am Post subject: |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
AMQERR01.LOG has 2 entries,
on in "general" path, another on the "particular qmgr" path.
The (spanish) text is at the end of this note (again).
The problem is only with CLIENT connection.
Listener is OK and I can change it to any value I want - I have ended at port 9988, to skip "SERVICES" values. No luck.
"netstat -an | find "9988" displays the new port in use.
I also have mr Russinovich "TCPVIEW".
No firewall - all is local. I dont need external net - we use "localhost".
IP is v4 - I hope to retire before IPV6 comes to our fields ...
Channel I have used are few :
SYS.DEF.SVRCONN, SYS.ADMIN.SVRCONN, SYS.BKR.CONFIG
No luck.
Thanks for your (impressive) list, mr Saper.
Today I have started installed on another "workstation" machine.
The one in problem is a LapTop ...
Thanks to all.
=========================================
in AMQERR01.LOG (not the qmgr-specific, but the general one) : there is a 10054 error detected :
----------------------------------------------------------------------------------
30/07/2008 12:23:18 - Process(2100.1) User(65652208) Program(amqsputc.exe)
AMQ9208: Error de recepción del sistema principal localhost (127.0.0.1).
EXPLICACIÓN:
Se ha producido un error al recibir datos de 'localhost (127.0.0.1)' a través
de TCP/IP. Esto puede deberse a un error de comunicaciones.
ACCIÓN:
El código de retorno de la llamada TCP/IP (recv) ha sido 10054 (X'2746'). Anote
estos valores y póngase en contacto con el administrador de sistemas.
----- amqccita.c : 3161 -------------------------------------------------------
And in the AMQERR01.LOG of the specific queue manager, we have 10038 error :
---------------------------------------------------------------------------------
30/07/2008 12:23:19 - Process(4120.44) User(65652208) Program(amqrmppa.exe)
AMQ9213: Se ha producido un error de comunicaciones en TCP/IP.
EXPLICACIÓN:
Se ha producido un error inesperado en las comunicaciones.
ACCIÓN:
El código de retorno de la llamada TCP/IP (ioctlsocket) ha sido el 10038
(X'2736'). Anote estos valores y póngase en contacto con el administrador de
sistemas.
----- amqccita.c : 1642 ------------------------------------------------------- |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Aug 06, 2008 8:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Contrary to belief you can set a firewall on localhost.
Normally communications from localhost to localhost are accepted by the firewall, but this too is subject to a rule. If you have a very paranoid admin the client connection to localhost will not work...
What is the result of
telnet localhost qmgrport
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Aug 07, 2008 12:13 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Saper - I have been looking for ZoneAlarm and Windows firewalls,
and I can say for sure (?) there is no firewall.
When I issue from a command line "telnel localhost 9876",
I get a "gray" screen with no prompt
(this is OK as far as I know)
but when I touch the first key,
the session gets broken
and the "C:>" comes back.
And AMQERR01.LOG on "my_qmgr" directory has 10038 tcp/ip error.
Thanks. Seb. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 07, 2008 12:27 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Sebastia,
Try this http://support.microsoft.com/kb/318584, it gets a mention in an old 5.2 -> 5.3 upgrade issue. If that doesn't work I am definitely all out of ideas!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Aug 07, 2008 8:16 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Exerc ... to remove the TCP stack is quite a drastic measure.
I will have to consider it ... atfer holidays.
I need 2 weeks to rest ... This "bussiness integration" word is very stressing !
Thanks. |
|
| Back to top |
|
|
| sebastia |
| Posted: Sat Aug 09, 2008 3:18 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Well - I just installed all the software again on another machine
(a workstation) and all works as supposed.
So, the laptop will keep its secret forever,
( ??? why any port was working ??? )
because I am not spending any more time on it.
Thanks to you all. |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Sep 17, 2008 6:24 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Gentlemen : here is the solution ...
Set "MQNOREMPOOL=1" and reboot.
Details : see PMR 39250,756,000 |
|
| Back to top |
|
|
| chauhan_samir |
| Posted: Thu Sep 25, 2008 9:37 am Post subject: TCP/IP (recv) error 10054 with MQRC 2059 |
|
|
Novice
Joined: 25 Aug 2005
Posts: 14
Location: USA
|
I am also getting the TCP/IP (recv) error 10054 with MQRC 2059 error for the local queue manager. I have MQv6.0.2.3 installed on Win2003 server. I got MQRC 2059 error in my WebSphere Application Server(WAS) while connecting to QM using client connection within application and event viewer logged the TCP/IP error. When I raised PMR to IBM, they told me that there should be sequence to stop IBM products (We have MQ, WAS and Message Broker). As per them, during the server reboot MQ stops before WAS and which should not be the case. Do you think that can be the issue?
I still have to try the resolution by setting MQNOREMPOOL=1.
Looking for your advice. |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Sep 25, 2008 9:49 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Absolutely NOT.
The problem is a CORRUPTED TCP/IP stack.
Can you see PMR's - see this one PMR 39250,756,000
It is VERY old, but .. IT WORKS
( i fixed a machines in a month !!! )
Enjoy ! |
|
| Back to top |
|
|
| chauhan_samir |
| Posted: Thu Sep 25, 2008 10:47 am Post subject: |
|
|
Novice
Joined: 25 Aug 2005
Posts: 14
Location: USA
|
Thank you for your response.
How do you access the PMR raised by others? My company has customer id but I am do know the IBM id? What do you need to see PMRs? |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Sep 25, 2008 11:10 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
I can't help with the PMR access ...
I can do other things, as providing (parts of) the PMR here ...
Enjoy !
===============================================
... Corrupted winsock install. See MS KnowledgeBase item Q318584.
... http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b318584
... http://www-1.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSWHKB&q1=amq9213+10038&uid=swg21109489&loc=en_US&cs=utf-8&lang=en
... Document reference number 1109489 says that the MQNOREMPOOL environment variable turns off the channel pooling process at system start-up time.
... The 10038 return code indicates that the WebSphere MQ listener pool has had trouble passing the initial socket from the listener to the pool.
... MQ V5.3 uses Channel Pooling mechanism (AMQRMPPA) to service incoming connection requests. Channel pooling enables the Queue Manager to distribute the MQ responder threads among multiple AMQRMPPA processes and evenly handle the volume of the inbound connections. When channel pooling is disabled, all the responder threads are spawned in a single MQ listener process, as opposed to distributing the load among multiple AMQRMPPA processes when channel pooling is enabled.
... that this is a known problem with winsock libraries being corrupted
by outside products in MQ, like Symantec Personal Firewall, VPN software, SINE, etc. Apparently these applications over-write something in the winsock libraries which cause MQ channels to break the connection.
... Setting this variable will force all new listener threads to be handled directly by the runmqlsr process rather than spawning off new threads in the pooling process amqrmppa. Also if you specify thread, the MCA runs on a thread of the RUNMQCHI process if MQNOREMPOOL is specified (otherwise MCA runs on a thread of the AMQRMPPA process).
Hope this helps. |
|
| Back to top |
|
|
|
|
