Author |
Message
|
fjb_saper |
Posted: Mon Dec 26, 2005 10:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
depends how open your net is. Are you sure this is not due to some port sniffing software (authorized or non authorized...)
This should give you some avenues of reflection....
Enjoy  |
|
Back to top |
|
 |
csmith28 |
Posted: Tue Dec 27, 2005 7:02 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
The 10054 return code means Connection reset by Peer and it occurs when an established connection is shut down for some reason by a remote host. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Dec 27, 2005 8:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Could that be a firewall not allowing either the protocol or the port, or the host ? |
|
Back to top |
|
 |
csmith28 |
Posted: Tue Dec 27, 2005 8:57 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
fjb_saper wrote: |
Could that be a firewall not allowing either the protocol or the port, or the host ? |
I doubt it. This alert generally means an application instance was bounced or there was some sort of network latency that caused an established connection fail.
If the connection was being refused buy the server hosting the MQManager I would expect the application to get a TCP/IP 10061 CONNECTION REFUSED or a 2035 but we wouldn't see an alert generated in the AMQERR0*.LOG. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Tue Dec 27, 2005 9:27 am; edited 1 time in total |
|
Back to top |
|
 |
EddieA |
Posted: Tue Dec 27, 2005 9:13 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
What are the circumstances to this. Did it just start happenening. Does it always happen. Is it a new installation, or a new channel.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
javagate |
Posted: Tue Dec 27, 2005 9:43 am Post subject: |
|
|
 Disciple
Joined: 15 Nov 2004 Posts: 159
|
|
Back to top |
|
 |
hguapluas |
Posted: Tue Dec 27, 2005 2:47 pm Post subject: |
|
|
Centurion
Joined: 05 Aug 2004 Posts: 105 Location: San Diego
|
If you are on windows, check name resolution of your targets as defined in your channel defs. If those names won't resolve, I've seen these errors crop up before. Putting these into either DNS or your HOSTS file frequently can resolve the problem. Just depends on how much maintenance you want to do later on when things change. DNS is easier to maintain while the HOSTS file can become a nightmare. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Dec 27, 2005 2:55 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
As a side note, HOSTS on Windows is in <WIN-Install>\system32\drivers\etc\. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|