On Nov 11, 2007, at 8:08 PM, Will Tao wrote:
> Hi all,
> We are trying integrate Resin with Quartz via RMI Registry, which
> Resin and Quartz are deployed in distributed manner.
> 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
> throws SocketTimeout.
That sounds more like a JMS application.
> Then we are trying to fire JMS message from Quartz to Resin, the JMS
> message wraps Job and JobExecutionContext, and can be picked by
> MessageBean in Resin side.
> The question is how can I get JMSConnectionFactory and JMSQueue
> resources via Hessian/JNDI if I try to fire the message remotely (i.e.
> in another JVM) ?
> I have tried put JNDI-link into resin.conf but no luck.
> There is no problem to locate JMS resources if it calls in the same
> but it seems very different if this happens cross JVM, and currently I
> cant find any docs about this. Any one have same issue?
Which JMS provider are you using?
In general, Resin treats JNDI as a local registry. Since the sending
JVM has a different view of JMS than the receiver, it would use a
different JNDI entry.
> Any suggestions will be appreciated, thanks in advance.
> Will Tao
> Java Developer
> ICT Group
> NetRegistry Pty Ltd
> resin-interest mailing list
resin-interest mailing list