Hi All,
Can the people who next respond to this thread *PLEASE* trim their
posts? Digest format can be long enough but this is making it enormous.
Many thanks,
--gps
E-mail is an informal method of communication and may
In our case the parallelism is a requirement.
We wait for threads to return and then proceed.
So ideally we would want to send messages to a
q where they get consumed simultaneously.
Pete Beck wrote:
> I'm not entirely sure how this would be handled in JBoss, but in
> principle you could send ou
I'm not entirely sure how this would be handled in JBoss, but in
principle you could send out a bunch of JMS messages to a topic or
queue.
The EJB container then launches threads to process the messages through
MDB instances. Therefore potentially, your code will be executed in
parallel.
Of cour
Hi Pete!
What was being acheived using threads obviously was some
parallelism...as in we wanted some actions to be executed
simulataneously.
Now I have not worked with MDBs,JMS etc yet.
Are you suggesting using MDBs its possible to acheive
the same and avoid violating the spec?
Any ellaboration is
; > Mob: +353 86 824 9736
> > Fax: +353 1 873 3612
> >
> > "rahul ganjoo" <[EMAIL PROTECTED]>
> > Sent by: [EMAIL PROTECTED]
> > 15.10.2002 13:46
> > Please respond to jboss-user
> >
> >
> > To: [EMAIL PROTECTED]
&g
I think there is a very simple solution to this which is much safer.
Instead of triggering threads off in your class, move the thread body
into a MDB and then simply send several messages from your session bean.
The MDB will enable your code to run asynchronously which is probably
the effect you
>I am looking forward to some good design practices on Worker Thread
>examples.
>
>TIA,
>Saroj
>
>
>
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]] On Behalf Of Marius
>Kotsbak
>Sent: Saturday, October 12, 2002 3:00 AM
>
Thanks Dude,I appreciate the help..
funnily enough we got it to work somehow though the design
needs to change...
- Original Message -
From: "Geer, Benjamin" <[EMAIL PROTECTED]>
Date: Wednesday, October 16, 2002 2:53 pm
Subject: RE: [JBoss-user] Strange Problem on Linux
Marius
Kotsbak
Sent: Saturday, October 12, 2002 3:00 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Strange Problem on Linux
saroj kumar wrote:
>HI All,
>
>I am facing "Transaction Timeout " exception while running
>the code on Redhat Linux 7.3/JDK1.4/JBOSS 3.0.3/Ora
rahul ganjoo wrote:
> Yes Ofcourse the EJB spec doesnt recommend threading
> in EJBs...
It specifically *prohibits* threading. Section 24.1.2 of the EJB 2.0
spec says:
"The enterprise bean must not attempt to manage threads. The enterprise
bean must not attempt
to start, stop, suspend, or resum
rahul ganjoo wrote:
> Yes Ofcourse the EJB spec doesnt recommend threading
> in EJBs...
Section 24.1.2 of the EJB 2.0 spec says:
An enterprise Bean must not use thread synchronization primitives to
synchronize execution of
multiple instances.
--
gt;
>
> To: [EMAIL PROTECTED]
> cc:
> Subject:Re: [JBoss-user] Strange Problem on Linux
>
> Guys any help with this would be much appreciated.
> I am repeating the scenario here:
> Environment: Jboss 3.0.3 ,Red hat Linux 7.2
>
>
ECTED]>
Sent by: [EMAIL PROTECTED]
15.10.2002 13:46
Please respond to jboss-user
To: [EMAIL PROTECTED]
cc:
Subject: Re: [JBoss-user] Strange Problem on Linux
Guys any help with this would be much appreciated.
I am repeating the scenario here:
Environment: Jbos
ead.run
> (AbstractDeploymentScanner.java:202)
>
> "Thread-3" daemon prio=1 tid=0x0x4d483d80 nid=0x5d9 waiting on monitor
> [4e123000..4e12386c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x44c52c70> (a java.util.TaskQueue)
>
at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=1 tid=0x0x80b1748 nid=0x5cf waiting on
monitor [4c4c1000..4c4c186c]
at java.lang.Object.wait(Native Method)
- waiting on <0x44afa740> (a java.lang.ref.Reference$Lock)
tsbak
> Sent: Friday, October 11, 2002 5:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Strange Problem on Linux
>
>
> saroj kumar wrote:
>
> >HI All,
> >
> >I am facing "Transaction Timeout " exception while running
> >the code on Redhat
Hello saroj,
it can be a locking problem. Is there a chance the second
call spawns a thread that calls entity bean that is currently involved
in the transaction initiated by the first call?
Why it doesn't happen on windows?.. Probably, on windows the
transaction needs less time to complete. May i
saroj kumar wrote:
HI All,
I am facing "Transaction Timeout " exception while running
the code on Redhat Linux 7.3/JDK1.4/JBOSS 3.0.3/Oracle9i.
Same code is working fine on Win2k/JBOSS 3.0.3/jdk1.4/Oracle9i.
Scenario is:
UI Layer makes a call to SLSB. This SLSB makes a call to another
SLSB w
18 matches
Mail list logo
