I know we have to move our file import processes to WorkManager
since we have a cluster and don't know which machine gets the
file and thus had to send the message to a Topic. Only MDBs on
a topic in a cluster will fire on only one of the servers (they
effectively act like a queue).
Still broken in 2.1 and JMS is not implemented yet in 3.0.
Brian
----- Original message -----
From: glassfish_at_javadesktop.org
To: users_at_glassfish.dev.java.net
Date: Tue, 10 Feb 2009 10:28:57 PST
Subject: Re: Queueing jobs for processing in their own thread/transaction?
> I thought I could use JMS for this but the JMS
> implementation with glassfish
> v2ur2 is too buggy and I can't upgrade to 2.1 due to
> some weird classpath
> issues in 2.1 I couldn't resolve.
What issues are you having with JMS? Seems to me that JMS with a constrained MDB (i.e. container can not make more than, say, 5 instances) would work well at letting you control resource uses. And this doesn't sound like a particularly exotic use of JMS.
So I'm curious what problems you're encountering with it.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=331076
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net