We have one application made with ejbs, and some of these ejbs have timers for batch jobs that we activate/desactivate from the client. The problem is that the timers are singleton services in the cluster. But, when we call the ejbs, the petitions are balanced within the cluster's nodes and then, some calls give us wrong information (no information) about the timers if the call is routed to an ejb that is living in a node that don't have the timer service activated. We can't call the nodes individually because the calls are balanced across the nodes automatically.
We are working with IBM WebSphere Application Server Network Deployment 220.127.116.11.