ms Uday

here is the actual post in Websphere group.

as this is architect certification group,I thought I would ask this question here..

https://coderanch.com/t/527888/Websphere/Suggestion-Design-consideration-possible-issues

thanks for your help.

appreciate any suggestions/pointers

Hi All,

I am working on an app, the requirement is to continuously monitor a db table for changes and if it finds any, it has to pull data from table(s) , build an xml message and put in on a Websphere MQ and update some other table(stating message posted).

I am planning to use JMX MBean Timer to continuously monitor the DB table for changes and would like to get your Suggestion/opinion/Design consideration & possible issues on below...
using JMX - MBean - Timer in WAS6.1
What are the things to consider when deploying in WAS cluster..?
is there a way to have a singleton timer..?
any suggestions for failover situations..and suggested design patterns to be followed..

thanks in advance..and appreciate any suggestions/pointers

Hi,

I am getting the following exception when a MBean which has a timer and implements NotificationListner-handleNotification calls a Dataaccess class.

If I call the Dataaccess class from jsp it works fine, however the class is giving the below exception when called in handleNotification method.

Any pointers will be greatly appericated.

A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component.
This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request.
Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application.
Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names.
Exception stack trace:
javax.naming.ConfigurationException [Root exception is javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".]
at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS