Actually, let me just take back my previous statement. The error below
is actually thrown by Castor

> Failed to get an active transaction from J2EE transaction manager.

Problem is, that the stack trace given by you is completely unrelated,
as far as I can tell.

With the error message given, Castor signals that your global
transaction is not active (though it should be).

Assuming that you are using EJBs, what kind of transaction demarcation
are you using (declarative vs. programmtic) ?

Werner

Werner Guttmann wrote:
> Hi,
> 
> the stack trace given below to me seems to be quite unrelated to Castor
> JDO. Is this the complete stack trace ? Or is there any more stacktrace
> information attached to the original error message ?
> 
> Werner
> 
> Tejesh Shetty wrote:
> 
>>I tried that, get the same error. It says 'Failed to get an active
>>transaction from J2EE transaction manager.' 
>>
>>Exception it throws is: 
>>
>>javax.ejb.EJBException: nested exception is:
>>com.mhub.core.error.DAOException: |1900:Unable to obtain a connection to
>>Database|
>>com.mhub.core.error.DAOException: |1900:Unable to obtain a connection to
>>Database|
>>        at com.mhub.core.ejb.PersistenceManagerBean.getDatabase(Unknown
>>Source)
>>        at com.mhub.core.ejb.PersistenceManagerBean.executeLoad(Unknown
>>Source)
>>        at
>>com.mhub.core.ejb.PersistenceManager_gi1prg_ELOImpl.executeLoad(Persiste
>>nceManager_gi1prg_ELOImpl.java:1133)
>>        at
>>com.mhub.core.ejb.client.LocalPersistenceManager.executeLoad(Unknown
>>Source)
>>        at com.mhub.core.security.Authenticator.authenticate(Unknown
>>Source)
>>        at com.mhub.ppa.common.LogonAction.execute(Unknown Source)
>>        at
>>org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
>>ocessor.java:484)
>>        at
>>org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
>>274)
>>        at
>>org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
>>        at
>>org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
>>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
>>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>>        at
>>weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
>>rvletStubImpl.java:1072)
>>        at
>>weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
>>java:465)
>>        at
>>weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
>>java:348)
>>        at
>>weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
>>un(WebAppServletContext.java:6981)
>>        at
>>weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
>>bject.java:321)
>>        at
>>weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
>>)
>>        at
>>weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
>>etContext.java:3892)
>>        at
>>weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
>>java:2766)
>>        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
>>        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>>
>>Tejesh Shetty | Software Programmer, MortgageHub Inc. | Conshohocken, PA
>>| Tel: 610.834.3800 ext 106 | [EMAIL PROTECTED]
>>
>>-----Original Message-----
>>From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
>>Sent: Tuesday, January 10, 2006 4:24 PM
>>To: [email protected]
>>Subject: Re: [castor-user] Castor Weblogic 8.1 transactionManager
>>returning null !!!
>>
>>Hmmm ... according to docs, with Weblogic 8.1, the transaction manager
>>is bound to "javax.transaction.TransactionManager". So changing below to
>>
>><transaction-demarcation mode="global">
>>   <transaction-manager name="jndi">
>>      <param name="jndiEnc"
>>             value="javax.transaction.TransactionManager"/>
>>   </transaction-manager>
>></transaction-demarcation>
>>
>>should do the trick. If not, what exceptions are you getting (if any) ?
>>
>>Werner
>>
>>Tejesh Shetty wrote:
>>
>>
>>><?xml version="1.0" encoding="UTF-8"?>
>>><!DOCTYPE jdo-conf PUBLIC "-//EXOLAB/Castor JDO Configuration DTD
>>>Version 1.0//EN"
>>>                           "http://castor.org/jdo-conf.dtd";>
>>><jdo-conf>
>>>     <database name="CoreHub" engine="oracle">
>>>             <jndi name="java:comp/env/jdbc/corehub"/>
>>>             <mapping href="CoreHub.xml"/>
>>>     </database>
>>>   <transaction-demarcation mode="global">
>>>    <transaction-manager name="jndi">
>>>        <!--<param name="jndiEnc"
>>>value="javax.transaction.TransactionManager"/>-->
>>>       <param name="jndiEnc" value="java:comp/UserTransaction"/>
>>>
>>>    </transaction-manager>
>>> </transaction-demarcation>
>>></jdo-conf>
>>>
>>>Tejesh Shetty | Software Programmer, MortgageHub Inc. | Conshohocken,
>>
>>PA
>>
>>
>>>| Tel: 610.834.3800 ext 106 | [EMAIL PROTECTED]
>>>
>>>-----Original Message-----
>>>From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
>>>Sent: Tuesday, January 10, 2006 4:13 PM
>>>To: [email protected]
>>>Subject: Re: [castor-user] Castor Weblogic 8.1 transactionManager
>>>returning null !!!
>>>
>>>Hi,
>>>
>>>what does your JDO config file look like ?
>>>
>>>Regards
>>>Werner
>>>
>>>Tejesh Shetty wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>
>>>>
>>>>I am trying to deploy an application on Weblogic 8.1 using castor
>>>
>>>0.991.
>>>
>>>
>>>
>>>>Looks like EJB deploys well but during login when ejb tries to go get
>>>>something from database it dies saying unable to get database
>>>>connection. I did some test method and found out that it's not getting
>>>>transaction out of TransactionManager and its returning null. I am not
>>>>sure if jndi is not set up correctly in database.xml. Currently it
>>>
>>>goes
>>>
>>>
>>>
>>>>look for "java:com/UserTransaction".I think other options were
>>>>"javax.transaction.TransactionManager" gives back the same exception.
>>>>
>>>>
>>>>
>>>>Any help on this will be great.
>>>>
>>>>
>>>>
>>>>Thanks in advance.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>**Tejesh Shetty | ****Software Programmer, MortgageHub Inc. |
>>>>Conshohocken, PA | Tel: 610.834.3800 ext 106 | [EMAIL PROTECTED]
>>>><mailto:[EMAIL PROTECTED]>m <mailto:[EMAIL PROTECTED]>**
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>-------------------------------------------------
>>>If you wish to unsubscribe from this list, please 
>>>send an empty message to the following address:
>>>
>>>[EMAIL PROTECTED]
>>>-------------------------------------------------
>>>
>>>
>>>-------------------------------------------------
>>>If you wish to unsubscribe from this list, please 
>>>send an empty message to the following address:
>>>
>>>[EMAIL PROTECTED]
>>>-------------------------------------------------
>>>
>>>
>>
>>
>>
>>-------------------------------------------------
>>If you wish to unsubscribe from this list, please 
>>send an empty message to the following address:
>>
>>[EMAIL PROTECTED]
>>-------------------------------------------------
>>
>>
>>-------------------------------------------------
>>If you wish to unsubscribe from this list, please 
>>send an empty message to the following address:
>>
>>[EMAIL PROTECTED]
>>-------------------------------------------------
>>
>>
> 
> 
> 
> -------------------------------------------------
> If you wish to unsubscribe from this list, please 
> send an empty message to the following address:
> 
> [EMAIL PROTECTED]
> -------------------------------------------------
> 
> 


-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

Reply via email to