Weblogic 10.3 and eclipselink

[kusanagihk]

Hi

I'm a newbie on eclipselink; currently I am setting up a demo using eclipselink under weblogic 10.3
However I met an exception (and this exception is quite well known on the web as well)

<pre>
Error An error occurred during activation of changes, please see the log for details.
Error Exception preparing module: EJBModule(core-1.0.jar)
Error Substituted for missing class Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.0.2 (Build 20081024)) - org.eclipse.persistence.exceptions.EntityManagerSetupException Exception Description: PersistenceUnitInfo jtaDS has transactionType JTA, but doesnt have jtaDataSource.
</pre>

Ok, the answers I've got on several forums/websites states that I have not setup the DataSource well. However... this is not my case; the DataSource is working (I have written a jsp just to get access to the global DataSource through JNDI)

And 1 funny thing is that the "jtaDS" has been removed by me earlier! I mean the persistence.xml doesn't define this "jtaDS" entry anymore~ So I wonder is this some sort of bug or the Weblogic / EclipseLink has cached down the previous config....

Any ideas would be definitely appreciated

Thx and good day~

Stack Traces below:
<Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Exception preparing module: EJBModule(core-1.0.jar)

        at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
        at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.Throwable: Substituted for missing class Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.0.2 (Build 20081024)) - org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo jtaDS has transactionType JTA, but doesnt have jtaDataSource.
        at org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
        at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:790)
        at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:189)
        at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330)
        at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
        at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
        at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
        at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
        at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209)
        at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310)
        at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
        at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:376)>

[mobrien]

Kusanagihk,
    Hi, this is a common scenario.  Either your JTA datasource is not
setup correctly on your server - check your datasource on your WebLogic
server if you wish to use it.
    Checkout...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#Setting_up_a_Globally_Scoped_JNDI_Datasource_on_the_WebLogic_Server_Console

    Or, you have transaction-type="JTA" in your persistence unit or are
defaulting to JTA in the absence of specifying
transaction-type="RESOURCE_LOCAL" when deploying to the server (running
in standalone SE would default to RESOURCE_LOCAL)
    However, it looks like you would like to run in RESOURCE_LOCAL or a
non-JTA SE mode where you manage your own transactions.

See
   
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#Troubleshooting
And
   
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#JTA_Datasource
   
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#RESOURCE_LOCAL_Datasource


    As an example, If i publish an EAR that contains a persistence unit
without a transaction-type, and do not define the datasource on the
server, the server defaults to JTA and I get the following exception.

Exception [EclipseLink-28010] ***:
org.eclipse.persistence.exceptions.EntityManagerSetupException Exception
Description: PersistenceUnitInfo example has transactionType JTA, but
doesnt have jtaDataSource. at
org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)


    thank you
    /michael
   


kusanagihk wrote:

