More information,
The root of this looks to be something to do with the TimerService when deployed in the cluster.
Caused by: java.lang.IllegalStateException: EJB Timer Service not available^M
at com.sun.ejb.containers.ContainerFactoryImpl.getEJBContextObject(ContainerFactoryImpl.java:854)^M
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:965)^M
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173)^M
What would cause this?
[Message sent by forum member 'samdoyle' (samdoyle)]
http://forums.java.net/jive/thread.jspa?messageID=237454