And why do you think that the lookup failure is because of the command
replication framework ? You mention that the resource was created
successfully which means the replication framework did not cause a
resource creation failure.
Please look into the real cause of lookup failure and let me know if it
is really because of the framework.
On 7/13/10 2:16 PM, Cheng Fang wrote:
> devtests/ejb/ejb31/embedded/** tests failed when settting
> ENABLE_REPLICATION true. They all passed when this flag is NOT set.
>
> To reproduce, go to appserv-tests/devtests/ejb/ejb31/embedded/basic;
> ant all.
>
> In embedded mode JPA provider failed to look up the default jdbc
> resource "jdbc/__embedded_default", which is dynamically created. I
> can see they are created successfully with CommandRunner, but
> subsequently look up failed.
>
> [java] java.lang.RuntimeException: javax.naming.NamingException:
> Lookup failed for 'jdbc/__embedded_default' in SerialContext [Root
> exception is javax.naming.NameNotFoundException: __embedded_default
> not found]
> [java] at
> org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:107)
>
> [java] at
> org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:151)
>
> [java] at
> org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:116)
>
> [java] at
> org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:136)
> [java] at
> com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:665)
>
> [java] at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:316)
>
> [java] at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:203)
>
> [java] at
> org.glassfish.kernel.embedded.EmbeddedDeployerImpl.deploy(EmbeddedDeployerImpl.java:196)
>
> [java] at
> org.glassfish.ejb.embedded.EJBContainerImpl.deploy(EJBContainerImpl.java:135)
>
> [java] at
> org.glassfish.ejb.embedded.EJBContainerProviderImpl.createEJBContainer(EJBContainerProviderImpl.java:124)
>
> [java] at
> javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:116)
>
> [java] at com.acme.Client.test(Client.java:71)
> [java] at com.acme.Client.main(Client.java:61)
> [java] Caused by: javax.naming.NamingException: Lookup failed for
> 'jdbc/__embedded_default' in SerialContext [Root exception is
> javax.naming.NameNotFoundException: __embedded_default not found]
> [java] at
> com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:456)
>
> [java] at
> javax.naming.InitialContext.lookup(InitialContext.java:392)
> [java] at
> javax.naming.InitialContext.lookup(InitialContext.java:392)
> [java] at
> com.sun.enterprise.connectors.service.ConnectorResourceAdminServiceImpl.lookup(ConnectorResourceAdminServiceImpl.java:203)
>
> [java] at
> com.sun.enterprise.connectors.ConnectorRuntime.lookupPMResource(ConnectorRuntime.java:430)
>
> [java] at
> org.glassfish.persistence.jpa.ProviderContainerContractInfoBase.lookupDataSource(ProviderContainerContractInfoBase.java:59)
>
> [java] at
> org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:104)
>
> [java] ... 12 more
> [java] Caused by: javax.naming.NameNotFoundException:
> __embedded_default not found
>
> -cheng
>
> On 7/11/10 6:15 PM, Vijay Ramachandran wrote:
>> Glassfish 3.1 module owners,
>>
>> As you may know, the command replication framework (which was
>> demonstrated @ MS1 and has been available for use by CLIs since MS2)
>> is NOT enabled by default in 3.1 builds. This was done to give time
>> for various CLIs to make changes and adapt to the cluster environment
>> using this framework.
>>
>> As of today, we have reached point where the build, unit tests that
>> are executed during build, QL and admin CLI dev tests pass with
>> command replication enabled by default.
>>
>> When you get a chance, can you please run your module's dev tests
>> (with the ENABLE_REPLICATION env variable set to true before starting
>> the domain/instances) and let me know if you are OK with me turning
>> on command replication by default ? Also, if your dev test fail
>> because of a command replication bug, let me know ?
>>
>> We would like to see if the framework can be switched on by default
>> by MS3 which is on 7/19. Your response by COB on Friday, 7/16, will
>> be deeply appreciated.
>>
>> Thanks
>>
>> Vijay
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>