Hi,
this is standard ejb behavior, the Bean gets locked if it is accessed, since
on BMP the app-server never knows what you are going to do, right (there is
no reson why you shouldn't do some update-statement when reading a value,
right?!? So go ahead and read the long and most entertaining discus
;[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 12:57 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> I cannot tell from your description whether the entity bean method's
transaction
> attribute is tx_supports. If it is, then JBoss should be throwing an
exception
are correct.)
Mike
- Original Message -
From: "Victor Langelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 12:31 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> Michael Jara wrote:
>
> > Yes, Sybase ASE
nds of LOCKING-WAITING messages go into the logfile (which grows and
grows, not unexpected behavior so I'm not complaining.) The transaction
eventually times out, but the entity bean remains locked until I restart the
application server.
Mike
- Original Message -----
From: "marc
I cannot tell from your description whether the entity bean method's transaction
attribute is tx_supports. If it is, then JBoss should be throwing an exception
since setRollbackOnly isn't valid in this context.
--Victor
Michael Jara wrote:
> FYI: I took a clue from bug #420714 an tried moving m
Michael Jara wrote:
> Yes, Sybase ASE is case sensitive as to table and column names. (SQL
> keywords may be any case.) I beleive this is not unique to Sybase, but is
> also the case in some other database servers such as Oracle. JAWS in JBoss
> 2.2.2 works properly, but Beta 2.4 does not...
server is
perfect.)
>
> Has nobody else noticed this problem?
>
> Mike
>
> - Original Message -
> From: "danch" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 27, 2001 11:02 PM
> Subject: Re: [JBoss-user] LOCKING-WAITING
EMAIL PROTECTED]]On Behalf Of Michael Jara
|Sent: Thursday, June 28, 2001 1:05 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
|
|
|Yes, Sybase ASE is case sensitive as to table and column names. (SQL
|keywords may be any case.) I beleive this is not uniq
;
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 27, 2001 11:02 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> Michael Jara wrote:
>
> > I've run into a problem previously mentioned in the archives here:
> >
http://www.mail-archive.com/jboss-user@
Michael Jara wrote:
> I've run into a problem previously mentioned in the archives here:
> http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg03141.html
>
>
>
> Does anyone have a good workaround for this (aside from "don't use
> setRollbackOnly", or "hack TxCapsule and build i
I've run into a problem previously mentioned in the
archives here: http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg03141.html
Does anyone have a good workaround for this (aside
from "don't use setRollbackOnly", or "hack TxCapsule and build it
yourself"?) This seems like a p
Hi,
ivanhoe Abrahams wrote:
> Could anyone point me in the right direction when it comes to solving
> the LOCKING-WAITING problem
> It hangs my client/keeps the server so busy that everything slows down
> to a snail's pace.
In the current CVS version of JBoss is a partial fix for that and
some d
Hey,
there is no problem.
You can reduce the log's size by removing the "Debug" option from the file
logger in jboss.conf
HTH,
Simon
> -Original Message-
> From: madhu [mailto:[EMAIL PROTECTED]]
> Sent: giovedì 3 maggio 2001 16:59
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] LOCKIN
e 2.3 developer version.
Achim
- Original Message -
From: "danch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 8:33 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> I'll put together a little sample and look i
I'll put together a little sample and look into this. By my reading of
the spec, you should be able to call into the bean (even the same
instance) after you call setRollbackOnly and throw an application
exception. Even if that weren't legal, locking-waiting would not be what
we'd want to see.
-d
> What version of JBoss is this?
>
2.2 binary distribution w/ tomcat 3.2.1
> The Classification that's being passed in is null, correct? Otherwise
> commenting out the call to setRollbackOnly should have no effect.
>
Yes, it's null. Oops, I see I've copied the wrong method into the email, but
What version of JBoss is this?
The Classification that's being passed in is null, correct? Otherwise
commenting out the call to setRollbackOnly should have no effect.
The test client calls the entity directly (not through a session
wrapper), correct?
-danch
Achim Demelt wrote:
>
> hi,
>
> I
Hi,
At 13:43 21.3.2001 -, you wrote:
>I'm also working on that, I fixed it but didn't tested it enough.
>Keep me informed if you will work on this.
I was only planning to drop the patch in...didn't want it to get lost. But
you can have this one, you're more familiar with it :) Enjoy!
-- J
Hey,
At 13:43 21.3.2001 -, you wrote:
>I'm also working on that, I fixed it but didn't tested it enough.
>Keep me informed if you will work on this.
I was only planning to drop the patch in...didn't want it to get lost. But
you can have this one, you're more familiar with it :) Enjoy!
--
Hi,
On Wed, 21 Mar 2001, Alexander Kogan wrote:
> marc fleury wrote:
> >
> > Just out of curiousity Simone...
> >
> > when we benched at SUN one of the big difference under load was the thread
> > management.
> >
> > The best in terms of resource usage was put the thread to sleep (with a 5
>
"Swarr, Bob" wrote:
>
> To address these problems a number of theorticians in concurrent
> programming, such as Brinch Hansen, developed the idea of a monitor. I guess
> today we would call it a design pattern. Some writers claim that Java
> wait() and notify() implement a monitor, although I've
Hey,
> Which leads to a question since I'm a JBoss novice. Is there
> a way to set
> the number of threads in JBoss? I use WebLogic regularly and
> it provides a
> configuration parameter that allows you to set the number of
> threads in the
> VM that the server uses.
No. (but this is open s
y, March 21, 2001 10:07 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] LOCKING-WAITING
marc fleury wrote:
>
> Just out of curiousity Simone...
>
> when we benched at SUN one of the big difference under load was the thread
> management.
>
> The best in terms of resource us
marc fleury wrote:
>
> Just out of curiousity Simone...
>
> when we benched at SUN one of the big difference under load was the thread
> management.
>
> The best in terms of resource usage was put the thread to sleep (with a 5
> sec timeout) and notify (1) and that REALLY flew and scaled REALLY
Marc,
> Just out of curiousity Simone...
>
> when we benched at SUN one of the big difference under load
> was the thread
> management.
>
> The best in terms of resource usage was put the thread to
> sleep (with a 5
> sec timeout) and notify (1) and that REALLY flew and scaled
> REALLY well
ECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bordet,
|Simone
|Sent: Wednesday, March 21, 2001 8:44 AM
|To: '[EMAIL PROTECTED]'
|Subject: RE: [JBoss-user] LOCKING-WAITING
|
|
|Juha,
|
|> Hi,
|>
|> will do (once the cvs is back online again)
|
|I'm also working on that, I fixed i
e the problem too. (having a log file of 400mb)
> >
> >will this fix be checked into cvs?
> >
> >thx markus
> >
> >
> >-Original Message-
> >From: Bill Burke [mailto:[EMAIL PROTECTED]]
> >Sent: Dienstag, 20. März 2001 21:14
> >To: [E
PROTECTED]]
>Sent: Dienstag, 20. März 2001 21:14
>To: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] LOCKING-WAITING
>
>
>You're may be getting such a performance hit because of all the
>LOCKING-WAITING messages being sent to jboss/logs/server.log. Check out
>
>that
I have the problem too. (having a log file of 400mb)
will this fix be checked into cvs?
thx markus
-Original Message-
From: Bill Burke [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 20. März 2001 21:14
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] LOCKING-WAITING
You're may be ge
You're may be getting such a performance hit because of all the
LOCKING-WAITING messages being sent to jboss/logs/server.log. Check out
that file, my guess it will be very, very large.
BTW, please don't remove that message. It is very useful for debugging
purposes.
Here's a fix for that ver
it is not a deadlock it is normal synchronization...
we must change that message
marc
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Dragan Milic
|Sent: Tuesday, March 20, 2001 1:05 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-user] LOCKING-WAITING
|
31 matches
Mail list logo
