You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Hilco Wijbenga <hi...@gmail.com> on 2006/12/15 20:38:15 UTC
Running Continuum WAR on JBoss 4.0.5
Hi all,
I checked out Continuum from Subversion and ran 'mvn clean install'.
This yielded a WAR in continuum-webapp/target. I copied this WAR into
the JBoss deploy directory and requested http://localhost/continuum.
The WAR fails to deploy, I get several very long stacktraces in the
JBoss' default/server.log file.
I can deploy proximity's WAR so I think my JBoss install is ok.
Should I be able to deploy the Continuum WAR like this? Do I need to
do something in the WAR before I deploy it? Set some property during
the build?
The problem appears to be related to the database (i.e. I think it's a
JDBC connection problem).
Cheers,
Hilco
P.S. I tried 'mvn jetty:run' but I got "The plugin
'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid
version could be found" so no love there.
P.P.S. Part of the stacktraces I get:
2006-12-15 19:28:59,473 INFO [STDOUT] 2006-12-15 19:28:59,472 [main]
INFO PlexusContainer - Loading on start [role]:
[org.apache.maven.continuum.Continuum]
2006-12-15 19:29:00,879 INFO [STDOUT] 2006-12-15 19:29:00,872 [main]
ERROR [/continuum] - Exception sending context
initialized event to listener instance of class
org.codehaus.plexus.xwork.PlexusLifecycleListener
org.jpox.exceptions.ConnectionFactoryNotFoundException: Connection
Factory "java:comp/env/jdbc/continuum" not found
at org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:175)
at org.jpox.AbstractPersistenceManagerFactory.freezeConfiguration(AbstractPersistenceManagerFactory.java:212)
at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:534)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478)
at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.doConfigure(AbstractConfigurableJdoFactory.java:134)
at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.configure(AbstractConfigurableJdoFactory.java:101)
at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.getPersistenceManagerFactory(AbstractConfigurableJdoFactory.java:64)
at org.apache.maven.continuum.store.JdoContinuumStore.initialize(JdoContinuumStore.java:106)
<snip/>
and
NestedThrowablesStackTrace:
javax.naming.NameNotFoundException: jdbc not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:171)
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 12/18/06, Emmanuel Venisse <em...@venisse.net> wrote:
> This pb is a conflict between the wagon version we use in continuum and the wagon version used by maven because the jetty plugin doens't fork the process
Thanks. I didn't see anything already in JIRA, and I still can't run
it from trunk, so I opened
http://jira.codehaus.org/browse/CONTINUUM-1073 .
--
Wendy
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Emmanuel Venisse <em...@venisse.net>.
This pb is a conflict between the wagon version we use in continuum and the wagon version used by maven because the jetty plugin doens't fork the process
Emmanuel
Wendy Smoak a écrit :
> On 12/17/06, Hilco Wijbenga <hi...@gmail.com> wrote:
>
> org.codehaus.plexus.component.repository.exception.ComponentRepositoryException:
>
>> Component descriptor role:
>> 'org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider',
>> implementation:
>> 'org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider',
>> role hint: 'file' has a hint, but there are other implementations that
>> don't
> ...
>> Any idea what's causing this?
>
> No, but two of us on IRC saw the same problem last night.
>
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 12/17/06, Hilco Wijbenga <hi...@gmail.com> wrote:
org.codehaus.plexus.component.repository.exception.ComponentRepositoryException:
> Component descriptor role:
> 'org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider',
> implementation:
> 'org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider',
> role hint: 'file' has a hint, but there are other implementations that
> don't
...
> Any idea what's causing this?
No, but two of us on IRC saw the same problem last night.
--
Wendy
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Hilco Wijbenga <hi...@gmail.com>.
On 12/15/06, Wendy Smoak <ws...@gmail.com> wrote:
> On 12/15/06, Hilco Wijbenga <hi...@gmail.com> wrote:
>
> > P.S. I tried 'mvn jetty:run' but I got "The plugin
> > 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid
> > version could be found" so no love there.
>
> I'm usually able to get past this error by deleting the plugin from my
> local repository. In this case,
> rm -rf $M2_REPO/org/codehaus/mojo/jetty-maven-plugin
I'm afraid that doesn't help. The only way I can get Jetty to run is
to type the rather verbose
mvn org.mortbay.jetty:maven-jetty-plugin:run
That at least starts Jetty but I don't get much further because after
a long stacktrace it complains about
Caused by: org.codehaus.plexus.component.repository.exception.ComponentRepositoryException:
Component descriptor role:
'org.apache.maven.wagon.providers.ssh.knownhost.KnownHostsProvider',
implementation:
'org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider',
role hint: 'file' has a hint, but there are other implementations that
don't
at org.codehaus.plexus.component.repository.DefaultComponentRepository.addComponentDescriptor(DefaultComponentRepository.java:181)
at org.codehaus.plexus.DefaultPlexusContainer.addComponentDescriptor(DefaultPlexusContainer.java:450)
at org.codehaus.plexus.container.initialization.ComponentDiscoveryPhase.discoverComponents(ComponentDiscoveryPhase.java:71)
at org.codehaus.plexus.container.initialization.ComponentDiscoveryPhase.execute(ComponentDiscoveryPhase.java:25)
... 42 more
3963 [main] INFO org.mortbay.log - Started SelectChannelConnector @ 0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 10 seconds.
So Jetty starts but Continuum doesn't. Any idea what's causing this?
Cheers,
Hilco
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 12/15/06, Hilco Wijbenga <hi...@gmail.com> wrote:
> P.S. I tried 'mvn jetty:run' but I got "The plugin
> 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid
> version could be found" so no love there.
I'm usually able to get past this error by deleting the plugin from my
local repository. In this case,
rm -rf $M2_REPO/org/codehaus/mojo/jetty-maven-plugin
I don't know what causes it, (bad metadata?) but it seems to be
happening more often lately.
--
Wendy
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Jesse McConnell <je...@gmail.com>.
On 12/15/06, Hilco Wijbenga <hi...@gmail.com> wrote:
> Ok, I got it working. :-)
>
> I should note that I have an extra requirement: I want to run Archiva
> in the same JBoss instance. Both Continuum and Archiva use jdbc/users
> so that clashes. I will change this to jdbc/continuum_users and
> jdbc/archiva_users for Continuum and Archiva, respectively.
>
actually, they can use the same users database and just share them,
the relevent roles duplicate roles will mesh together for things like
System Admin, etc.
jesse
> I already got Archiva working (still with jdbc/users), see
>
> http://docs.codehaus.org/display/MAVENUSER/Archiva+on+JBoss
>
> (thanks Wendy!).
>
> On 12/15/06, Robert Dale <ro...@duke.edu> wrote:
> > Create a Derby datasource bound to java:comp/env/jdbc/continuum
> > or dig through the configuration to change the binding name.
>
> The instructions below also include the setup of Archiva. Of course,
> you can safely ignore those if you don't want to run Archiva.
>
> (Note that I'm running the 'default' JBoss configuration.)
>
> 1. copy derby-10.1.3.1.jar into $JBOSS_HOME/server/default/lib (it's
> available in both continuum-webapp/src/main/webapp/WEB-INF/lib and
> archiva-webapp/src/main/webapp/WEB-INF/lib);
>
> 2a. create $JBOSS_HOME/server/default/deploy/archiva-derby-ds.xml
> (make sure the file name ends in '-ds.xml', the prefix is irrelevant)
> <?xml version="1.0" encoding="UTF-8"?>
> <datasources>
> <local-tx-datasource>
> <jndi-name>archiva_users</jndi-name>
> <connection-url>jdbc:derby:database/archiva_users;create=true</connection-url>
> <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
> <user-name>sa</user-name>
> <password></password>
> <min-pool-size>5</min-pool-size>
> <max-pool-size>20</max-pool-size>
> <idle-timeout-minutes>5</idle-timeout-minutes>
> <track-statements/>
> </local-tx-datasource>
> </datasources>
>
> 2b. create $JBOSS_HOME/server/default/deploy/continuum-derby-ds.xml
> (again, make sure the file name ends in '-ds.xml', the prefix is
> irrelevant)
> <?xml version="1.0" encoding="UTF-8"?>
> <datasources>
> <local-tx-datasource>
> <jndi-name>continuum</jndi-name>
> <connection-url>jdbc:derby:database/continuum;create=true</connection-url>
> <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
> <user-name>sa</user-name>
> <password></password>
> <min-pool-size>5</min-pool-size>
> <max-pool-size>20</max-pool-size>
> <idle-timeout-minutes>5</idle-timeout-minutes>
> <track-statements/>
> </local-tx-datasource>
> <local-tx-datasource>
> <jndi-name>continuum_users</jndi-name>
> <connection-url>jdbc:derby:database/continuum_users;create=true</connection-url>
> <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
> <user-name>sa</user-name>
> <password></password>
> <min-pool-size>5</min-pool-size>
> <max-pool-size>20</max-pool-size>
> <idle-timeout-minutes>5</idle-timeout-minutes>
> <track-statements/>
> </local-tx-datasource>
> </datasources>
>
> 3a. cd into the main archiva directory and run from there
> mvn clean
> for FILE in $(find . -name '.svn' -prune -o -type f | xargs grep -l
> 'jdbc/users'); do \
> sed -e 's/jdbc\/users/jdbc\/archiva_users/' $FILE >$FILE.new; \
> mv $FILE.new $FILE; \
> done
>
> 3b. cd into the main continuum directory and run from there
> mvn clean
> for FILE in $(find . -name '.svn' -prune -o -type f | xargs grep -l
> 'jdbc/users'); do \
> sed -e 's/jdbc\/users/jdbc\/continuum_users/' $FILE >$FILE.new; \
> mv $FILE.new $FILE; \
> done
>
> 4a. edit archiva-webapp/src/main/webapp/WEB-INF/web.xml and add
> <resource-ref>
> <res-ref-name>jdbc/archiva_users</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> 4b. edit continuum-webapp/src/main/webapp/WEB-INF/web.xml and add
> <resource-ref>
> <res-ref-name>jdbc/continuum</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
> <resource-ref>
> <res-ref-name>jdbc/continuum_users</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> 5a. create archiva-webapp/src/main/webapp/WEB-INF/jboss-web.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <resource-ref>
> <res-ref-name>jdbc/archiva_users</res-ref-name>
> <jndi-name>java:/archiva_users</jndi-name>
> </resource-ref>
> </jboss-web>
>
> 5b. create continuum-webapp/src/main/webapp/WEB-INF/jboss-web.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <resource-ref>
> <res-ref-name>jdbc/continuum</res-ref-name>
> <jndi-name>java:/continuum</jndi-name>
> </resource-ref>
> <resource-ref>
> <res-ref-name>jdbc/continuum_users</res-ref-name>
> <jndi-name>java:/continuum_users</jndi-name>
> </resource-ref>
> </jboss-web>
>
> 6a. in archiva run 'mvn install' (to update the WAR with all our changes);
>
> 6b. in continuum run 'mvn install' (to update the WAR with all our changes);
>
> 7a. deploy the Archiva WAR (archiva-webapp/target);
>
> 7b. deploy the Continuum WAR (continuum-webapp/target);
>
> That's it, both Archiva and Continuum should work now.
>
> DISCLAIMER: I'm not, by any stretch of the word, an expert on JBoss so
> this is probably not the *best* way to do it ... but it works. :-)
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Hilco Wijbenga <hi...@gmail.com>.
Ok, I got it working. :-)
I should note that I have an extra requirement: I want to run Archiva
in the same JBoss instance. Both Continuum and Archiva use jdbc/users
so that clashes. I will change this to jdbc/continuum_users and
jdbc/archiva_users for Continuum and Archiva, respectively.
I already got Archiva working (still with jdbc/users), see
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+JBoss
(thanks Wendy!).
On 12/15/06, Robert Dale <ro...@duke.edu> wrote:
> Create a Derby datasource bound to java:comp/env/jdbc/continuum
> or dig through the configuration to change the binding name.
The instructions below also include the setup of Archiva. Of course,
you can safely ignore those if you don't want to run Archiva.
(Note that I'm running the 'default' JBoss configuration.)
1. copy derby-10.1.3.1.jar into $JBOSS_HOME/server/default/lib (it's
available in both continuum-webapp/src/main/webapp/WEB-INF/lib and
archiva-webapp/src/main/webapp/WEB-INF/lib);
2a. create $JBOSS_HOME/server/default/deploy/archiva-derby-ds.xml
(make sure the file name ends in '-ds.xml', the prefix is irrelevant)
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>archiva_users</jndi-name>
<connection-url>jdbc:derby:database/archiva_users;create=true</connection-url>
<driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
<user-name>sa</user-name>
<password></password>
<min-pool-size>5</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<track-statements/>
</local-tx-datasource>
</datasources>
2b. create $JBOSS_HOME/server/default/deploy/continuum-derby-ds.xml
(again, make sure the file name ends in '-ds.xml', the prefix is
irrelevant)
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>continuum</jndi-name>
<connection-url>jdbc:derby:database/continuum;create=true</connection-url>
<driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
<user-name>sa</user-name>
<password></password>
<min-pool-size>5</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<track-statements/>
</local-tx-datasource>
<local-tx-datasource>
<jndi-name>continuum_users</jndi-name>
<connection-url>jdbc:derby:database/continuum_users;create=true</connection-url>
<driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
<user-name>sa</user-name>
<password></password>
<min-pool-size>5</min-pool-size>
<max-pool-size>20</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<track-statements/>
</local-tx-datasource>
</datasources>
3a. cd into the main archiva directory and run from there
mvn clean
for FILE in $(find . -name '.svn' -prune -o -type f | xargs grep -l
'jdbc/users'); do \
sed -e 's/jdbc\/users/jdbc\/archiva_users/' $FILE >$FILE.new; \
mv $FILE.new $FILE; \
done
3b. cd into the main continuum directory and run from there
mvn clean
for FILE in $(find . -name '.svn' -prune -o -type f | xargs grep -l
'jdbc/users'); do \
sed -e 's/jdbc\/users/jdbc\/continuum_users/' $FILE >$FILE.new; \
mv $FILE.new $FILE; \
done
4a. edit archiva-webapp/src/main/webapp/WEB-INF/web.xml and add
<resource-ref>
<res-ref-name>jdbc/archiva_users</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
4b. edit continuum-webapp/src/main/webapp/WEB-INF/web.xml and add
<resource-ref>
<res-ref-name>jdbc/continuum</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/continuum_users</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
5a. create archiva-webapp/src/main/webapp/WEB-INF/jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/archiva_users</res-ref-name>
<jndi-name>java:/archiva_users</jndi-name>
</resource-ref>
</jboss-web>
5b. create continuum-webapp/src/main/webapp/WEB-INF/jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/continuum</res-ref-name>
<jndi-name>java:/continuum</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jdbc/continuum_users</res-ref-name>
<jndi-name>java:/continuum_users</jndi-name>
</resource-ref>
</jboss-web>
6a. in archiva run 'mvn install' (to update the WAR with all our changes);
6b. in continuum run 'mvn install' (to update the WAR with all our changes);
7a. deploy the Archiva WAR (archiva-webapp/target);
7b. deploy the Continuum WAR (continuum-webapp/target);
That's it, both Archiva and Continuum should work now.
DISCLAIMER: I'm not, by any stretch of the word, an expert on JBoss so
this is probably not the *best* way to do it ... but it works. :-)
Re: Running Continuum WAR on JBoss 4.0.5
Posted by Robert Dale <ro...@duke.edu>.
Hilco,
Create a Derby datasource bound to java:comp/env/jdbc/continuum
or dig through the configuration to change the binding name.
If you don't want to use Derby, then you'll probably have to do some more
digging
to see what databases are supported by the underlying persistence layer
and how
to configure it.
--
Robert Dale
"Hilco Wijbenga" <hi...@gmail.com> wrote on 12/15/2006 02:38:15
PM:
> Hi all,
>
> I checked out Continuum from Subversion and ran 'mvn clean install'.
> This yielded a WAR in continuum-webapp/target. I copied this WAR into
> the JBoss deploy directory and requested http://localhost/continuum.
>
> The WAR fails to deploy, I get several very long stacktraces in the
> JBoss' default/server.log file.
>
> I can deploy proximity's WAR so I think my JBoss install is ok.
>
> Should I be able to deploy the Continuum WAR like this? Do I need to
> do something in the WAR before I deploy it? Set some property during
> the build?
>
> The problem appears to be related to the database (i.e. I think it's a
> JDBC connection problem).
>
> Cheers,
> Hilco
>
> P.S. I tried 'mvn jetty:run' but I got "The plugin
> 'org.codehaus.mojo:jetty-maven-plugin' does not exist or no valid
> version could be found" so no love there.
> P.P.S. Part of the stacktraces I get:
> 2006-12-15 19:28:59,473 INFO [STDOUT] 2006-12-15 19:28:59,472 [main]
> INFO PlexusContainer - Loading on start [role]:
> [org.apache.maven.continuum.Continuum]
> 2006-12-15 19:29:00,879 INFO [STDOUT] 2006-12-15 19:29:00,872 [main]
> ERROR [/continuum] - Exception sending context
> initialized event to listener instance of class
> org.codehaus.plexus.xwork.PlexusLifecycleListener
> org.jpox.exceptions.ConnectionFactoryNotFoundException: Connection
> Factory "java:comp/env/jdbc/continuum" not found
> at org.jpox.AbstractPersistenceManagerFactory.
> lookupDataSource(AbstractPersistenceManagerFactory.java:175)
> at org.jpox.AbstractPersistenceManagerFactory.
> freezeConfiguration(AbstractPersistenceManagerFactory.java:212)
> at org.jpox.PersistenceManagerFactoryImpl.
> getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at javax.jdo.JDOHelper.
> getPersistenceManagerFactory(JDOHelper.java:534)
> at javax.jdo.JDOHelper.
> getPersistenceManagerFactory(JDOHelper.java:478)
> at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.
> doConfigure(AbstractConfigurableJdoFactory.java:134)
> at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.
> configure(AbstractConfigurableJdoFactory.java:101)
> at org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.
> getPersistenceManagerFactory(AbstractConfigurableJdoFactory.java:64)
> at org.apache.maven.continuum.store.JdoContinuumStore.
> initialize(JdoContinuumStore.java:106)
> <snip/>
>
> and
>
> NestedThrowablesStackTrace:
> javax.naming.NameNotFoundException: jdbc not bound
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
> at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
> at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
> at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
> at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
> at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
> at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716)
> at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at org.jpox.AbstractPersistenceManagerFactory.
> lookupDataSource(AbstractPersistenceManagerFactory.java:171)