MQSeries.net :: View topic - QFlex: Problem with "Channel" Monitor Object Type

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Performance Monitoring » QFlex: Problem with "Channel" Monitor Object Type

QFlex: Problem with "Channel" Monitor Object Type

« View previous topic :: View next topic »

Author

Message

myles

Posted: Fri Apr 14, 2006 6:21 am Post subject: QFlex: Problem with "Channel" Monitor Object Type

Newbie

Joined: 09 Dec 2005
Posts: 3
Location: New York, NY

I've created a "Channel" Monitor Object Type, and the following is written to Tomcat's "stdout.log" every time it fires:

Code:

2006-04-14 09:57:24,845 ERROR [QflexScheduler_Worker-4] core.JobRunShell (JobRunShell.java:200) - Job alertsGroup.alertsJobDetail479123086 threw an unhandled Exception:
java.lang.NullPointerException
at com.netflexity.qflex.alert.triggers.ChannelIsRunningTrigger.performCheck(ChannelIsRunningTrigger.java:19)
at com.netflexity.qflex.alert.triggers.AbstractChannelTrigger.check(AbstractChannelTrigger.java:41)
at com.netflexity.qflex.jobs.AlertJob.execute(AlertJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
2006-04-14 09:57:24,845 ERROR [QflexScheduler_Worker-4] core.ErrorLogger (QuartzScheduler.java:1896) - Job (alertsGroup.alertsJobDetail479123086 threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
* Nested Exception (Underlying Cause) ---------------
java.lang.NullPointerException
at com.netflexity.qflex.alert.triggers.ChannelIsRunningTrigger.performCheck(ChannelIsRunningTrigger.java:19)
at com.netflexity.qflex.alert.triggers.AbstractChannelTrigger.check(AbstractChannelTrigger.java:41)
at com.netflexity.qflex.jobs.AlertJob.execute(AlertJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)

The "Queue" Monitor Object Types that I've created work fine.

Here's the row from the "monitors" database table for my "Channel" monitor:

Code:

"monitor_id","company_id","qmanager_id","monitor_object_id","monitor_type_id","trig_condition_type_id","trig_condition_param","criticality_type_id","monitor_nm","message_text","recovery_text","occurrence_interval","polling_interval","log_file","status","modified_dt","modified_by","email_list"
950094353,1,613284735,48175541,3,12,,1,"NYPDPROD2.SUNPROD1::NYPDPROD::CHANNEL_STOPPED","Sender channel stopped.","Check network connectivity to business partner.",15,1,"",1,"","","user@domain.tld"

Can anyone lend a hand with this?

Thanks,
Myles

myles

Posted: Fri Apr 14, 2006 10:48 am Post subject: Re: QFlex: Problem with "Channel" Monitor Object

Newbie

Joined: 09 Dec 2005
Posts: 3
Location: New York, NY

myles wrote:

I've created a "Channel" Monitor Object Type, and the following is written to Tomcat's "stdout.log" every time it fires:

Code:

The "Queue" Monitor Object Types that I've created work fine.

Here's the row from the "monitors" database table for my "Channel" monitor:

Code:

Can anyone lend a hand with this?

Thanks,
Myles

This also appears in "stdout.log":

Code:

Apr 14, 2006 2:43:48 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already (the eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact)
Apr 14, 2006 2:43:48 PM org.apache.catalina.loader.WebappClassLoader loadClass

jefflowrey

Posted: Fri Apr 14, 2006 11:11 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I expect one of the authors of QFlex to be along in this thread at some point...

Just be patient. You may have to wait until Monday.
_________________
I am *not* the model of the modern major general.

myles

Posted: Thu Apr 20, 2006 12:08 pm Post subject: Still no joy.

Newbie

Joined: 09 Dec 2005
Posts: 3
Location: New York, NY

No such luck. I emailed qflex@netflexity.com as well. Dead air. Is there another address I should be using?

Thanks,
Myles

jefflowrey

Posted: Thu Apr 20, 2006 12:15 pm Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Weird.

http://www.mqseries.net/phpBB2/profile.php?mode=viewprofile&u=7995
_________________
I am *not* the model of the modern major general.

malammik

Posted: Tue May 09, 2006 5:55 am Post subject:

Partisan

Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA

Fix was posted yesterday.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex

mapa

Posted: Mon Jun 26, 2006 4:20 am Post subject: Channel

Master

Joined: 09 Aug 2001
Posts: 257
Location: MalmÃ¶, Sweden

Hi,

I've just started to try out this software and it looks quite nice so far. (Currently running self-written java application to monitor MQ and looking for a better alternative.)
However I have the same problem with the monitoring of channels.
Where can I find the fix you are talking about.
Running the 1.0.22.10 build of Qflex, downloaded last week.

Code:

2006-06-26 14:16:00,096 ERROR [QflexScheduler_Worker-1] core.JobRunShell (JobRunShell.java:200) - Job alertsGroup.alertsCronJobDetail884605275 threw an unhandled Exception:
java.lang.NullPointerException
at com.netflexity.qflex.alert.triggers.ChannelIsRetryingTrigger.performCheck(ChannelIsRetryingTrigger.java:20)
at com.netflexity.qflex.alert.triggers.AbstractChannelTrigger.check(AbstractChannelTrigger.java:41)
at com.netflexity.qflex.jobs.AlertJob.execute(AlertJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
2006-06-26 14:16:00,096 ERROR [QflexScheduler_Worker-1] core.ErrorLogger (QuartzScheduler.java:1896) - Job (alertsGroup.alertsCronJobDetail884605275 threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
* Nested Exception (Underlying Cause) ---------------
java.lang.NullPointerException
at com.netflexity.qflex.alert.triggers.ChannelIsRetryingTrigger.performCheck(ChannelIsRetryingTrigger.java:20)
at com.netflexity.qflex.alert.triggers.AbstractChannelTrigger.check(AbstractChannelTrigger.java:41)
at com.netflexity.qflex.jobs.AlertJob.execute(AlertJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » IBM MQ Performance Monitoring » QFlex: Problem with "Channel" Monitor Object Type

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