Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-users] RE: eclipselink-users Digest, Vol 18, Issue 44 
Kevin:

Regarding to the datasource issue in Jboss 5.0 GA, per your sugestion, I tested with  

<jta-data-source>java:/jpaTestJtaDS</jta-data-source>

However, it still gives me the same error. You mentioned that it went well when you tested EclipseLink with JBoss GA 5.0.
What is your EclipseLink and Jboss related configuration inside persistence.xml? Did you configure a SessionCustomizer?
Do you mind sharing your persistence.xml file?

Michael:
Your suggestion to configure a SessionCustomer seems to be on the right track so that EclipseLink JNDIConnector will be using
STRING_LOOKUP instead of "COMPOSITE_NAME_LOOKUP". However, when I tried to define a session customizer, I found the base class

org.eclipse.persistence.internal.sessions.factories.SessionCustomizer;

No long exists in EclipseLin 1.0.2. I suspect that a common string lookup session customizer class would be included with the distribution of EclipseLink so that a developer can just configure it inside persistence.xml without having to extending the base class. Is this the case? If not, could you point out the new base class for session customizers? 

Many thanks,


Regards,
Daoqi  Yang
Application Technology Architect
Ford Java Center of Excellence, E1F001 iTek
dyang11@xxxxxxxx, 313-206-3960

-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of eclipselink-users-request@xxxxxxxxxxx
Sent: Monday, February 23, 2009 11:48 AM
To: eclipselink-users@xxxxxxxxxxx
Subject: eclipselink-users Digest, Vol 18, Issue 44

Send eclipselink-users mailing list submissions to
	eclipselink-users@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://dev.eclipse.org/mailman/listinfo/eclipselink-users
or, via email, send a message with subject or body 'help' to
	eclipselink-users-request@xxxxxxxxxxx

You can reach the person managing the list at
	eclipselink-users-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of eclipselink-users digest..."


Today's Topics:

   1. RE: eclipselink-users Digest, Vol 18, Issue 43 (Yang, Daoqi (D.))
   2. Re: EclipseLink cannot acquire datasource in	JBoss 5.0
      (Michael O'Brien)


----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Feb 2009 10:56:00 -0500
From: "Yang, Daoqi (D.)" <dyang11@xxxxxxxx>
Subject: [eclipselink-users] RE: eclipselink-users Digest, Vol 18,
	Issue 43
To: <eclipselink-users@xxxxxxxxxxx>
Message-ID:
	<C3ED54EC58DC564EB58A827F46B80D6105940BD8@xxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain;	charset="UTF-8"

I have tried  in persistence.xml several other ways:
<jta-data-source>java:/jpaTestJtaDS</jta-data-source>

And 
 <jta-data-source>jpaTestJtaDS</jta-data-source> 

I still got the same errors. But I will do more testing tonight.
Notice that I have tried straightforward JNDI look up, which works fine.

InitialContext ctx = New InitialContect();
DataSource ds = (DataSource) ctx.lookup(“java:jpaTestJtaDS”);

Hibernate JPA works also.

Any other suggestions? Thanks a lot.



Regards,
Daoqi  Yang
Application Technology Architect
Ford Java Center of Excellence, E1F001 iTek
dyang11@xxxxxxxx, 313-206-3960

-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx [mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of eclipselink-users-request@xxxxxxxxxxx
Sent: Monday, February 23, 2009 10:40 AM
To: eclipselink-users@xxxxxxxxxxx
Subject: eclipselink-users Digest, Vol 18, Issue 43

Send eclipselink-users mailing list submissions to
	eclipselink-users@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	https://dev.eclipse.org/mailman/listinfo/eclipselink-users
or, via email, send a message with subject or body 'help' to
	eclipselink-users-request@xxxxxxxxxxx

You can reach the person managing the list at
	eclipselink-users-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of eclipselink-users digest..."


Today's Topics:

   1. Re: EclipseLink cannot acquire datasource in	JBoss 5.0
      (krisusa123)
   2. Re: EclipseLink cannot acquire datasource in	JBoss 5.0
      (Kevin Yuan)


----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Feb 2009 07:27:47 -0800 (PST)
From: krisusa123 <krisusa123@xxxxxxxxx>
Subject: Re: [eclipselink-users] EclipseLink cannot acquire datasource
	in	JBoss 5.0
To: EclipseLink User Discussions <eclipselink-users@xxxxxxxxxxx>
Message-ID: <775314.16723.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi 
Did you try just having just this
 
<jta-data-source>jpaTestJtaDS</jta-data-source> in persistence.xml file?
 
Thanks
Kris


f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng

--- On Mon, 2/23/09, Yang, Daoqi (D.) <dyang11@xxxxxxxx> wrote:

From: Yang, Daoqi (D.) <dyang11@xxxxxxxx>
Subject: [eclipselink-users] EclipseLink cannot acquire datasource in JBoss 5.0
To: eclipselink-users@xxxxxxxxxxx
Date: Monday, February 23, 2009, 9:14 AM



Hi, 
I am using EclipseLink 1.0.2 inside JBoss 5.0. The datasource is configured correctly as I am able to manually look up the datasource:
InitialContext ctx = New InitialContect(); 
DataSource ds = (DataSource) ctx.lookup(“java:jpaTestJtaDS”); 
However, when I put the datasource inside persistence.xml as in 
<persistence-unit name="jpaTestJtaPU" transaction-type="JTA"> 
  <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> 
  <jta-data-source>java:jpaTestJtaDS</jta-data-source> 
  <properties> 
     <property name="eclipselink.target-server" value="JBoss" /> 
    <property name="eclipselink.target-database" value="Derby" /> 
  </properties> 
I run into the following exception. Any suggestion is greatly appreciated. 
Exception Description: Cannot acquire data source [java:jpaTestJtaDS]. 
Internal Exception: 
javax.naming.InvalidNameException: Not a compound name: jpaTestJtaDS 
at javax.naming.CompoundName.addAll(Unknown Source) 
at org.jnp.interfaces.NamingContext.composeName(NamingContext.java:1064) 
at org.jnp.interfaces.NamingContext.getAbsoluteName(NamingContext.java:1777) 
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:704) 
at javax.naming.InitialContext.lookup(Unknown Source) 
at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:117) 
at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94) 
at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource 
   (DatasourceLogin.java:164) 
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal 
   (DatasourceAccessor.java:324) 
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal 
   (DatabaseAccessor.java:264) 
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect 
   (DatasourceAccessor.java:407) 