> Hi
>
> I'm a newbie on eclipselink; currently I am setting up a demo using
> eclipselink under weblogic 10.3
> However I met an exception (and this exception is quite well known on the
> web as well)
>
> <pre>
> Error An error occurred during activation of changes, please see the log for
> details.
> Error Exception preparing module: EJBModule(core-1.0.jar)
> Error Substituted for missing class Exception [EclipseLink-28010] (Eclipse
> Persistence Services - 1.0.2 (Build 20081024)) -
> org.eclipse.persistence.exceptions.EntityManagerSetupException Exception
> Description: PersistenceUnitInfo jtaDS has transactionType JTA, but doesnt
> have jtaDataSource.
> </pre>
>
> Ok, the answers I've got on several forums/websites states that I have not
> setup the DataSource well. However... this is not my case; the DataSource is
> working (I have written a jsp just to get access to the global DataSource
> through JNDI)
>
> And 1 funny thing is that the "jtaDS" has been removed by me earlier! I mean
> the persistence.xml doesn't define this "jtaDS" entry anymore~ So I wonder
> is this some sort of bug or the Weblogic / EclipseLink has cached down the
> previous config....
>
> Any ideas would be definitely appreciated
>
> Thx and good day~
>
> Stack Traces below:
> <Error> <Console> <BEA-240003> <Console encountered the following error
> weblogic.application.ModuleException: Exception preparing module:
> EJBModule(core-1.0.jar)
>
>         at
> weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
>         at
> weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
>         at
> weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
>         at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
>         at
> weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
>         at
> weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
>         at
> weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
>         at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
>         at
> weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
>         at
> weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
>         at
> weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
>         at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
>         at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
>         at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
>         at
> weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
>         at
> weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
>         at
> weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
>         at
> weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
>         at
> weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
>         at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
>         at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
>         at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
>         at
> weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
>         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
>         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
> Caused by: java.lang.Throwable: Substituted for missing class Exception
> [EclipseLink-28010] (Eclipse Persistence Services - 1.0.2 (Build 20081024))
> - org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: PersistenceUnitInfo jtaDS has transactionType JTA,
> but doesnt have jtaDataSource.
>         at
> org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
>         at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:790)
>         at
> org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:189)
>         at
> weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330)
>         at
> weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
>         at
> weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
>         at
> weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
>         at
> weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
>         at
> weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209)
>         at
> weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310)
>         at
> weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
>         at
> weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:376)>
>
>
>  

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

[Andrei Ilitchev]

The exception indicates that persistence unit has transaction type JTA:
in persistence.xml it either explicitly defined transaction type JTA or
skips
transaction type - in this case it's defaulted to JTA.
but does not specify jta data source:
    <jta-data-source>...jtaDS</jta-data-source>

Either add jta-data-source definition, or change persistence unit
transaction type to RESOURCE_LOCAL:
   <persistence-unit name="MyPU" transaction-type="RESOURCE_LOCAL">



----- Original Message -----
From: "kusanagihk" <kusanagihk@...>
To: <eclipselink-users@...>
Sent: Monday, August 10, 2009 10:10 AM
Subject: [eclipselink-users] Weblogic 10.3 and eclipselink

>
> Hi
>
> I'm a newbie on eclipselink; currently I am setting up a demo using
> eclipselink under weblogic 10.3
> However I met an exception (and this exception is quite well known on the
> web as well)
>
> <pre>
> Error An error occurred during activation of changes, please see the log
> for
> details.
> Error Exception preparing module: EJBModule(core-1.0.jar)
> Error Substituted for missing class Exception [EclipseLink-28010] (Eclipse
> Persistence Services - 1.0.2 (Build 20081024)) -
> org.eclipse.persistence.exceptions.EntityManagerSetupException Exception
> Description: PersistenceUnitInfo jtaDS has transactionType JTA, but doesnt
> have jtaDataSource.
> </pre>
>
> Ok, the answers I've got on several forums/websites states that I have not
> setup the DataSource well. However... this is not my case; the DataSource
> is
> working (I have written a jsp just to get access to the global DataSource
> through JNDI)
>
> And 1 funny thing is that the "jtaDS" has been removed by me earlier! I
> mean
> the persistence.xml doesn't define this "jtaDS" entry anymore~ So I wonder
> is this some sort of bug or the Weblogic / EclipseLink has cached down the
> previous config....
>
> Any ideas would be definitely appreciated
>
> Thx and good day~
>
> Stack Traces below:
> <Error> <Console> <BEA-240003> <Console encountered the following error
> weblogic.application.ModuleException: Exception preparing module:
> EJBModule(core-1.0.jar)
>
>        at
> weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
>        at
> weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
>        at
> weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
>        at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
>        at
> weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
>        at
> weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
>        at
> weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
>        at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
>        at
> weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
>        at
> weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
>        at
> weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
>        at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
>        at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
>        at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
>        at
> weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
>        at
> weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
>        at
> weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
>        at
> weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
>        at
> weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
>        at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
>        at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
>        at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
>        at
> weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
>        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
>        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
> Caused by: java.lang.Throwable: Substituted for missing class Exception
> [EclipseLink-28010] (Eclipse Persistence Services - 1.0.2 (Build
> 20081024))
> - org.eclipse.persistence.exceptions.EntityManagerSetupException
> Exception Description: PersistenceUnitInfo jtaDS has transactionType JTA,
> but doesnt have jtaDataSource.
>        at
> org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
>        at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:790)
>        at
> org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:189)
>        at
> weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330)
>        at
> weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
>        at
> weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
>        at
> weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
>        at
> weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
>        at
> weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209)
>        at
> weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310)
>        at
> weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
>        at
> weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:376)>
>
>
> --
> View this message in context:
> http://www.nabble.com/Weblogic-10.3-and-eclipselink-tp24895850p24895850.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@...
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>

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

