ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » how to know when a queue manager got restarted on windows

Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next
 how to know when a queue manager got restarted on windows « View previous topic :: View next topic » 
Author Message
raj429
PostPosted: Tue Apr 26, 2011 11:12 pm    Post subject: Reply with quote

Acolyte

Joined: 04 Jul 2009
Posts: 53

Apologies for late reply.

Vitor, is absolutley right about error logs fill up.
In he windows box I am getting the frequent error as below

27/04/2011 06:02:19 - Process(8248.11826) User(DDD) Program(amqrmppa.exe)
Host(ABCD)
AMQ9208: Error on receive from host XYZ.

EXPLANATION:
An error occurred receiving data from XYZ over TCP/IP.
This may be due to a communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10054 (X'2746'). Record these
values and tell the systems administrator.

on checking found
http://www-01.ibm.com/support/docview.wss?uid=swg21106218
http://www-01.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&uid=swg21237211

The statement in the first link, *on queue manage shutdown when active client connectiion exist* made me to think, how can I know when a queeu maager is restarted recently.

I am still checking with client, on why this error is reoccuring..
Note: it is occuring intermittently.
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Apr 26, 2011 11:28 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

shashivarungupta wrote:
Oldest start date/time of the running channel will give the information that which channel has got started first after the queue manager came to the running state. ( and by that you can assume as soon as qmgr came to the running state that channel came in running state ).

Really? How so? Queue manager starts at 08:00 on Monday and the first channel starts 08:00 today, ergo (by your reckoning) the queue manager has only been running approximately 1.5 hours...
_________________
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
View user's profile Send private message
exerk
PostPosted: Tue Apr 26, 2011 11:33 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

As you are getting TCP/IP 10054 errors I suggest you look at THIS link for additional candidates to those mentioned in the links you have quoted. Time to get your network people involved I think.
_________________
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
View user's profile Send private message
shashivarungupta
PostPosted: Tue Apr 26, 2011 11:42 pm    Post subject: Reply with quote

Grand Master

Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.

exerk wrote:
shashivarungupta wrote:
Oldest start date/time of the running channel will give the information that which channel has got started first after the queue manager came to the running state. ( and by that you can assume as soon as qmgr came to the running state that channel came in running state ).

Really? How so? Queue manager starts at 08:00 on Monday and the first channel starts 08:00 today, ergo (by your reckoning) the queue manager has only been running approximately 1.5 hours...


I said there is no guarantee that I would believe on the data that I would get from oldest running channel's start date/time. (that could be approx not exact date/time)
But suppose qmgr came to the running state (at 1:00 pm on 25th Aprl 11) and an application was keep on trying to get connected to that qmgr and has got the connection finally over it using some channel (as soon as qmgr came to the running state , say 1:01 pm on 25th Aprl 11).. then data from that channel's start date/time can give approximate infor. of when the qmgr has got started.

_________________
*Life will beat you down, you need to decide to fight back or leave it.
Back to top
View user's profile Send private message Send e-mail
raj429
PostPosted: Wed Apr 27, 2011 4:29 am    Post subject: Reply with quote

Acolyte

Joined: 04 Jul 2009
Posts: 53

an update on the issue..
It seems an unwanted application is trying to make connection from a host to MQ host. Concern team is working on identifying it.

For now,
the best option to find out when a queue manager restarted on windows is through error logs.

but Microsoft could have included the process start time & a bit more drill down to applications associated with it, as an option in task manager rather than providing another download eg: process explorer

The above would have simplified our life, in identifying the start time and which process is associate to which queue manager.
Back to top
View user's profile Send private message
shashivarungupta
PostPosted: Wed Apr 27, 2011 4:46 am    Post subject: Reply with quote

Grand Master

Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.

Quote:
It seems an unwanted application is trying to make connection from a host to MQ host.

Have mq security in the system ?
_________________
*Life will beat you down, you need to decide to fight back or leave it.
Back to top
View user's profile Send private message Send e-mail
exerk
PostPosted: Wed Apr 27, 2011 4:52 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

raj429 wrote:
For now,
the best option to find out when a queue manager restarted on windows is through error logs.

Did you check the time/date stamps of the files I mentioned in a previous post?
_________________
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
View user's profile Send private message
bruce2359
PostPosted: Wed Apr 27, 2011 5:10 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

raj429 wrote:
an update on the issue..
It seems an unwanted application is trying to make connection from a host to MQ host. Concern team is working on identifying it.

Denial-of-service attack. Cool.

Should this move to the Security forum?
_________________
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
View user's profile Send private message
Vitor
PostPosted: Wed Apr 27, 2011 5:16 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bruce2359 wrote:
Should this move to the Security forum?


Umph. No. By a nose.

I'm assuming here that the application in question is a badly written in house application rather than a specific DoS. Though it is acting like one of course.

The Security section is more concerned with securing a queue manager against external threats, and unauthorized internal users. So this problem doesn't quite fit. Quite. Just. Sort Of. This is a situation where the guilty should be trouted rather than prosecuted.

The Moderator Has Spoken. A few posts down the road this may all change.....
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Apr 27, 2011 5:18 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

shashivarungupta wrote:
Have mq security in the system ?


So you get SSL errors in the log rather than IP ones? This does not advance the OP's cause.

My take is that the application wasn't trying to connect to MQ but the host it was running on, and believes one port is as good as another.

Could be wrong.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Apr 27, 2011 5:20 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

any port in a storm?
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Apr 27, 2011 5:26 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqjeff wrote:
any port in a storm?


Ok, yes, point taken, point taken.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
shashivarungupta
PostPosted: Wed Apr 27, 2011 5:49 am    Post subject: Reply with quote

Grand Master

Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.

Vitor wrote:
My take is that the application wasn't trying to connect to MQ but the host it was running on, and believes one port is as good as another.

Can you please be clear on that. (may be some example, being curious )

You mean an application which is written badly, is trying to connect to mq host where port is open (or application is trying to connect to mq host by mistake?)

raj429 wrote:
It seems an unwanted application is trying to make connection from a host to MQ host

_________________
*Life will beat you down, you need to decide to fight back or leave it.
Back to top
View user's profile Send private message Send e-mail
bruce2359
PostPosted: Wed Apr 27, 2011 5:57 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

The uninvited app may not be an mq app. Rather, it may be inbound ip packets with the the destination ip(port) of your mq listener.
_________________
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
View user's profile Send private message
ramires
PostPosted: Wed Apr 27, 2011 7:25 am    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

look to this:

http://hursleyonwmq.wordpress.com/2007/05/04/introduction-to-ffsts/

you can manually force generate an fdc file, and then edit it and look for the date/time mq processes have. For example:

amqldbgn.exe -n amqzxma0.exe

will create an fdc file, edit it and search for "starttime"
_________________
Obrigado / Thanks you
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next Page 2 of 3

MQSeries.net Forum Index » General IBM MQ Support » how to know when a queue manager got restarted on windows
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.