problem solved :) i've done a lookup forcing the marshalling for method
invocation (called-by-value) by putting the full scheme in the lookup :
| new InitialContext(jnp://localhost:1099/EJBJndiName);
|
(my project manager wanted to keep the scoping of classloading for my ear so
that was
so the problem is caused by the isolation of classloading in my ear.
I tested by putting the attribute calledByValue in
default/deploy/conf/jboss-service.xml and it worked, but it's not an acceptable
solution as it has repercutions on all jndi lookups, and it increase a lot the
ressource usage
i finally got rid of the Wrong tx on thread, but another strange issue is
happening :
I first get the TransactionManager via jndi (java:TransactionManager).
then i suspend the current transaction :
t = tm.suspend();
then i do the lookup of my EJB remote or local interface, and i put it into an
i've done some tests they might be helpfull to resolve this issue.
i've changed the instruction :
obj = (NameOfEJBLocalInterface) new InitialContext().lookup(jndiName);
to :
Object obj = new InitialContext().lookup(jndiName);
System.out.println(obj.toString());
NameOfEJBLocalInterface obj2 =