[kusanagihk]

thx to your replies

yes, I am running in weblogic so the default transaction-type MUST be JTA and the datasource is setuped on weblogic admin console and it is globally defined (ie. can be accessed through jndi) <-- I proved it worked earlier using a jsp

so the problem lies somewhere in the configuration (I guess); and once again, I need to remind a funny point --> I already removed the persistence unit --> jtaDS (however the exception still tells me I have defined this jtaDS which is the funny thing)

also I tried to remove the persistence.xml file and deploy again --> same exception was caught (jtaDS not defined etc etc) this doesn't make sense... since there is no persistence.xml... already... how come eclipselink tries to setup the non-existing things????

So I wonder if this is a bug or something on either eclipselink or weblogic
But I hope it is config problems only

thx and nice day folks

[mobrien]

Hi,
    WebLogic may cache EJB session beans in certain situations, If you are using injection of the persistence unit the PU may be cached along with this bean, as issue with caching was fixed on the server in the 11gR1 release in July 2009 - if you are using the following PU injection on a session bean.

@PersistenceContext(unitName="example", type=PersistenceContextType.TRANSACTION)

    Try undeploying and redeploying and/or bouncing your server to clear the cache, the cache may behave differently depending on how you deploy..

See also...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#Troubleshooting_2
"3) If you have changed your entity schema between deployments and you find some weird behavior where you are seeing both your new entities and the old entities (without the schema changes) - this is most likely due to a cached entity on the server that has not been updated for some reason - usually when you combine both manual deployment to the autodeploy directory and "run-on-server" from the Eclipse IDE.

• The workaround is to clear non-session entities from the cache under
• user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache"

If you are using session bean PU deployment, you may see something similar to the following for  WebLogic 10.3.0 (However this was fixed in WebLogic in Dec 2008 - which would align with 10.3.1 released in July 2009 as part of 11gR1)
C:\opt\wls103far8a\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\bi5iz0rnwaep\org\eclipse\persistence\example\jpa\server\business>dir /B ApplicationService.class ApplicationService2_dt84dc_ApplicationServiceLocal2Impl.class
ApplicationService2_dt84dc_ApplicationServiceLocal2Impl.java
ApplicationService2_dt84dc_Impl.class
ApplicationService2_dt84dc_Impl.java
ApplicationService2_dt84dc_Intf.class
ApplicationService2_dt84dc_Intf.java
ApplicationServiceLocal.class
ApplicationService_5ptwty_ApplicationServiceLocalImpl.class
ApplicationService_5ptwty_ApplicationServiceLocalImpl.java
ApplicationService_5ptwty_Impl.class
ApplicationService_5ptwty_Impl.java
ApplicationService_5ptwty_Intf.class
ApplicationService_5ptwty_Intf.java
Cell.class

Can you also...
    - rename your jta datasource in you persistence.xml and verify that the change is picked up on the redeployment (ie you get a different name not found)
    - post your persistence.xml (version with original JTA setup)
    - post your persistence.xml (version with RESOURCE_LOCAL setup - that is not working)
    - state how you are using the PU (Servlet injection, EJB injection or static factory)
    - search your server's file system for cached versions of your persistence.xml
    - verify in your admin console that there is no persistence unit under the application entry in the deployment explorer on the domain

    thank you
    /michael