at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection 
   (ConnectionPool.java:130) 
at org.eclipse.persistence.sessions.server.ExternalConnectionPool.startUp 
   (ExternalConnectionPool.java:110) 
at org.eclipse.persistence.sessions.server.ServerSession.connect 
   (ServerSession.java:500) 
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login 
   (DatabaseSessionImpl.java:606) 
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login 
   (EntityManagerFactoryProvider.java:211) 
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy 
   (EntityManagerSetupImpl.java:246) 
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession 
   (EntityManagerFactoryImpl.java:69) 
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl 
   (EntityManagerFactoryImpl.java:118) 
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl 
   (EntityManagerFactoryImpl.java:112) 
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager 
   (EntityManagerFactoryImpl.java:100) 
The datasource is set in a file called “derbydb-ds.xml” as 
  <xa-datasource> 
       <jndi-name>jpaTestJtaDS</jndi-name> 
       <use-java-context>true</use-java-context> 
When I swithc to use Hibernate JPA, the same configuration works. 
Regards, 
Daoqi  Yang 
Application Technology Architect 
Ford Java Center of Excellence, E1F001 iTek 
dyang11@xxxxxxxx, 313-206-3960 _______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/eclipselink-users/attachments/20090223/f27fa067/attachment.html

------------------------------

Message: 2
Date: Mon, 23 Feb 2009 10:40:06 -0500
From: Kevin Yuan <kevin.yuan@xxxxxxxxxx>
Subject: Re: [eclipselink-users] EclipseLink cannot acquire datasource
	in	JBoss 5.0
To: krisusa123@xxxxxxxxx,	EclipseLink User Discussions
	<eclipselink-users@xxxxxxxxxxx>
Message-ID: <49A2C356.4080608@xxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi Daoqi,
It should be <jta-data-source>java:/jpaTestJtaDS</jta-data-source>, I 
have run our JPA testing on JBoss-5.0.0.GA, everything is fine.

Regards,
Kevin


