In reference to:
http://www.jboss.org/forums/thread.jsp?forum=48&thread=3150
My first cut at this is that it has to do with the pool. The exception
happens when the pool is trying to clean up and the XA resource is no
longer tied to any sessionID. (any one interested in seeing the trace,
it's 1 M).
Look at this:
[94230] [Thread Pool Worker-2] [JmsXA] Pool org.jboss.jms.ra.JmsManagedConnectio
nFactory-1 [1/2/10] gave out pooled object: org.jboss.jms.ra.JmsManagedConnectio
n@41c92b
[94321] [Thread Pool Worker-0] [JmsXA] Pool org.jboss.jms.ra.JmsManagedConnectio
nFactory-1 [1/2/10] gave out pooled object: org.jboss.jms.ra.JmsManagedConnectio
n@41c92b
[94327] [Thread Pool Worker-0] [JmsXA] Pool org.jboss.jms.ra.JmsManagedConnectio
nFactory-1 [0/2/10] returned object org.jboss.jms.ra.JmsManagedConnection@41c92b
to the pool.
[94354] [Thread Pool Worker-2] [JmsXA] Pool org.jboss.jms.ra.JmsManagedConnectio
nFactory-1 [0/2/10] returned object org.jboss.jms.ra.JmsManagedConnection@41c92b
to the pool.
The pool leaves out the same ManagedConnection twice, the one in Worker
0 will ovewrite the one in Worker-2, and when worker two closes there is
no longer a corrext XAResource connected to it. Why this happens I don't
know.
Here what I found in a more modern BaseConnectionManager:
if ( pool != null ) {
//Avoid race condition whereby con can be reused before clear is called.
ObjectPool mypool = pool;
ManagedConnection mycon = con;
clear();
mypool.releaseObject( mycon );
}
But here is from the same spot from 2.4:
if(pool != null) {
pool.releaseObject(con);
clear();
}
But I do not know if this is the problem you are having.
//Peter
On 23 Okt, Lars Olsson wrote:
> Peter Antman wrote:
>
>>
>> Hej, tja det kan du g�ra. De n�rmaste dagarna kommer jaga vara r�tt
>> ordenligt chokad. Dessutom �r det Hiram som har gjort all
>> transaktionshatering. Jag vet inte ens vad XAER_OUTSIDE �r f�r n�got.
>>
>> Men skicka den du f�r vi se vad den triggar hos mig ;-)
>
>
> OK - tack. Jag bifogar konsol-loggen plus den modifierade log4j.properties
> jag anv�nt.
>
> Applikationen best�r av ett antal Mdb:er som drivs av samma MDB-klass.
> Varje mdb har ett egen-uppfunnet instans-namn. Log4j-kategorinamnen
> �r baserade p� dessa instans-namn f�ljt av Hash-code f�r MDB-klass
> java-instansen.
>
> Lars
--
------------------------------------------------------------
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems Architect WWW: http://www.tim.se
Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
------------------------------------------------------------
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
