>> The first approach we tried is pass the job into Resin by using Remote
>> EJB, but since some jobs take more than hours to run, this causes
>> Resin
>> throws SocketTimeout.
>>
>
> That sounds more like a JMS application.
>
* The application is still more towards to J2EE, JMS is intro
I have a quick question. This may possibly be directed to Scott.
How does resin determine what resin server instances run under the
same watchdog process? This relates to a bug issue that I just posted
in bug track.
Does resin use the server root, the monitored ports, the resin.conf,
and
I'm running resin-pro-3.0.23 and have seen a lot of these errors in my
logs today:
java.lang.IllegalStateException
at
com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:253)
at
com.caucho.server.session.SessionImpl.load(SessionImpl.java:702)
at
com.caucho.server.sess