Dear Gianluca,
sorry for the delay, I was busy.
> In the jboss mailinglist archive I found the mail Georg Rehfeld mail (08
May
> 2001) with subject: Transaction blocks forever, LOCKING-WAITING
>
> > > ...
> > > I can access several beans in the first
> > > place, but after a short while I again get a block in the JNDI
> > > lookup() method followed by a transaction timeout message but
> > > with no exception raised. The entity bean remains associated
> > > with the transaction for ever; the next access to it again
> > > produces the millions of 'LOCKING-WAITING (TRANSACTION)'
> > > messages and only a server shutdown helps. .......
>
> I read the Bordet Simone reply that this is a bug and it has to add on the
> SourceForge site...
In my case the problem was really a JNDI lookup. Another user
(Max Du Prel) had a similar problem and could solve it, in his
case someone broke his network configuration, see his bug report
at
https://sourceforge.net/tracker/index.php?func=detail&aid=421293&group_id=22
866&atid=376685.
Until today I believed, that the JNDI lookup on my machine was
not related to network config problems, so I did work around the
problem by implementing a JNDIHelper class, that does the lookup
in a seperate thread, kills that thread when not responding in
time, does the lookup again and caches the result for later use.
If you would be interested, I can send the code.
But today I was able to resolve another issue (could not start JBoss
CVS built from source, problem reportet, I'll report the solution
separately) and I think (but havn't tested yet) this could be
the reason for the lookup problem too:
My ISDN card (AVM Fritz! card) had installed a 2nd (pseudo) network
device. Today I recognized, that pinging myself (via my official
name, not localhost) resolved to the ISDN pseudo interface instead
of the primary interface. I disabled that ISDN interface and, voila,
JBoss CVS started up cleanly. Please note, that all obvious network
settings including winnt/system32/drivers/etc/hosts were perfectly
ok, but W2K did the resolving wrong. And, except with JBoss, all
my networking seemed to be unproblematic. What I think is going on
is, that resolving names sometimes gets one interface and sometimes
the other so that reliable communication can't be done.
So, please, triple check, that your W2K really, really, really
behaves as you expect it to behave and as you think you have it
configured.
> I have the same (or similar) problem:
>
> I'm using CMP entitys and after a while I'm using the entitys by a session
I get
> a lot of this log message (millions):
>
> [Scenario] LOCKING-WAITING (TRANSACTION) for id 1 ctx.hash 8040172
> tx:TransactionImpl:XidImpl [FormatId=257, GlobalId=byrne//801,
BranchQual=]
This problem [the repeating messages and the tight loop stressing
CPU] just was heavily addressed yesterday at the jboss-dev
mailing list and it seems that 2 developers decided to cooperate
on a solution for it, Bill Burke, who said he would do the initial
coding (in context of just another problem he has detected) and
Dan Christopherson, reviewing the change; thanks to both of them.
> and some time between the message log before in the log file I found:
>
> [ScenarioShp] Transaction XidImpl [FormatId=257, GlobalId=byrne//799,
> BranchQual=] timed out. status=STATUS_ACTIVE
> ...
> [ScenarioShp] Transaction XidImpl [FormatId=257, GlobalId=byrne//801,
> BranchQual=] timed out. status=STATUS_ACTIVE
> ...
> [ScenarioShp] Transaction XidImpl [FormatId=257, GlobalId=byrne//803,
> BranchQual=] timed out. status=STATUS_ACTIVE
> ...
This looks to me, as if 3 (or more?) beans are deadlocked, because
of the 3 different GlobalID's 799, 801 and 803, this should be
reflected also in the LOCKING-WAITING messages. Bill and Dan for
sure will solve the deadlock problem (via timeout) as this issue
was discussed yesterday too.
> Another similar problem I think is the following:
>
> I have 2 application deployed in jboss:
> - application A: datasource DA, database DBA
> - application B: datasource DB, database DBA
>
> In both applications I'm using some entity CMP and a session (stateless).
>
> Application B in a session bean (stateless) uses some entity of
application A,
> because need to make a copy in the application B. So it get information
from
> application A by entity, create new entity in the application B and make a
copy.
> After a while my application don't give me any answer, but I didn't get
any
> exception (like a loop).
> After some time in the log file I get the message:
>
> [Emergenza] Transaction XidImpl [FormatId=257, GlobalId=byrne//441,
BranchQual=]
> timed out. status=STATUS_ACTIVE
>
> but the application still blocked and I have to restart JBoss.
Hmmm, if only one Transaction times out, it might be similar to
my initial problem: something hangs. But might be, your App B tries
to access some bean in App A, that itself is deadlocked? Nevertheless,
whatever the cause is, Bill and Dan will fix that soon by deadlock timeout.
> I have to leave jboss? :-(
I don't think so, I've some experience with the Ejipt EJB server,
now integrated into JRun from Allaire. Support for Ejipt was good
as long as they were a little (2 person I believe) company; and then
I even had no source, but had to rely on the good will of the
company. Since Allaire has put it's money on it, support is 'as
usual': nothing except more or less friendly clerks, not understanding
any word in a bug report.
In JBoss I've seen developers react with code changes checked
into CVS 2 hours after someone asked for it! And then, as it
is Open Source, just do it yourself :-)
best regards
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
