Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: JBoss JTA transaction timeout
Date: Mon, 2 Jul 2007 14:52:52 +0300
Message-ID: <62A1225A562C114FA7D70C58B5D35A42027C44BF@mailer.totalsoft.local>
Thread-Topic: JBoss JTA transaction timeout
Thread-Index: 
 Ace6VJ7A13k1DJ3oSFO7xfdd6X9ZoACFajVgAAafo8AAAH7SMAAAJ0WAAACc8PAAAODpoA==
From: "Mihai Anescu" <manescu@totalsoft.ro>
To: <users@jackrabbit.apache.org>

Yes, I got it.
I modified my code, so I create a session attribute and init that one, =
and I test before doing the repo.login() to see if I don't have an =
active session.=20
I cannot use session.logout() as this also comes with its bugs :(. =
Apparently inside a JTA transaction the session will attach to it and be =
closed when the JTA transaction performs the commit.

So, I modified my code to have only one session. I can upload the =
message, but when it downloads it after that it says:

Caused by: java.lang.IllegalStateException: Inactive logical session =
handle called
	at =
org.apache.jackrabbit.jca.JCAManagedConnection.getSession(JCAManagedConne=
ction.java:227)
	at =
org.apache.jackrabbit.jca.JCASessionHandle.getSession(JCASessionHandle.ja=
va:84)
	at =
org.apache.jackrabbit.jca.JCASessionHandle.getRootNode(JCASessionHandle.j=
ava:135)


-----Original Message-----
From: K=D6LL Claus [mailto:C.KOELL@TIROL.GV.AT]=20
Sent: Monday, July 02, 2007 12:42 PM
To: users@jackrabbit.apache.org
Subject: AW: JBoss JTA transaction timeout

> Yes, I may open a new session inside the same transaction (I'm quite =
new to Seam so I don't know in detail how it handles everything, but =
almost sure I open more=20
> than one transaction).=20

... you can not open more than 1 session inside a container transaction =
..

> Both the upload & download methods get a new session when they start =
doing their job.
ok thats the normal way ..

public void testme() { <-- is a EJB SesssionBean Method
//ContainerTransaction begnis ...
Session sess =3D getRepository().login(credentials, workspaceName);
sess.getRootNode().addNode(....);
...
sess.save();
sess.logout();
}
//Container Transaction ends
if you now open a second session inside this transaction you will get a =
timeout eception ...

BR,
claus

-----Original Message-----
From: K=D6LL Claus [mailto:C.KOELL@TIROL.GV.AT]=20
Sent: Monday, July 02, 2007 11:58 AM
To: users@jackrabbit.apache.org
Subject: AW: JBoss JTA transaction timeout

the only thing you must looking for not to open 2 sessions in 1 =
transaction !
maybe you are opening a adminsession in the accessmanager ?
even if you do only reading with the second session you will get a =
timeout exception !

the locking strategy is at the moment designed not to allow 2 sessions =
in one transaction !

BR,
claus