krisusa123 wrote:
> Hi
> Did you try just having just this
>  
> <jta-data-source>jpaTestJtaDS</jta-data-source> in persistence.xml file?
>  
> Thanks
> Kris
>
>
> f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng
>
> --- On *Mon, 2/23/09, Yang, Daoqi (D.) /<dyang11@xxxxxxxx>/* wrote:
>
>     From: Yang, Daoqi (D.) <dyang11@xxxxxxxx>
>     Subject: [eclipselink-users] EclipseLink cannot acquire datasource
>     in JBoss 5.0
>     To: eclipselink-users@xxxxxxxxxxx
>     Date: Monday, February 23, 2009, 9:14 AM
>
>     Hi,
>     I am using EclipseLink 1.0.2 inside JBoss 5.0. The datasource is
>     configured correctly as I am able to manually look up the datasource:
>     InitialContext ctx = New InitialContect();
>     DataSource ds = (DataSource) ctx.lookup(“java:jpaTestJtaDS”);
>     However, when I put the datasource inside persistence.xml as in
>     <persistence-unit name=/"jpaTestJtaPU"/ transaction-type=/"JTA"/>
>      
>     <provider>_org_.eclipse.persistence._jpa_.PersistenceProvider</provider>
>
>       <jta-data-source>java:jpaTestJtaDS</jta-data-source>
>       <properties>
>          <property name=/"eclipselink.target-server"/ value=/"JBoss"/ />
>         <property name=/"eclipselink.target-database"/ value=/"Derby"/ />
>       </properties>
>     I run into the following exception. Any suggestion is greatly
>     appreciated.
>     Exception Description: Cannot acquire data source
>     [java:jpaTestJtaDS].
>     Internal Exception:
>     _javax.naming.InvalidNameException_: Not a compound name:
>     jpaTestJtaDS
>     at javax.naming.CompoundName.addAll(Unknown Source)
>     at
>     org.jnp.interfaces.NamingContext.composeName(_NamingContext.java:1064_)
>
>     at
>     org.jnp.interfaces.NamingContext.getAbsoluteName(_NamingContext.java:1777_)
>
>     at org.jnp.interfaces.NamingContext.lookup(_NamingContext.java:704_)
>     at javax.naming.InitialContext.lookup(Unknown Source)
>     at
>     org.eclipse.persistence.sessions.JNDIConnector.connect(_JNDIConnector.java:117_)
>
>     at
>     org.eclipse.persistence.sessions.JNDIConnector.connect(_JNDIConnector.java:94_)
>
>     at
>     org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource
>        (_DatasourceLogin.java:164_)
>     at
>     org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal
>
>        (_DatasourceAccessor.java:324_)
>     at
>     org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal
>
>        (_DatabaseAccessor.java:264_)
>     at
>     org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect
>
>        (_DatasourceAccessor.java:407_)
>     at
>     org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection
>
>        (_ConnectionPool.java:130_)
>     at
>     org.eclipse.persistence.sessions.server.ExternalConnectionPool.startUp
>
>        (_ExternalConnectionPool.java:110_)
>     at org.eclipse.persistence.sessions.server.ServerSession.connect
>        (_ServerSession.java:500_)
>     at
>     org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login
>        (_DatabaseSessionImpl.java:606_)
>     at
>     org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login
>
>        (_EntityManagerFactoryProvider.java:211_)
>     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy
>        (_EntityManagerSetupImpl.java:246_)
>     at
>     org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession
>
>        (_EntityManagerFactoryImpl.java:69_)
>     at
>     org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl
>
>        (_EntityManagerFactoryImpl.java:118_)
>     at
>     org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl
>
>        (_EntityManagerFactoryImpl.java:112_)
>     at
>     org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager
>
>        (_EntityManagerFactoryImpl.java:100_)
>     The datasource is set in a file called “derbydb-ds.xml” as
>       <xa-datasource>
>            <jndi-name>jpaTestJtaDS</jndi-name>
>            <use-java-context>true</use-java-context>
>     When I swithc to use Hibernate JPA, the same configuration works.
>     Regards,
>     Daoqi  Yang
>     Application Technology Architect
>     Ford Java Center of Excellence, E1F001 iTek
>     dyang11@xxxxxxxx, 313-206-3960
>
>     _______________________________________________
>     eclipselink-users mailing list
>     eclipselink-users@xxxxxxxxxxx
>     https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>               
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/eclipselink-users/attachments/20090223/57990e1e/attachment.html

------------------------------

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users


End of eclipselink-users Digest, Vol 18, Issue 43
*************************************************

------------------------------

Message: 2
Date: Mon, 23 Feb 2009 11:47:22 -0500
From: "Michael O'Brien" <michael.obrien@xxxxxxxxxx>
Subject: Re: [eclipselink-users] EclipseLink cannot acquire datasource
	in	JBoss 5.0
To: EclipseLink User Discussions <eclipselink-users@xxxxxxxxxxx>
Message-ID: <49A2D31A.2060909@xxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Yang,
    Hi, you may be experiencing a common configuration issue with 
application servers that are based on the Catalina (Tomcat) servlet 
container where the lookupType must be STRING_LOOKUP.
    However that usually emits the exception (sic "throught") 
*javax.naming.NamingException: This context must be accessed throught a 
java: URL"*
    I see you are correctly setting the target-server property so you 
are getting the costomized JBossPlatform that uses the jndi lookup 
"java:/TransactionManager" for the JTATransactionManager.
    Hibernate may default to STRING_LOOKUP as the lookupType because it 
normally runs in JBoss which is Catalina based.

    See the following EclipseLink on JBoss tutorial where we describe 
configuring the eclipselink.session.customizer so that the lookupType on 
ideally both JTA and non-JTA datasource connectors are changed from " 
COMPOSITE_NAME_LOOKUP" to "STRING_LOOKUP".

http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial#Session_Customizer

The following page describes the use of JNDIConnector.STRING_LOOKUP in 
general for all Catalina based servers.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial#Session_Customizer

    Also verify that the *-ds.xml config files are setup using the 
following section as a guide.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial#JNDI_JTA.2Fnon-JTA_Server_DataSource_Setup

    thank you
    /michael



Yang, Daoqi (D.) wrote:
>
> Hi,
> I am using EclipseLink 1.0.2 inside JBoss 5.0. The datasource is 
> configured correctly as I am able to manually look up the datasource:
>
> InitialContext ctx = New InitialContect();
> DataSource ds = (DataSource) ctx.lookup("java:jpaTestJtaDS");
>
> However, when I put the datasource inside persistence.xml as in
>
> <persistence-unit name=/"jpaTestJtaPU"/ transaction-type=/"JTA"/>
>   
> <provider>_org_.eclipse.persistence._jpa_.PersistenceProvider</provider>
>   <jta-data-source>java:jpaTestJtaDS</jta-data-source>
>   <properties>
>      <property name=/"eclipselink.target-server"/ value=/"JBoss"/ />
>     <property name=/"eclipselink.target-database"/ value=/"Derby"/ />
>   </properties>
>
> I run into the following exception. Any suggestion is greatly 
> appreciated.
>
> Exception Description: Cannot acquire data source [java:jpaTestJtaDS].
> Internal Exception:
> _javax.naming.InvalidNameException_: Not a compound name: jpaTestJtaDS
> at javax.naming.CompoundName.addAll(Unknown Source)
> at 
> org.jnp.interfaces.NamingContext.composeName(_NamingContext.java:1064_)
> at 
> org.jnp.interfaces.NamingContext.getAbsoluteName(_NamingContext.java:1777_) 
>
> at org.jnp.interfaces.NamingContext.lookup(_NamingContext.java:704_)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at 
> org.eclipse.persistence.sessions.JNDIConnector.connect(_JNDIConnector.java:117_) 
>
> at 
> org.eclipse.persistence.sessions.JNDIConnector.connect(_JNDIConnector.java:94_) 
>
> at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource
>    (_DatasourceLogin.java:164_)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal 
>
>    (_DatasourceAccessor.java:324_)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal 
>
>    (_DatabaseAccessor.java:264_)
> at 
> org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect 
>
>    (_DatasourceAccessor.java:407_)
> at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection
>    (_ConnectionPool.java:130_)
> at org.eclipse.persistence.sessions.server.ExternalConnectionPool.startUp
>    (_ExternalConnectionPool.java:110_)
> at org.eclipse.persistence.sessions.server.ServerSession.connect
>    (_ServerSession.java:500_)
> at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login
>    (_DatabaseSessionImpl.java:606_)
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login
>    (_EntityManagerFactoryProvider.java:211_)
> at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy
>    (_EntityManagerSetupImpl.java:246_)
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession 
>
>    (_EntityManagerFactoryImpl.java:69_)
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl 
>
>    (_EntityManagerFactoryImpl.java:118_)
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl 
>
>    (_EntityManagerFactoryImpl.java:112_)
> at 
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager 
>
>    (_EntityManagerFactoryImpl.java:100_)
>
> The datasource is set in a file called "derbydb-ds.xml" as
>   <xa-datasource>
>        <jndi-name>jpaTestJtaDS</jndi-name>
>        <use-java-context>true</use-java-context>
>
> When I swithc to use Hibernate JPA, the same configuration works.
>
> Regards,
> Daoqi  Yang
> Application Technology Architect
> Ford Java Center of Excellence, E1F001 iTek
> dyang11@xxxxxxxx, 313-206-3960
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/eclipselink-users/attachments/20090223/56bff845/attachment.html

------------------------------

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users


End of eclipselink-users Digest, Vol 18, Issue 44
*************************************************

Back to the top