hari haran sethu raman

ok. In the following sequence, do you mean that,

session.open // open a sssion and load object A
A.getB() //will return me B proxy . Here I should be careful to perform getImplementation for B actual object? But still I didnt do
A.getB().getRef() // will load B actual object since I did an action in B object through getRef
B b = A.getB() // no more proxy here

Thanks,
Hari

Hi,

I have an object A and B where A has a reference of B and from B to A. B is configured as lazy in A.hbm.xml

When I do a session.createCriteria by giving the A's row-identifier it returns me the A object. And when I perform A.getB(), it returns me the object of type something like this B__$$_javassist_46.

What is this? Sometimes I have also seen when I invoke A.getB() it returns me the object of type B. Why sometimes it returns me B__$$_javaassist_46?

What is this?
What I have to do such that, my code for A.getB() should always return the object of type B and not as B__$$_javaassist_46 type?

Thanks,
Hari

DId you get the solution?

Yea thats right, I will try with TRACE next time. I am not sure whether I will reproduce this. Already I have tried twice . Not reproducing

In the meanwhile I am trying to find out the possibilities.

Did you get the solution for this problem?

I am struggling to a similar issue.

Hi All,


I have written one jboss service which will spawn threads. In the thread I will open Hibernate transaction and do some commits. I will invoke the service through my API.

In this API, the implementation is, here also I will open a Hibernate transaction, do some manipulation, then will invoke above service and commits the changes to DB done in the API and return from API.

I am sure that both the transaction in my service and API uses its own hibernate transaction. I am also sure the API doesnt have any big implementation for any timeout. it may take only few milliseconds to complete the API.

When I invoke the API from my client, I get the below trace in the client side exception catch. I have invoked thie API for around 45 times, it worked fine. when I invoked after this 45th, I get the below exception. But after sometime, the API again works fine. This is not getting reproduced consistently. What are all the chances for the same transaction to be used by multiple threads? Is there any chance during the thread reuse?

In the above usecase I may have threads running parallel maximum of two at a time. Means, i would have called the same API continuously and quickly. But this continuous call is very rare. Any inputs from jboss transaction perspective would be helpful.

Thanks,
Hari


- [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1379)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at com.example.testInterceptor.invoke(testInterceptor.java:48)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at com.cisco.dcbu.dcm.interceptor.ejb3.AuditInterceptor.invoke(AuditInterceptor.java:96)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)

I couldnt get much information from google or i may not be able understanding it.

What is delete cascade option?
What is delete-orphan cascade option?
Difference btwn it?

Adding C to the project a should solve the problem.

What the actual clarification that I require is, why the indirect reference from project A is illegal project C? Why such restriction?

Because ever I move the code to any place, i have to move my project B as well. In turn, I have to project C.

Yes

Assume those(A,B,C) as project in eclipse. We makes dependancy using the Java build path options in project available in eclipse. I open a java file under project A. I can see the reference(types) available using a Ctl-Space, where I cannot see the class files in project C. Though they are going to execute under same classloader? Why the reference of C is illegal to A. Why it is restricted?

Hi,

We have three projects A,B,C; where A depends on B and B depends on C. From project-A, why I couldnt get a refernece to a class in project-C. I hope all should be loaded from the same class loader? Or any link that clarifies my doubt will be helpful.

Thanks,
Hari