kusanagihk wrote:

thx to your replies

yes, I am running in weblogic so the default transaction-type MUST be JTA
and the datasource is setuped on weblogic admin console and it is globally
defined (ie. can be accessed through jndi) <-- I proved it worked earlier
using a jsp

so the problem lies somewhere in the configuration (I guess); and once
again, I need to remind a funny point --> I already removed the persistence
unit --> jtaDS (however the exception still tells me I have defined this
jtaDS which is the funny thing)

also I tried to remove the persistence.xml file and deploy again --> same
exception was caught (jtaDS not defined etc etc) this doesn't make sense...
since there is no persistence.xml... already... how come eclipselink tries
to setup the non-existing things????

So I wonder if this is a bug or something on either eclipselink or weblogic
But I hope it is config problems only

thx and nice day folks
  

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

[kusanagihk]

hi all,

problem seems to be solved, yes, weblogic has cached the EJB contents/classes etc

I managed to delete those cached contents manually and no more strange exception caught. (at least the ear is deployed successfully by the mean time)

thanks for all your advises

[mobrien]

Kusanagihk,
    Good to hear.  Thank you for the update.
    Could I ask what version of WebLogic you are running 10.3.1.0 or
10.3.1 (11gR1) in order to determine if this caching issue is still present?

    See:
       
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html?rssid=rss_otn_soft

    thank you
    /michael

kusanagihk wrote:

> hi all,
>
> problem seems to be solved, yes, weblogic has cached the EJB
> contents/classes etc
>
> I managed to delete those cached contents manually and no more strange
> exception caught. (at least the ear is deployed successfully by the mean
> time)
>
> thanks for all your advises
>  

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

[kusanagihk]

Hi michael,

my weblogic server is a bundled version (ie. bundled with Jdeveloper)
I forgot the exact url for downloading the bundle but the versions are as below:
JDeveloper : 11g 11.1.1.0.2
Weblogic : 10.3.0.0

So since it is not weblogic 10.3.1.0 (as you expected) are there any patches available for my current version ??? or actually I just clean up the cache manually like what I just did???

thx and hope it helped
:)

[mobrien]

Hi,
    Thank you for verifying that this WebLogic issue does not occur for
10.3.1.0 (for yourself)
    You will want to upgrade to JDeveloper 11g (11.1.1.1.0) which
matches WebLogic Server 10.1.3.1.0 - that contains the container fix for
this EJB caching issue.
    I reviewed the available patches via Smart Update 3.2.0.0 for both
products - I would like to assist with patching but I am currently
unfamiliar with the matching algorithm between the corporate CR #s (in
Smart Update) and WebLogic Bug #s (for Development) - however you will
want the patch that contains the following WebLogic bug# 7638986  - I
recommend contacting your support representative if you would like to go
this route.

(You may not have access to this link - here are some details)
BUG 7638986 - WLS: EJBCOMPILERCACHE NOT UPDATING ENTITY CLASS FILES
AFTER REDEPLOY IN ECLIPSE
Status: 90 - Closed, Verified by Filer
Fix By: 10.3.1.0 Fixed Ver: 10.3.1.0
https://bug.oraclecorp.com/pls/bug/webbug_print.show?c_rptno=7638986

    thank you
    /michael

kusanagihk wrote:

> Hi michael,
>
> my weblogic server is a bundled version (ie. bundled with Jdeveloper)
> I forgot the exact url for downloading the bundle but the versions are as
> below:
> JDeveloper : 11g 11.1.1.0.2
> Weblogic : 10.3.0.0
>
> So since it is not weblogic 10.3.1.0 (as you expected) are there any patches
> available for my current version ??? or actually I just clean up the cache
> manually like what I just did???
>
> thx and hope it helped
> :)
>  

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