Groups > comp.lang.java.programmer > #10032

Re: JMS scalability question

From	Saxo <saxo123@gmx.de>
Newsgroups	comp.lang.java.programmer
Subject	Re: JMS scalability question
Date	2011-11-17 23:27 -0800
Organization	http://groups.google.com
Message-ID	<02f111c6-77f8-4413-873e-e30b03b809f1@o5g2000yqa.googlegroups.com> (permalink)
References	<bb8b61d2-fe1f-42b8-93d8-2d1a329e6afb@a16g2000yqk.googlegroups.com> <slrnjc9gda.tm7.fredrik@scout.jonson.org> <39166d35-4fc6-40ed-898a-d747b5f761c0@m7g2000vbc.googlegroups.com> <slrnjcatit.u4r.fredrik@scout.jonson.org>

Show all headers | View raw

> Without having the actors also transacted by default you can't interrupt
> them reliably. Was the current message content acted on, not acted on, or
> partially acted on? Now, if you use jms you can simply close the session,
> and the consumer thread will rollback a transacted dispatch, or wait for
> completion of non-transacted dispatch.

It can only be done with the assistance of the framework user by being
nice to the system. If an interrupt message arrives, some synchronized
flag is changed. The method being invoked at that time needs to poll
this flag periodically. If it is observed as having changed the user
has to do something himself to get the context stored, invoke the
interrupt handler, restore the context and continue. Not very elegant,
but in Java there is no API to access the threading system in order to
suspend/save context/resume threads.

> I hope you get your project of the ground, sounds like fun hacking on a
> interesting problem.

All right :-). Yes would be fun and you would gain many new insights.

Regards, Oliver

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

JMS scalability question saxo123@gmx.de - 2011-11-15 02:07 -0800
  Re: JMS scalability question Roedy Green <see_website@mindprod.com.invalid> - 2011-11-16 06:21 -0800
    Re: JMS scalability question saxo123@gmx.de - 2011-11-16 09:35 -0800
      Re: JMS scalability question Lew <lewbloch@gmail.com> - 2011-11-16 10:30 -0800
        Re: JMS scalability question saxo123@gmx.de - 2011-11-16 14:25 -0800
          Re: JMS scalability question Lew <lewbloch@gmail.com> - 2011-11-16 17:18 -0800
            Re: JMS scalability question saxo123@gmx.de - 2011-11-16 22:59 -0800
              Re: JMS scalability question jlp <jlp@jlp.com> - 2011-11-17 08:41 +0100
                Re: JMS scalability question saxo123@gmx.de - 2011-11-17 01:00 -0800
      Re: JMS scalability question Roedy Green <see_website@mindprod.com.invalid> - 2011-11-16 16:16 -0800
  Re: JMS scalability question Fredrik Jonson <fredrik@jonson.org> - 2011-11-17 08:11 +0000
    Re: JMS scalability question saxo123@gmx.de - 2011-11-17 01:26 -0800
      Re: JMS scalability question Fredrik Jonson <fredrik@jonson.org> - 2011-11-17 21:01 +0000
        Re: JMS scalability question Saxo <saxo123@gmx.de> - 2011-11-17 23:27 -0800

csiph-web