Nabble - Apache Geronimo - Users

Re: Remote Deployment: Connection Refused

2009-11-24T17:51:37Z

If you want to deploy applications to B, then edit the value of RemoteDeployHostname in config-subsitutions.properties file on B.

Then on A, use the deploy command like

./deploy.sh -host <ip of B> -u system -p manager deploy <application on A>

BTW, Kevan opened a JIRA(GERONIMO-4959) for 2.1.4 Geronimo-Jetty assembly. You may want to try remote deploy on Geronimo-Tomcat one.

Any questions, please let us know.

Jeff

On Wed, Nov 25, 2009 at 12:27 AM, MDiamond <Michael.Diamond@...> wrote:

On which machine should I change that information? A or B?

I tried it on both in various combinations and still get the same error. As
I understand it, I'm supposed to change it on B only, but, again, this
results in the same error. Thoughts?

P.S. If it matters, the relevant portion of my config.xml is (which I
believe is the default):
<module
name="org.apache.geronimo.framework/geronimo-gbean-deployer/2.1.4/car">
<gbean name="Deployer">
<attribute
name="remoteDeployAddress">http://${RemoteDeployHostname}:${HTTPPort
+PortOffset}</attribute>
</gbean>
</module>

--
View this message in context: http://old.nabble.com/Remote-Deployment%3A-Connection-Refused-tp26421415s134p26498548.html

Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Remote Deployment: Connection Refused

2009-11-24T08:27:34Z

On which machine should I change that information? A or B?

I tried it on both in various combinations and still get the same error. As I understand it, I'm supposed to change it on B only, but, again, this results in the same error. Thoughts?

P.S. If it matters, the relevant portion of my config.xml is (which I believe is the default):
<module name="org.apache.geronimo.framework/geronimo-gbean-deployer/2.1.4/car">
<gbean name="Deployer">
<attribute name="remoteDeployAddress">http://${RemoteDeployHostname}:${HTTPPort +PortOffset}</attribute>
</gbean>
</module>

Re: ActiveMQ questions

2009-11-24T07:09:25Z

I use geronimo 2.1.2.
It seems that the only way to configurate embedded AMQ is through "ServerUrl".

For example:
<config-property-setting name="ServerUrl">tcp://localhost:61616?jms.copyMessageOnSend=false&jms.watchTopicAdvisories=false&socket.tcpNoDelay=true&wireFormat.tcpNoDelayEnabled=true</config-property-setting>

Now I want to completely disable advisory message.
See: http://activemq.apache.org/advisory-message.html
The configuration is through XML config data.
<broker advisorySupport="false">...

How can I do that in geronimo?
I try to follow the instructions from http://activemq.apache.org/resource-adapter-properties.html

To add this in deploy plan...
<config-property-setting name="BrokerXmlConfig">xbean:config.xml</config-property-setting>

But geronimo can not handle xbean schema.
...did not start because Failed to startup an embedded broker: xbean:config.xml, due to: java.io.IOException: Could load xbean factory:java.lang.NoClassDefFoundError: org/springframework/beans/BeansException

Re: JDBC4 Postgresql Driver fails to install

2009-11-24T01:38:54Z

About the exception shows while leaving it blank, the fix is also made with the help messages changes together.

2009/11/24 Quintin Beukes <quintin@...>

I might be missing something, but if you require it like this:

<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>8.4.701.jdbc4</version>
<type>jar</type>

And have this:

> Group: org.postgresql
> Artifact: postgresql
> Version: 8.4-701
> Type: jar

It's not the same thing. The version's don't match (the reference has
-jdbc4 in it).

Quintin Beukes

On Mon, Nov 23, 2009 at 1:55 PM, Juergen Weber <weberjn@...> wrote:
>
> Hi,
>
> I just checked with 2.1.4, there the driver installs as
>
> <groupId>org.postgresql</groupId>
> <artifactId>postgresql</artifactId>
> <version>8.4.701.jdbc4</version>
> <type>jar</type>
>
> I rechecked with 2.2 with these IDs, the exception stays the same.
>
> Thanks,
> Juergen
>
>
> Juergen Weber wrote:
>>
>> Hi,
>>
>> I tried to install postgresql-8.4-701.jdbc4.jar to the repository of
>> 2.2-SNAPSHOT
>> Build 2009.11.22-08:16:13.118-0500
>> as
>>
>> Group: org.postgresql
>> Artifact: postgresql
>> Version: 8.4-701
>> Type: jar
>> Name: postgresqljdbc
>>
>> and get the exception below. What is wrong? The Name: field is new, isn't
>> it?
>>
>> Thanks,
>> Juergen
>>
>> java.lang.IllegalArgumentException: id must be in the form
>> [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
>> org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
>>
>> org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
>>
>> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
>>
>> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
>>
>> org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
>> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
>> org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>>
>> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
>>
>> org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
>>
>> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
>>
>> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
>>
>> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>>
>> org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
>>
>> org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)
>>
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/IllegalArgumentException%3A-id-must-be-in-the-form-...-tp26467880s134p26476753.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

--
Ivan

Re: JDBC4 Postgresql Driver fails to install

2009-11-24T01:09:38Z

I might be missing something, but if you require it like this:
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>8.4.701.jdbc4</version>
<type>jar</type>

And have this:
> Group: org.postgresql
> Artifact: postgresql
> Version: 8.4-701
> Type: jar

It's not the same thing. The version's don't match (the reference has
-jdbc4 in it).

Quintin Beukes

On Mon, Nov 23, 2009 at 1:55 PM, Juergen Weber <weberjn@...> wrote:

>
> Hi,
>
> I just checked with 2.1.4, there the driver installs as
>
> <groupId>org.postgresql</groupId>
> <artifactId>postgresql</artifactId>
> <version>8.4.701.jdbc4</version>
> <type>jar</type>
>
> I rechecked with 2.2 with these IDs, the exception stays the same.
>
> Thanks,
> Juergen
>
>
> Juergen Weber wrote:
>>
>> Hi,
>>
>> I tried to install postgresql-8.4-701.jdbc4.jar to the repository of
>> 2.2-SNAPSHOT
>> Build 2009.11.22-08:16:13.118-0500
>> as
>>
>> Group: org.postgresql
>> Artifact: postgresql
>> Version: 8.4-701
>> Type: jar
>> Name: postgresqljdbc
>>
>> and get the exception below. What is wrong? The Name: field is new, isn't
>> it?
>>
>> Thanks,
>> Juergen
>>
>> java.lang.IllegalArgumentException: id must be in the form
>> [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
>> org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
>>
>> org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
>>
>> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
>>
>> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
>>
>> org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
>> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
>> org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>>
>> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
>>
>> org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
>>
>> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
>>
>> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
>>
>> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>>
>> org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
>>
>> org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)
>>
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/IllegalArgumentException%3A-id-must-be-in-the-form-...-tp26467880s134p26476753.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

Re: JDBC4 Postgresql Driver fails to install

2009-11-24T00:49:34Z

OK, then if I don't want to replace an existing one but install new, the name field should be empty?

But for an empty name field, I get the exception, too.

Greetings,
Juergen

Ivan Xu wrote:

It is a new feature of Geroinmo 2.2, it will allow you to replace an existed
artifact with the intalled artifact in the runtime. The name should be in
the format of group/artifact/version/type. I will add some help message on
the page.

2009/11/23 Juergen Weber <weberjn@gmail.com>

>
> Hi,
>
> I just checked with 2.1.4, there the driver installs as
>
> <groupId>org.postgresql</groupId>
> <artifactId>postgresql</artifactId>
> <version>8.4.701.jdbc4</version>
> <type>jar</type>
>
> I rechecked with 2.2 with these IDs, the exception stays the same.
>
> Thanks,
> Juergen
>
>
> Juergen Weber wrote:
> >
> > Hi,
> >
> > I tried to install postgresql-8.4-701.jdbc4.jar to the repository of
> > 2.2-SNAPSHOT
> > Build 2009.11.22-08:16:13.118-0500
> > as
> >
> > Group: org.postgresql
> > Artifact: postgresql
> > Version: 8.4-701
> > Type: jar
> > Name: postgresqljdbc
> >
> > and get the exception below. What is wrong? The Name: field is new, isn't
> > it?
> >
> > Thanks,
> > Juergen
> >
> > java.lang.IllegalArgumentException: id must be in the form
> > [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
> >
> org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
> >
> >
> org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
> >
> >
> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
> >
> >
> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
> >
> >
> org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
> >
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
> >
> org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> >
> >
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
> >
> >
> org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
> >
> >
> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
> >
> >
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
> >
> >
> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> > javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> >
> >
> org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
> >
> >
> org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)
> >
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/IllegalArgumentException%3A-id-must-be-in-the-form-...-tp26467880s134p26476753.html
> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

--
Ivan

Re: JDBC4 Postgresql Driver fails to install

2009-11-23T17:48:06Z

It is a new feature of Geroinmo 2.2, it will allow you to replace an existed artifact with the intalled artifact in the runtime. The name should be in the format of group/artifact/version/type. I will add some help message on the page.

2009/11/23 Juergen Weber <weberjn@...>

Hi,

I just checked with 2.1.4, there the driver installs as

<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>8.4.701.jdbc4</version>
<type>jar</type>

I rechecked with 2.2 with these IDs, the exception stays the same.

Thanks,
Juergen

Juergen Weber wrote:
>
> Hi,
>
> I tried to install postgresql-8.4-701.jdbc4.jar to the repository of
> 2.2-SNAPSHOT
> Build 2009.11.22-08:16:13.118-0500
> as
>
> Group: org.postgresql
> Artifact: postgresql
> Version: 8.4-701
> Type: jar
> Name: postgresqljdbc
>
> and get the exception below. What is wrong? The Name: field is new, isn't
> it?
>
> Thanks,
> Juergen
>
> java.lang.IllegalArgumentException: id must be in the form
> [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
> org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
>
> org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
>
> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
>
> org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
>
> org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
> org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
>
> org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
>
> org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
>
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
>
> org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>
> org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
>
> org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)
>
>
>
>

--
View this message in context: http://old.nabble.com/IllegalArgumentException%3A-id-must-be-in-the-form-...-tp26467880s134p26476753.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

--
Ivan

JDBC4 Postgresql Driver fails to install

2009-11-23T03:55:34Z

Hi,

I just checked with 2.1.4, there the driver installs as

<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>8.4.701.jdbc4</version>
<type>jar</type>

I rechecked with 2.2 with these IDs, the exception stays the same.

Thanks,
Juergen

Juergen Weber wrote:

Hi,

I tried to install postgresql-8.4-701.jdbc4.jar to the repository of 2.2-SNAPSHOT
Build 2009.11.22-08:16:13.118-0500
as

Group: org.postgresql
Artifact: postgresql
Version: 8.4-701
Type: jar
Name: postgresqljdbc

and get the exception below. What is wrong? The Name: field is new, isn't it?

Thanks,
Juergen

java.lang.IllegalArgumentException: id must be in the form [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)

fetching deployed server instance value

2009-11-22T12:17:54Z

I am deploying a web app on geronimo application server. I would like to know whether there are any specific apis from which would allow to fetch the specific application server instance value, the reason being the same application would be deployed on two different application server instances and the unique application server instance would be required to do some operations.

Anshuk

IllegalArgumentException: id must be in the form ...

2009-11-22T12:15:47Z

Hi,

I tried to install postgresql-8.4-701.jdbc4.jar to the repository of 2.2-SNAPSHOT
Build 2009.11.22-08:16:13.118-0500
as

Group: org.postgresql
Artifact: postgresql
Version: 8.4-701
Type: jar
Name: postgresqljdbc

and get the exception below. What is wrong? The Name: field is new, isn't it?

Thanks,
Juergen

java.lang.IllegalArgumentException: id must be in the form [groupId]/[artifactId]/[version]/[type] : postgresqljdbc
org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:61)
org.apache.geronimo.kernel.repository.Artifact.createPartial(Artifact.java:55)
org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.propertiesToArtifactMap(ExplicitDefaultArtifactResolver.java:98)
org.apache.geronimo.system.resolver.ExplicitDefaultArtifactResolver.addAliases(ExplicitDefaultArtifactResolver.java:140)
org.apache.geronimo.console.repository.RepositoryViewPortlet.processAction(RepositoryViewPortlet.java:203)
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217)
org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121)
org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:167)
javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)

Re: Geronimo book now available - Apache Geronimo 2.1: Quick Reference

2009-11-20T05:53:29Z

Nice. Congrats Vamsi and Manu. Any Geronimo Committer's discount available? :-)

--kevan

On Nov 15, 2009, at 10:59 PM, Vamsavardhana Reddy wrote:

Hi All,

The book titled "Apache Geronimo 2.1: Quick Reference" authored by Manu T. George and myself is released by Packt Publishing and is now available. Please see [1].

Thanks and best regards,
Vamsi
Committer and Member of Apache Geronimo PMC
Committer on Apache Tuscany

[1] http://www.packtpub.com/apache-geronimo-2-2-quick-reference/book

Re: Remote Deployment: Connection Refused

2009-11-19T10:06:01Z

On Nov 19, 2009, at 12:46 PM, MDiamond wrote:

<snip>

> Both machines are in each other's /etc/hosts file and the iptables on
> machine B are set to allow connections on ports 1099, 9999, 9998, 8080, and
> 8443 (not that all of those are necessary). Any ideas as to what's going
> wrong?

Edit the file var/config/config-substitutions.properties

Locate the following:

RemoteDeployHostname=localhost

and change to configure the ip address of machine B (hostname or dotted ip).

RemoteDeployHostname=B

This isn't very intuitive... Would be nice to simplify this...

--kevan

Remote Deployment: Connection Refused

2009-11-19T09:46:03Z

I'm try to use deploy.sh to deploy a WAR to a remote Geronimo 2.1.4 server, but I can't even get list-modules to work.
Basically, I have two machines, A and B. A Geronimo server is running on B. On A, I try the following:
./deploy.sh --host B list-modules
and get the following error:

Error: Unable to connect to server at
deployer:geronimo:jmx://B:1099 -- Connection refused to host:
127.0.0.1; nested exception is:

java.net.ConnectException: Connection refused
javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused
at org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.newRemoteDeploymentManager(BaseDeploymentFactory.java:190)
at org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.getDeploymentManager(BaseDeploymentFactory.java:140)
at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManager.java:111)
at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:148)
at org.apache.geronimo.deployment.cli.ServerConnection.<init>(ServerConnection.java:88)
at org.apache.geronimo.deployment.cli.ServerConnection.<init>(ServerConnection.java:57)
at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161)
at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67)
at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2327)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:279)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.newRemoteDeploymentManager(BaseDeploymentFactory.java:182)
... 9 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at java.net.Socket.<init>(Socket.java:372)
at java.net.Socket.<init>(Socket.java:186)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
... 17 more

Both machines are in each other's /etc/hosts file and the iptables on machine B are set to allow connections on ports 1099, 9999, 9998, 8080, and 8443 (not that all of those are necessary). Any ideas as to what's going wrong?

Re: JNDI lookup fails with Hibernate + application-scoped datasource

2009-11-17T21:12:39Z

Hi David,
Thanks again for the prompt reply.

I certainly agree that a global JNDI registry seems like it can be easily "polluted". Ideally, developers/deployers would be providing enough context in their JNDI names to avoid collisions instead of leaving that to Geronimo, but I guess that kind of well-known convention is still a ways off.

I'm uncomfortable declaring a resource-ref for any of my EJBs just for the sake of registering my data source with a JNDI name of my own choosing. My EJBs don't access the data source directly... it's all Hibernate.

Is there a way to provide some kind of mapping in the EAR metadata (application.xml, geronimo-application.xml or the deploy plan) or perhaps "force" a given JNDI name?

I'll do some investigating on the JNDI API Context.rename(String, String). Perhaps I can unmangle the JNDI name before Hibernate gets to it ;-).

Kind Regards,
Bevon

djencks wrote:

On Nov 15, 2009, at 8:37 PM, Bevon wrote:

>
> Hi David,
> Thanks for your prompt reply. I tried digging into what the actual
> JNDI
> name was for the data source as you suggested and also went with the
> standard Geronimo JNDI as well (as opposed to the EJB JNDI). Here’s
> what I
> found:
>
> In both the Hibernate-JPA and Hibernate-Core case, the data source
> showed
> (in the Geronimo console’s JNDI Viewer) as:
> jca:/default/Psop_EAR50_Test/JCAManagedConnectionFactory/jdbc/psop/
> derbyDs1
>
> The fact that it's the same in both cases makes sense, since I'm
> declaring
> the data source at the application level and it doesn't change based
> on what
> EJB module I'm using. If I look at the Database Pools view in the
> console,
> I see my data source with "jdbc/psop/derbyDs1" as its name and
> deployed as
> "default/Psop_EAR_50_Test/1.0/car". Again, the same for both cases
> and as
> expected.
>
> Based on what you stated earlier, in the Hibernate-JPA case, Geronimo
> doesn't use JNDI, it just uses the name to lookup the data source.
> And in
> the Hibernate-Core case, Hibernate uses JNDI to do the lookup.
>
> I guess my next question is -- is there a way to provide a "better"
> JNDI
> name for a data source in Geronimo? I'd think maybe in the
> application
> metadata somwhere (application.xml, geronimo-application.xml or the
> vendor-specific deployment plan for the database pool). The reason
> I ask
> is:
> 1) The JNDI name is... unwieldy and non-obvious (ie. it's not
> obvious that
> "jdbc/psop/derbyDs1" is registered in JNDI as "jca:/default/...." and
> 2) It contains the EAR name in it, which I'd rather not have
> hardcoded into
> my EJB module's metadata (for ease of portability reasons).

I am a definite opponent of using global jndi for anything partly for
these kind or reasons. In a global jndi name you need a lot of
context info to assure that there won't be naming collisions when you
deploy 57 datasources named "myDS" for your 114 different independent
apps. That's why the ear name gets into the global jndi name, and why
it will stay there.

That being said you can modify the global jndi name format with a
template in var/config/config-substitutions.properties. I done't
advise it however.

I would try to declare a resource-ref in each of your ejb jars and
look up the java:comp/env/<res-ref-name> string in hibernate. This
will work as long as all calls into hibernate come from javaee
components such as ejbs (or on threads whose call stack goes through
such a component). This has a little more configuration but doesn't
need the context info you are objecting to in the global name.

hope this helps
david jencks

>
> In any case, changing the data source JNDI name in Hibernate
> configuration
> file gets around the publishing errors:
> hibernate.cfg.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
> Configuration DTD 3.0//EN"
> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
> <hibernate-configuration>
> <session-factory name="jdbc/psop/hibernateSf1">
>
> 
> <property
> name="hibernate.connection.datasource">jca:/default/Psop_EAR50_Test/
> JCAManagedConnectionFactory/jdbc/psop/derbyDs1</property>
>
> 
> <property
> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .manager_lookup_class
> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
> property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .factory_class">org.hibernate.transaction.JTATransactionFactory</
> property>
>
> 
> <property name="hibernate.show_sql">true</property>
> <property name="hibernate.format_sql">true</property>
>
> 
> <mapping
> resource="META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml"/>
> </session-factory>
> </hibernate-configuration>
>
>
> Thanks in advance,
> Bevon
>
>
>
>
> djencks wrote:
>>
>> Hi Bevon,
>>
>> I haven't looked through all the files you post but want to give a
>> couple hints, maybe you can easily track down what is going on.
>>
>> In Geronimo, the jta-datasource and non-jta-datasource values don't
>> refer to anything in jndi, they basically look up components
>> registered in the geronimo kernel. The JPA architecture has the
>> container (geronimo's jpa support) setting up an object that includes
>> these datasources and the rest of the info from the persistence.xml,
>> suitably resolved. So, you don't need to declare any resource-refs
>> in
>> your ejb jar anywhere to use jpa.
>>
>> For non-jpa hibernate, IIUC your explanation, jndi is really used to
>> find the datasource(s). I'm not clear on exactly what is getting
>> looked up.... I strongly advise finding out. I also suggest using
>> the
>> standard geronimo jndi rather than the openejb jndi context which is
>> unlikely to have any datasources in it since it is for looking up
>> ejbs. I'd hope that if you _don't_ set the hibernate property it
>> would just use
>> new InitialContext() which ought to work.
>>
>> Finally, hibernate might be trying to look up a java:comp/env jndi
>> name defined by a resource ref in the ejb jar or some completely
>> specified string for a global jndi name. In the latter case, you'll
>> want to check the geronimo.log to make sure you know exactly what the
>> global jndi name for your datasource actually is.... it gets logged
>> as
>> the datasource starts.
>>
>> hope this helps, and if you want to update our docs when you get it
>> working that would be great!
>>
>> thanks
>> david jencks
>>
>> On Nov 14, 2009, at 11:59 AM, Bevon wrote:
>>
>>>
>>> First, my apologies in advance is this should be posted on a
>>> Hibernate board.
>>> But this seems more of a configuration issue specific to Geronimo
>>> so...
>>>
>>> Geronimo: v2.1.4
>>> Hibernate core: v3.3.2
>>> Derby Network Server: v10.4.2
>>>
>>> I was able to get Hibernate working as my JPA provider (instead of
>>> OpenJPA)
>>> for my EJB3 module. However, as an academic/learning exercise, I
>>> have been
>>> trying to get Hibernate core working as my persistence layer for my
>>> EJB3
>>> module. The problem I'm seeing is that during the Hibernate
>>> Configuration.buildSessionFactory() call, a JNDI exception is thrown
>>> stating
>>> that the datasource could not be found.
>>>
>>>
>>> I have an application-scoped managed datasource declared for my
>>> EAR as
>>> follows:
>>> application.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns="http://java.sun.com/xml/ns/javaee"
>>>
>>> xmlns:application="http://java.sun.com/xml/ns/javaee/
>>> application_5.xsd"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>>> http://java.sun.com/xml/ns/javaee/application_5.xsd"
>>> id="Application_ID"
>>> version="5">
>>> <display-name>PsopEAR5_Test</display-name>
>>> <module>
>>> <connector>Derby/tranql-connector-derby-client-local-1.4.rar</
>>> connector>
>>> </module>
>>> <module>
>>> <web>
>>> <web-uri>Psop_Servlet25_Jsp21.war</web-uri>
>>> <context-root>Psop_Servlet25_Jsp21</context-root>
>>> </web>
>>> </module>
>>> <module>
>>> <ejb>Psop_Ejb30_Hibernate33.jar</ejb>
>>> </module>
>>> </application>
>>>
>>>
>>> geronimo-application.xml:
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <app:application
>>> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
>>>
>>> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
>>> "
>>>
>>> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
>>>
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
>>>
>>> xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
>>> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2
>>> "
>>> xmlns:pers="http://java.sun.com/xml/ns/persistence"
>>> xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1
>>> "
>>> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0
>>> "
>>>
>>> xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
>>> application-name="PsopEAR5_Test">
>>> <dep:environment>
>>> <dep:moduleId>
>>> <dep:groupId>default</dep:groupId>
>>> <dep:artifactId>PsopEAR5_Test</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>car</dep:type>
>>> </dep:moduleId>
>>> <dep:dependencies />
>>> </dep:environment>
>>> <app:module>
>>> 
>>>
>>> <app:connector>Derby/tranql-connector-derby-client-local-1.4.rar</
>>> app:connector>
>>>
>>> 
>>> <app:alt-dd>Derby/derby-network-server-plan.xml</app:alt-dd>
>>> </app:module>
>>> </app:application>
>>>
>>>
>>> derby-network-server-plan.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/
>>> connector-1.2">
>>> <dep:environment
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
>>> <dep:moduleId>
>>> <dep:groupId>console.dbpool</dep:groupId>
>>> <dep:artifactId>jdbc_psop_derbyDs1</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>rar</dep:type>
>>> </dep:moduleId>
>>> <dep:dependencies>
>>> <dep:dependency>
>>> <dep:groupId>org.apache.geronimo.configs</dep:groupId>
>>> <dep:artifactId>system-database</dep:artifactId>
>>> <dep:version>2.1.4</dep:version>
>>> <dep:type>car</dep:type>
>>> </dep:dependency>
>>> </dep:dependencies>
>>> </dep:environment>
>>> <resourceadapter>
>>> <outbound-resourceadapter>
>>> <connection-definition>
>>>
>>> <connectionfactory-interface>javax.sql.DataSource</
>>> connectionfactory-
>>> interface>
>>> <connectiondefinition-instance>
>>> <name>jdbc/psop/derbyDs1</name>
>>> <config-property-setting
>>> name="DatabaseName">E:\PSOP\Databases\Derby\PSOP_DATABASE</config-
>>> property-setting>
>>> <config-property-setting
>>> name="Password">app</config-property-setting>
>>> <config-property-setting
>>> name="UserName">app</config-property-setting>
>>> <config-property-setting name="LoginTimeout"/>
>>> <connectionmanager>
>>> <local-transaction/>
>>> <single-pool>
>>> <max-size>10</max-size>
>>> <min-size>0</min-size>
>>> <match-one/>
>>> </single-pool>
>>> </connectionmanager>
>>> </connectiondefinition-instance>
>>> </connection-definition>
>>> </outbound-resourceadapter>
>>> </resourceadapter>
>>> </connector>
>>>
>>>
>>> My EJB3 module metadata is as follows:
>>> ejb-jar.xml (essentially empty since I'm using EJB3 annotations):
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns="http://java.sun.com/xml/ns/javaee"
>>> xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>>> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>>> version="3.0">
>>> <description>PSOP model implemented with EJB 3.0. PSOP
>>> persistence
>>> implemented with Hibernate 3.3 (native).</description>
>>> <display-name>Psop_Ejb30_Hibernate33</display-name>
>>> </ejb-jar>
>>>
>>>
>>> openejb-jar.xml (all of the dependency jars were copied into the
>>> Geronimo
>>> repository):
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-
>>> jar-2.2"
>>> xmlns:naming="http://geronimo.apache.org/xml/ns/
>>> naming-1.2"
>>> xmlns:sec="http://geronimo.apache.org/xml/ns/
>>> security-2.0"
>>> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2
>>> ">
>>> <sys:environment>
>>> <sys:moduleId>
>>> <sys:groupId>default</sys:groupId>
>>> <sys:artifactId>Psop_Ejb30_Hibernate33</sys:artifactId>
>>> <sys:version>1.0</sys:version>
>>> <sys:type>car</sys:type>
>>> </sys:moduleId>
>>> <sys:dependencies>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>core</sys:artifactId>
>>> <sys:version>3.3</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>antlr</sys:artifactId>
>>> <sys:version>2.7.6</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>commons-collections</sys:artifactId>
>>> <sys:version>3.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>dom4j</sys:artifactId>
>>> <sys:version>1.6.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>javassist</sys:artifactId>
>>> <sys:version>3.9.0.GA</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>jta</sys:artifactId>
>>> <sys:version>1.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>GeronimoTransactionManager</
>>> sys:artifactId>
>>> <sys:version>1.0</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>org.slf4j</sys:groupId>
>>> <sys:artifactId>slf4j-api</sys:artifactId>
>>> <sys:version>1.4.3</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> </sys:dependencies>
>>> </sys:environment>
>>> </openejb-jar>
>>>
>>>
>>> hibernate.cfg.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
>>> Configuration DTD 3.0//EN"
>>> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
>>> <hibernate-configuration>
>>> <session-factory name="jdbc/psop/hibernateSf1">
>>>
>>> 
>>> <property
>>> name="hibernate.connection.datasource">jdbc/psop/derbyDs1</property>
>>>
>>> 
>>> <property
>>> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</
>>> property>
>>>
>>> 
>>> <property
>>> name
>>> =
>>> "hibernate
>>> .transaction
>>> .manager_lookup_class
>>> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
>>> property>
>>>
>>> 
>>> <property
>>> name
>>> =
>>> "hibernate
>>> .transaction
>>> .factory_class">org.hibernate.transaction.JTATransactionFactory</
>>> property>
>>>
>>> 
>>> <property name="hibernate.show_sql">true</property>
>>> <property name="hibernate.format_sql">true</property>
>>>
>>> 
>>> <mapping
>>> resource="META-INF/mappings/com/psop/model/hibernate/
>>> PlayerHibernateEntity.hbm.xml"/>
>>> </session-factory>
>>> </hibernate-configuration>
>>>
>>>
>>>
>>>
>>> Here is the code that tries to build the SessionFactory:
>>> Configuration hibernateConfiguration = new
>>> Configuration().configure(
>>> "/META-INF/hibernate.cfg.xml" );
>>> hibernateConfiguration.setProperty(
>>> org.hibernate.cfg.Environment.JNDI_CLASS,
>>> "org.apache.openejb.client.RemoteInitialContextFactory" ) );
>>> hibernateConfiguration
>>> .setProperty( org.hibernate.cfg.Environment.JNDI_URL,
>>> "ejbd://localhost:4201" );
>>>
>>> sessionFactorySingleInstance =
>>> hibernateConfiguration.buildSessionFactory();
>>> // throws JNDI exception
>>> // as a test, if I do a JNDI lookup on "jdbc/psop/derbyDs1", I get
>>> the same
>>> exception
>>>
>>>
>>> Here is the exception that occurs during publishing (I'm using
>>> Eclipse
>>> Ganymede with GEP):
>>> javax.naming.NameNotFoundException: /jdbc/psop/derbyDs1 does not
>>> exist in
>>> the system. Check that the app was successfully deployed.
>>> at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:
>>> 277)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> com
>>> .psop
>>> .model
>>> .ejb
>>> .config
>>> .EjbHibernateModelConfig
>>> .initializeSessionFactory(EjbHibernateModelConfig.java:234)
>>> at
>>> com
>>> .psop
>>> .model
>>> .ejb
>>> .config
>>> .EjbHibernateModelConfig
>>> .initializeModel(EjbHibernateModelConfig.java:292)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at
>>> org.apache.openejb.core.interceptor.ReflectionInvocationContext
>>> $Invocation.invoke(ReflectionInvocationContext.java:158)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core
>>> .interceptor
>>> .ReflectionInvocationContext
>>> .proceed(ReflectionInvocationContext.java:141)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
>>> 210)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
>>> 188)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer.invoke(StatelessContainer.java:
>>> 165)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .server
>>> .ejbd
>>> .EjbRequestHandler
>>> .doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .server
>>> .ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:
>>> 129)
>>> at
>>> org
>>> .apache
>>> .openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164)
>>> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
>>> 122)
>>> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
>>> 84)
>>> at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:
>>> 60)
>>> at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:78)
>>> at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:
>>> 101)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>>> Source)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>> Source)
>>> at java.lang.Thread.run(Unknown Source)
>>>
>>>
>>>
>>> Geronimo log (I don't see any binding of the datasource to JNDI
>>> here):
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default
>>> Stateless Container, type=Container, provider-id=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default
>>> Stateful Container, type=Container, provider-id=Default Stateful
>>> Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default BMP
>>> Container, type=Container, provider-id=Default BMP Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default CMP
>>> Container, type=Container, provider-id=Default CMP Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring app:
>>> default/PsopEAR5_Test/1.0/car
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateFinder:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateDestroyer:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateCreator:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateModelConfig:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig)
>>> 2009-11-14 14:30:06,919 INFO [config] Loaded Module:
>>> default/PsopEAR5_Test/1.0/car
>>> 2009-11-14 14:30:07,810 INFO [KernelContextGBean] bound gbean
>>> default/PsopEAR5_Test/1.0/car?J2EEApplication=default/PsopEAR5_Test/
>>> 1.0/car,JCAConnectionFactory=jdbc/psop/derbyDs1,JCAResource=Derby/
>>> tranql-connector-derby-client-local-1.4.rar,ResourceAdapter=Derby/
>>> tranql-connector-derby-client-
>>> local-1.4.rar,ResourceAdapterModule=Derby/tranql-connector-derby-
>>> client-local-1.4.rar,j2eeType=JCAManagedConnectionFactory,name=jdbc/
>>> psop/derbyDs1
>>> at name default/PsopEAR5_Test/JCAManagedConnectionFactory/jdbc/psop/
>>> derbyDs1
>>> 2009-11-14 14:30:07,810 INFO [startup] Assembling app: C:\Documents
>>> and
>>> Settings\Bevon Palod\Local
>>> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateFinderRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateDestroyerRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateCreatorRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateModelConfigRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder,
>>> ejb-name=ejb/psop/ejbHibernateFinder, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer,
>>> ejb-name=ejb/psop/ejbHibernateDestroyer, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator,
>>> ejb-name=ejb/psop/ejbHibernateCreator, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig,
>>> ejb-name=ejb/psop/ejbHibernateModelConfig, container=Default
>>> Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Deployed
>>> Application(path=C:\Documents and Settings\Bevon Palod\Local
>>> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar)
>>> 2009-11-14 14:30:08,013 INFO [OpenEJB] invoking method create on
>>> Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig
>>> 2009-11-14 14:30:08,013 INFO [OpenEJB] finished invoking method
>>> create
>>> 2009-11-14 14:30:08,013 INFO [Transaction] TX Required: Started
>>> transaction
>>> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>>> 2009-11-14 14:30:08,091 INFO [Environment] Hibernate 3.3.2.GA
>>> 2009-11-14 14:30:08,091 INFO [Environment] hibernate.properties not
>>> found
>>> 2009-11-14 14:30:08,106 INFO [Environment] Bytecode provider name :
>>> javassist
>>> 2009-11-14 14:30:08,122 INFO [Environment] using JDK 1.4
>>> java.sql.Timestamp
>>> handling
>>> 2009-11-14 14:30:08,356 INFO [Configuration] configuring from
>>> resource:
>>> /META-INF/hibernate.cfg.xml
>>> 2009-11-14 14:30:08,356 INFO [Configuration] Configuration
>>> resource:
>>> /META-INF/hibernate.cfg.xml
>>> 2009-11-14 14:30:08,497 INFO [Configuration] Reading mappings from
>>> resource
>>> : META-INF/mappings/com/psop/model/hibernate/
>>> PlayerHibernateEntity.hbm.xml
>>> 2009-11-14 14:30:08,606 INFO [HbmBinder] Mapping class:
>>> com.psop.model.hibernate.PlayerHibernateEntity -> PLAYERS
>>> 2009-11-14 14:30:08,685 INFO [Configuration] Configured
>>> SessionFactory:
>>> jdbc/psop/hibernateSf1
>>> 2009-11-14 14:30:08,685 INFO [Transaction] TX Required: Committing
>>> transaction
>>> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>>>
>>>
>>> I do not see this exception when I make use of Hibernate
>>> Annotations +
>>> EnitityManager and stick with JPA-only API/annotations in my code.
>>> In terms
>>> of configuration, the EAR metadata is exactly the same (save for
>>> swapping
>>> the EJB3 modules). The EJB3 module metadata has two differences:
>>> 1. I've got a persistence.xml instead of hibernate.cfg.xml.
>>> 2. I've added the Hibernate Annotations + EntityManager
>>> dependencies to my
>>> openejb-jar.xml (won't bother pasting it again here).
>>>
>>> persistence.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <persistence xmlns="http://java.sun.com/xml/ns/persistence"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/
>>> persistence
>>> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
>>> version="1.0" >
>>> <persistence-unit name="Psop_Ejb30_Jpa10" transaction-type="JTA">
>>> <description>Hibernate v3.3 JPA provider</description>
>>> <provider>org.hibernate.ejb.HibernatePersistence</provider>
>>> <jta-data-source>jdbc/psop/derbyDs1</jta-data-source>
>>> <class>com.psop.model.jpa.PlayerJpaEntity</class>
>>> <properties>
>>> <property
>>> name="hibernate.transaction.manager_lookup_class"
>>> value="org.hibernate.transaction.GeronimoTransactionManagerLookup"/>
>>> <property name="hibernate.show_sql" value="true"/>
>>> <property name="hibernate.format_sql" value="true"/>
>>> <property name="hibernate.dialect"
>>> value="org.hibernate.dialect.DerbyDialect"/>
>>> </properties>
>>> </persistence-unit>
>>> </persistence>
>>>
>>>
>>> My best guess -- I'm doing something wrong or it's a faulty
>>> assumption that
>>> my datasource will automagically be registered in JNDI (as it is
>>> with JPA).
>>>
>>> Please bear with me as I'm a newbie. I've been banging on Geronimo
>>> for just
>>> about a month and have been at Hibernate for maybe a week. If
>>> someone could
>>> shed some light on this problem or perhaps point me to some
>>> documentation
>>> (yes, I've read the Hibernate to Geronimo migration docs, yes, I've
>>> googled,
>>> yes, I did a keyword search on this forum for "Hibernate
>>> datasource").
>>>
>>> Many thanks in advance!!!
>>> Bevon
>>> --
>>> View this message in context:
>>> http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26353366.html
>>> Sent from the Apache Geronimo - Users mailing list archive at
>>> Nabble.com.
>>>
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26366792.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>

Re: Geronimo with Hibernate

2009-11-17T11:42:54Z

Have a look at:
http://qbeukes.blogspot.com/2009/09/geronimo-using-hibernate-as-your-jpa.html

If you need help just let me know.

Quintin Beukes

On Tue, Nov 17, 2009 at 4:57 PM, Donald Woods <dwoods@...> wrote:

> You would need to create a set of Hibernate plugins that replaces the
> OpenJPA ones provided in Geronimo.
>
> Take a look at how I created the OpenJPA2 plugins to see how it could be
> done -
> https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/branches
>
>
> -Donald
>
> Michael Simons wrote:
>>
>> Hello,
>>
>> Does anybody know whether you can substitute the ORM OpenJPA used by
>> Geronimo by default with
>> the Hibernate persistence layer? Is there a documentation how to
>> substitute modules of Geronimo,
>> generally?
>>
>> Kind Regards,
>> Michael
>>
>

Re: Serious Problem with Roles

2009-11-17T10:18:10Z

On Nov 17, 2009, at 1:01 AM, Quintin Beukes wrote:

> I think what I'm going to do is add another level of abstraction
> around roles in my database.
>
> Where I now have
> Operators->Roles
>
> I will have
> Operators->Roles->ContainerRoles
>
> So each module defines it's roles and has a OneToMany on
> ContainerRoles. ContainerRoles will then have a OneToOne mapping to a
> role in the deployment descriptor and my SQLLoginModule will then do
> another LEFT JOIN on ContainerRoles which would then become the
> GeronimoGroupPrincipals for the subject.

This seems like a reasonable solution. I can't think of a better one
that doesn't involve writing a whole new security system.

I'm not sure it's immediately relevant to your situation but, if you
are not already familiar with the ideas, you might be interested in
investigating hierarchical role-base access control (RBAC). I spent
some time working on an implementation (soter at codehaus) but didn't
get it integrated into geronimo.

thanks
david jencks

>
> Quintin Beukes
>
>
>
> On Tue, Nov 17, 2009 at 10:25 AM, Quintin Beukes <quintin@...
> > wrote:
>> This is my situation.
>>
>> I have the server, which has the roles/users and EJB security with
>> @RolesAllowed. This is container managed and the important part, as
>> it's absolutely crucial that you can't execute what you're not
>> allowed
>> to. This works fine.
>>
>> Further it's a modular system. You load the modules you want and they
>> work together to form a system. Each module has it's own roles.
>>
>> For example, we have the platform (core) module which defines
>> "Standard User" and "Admin". The "Admin" has access to almost
>> everything as each module lists it explicitly to be allowed to do
>> almost everything (just a few things like those for services which it
>> can't do). Then the personnel module which defines "Personnel Admin"
>> and "Personnel User". And for arguments sake on more called "Lamp"
>> with say, "Lamp Room" and some others. So Personnel module has no
>> concept of "Lamp Room". In the Lamp EJB when I do the mappings I here
>> list that the "Lamp Room" group maps to "Lamp Room", "Personnel User"
>> and "Standard User". So each module down the hierarchy lists the
>> roles
>> upwards which it maps to, like in this case "Lamp Room" users need
>> read access to personnel as well.
>>
>> This is all fine for the server, as it works. The problem is on the
>> client. I need a way for this information to be retrieved from the
>> server. I am hoping to get the information as the server understands
>> it to reduce maintenance and thus avoid potential bugs. If I have to
>> start maintaining multiple hard coded lists of permissions I'm just
>> looking for trouble. Especially when another developer has to start
>> working on this code base, which is the case as I usually don't do
>> the
>> maintenance.
>>
>> The reason I need it client side is to construct the UI. The main
>> terminal GUI is a desktop application and it has to
>> enable/disable/hide/show actions based on the user's roles. Also,
>> since it's modular I have exposed certain services, like for
>> navigation. Each module broadcasts only it's actions, and the
>> navigation module automatically takes care of authorization using
>> annotations on the action's class. The typical modular system...
>> trying to modularize everything and on duplication.
>>
>> Is there perhaps a way I can tell the server how to do the role
>> mappings programmatically? So, instead of listing it in a deployment
>> descriptor it's listed in the database and when one of my Singleton
>> beans load I can configure the role mappings?
>>
>> Quintin Beukes
>>
>>
>>
>> On Mon, Nov 16, 2009 at 10:37 PM, David Jencks <david_jencks@...
>> > wrote:
>>>
>>> On Nov 16, 2009, at 10:39 AM, Quintin Beukes wrote:
>>>
>>>> Even if it means quite a bit of code. I seriously need a way to
>>>> determine the roles. It's either this or a massive overhaul on our
>>>> user/group/role system where the whole system is already
>>>> standing at 80000 lines of code. Changing the auth structure at
>>>> this
>>>> point would postpone the release too much.
>>>>
>>>> This is the last thing standing between me and a phase 1 release.
>>>> Any
>>>> suggestions would thus be greatly appreciated.
>>>
>>> I've also wanted a
>>>
>>> Collection<String> getUserRoles()
>>>
>>> method but there isn't one. About the only thing you can do is
>>>
>>> List<String> allRoles = //hard-code or read from a property file???
>>> List<String> userRoles = new ArrayList<String>();
>>> for (String role: allRoles) {
>>> if (context.isUserInRole(role)) {
>>> userRoles.add(role);
>>> }
>>> }
>>>
>>> I'm curious why you need this much information for this kind of
>>> partially
>>> app managed security. Maybe there's another way to approach this.
>>>
>>> One possibility is to add more container managed security -- a whole
>>> additional kind of permission -- to your setup. You can write
>>> security
>>> deployers to add more role-permission mappings to the security
>>> system and
>>> then at runtime your app can test with
>>> accessControlContext.implies(new
>>> MySpecialPermission(info)). This may well not be enough info, but
>>> if this
>>> sounds remotely plausible let me know....
>>>
>>> hope this helps
>>> david jencks
>>>
>>>
>>>
>>>>
>>>> Quintin Beukes
>>>>
>>>>
>>>>
>>>> On Mon, Nov 16, 2009 at 8:04 PM, Quintin Beukes <quintin@...
>>>> >
>>>> wrote:
>>>>>
>>>>> Oh yes :<
>>>>>
>>>>> I was so focussed on my initial problem that I forgot about the
>>>>> workings of isCallerInRole(). You have to do @DeclareRoles({..})
>>>>> at
>>>>> the class level. I actually do this everywhere I call
>>>>> isCallerInRole(). It was just in this case where I'm trying to
>>>>> determine the call's roles. The subject wasn't working (I now know
>>>>> it's obvious, as a role isn't a principal), so I tried to do
>>>>> isCallerInRole() without using it properly.
>>>>>
>>>>> I have a big problem though.
>>>>>
>>>>> Is there any way at all to get a list of roles for a user as
>>>>> mapped in
>>>>> the deployment descriptor? Even if I have to query the Geronimo
>>>>> API.
>>>>> Portability when it comes to security is really not a big issue
>>>>> for me
>>>>> as I feel JavaEE's security is vague in any case. Besides, where
>>>>> ever
>>>>> I break portability I do so through interfaces and implementations
>>>>> with some "container validation". So if someone following me
>>>>> tries to
>>>>> port he'll get a "friendly" message stating he needs to make his
>>>>> own
>>>>> implementation.
>>>>>
>>>>> Quintin Beukes
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Nov 16, 2009 at 7:29 PM, David Jencks <david_jencks@...
>>>>> >
>>>>> wrote:
>>>>>>
>>>>>> Hi Quintin,
>>>>>>
>>>>>> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>>>>>>
>>>>>>> Hey,
>>>>>>>
>>>>>>> I basically have a bunch of roles which should each be mapped to
>>>>>>> different combinations of a user's "GroupPrincipals".
>>>>>>> Something like
>>>>>>> this:
>>>>>>>
>>>>>>> <sec:role role-name="Lamp Room">
>>>>>>> <sec:principal
>>>>>>> class
>>>>>>> =
>>>>>>> "org
>>>>>>> .apache
>>>>>>> .geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>>> name="Lamp Room"/>
>>>>>>> </sec:role>
>>>>>>> <sec:role role-name="VDS User">
>>>>>>> <sec:principal
>>>>>>> class
>>>>>>> =
>>>>>>> "org
>>>>>>> .apache
>>>>>>> .geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>>> name="Lamp Room"/>
>>>>>>> </sec:role>
>>>>>>> <sec:role role-name="Personnel User">
>>>>>>> <sec:principal
>>>>>>> class
>>>>>>> =
>>>>>>> "org
>>>>>>> .apache
>>>>>>> .geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>>> name="Lamp Room"/>
>>>>>>> </sec:role>
>>>>>>>
>>>>>>> This means that named roles are all assigned to a user of
>>>>>>> group "Lamp
>>>>>>> Room".
>>>>>>>
>>>>>>> Though doing the following I don't see these "virtual roles",
>>>>>>> only the
>>>>>>> actual group.
>>>>>>> Subject subject = ContextManager.getCurrentCaller();
>>>>>>> Set<Principal> principals = subject.getPrincipals();
>>>>>>
>>>>>> roles are just names, not principals, so there's no way you'll
>>>>>> see them
>>>>>> in
>>>>>> the Subject. Here's how it works, in PolicyContextGeneric:
>>>>>>
>>>>>> 1. the principal-role map specified above is fed in.
>>>>>> 2. the role-permission map specified by the DD or annotations
>>>>>> is fed in
>>>>>> 3. these are combined to form a principal-permission map as the
>>>>>> app
>>>>>> starts
>>>>>> up
>>>>>> 4. when you test a permission (either through container access
>>>>>> control
>>>>>> or an
>>>>>> isUserInRole/isCallerInRole call) we run through the Subject's
>>>>>> principals,
>>>>>> get the PermissionCollection for that principal, and see if it
>>>>>> implies
>>>>>> the
>>>>>> permission desired.
>>>>>>
>>>>>> One thing to note about this is that geronimo needs to know
>>>>>> about the
>>>>>> role
>>>>>> and permission you're going to check. So the role has to be
>>>>>> declared
>>>>>> somewhere. I'm less sure about the role-ref permission...
>>>>>> for web apps there is an implicit role-ref permission set up
>>>>>> mapping the
>>>>>> role to itself for any role without an explicit role-ref. I
>>>>>> don't
>>>>>> recall
>>>>>> how ejbs work, I kinda think that you have to declare all the
>>>>>> roles you
>>>>>> are
>>>>>> going to test with a role-ref.
>>>>>>
>>>>>>>
>>>>>>> I can see how this would be the case, though the following must
>>>>>>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>>>>>>> isCallerInRole("Lamp Room"). They all return false.
>>>>>>>
>>>>>>> If I have a method annotated with @RolesAllowed({"Personnel
>>>>>>> User"}),
>>>>>>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>>>>>>> InterfaceType typee) return TRUE.
>>>>>>> Though, GeronimoSecurityService.isCallerInRole(String role)
>>>>>>> returns
>>>>>>> FALSE when I query isCallerInRole("Personnel User").
>>>>>>
>>>>>> I think this might support my idea that you have to explicitly
>>>>>> set up a
>>>>>> role-ref for any role you mean to test in an ejb.
>>>>>>>
>>>>>>> I assume somewhere the AccessControlContext isn't populated
>>>>>>> correctly?
>>>>>>> I'm not really sure how this should work, so if someone can
>>>>>>> tell me
>>>>>>> how this all fits together I can have a look.
>>>>>>>
>>>>>>
>>>>>> Let me know if the above doesn't answer your questions
>>>>>>
>>>>>> thanks
>>>>>> david jencks
>>>>>>
>>>>>>> Quintin Beukes
>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>

Re: Geronimo with Hibernate

2009-11-17T06:57:08Z

You would need to create a set of Hibernate plugins that replaces the
OpenJPA ones provided in Geronimo.

Take a look at how I created the OpenJPA2 plugins to see how it could be
done -
https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/branches

-Donald

Michael Simons wrote:
> Hello,
>
> Does anybody know whether you can substitute the ORM OpenJPA used by Geronimo by default with
> the Hibernate persistence layer? Is there a documentation how to substitute modules of Geronimo,
> generally?
>
> Kind Regards,
> Michael
>

Geronimo with Hibernate

2009-11-17T02:31:17Z

Hello,

Does anybody know whether you can substitute the ORM OpenJPA used by Geronimo by default with
the Hibernate persistence layer? Is there a documentation how to substitute modules of Geronimo,
generally?

Kind Regards,
Michael

Re: Serious Problem with Roles

2009-11-17T01:01:03Z

I think what I'm going to do is add another level of abstraction
around roles in my database.

Where I now have
Operators->Roles

I will have
Operators->Roles->ContainerRoles

So each module defines it's roles and has a OneToMany on
ContainerRoles. ContainerRoles will then have a OneToOne mapping to a
role in the deployment descriptor and my SQLLoginModule will then do
another LEFT JOIN on ContainerRoles which would then become the
GeronimoGroupPrincipals for the subject.

Quintin Beukes

On Tue, Nov 17, 2009 at 10:25 AM, Quintin Beukes <quintin@...> wrote:

> This is my situation.
>
> I have the server, which has the roles/users and EJB security with
> @RolesAllowed. This is container managed and the important part, as
> it's absolutely crucial that you can't execute what you're not allowed
> to. This works fine.
>
> Further it's a modular system. You load the modules you want and they
> work together to form a system. Each module has it's own roles.
>
> For example, we have the platform (core) module which defines
> "Standard User" and "Admin". The "Admin" has access to almost
> everything as each module lists it explicitly to be allowed to do
> almost everything (just a few things like those for services which it
> can't do). Then the personnel module which defines "Personnel Admin"
> and "Personnel User". And for arguments sake on more called "Lamp"
> with say, "Lamp Room" and some others. So Personnel module has no
> concept of "Lamp Room". In the Lamp EJB when I do the mappings I here
> list that the "Lamp Room" group maps to "Lamp Room", "Personnel User"
> and "Standard User". So each module down the hierarchy lists the roles
> upwards which it maps to, like in this case "Lamp Room" users need
> read access to personnel as well.
>
> This is all fine for the server, as it works. The problem is on the
> client. I need a way for this information to be retrieved from the
> server. I am hoping to get the information as the server understands
> it to reduce maintenance and thus avoid potential bugs. If I have to
> start maintaining multiple hard coded lists of permissions I'm just
> looking for trouble. Especially when another developer has to start
> working on this code base, which is the case as I usually don't do the
> maintenance.
>
> The reason I need it client side is to construct the UI. The main
> terminal GUI is a desktop application and it has to
> enable/disable/hide/show actions based on the user's roles. Also,
> since it's modular I have exposed certain services, like for
> navigation. Each module broadcasts only it's actions, and the
> navigation module automatically takes care of authorization using
> annotations on the action's class. The typical modular system...
> trying to modularize everything and on duplication.
>
> Is there perhaps a way I can tell the server how to do the role
> mappings programmatically? So, instead of listing it in a deployment
> descriptor it's listed in the database and when one of my Singleton
> beans load I can configure the role mappings?
>
> Quintin Beukes
>
>
>
> On Mon, Nov 16, 2009 at 10:37 PM, David Jencks <david_jencks@...> wrote:
>>
>> On Nov 16, 2009, at 10:39 AM, Quintin Beukes wrote:
>>
>>> Even if it means quite a bit of code. I seriously need a way to
>>> determine the roles. It's either this or a massive overhaul on our
>>> user/group/role system where the whole system is already
>>> standing at 80000 lines of code. Changing the auth structure at this
>>> point would postpone the release too much.
>>>
>>> This is the last thing standing between me and a phase 1 release. Any
>>> suggestions would thus be greatly appreciated.
>>
>> I've also wanted a
>>
>> Collection<String> getUserRoles()
>>
>> method but there isn't one. About the only thing you can do is
>>
>> List<String> allRoles = //hard-code or read from a property file???
>> List<String> userRoles = new ArrayList<String>();
>> for (String role: allRoles) {
>> if (context.isUserInRole(role)) {
>> userRoles.add(role);
>> }
>> }
>>
>> I'm curious why you need this much information for this kind of partially
>> app managed security. Maybe there's another way to approach this.
>>
>> One possibility is to add more container managed security -- a whole
>> additional kind of permission -- to your setup. You can write security
>> deployers to add more role-permission mappings to the security system and
>> then at runtime your app can test with accessControlContext.implies(new
>> MySpecialPermission(info)). This may well not be enough info, but if this
>> sounds remotely plausible let me know....
>>
>> hope this helps
>> david jencks
>>
>>
>>
>>>
>>> Quintin Beukes
>>>
>>>
>>>
>>> On Mon, Nov 16, 2009 at 8:04 PM, Quintin Beukes <quintin@...>
>>> wrote:
>>>>
>>>> Oh yes :<
>>>>
>>>> I was so focussed on my initial problem that I forgot about the
>>>> workings of isCallerInRole(). You have to do @DeclareRoles({..}) at
>>>> the class level. I actually do this everywhere I call
>>>> isCallerInRole(). It was just in this case where I'm trying to
>>>> determine the call's roles. The subject wasn't working (I now know
>>>> it's obvious, as a role isn't a principal), so I tried to do
>>>> isCallerInRole() without using it properly.
>>>>
>>>> I have a big problem though.
>>>>
>>>> Is there any way at all to get a list of roles for a user as mapped in
>>>> the deployment descriptor? Even if I have to query the Geronimo API.
>>>> Portability when it comes to security is really not a big issue for me
>>>> as I feel JavaEE's security is vague in any case. Besides, where ever
>>>> I break portability I do so through interfaces and implementations
>>>> with some "container validation". So if someone following me tries to
>>>> port he'll get a "friendly" message stating he needs to make his own
>>>> implementation.
>>>>
>>>> Quintin Beukes
>>>>
>>>>
>>>>
>>>> On Mon, Nov 16, 2009 at 7:29 PM, David Jencks <david_jencks@...>
>>>> wrote:
>>>>>
>>>>> Hi Quintin,
>>>>>
>>>>> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>>>>>
>>>>>> Hey,
>>>>>>
>>>>>> I basically have a bunch of roles which should each be mapped to
>>>>>> different combinations of a user's "GroupPrincipals". Something like
>>>>>> this:
>>>>>>
>>>>>> <sec:role role-name="Lamp Room">
>>>>>> <sec:principal
>>>>>> class
>>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>> name="Lamp Room"/>
>>>>>> </sec:role>
>>>>>> <sec:role role-name="VDS User">
>>>>>> <sec:principal
>>>>>> class
>>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>> name="Lamp Room"/>
>>>>>> </sec:role>
>>>>>> <sec:role role-name="Personnel User">
>>>>>> <sec:principal
>>>>>> class
>>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>>> name="Lamp Room"/>
>>>>>> </sec:role>
>>>>>>
>>>>>> This means that named roles are all assigned to a user of group "Lamp
>>>>>> Room".
>>>>>>
>>>>>> Though doing the following I don't see these "virtual roles", only the
>>>>>> actual group.
>>>>>> Subject subject = ContextManager.getCurrentCaller();
>>>>>> Set<Principal> principals = subject.getPrincipals();
>>>>>
>>>>> roles are just names, not principals, so there's no way you'll see them
>>>>> in
>>>>> the Subject. Here's how it works, in PolicyContextGeneric:
>>>>>
>>>>> 1. the principal-role map specified above is fed in.
>>>>> 2. the role-permission map specified by the DD or annotations is fed in
>>>>> 3. these are combined to form a principal-permission map as the app
>>>>> starts
>>>>> up
>>>>> 4. when you test a permission (either through container access control
>>>>> or an
>>>>> isUserInRole/isCallerInRole call) we run through the Subject's
>>>>> principals,
>>>>> get the PermissionCollection for that principal, and see if it implies
>>>>> the
>>>>> permission desired.
>>>>>
>>>>> One thing to note about this is that geronimo needs to know about the
>>>>> role
>>>>> and permission you're going to check. So the role has to be declared
>>>>> somewhere. I'm less sure about the role-ref permission...
>>>>> for web apps there is an implicit role-ref permission set up mapping the
>>>>> role to itself for any role without an explicit role-ref. I don't
>>>>> recall
>>>>> how ejbs work, I kinda think that you have to declare all the roles you
>>>>> are
>>>>> going to test with a role-ref.
>>>>>
>>>>>>
>>>>>> I can see how this would be the case, though the following must
>>>>>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>>>>>> isCallerInRole("Lamp Room"). They all return false.
>>>>>>
>>>>>> If I have a method annotated with @RolesAllowed({"Personnel User"}),
>>>>>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>>>>>> InterfaceType typee) return TRUE.
>>>>>> Though, GeronimoSecurityService.isCallerInRole(String role) returns
>>>>>> FALSE when I query isCallerInRole("Personnel User").
>>>>>
>>>>> I think this might support my idea that you have to explicitly set up a
>>>>> role-ref for any role you mean to test in an ejb.
>>>>>>
>>>>>> I assume somewhere the AccessControlContext isn't populated correctly?
>>>>>> I'm not really sure how this should work, so if someone can tell me
>>>>>> how this all fits together I can have a look.
>>>>>>
>>>>>
>>>>> Let me know if the above doesn't answer your questions
>>>>>
>>>>> thanks
>>>>> david jencks
>>>>>
>>>>>> Quintin Beukes
>>>>>
>>>>>
>>>>
>>
>>
>

Re: Serious Problem with Roles

2009-11-17T00:25:27Z

This is my situation.

I have the server, which has the roles/users and EJB security with
@RolesAllowed. This is container managed and the important part, as
it's absolutely crucial that you can't execute what you're not allowed
to. This works fine.

Further it's a modular system. You load the modules you want and they
work together to form a system. Each module has it's own roles.

For example, we have the platform (core) module which defines
"Standard User" and "Admin". The "Admin" has access to almost
everything as each module lists it explicitly to be allowed to do
almost everything (just a few things like those for services which it
can't do). Then the personnel module which defines "Personnel Admin"
and "Personnel User". And for arguments sake on more called "Lamp"
with say, "Lamp Room" and some others. So Personnel module has no
concept of "Lamp Room". In the Lamp EJB when I do the mappings I here
list that the "Lamp Room" group maps to "Lamp Room", "Personnel User"
and "Standard User". So each module down the hierarchy lists the roles
upwards which it maps to, like in this case "Lamp Room" users need
read access to personnel as well.

This is all fine for the server, as it works. The problem is on the
client. I need a way for this information to be retrieved from the
server. I am hoping to get the information as the server understands
it to reduce maintenance and thus avoid potential bugs. If I have to
start maintaining multiple hard coded lists of permissions I'm just
looking for trouble. Especially when another developer has to start
working on this code base, which is the case as I usually don't do the
maintenance.

The reason I need it client side is to construct the UI. The main
terminal GUI is a desktop application and it has to
enable/disable/hide/show actions based on the user's roles. Also,
since it's modular I have exposed certain services, like for
navigation. Each module broadcasts only it's actions, and the
navigation module automatically takes care of authorization using
annotations on the action's class. The typical modular system...
trying to modularize everything and on duplication.

Is there perhaps a way I can tell the server how to do the role
mappings programmatically? So, instead of listing it in a deployment
descriptor it's listed in the database and when one of my Singleton
beans load I can configure the role mappings?

Quintin Beukes

On Mon, Nov 16, 2009 at 10:37 PM, David Jencks <david_jencks@...> wrote:

>
> On Nov 16, 2009, at 10:39 AM, Quintin Beukes wrote:
>
>> Even if it means quite a bit of code. I seriously need a way to
>> determine the roles. It's either this or a massive overhaul on our
>> user/group/role system where the whole system is already
>> standing at 80000 lines of code. Changing the auth structure at this
>> point would postpone the release too much.
>>
>> This is the last thing standing between me and a phase 1 release. Any
>> suggestions would thus be greatly appreciated.
>
> I've also wanted a
>
> Collection<String> getUserRoles()
>
> method but there isn't one. About the only thing you can do is
>
> List<String> allRoles = //hard-code or read from a property file???
> List<String> userRoles = new ArrayList<String>();
> for (String role: allRoles) {
> if (context.isUserInRole(role)) {
> userRoles.add(role);
> }
> }
>
> I'm curious why you need this much information for this kind of partially
> app managed security. Maybe there's another way to approach this.
>
> One possibility is to add more container managed security -- a whole
> additional kind of permission -- to your setup. You can write security
> deployers to add more role-permission mappings to the security system and
> then at runtime your app can test with accessControlContext.implies(new
> MySpecialPermission(info)). This may well not be enough info, but if this
> sounds remotely plausible let me know....
>
> hope this helps
> david jencks
>
>
>
>>
>> Quintin Beukes
>>
>>
>>
>> On Mon, Nov 16, 2009 at 8:04 PM, Quintin Beukes <quintin@...>
>> wrote:
>>>
>>> Oh yes :<
>>>
>>> I was so focussed on my initial problem that I forgot about the
>>> workings of isCallerInRole(). You have to do @DeclareRoles({..}) at
>>> the class level. I actually do this everywhere I call
>>> isCallerInRole(). It was just in this case where I'm trying to
>>> determine the call's roles. The subject wasn't working (I now know
>>> it's obvious, as a role isn't a principal), so I tried to do
>>> isCallerInRole() without using it properly.
>>>
>>> I have a big problem though.
>>>
>>> Is there any way at all to get a list of roles for a user as mapped in
>>> the deployment descriptor? Even if I have to query the Geronimo API.
>>> Portability when it comes to security is really not a big issue for me
>>> as I feel JavaEE's security is vague in any case. Besides, where ever
>>> I break portability I do so through interfaces and implementations
>>> with some "container validation". So if someone following me tries to
>>> port he'll get a "friendly" message stating he needs to make his own
>>> implementation.
>>>
>>> Quintin Beukes
>>>
>>>
>>>
>>> On Mon, Nov 16, 2009 at 7:29 PM, David Jencks <david_jencks@...>
>>> wrote:
>>>>
>>>> Hi Quintin,
>>>>
>>>> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>>>>
>>>>> Hey,
>>>>>
>>>>> I basically have a bunch of roles which should each be mapped to
>>>>> different combinations of a user's "GroupPrincipals". Something like
>>>>> this:
>>>>>
>>>>> <sec:role role-name="Lamp Room">
>>>>> <sec:principal
>>>>> class
>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>> name="Lamp Room"/>
>>>>> </sec:role>
>>>>> <sec:role role-name="VDS User">
>>>>> <sec:principal
>>>>> class
>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>> name="Lamp Room"/>
>>>>> </sec:role>
>>>>> <sec:role role-name="Personnel User">
>>>>> <sec:principal
>>>>> class
>>>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>>> name="Lamp Room"/>
>>>>> </sec:role>
>>>>>
>>>>> This means that named roles are all assigned to a user of group "Lamp
>>>>> Room".
>>>>>
>>>>> Though doing the following I don't see these "virtual roles", only the
>>>>> actual group.
>>>>> Subject subject = ContextManager.getCurrentCaller();
>>>>> Set<Principal> principals = subject.getPrincipals();
>>>>
>>>> roles are just names, not principals, so there's no way you'll see them
>>>> in
>>>> the Subject. Here's how it works, in PolicyContextGeneric:
>>>>
>>>> 1. the principal-role map specified above is fed in.
>>>> 2. the role-permission map specified by the DD or annotations is fed in
>>>> 3. these are combined to form a principal-permission map as the app
>>>> starts
>>>> up
>>>> 4. when you test a permission (either through container access control
>>>> or an
>>>> isUserInRole/isCallerInRole call) we run through the Subject's
>>>> principals,
>>>> get the PermissionCollection for that principal, and see if it implies
>>>> the
>>>> permission desired.
>>>>
>>>> One thing to note about this is that geronimo needs to know about the
>>>> role
>>>> and permission you're going to check. So the role has to be declared
>>>> somewhere. I'm less sure about the role-ref permission...
>>>> for web apps there is an implicit role-ref permission set up mapping the
>>>> role to itself for any role without an explicit role-ref. I don't
>>>> recall
>>>> how ejbs work, I kinda think that you have to declare all the roles you
>>>> are
>>>> going to test with a role-ref.
>>>>
>>>>>
>>>>> I can see how this would be the case, though the following must
>>>>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>>>>> isCallerInRole("Lamp Room"). They all return false.
>>>>>
>>>>> If I have a method annotated with @RolesAllowed({"Personnel User"}),
>>>>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>>>>> InterfaceType typee) return TRUE.
>>>>> Though, GeronimoSecurityService.isCallerInRole(String role) returns
>>>>> FALSE when I query isCallerInRole("Personnel User").
>>>>
>>>> I think this might support my idea that you have to explicitly set up a
>>>> role-ref for any role you mean to test in an ejb.
>>>>>
>>>>> I assume somewhere the AccessControlContext isn't populated correctly?
>>>>> I'm not really sure how this should work, so if someone can tell me
>>>>> how this all fits together I can have a look.
>>>>>
>>>>
>>>> Let me know if the above doesn't answer your questions
>>>>
>>>> thanks
>>>> david jencks
>>>>
>>>>> Quintin Beukes
>>>>
>>>>
>>>
>
>

Re: Serious Problem with Roles

2009-11-16T12:37:14Z

On Nov 16, 2009, at 10:39 AM, Quintin Beukes wrote:

> Even if it means quite a bit of code. I seriously need a way to
> determine the roles. It's either this or a massive overhaul on our
> user/group/role system where the whole system is already
> standing at 80000 lines of code. Changing the auth structure at this
> point would postpone the release too much.
>
> This is the last thing standing between me and a phase 1 release. Any
> suggestions would thus be greatly appreciated.

I've also wanted a

Collection<String> getUserRoles()

method but there isn't one. About the only thing you can do is

List<String> allRoles = //hard-code or read from a property file???
List<String> userRoles = new ArrayList<String>();
for (String role: allRoles) {
if (context.isUserInRole(role)) {
userRoles.add(role);
}
}

I'm curious why you need this much information for this kind of
partially app managed security. Maybe there's another way to approach
this.

One possibility is to add more container managed security -- a whole
additional kind of permission -- to your setup. You can write
security deployers to add more role-permission mappings to the
security system and then at runtime your app can test with
accessControlContext.implies(new MySpecialPermission(info)). This may
well not be enough info, but if this sounds remotely plausible let me
know....

hope this helps
david jencks

>
> Quintin Beukes
>
>
>
> On Mon, Nov 16, 2009 at 8:04 PM, Quintin Beukes
> <quintin@...> wrote:
>> Oh yes :<
>>
>> I was so focussed on my initial problem that I forgot about the
>> workings of isCallerInRole(). You have to do @DeclareRoles({..}) at
>> the class level. I actually do this everywhere I call
>> isCallerInRole(). It was just in this case where I'm trying to
>> determine the call's roles. The subject wasn't working (I now know
>> it's obvious, as a role isn't a principal), so I tried to do
>> isCallerInRole() without using it properly.
>>
>> I have a big problem though.
>>
>> Is there any way at all to get a list of roles for a user as mapped
>> in
>> the deployment descriptor? Even if I have to query the Geronimo API.
>> Portability when it comes to security is really not a big issue for
>> me
>> as I feel JavaEE's security is vague in any case. Besides, where ever
>> I break portability I do so through interfaces and implementations
>> with some "container validation". So if someone following me tries to
>> port he'll get a "friendly" message stating he needs to make his own
>> implementation.
>>
>> Quintin Beukes
>>
>>
>>
>> On Mon, Nov 16, 2009 at 7:29 PM, David Jencks
>> <david_jencks@...> wrote:
>>> Hi Quintin,
>>>
>>> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>>>
>>>> Hey,
>>>>
>>>> I basically have a bunch of roles which should each be mapped to
>>>> different combinations of a user's "GroupPrincipals". Something
>>>> like
>>>> this:
>>>>
>>>> <sec:role role-name="Lamp Room">
>>>> <sec:principal
>>>> class
>>>> =
>>>> "org
>>>> .apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>> name="Lamp Room"/>
>>>> </sec:role>
>>>> <sec:role role-name="VDS User">
>>>> <sec:principal
>>>> class
>>>> =
>>>> "org
>>>> .apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>> name="Lamp Room"/>
>>>> </sec:role>
>>>> <sec:role role-name="Personnel User">
>>>> <sec:principal
>>>> class
>>>> =
>>>> "org
>>>> .apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>>> name="Lamp Room"/>
>>>> </sec:role>
>>>>
>>>> This means that named roles are all assigned to a user of group
>>>> "Lamp
>>>> Room".
>>>>
>>>> Though doing the following I don't see these "virtual roles",
>>>> only the
>>>> actual group.
>>>> Subject subject = ContextManager.getCurrentCaller();
>>>> Set<Principal> principals = subject.getPrincipals();
>>>
>>> roles are just names, not principals, so there's no way you'll see
>>> them in
>>> the Subject. Here's how it works, in PolicyContextGeneric:
>>>
>>> 1. the principal-role map specified above is fed in.
>>> 2. the role-permission map specified by the DD or annotations is
>>> fed in
>>> 3. these are combined to form a principal-permission map as the
>>> app starts
>>> up
>>> 4. when you test a permission (either through container access
>>> control or an
>>> isUserInRole/isCallerInRole call) we run through the Subject's
>>> principals,
>>> get the PermissionCollection for that principal, and see if it
>>> implies the
>>> permission desired.
>>>
>>> One thing to note about this is that geronimo needs to know about
>>> the role
>>> and permission you're going to check. So the role has to be
>>> declared
>>> somewhere. I'm less sure about the role-ref permission...
>>> for web apps there is an implicit role-ref permission set up
>>> mapping the
>>> role to itself for any role without an explicit role-ref. I don't
>>> recall
>>> how ejbs work, I kinda think that you have to declare all the
>>> roles you are
>>> going to test with a role-ref.
>>>
>>>>
>>>> I can see how this would be the case, though the following must
>>>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>>>> isCallerInRole("Lamp Room"). They all return false.
>>>>
>>>> If I have a method annotated with @RolesAllowed({"Personnel
>>>> User"}),
>>>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>>>> InterfaceType typee) return TRUE.
>>>> Though, GeronimoSecurityService.isCallerInRole(String role) returns
>>>> FALSE when I query isCallerInRole("Personnel User").
>>>
>>> I think this might support my idea that you have to explicitly set
>>> up a
>>> role-ref for any role you mean to test in an ejb.
>>>>
>>>> I assume somewhere the AccessControlContext isn't populated
>>>> correctly?
>>>> I'm not really sure how this should work, so if someone can tell me
>>>> how this all fits together I can have a look.
>>>>
>>>
>>> Let me know if the above doesn't answer your questions
>>>
>>> thanks
>>> david jencks
>>>
>>>> Quintin Beukes
>>>
>>>
>>

Re: Serious Problem with Roles

2009-11-16T10:39:58Z

Even if it means quite a bit of code. I seriously need a way to
determine the roles. It's either this or a massive overhaul on our
user/group/role system where the whole system is already
standing at 80000 lines of code. Changing the auth structure at this
point would postpone the release too much.

This is the last thing standing between me and a phase 1 release. Any
suggestions would thus be greatly appreciated.

Quintin Beukes

On Mon, Nov 16, 2009 at 8:04 PM, Quintin Beukes <quintin@...> wrote:

> Oh yes :<
>
> I was so focussed on my initial problem that I forgot about the
> workings of isCallerInRole(). You have to do @DeclareRoles({..}) at
> the class level. I actually do this everywhere I call
> isCallerInRole(). It was just in this case where I'm trying to
> determine the call's roles. The subject wasn't working (I now know
> it's obvious, as a role isn't a principal), so I tried to do
> isCallerInRole() without using it properly.
>
> I have a big problem though.
>
> Is there any way at all to get a list of roles for a user as mapped in
> the deployment descriptor? Even if I have to query the Geronimo API.
> Portability when it comes to security is really not a big issue for me
> as I feel JavaEE's security is vague in any case. Besides, where ever
> I break portability I do so through interfaces and implementations
> with some "container validation". So if someone following me tries to
> port he'll get a "friendly" message stating he needs to make his own
> implementation.
>
> Quintin Beukes
>
>
>
> On Mon, Nov 16, 2009 at 7:29 PM, David Jencks <david_jencks@...> wrote:
>> Hi Quintin,
>>
>> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>>
>>> Hey,
>>>
>>> I basically have a bunch of roles which should each be mapped to
>>> different combinations of a user's "GroupPrincipals". Something like
>>> this:
>>>
>>> <sec:role role-name="Lamp Room">
>>> <sec:principal
>>> class
>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>> name="Lamp Room"/>
>>> </sec:role>
>>> <sec:role role-name="VDS User">
>>> <sec:principal
>>> class
>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>> name="Lamp Room"/>
>>> </sec:role>
>>> <sec:role role-name="Personnel User">
>>> <sec:principal
>>> class
>>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>>> name="Lamp Room"/>
>>> </sec:role>
>>>
>>> This means that named roles are all assigned to a user of group "Lamp
>>> Room".
>>>
>>> Though doing the following I don't see these "virtual roles", only the
>>> actual group.
>>> Subject subject = ContextManager.getCurrentCaller();
>>> Set<Principal> principals = subject.getPrincipals();
>>
>> roles are just names, not principals, so there's no way you'll see them in
>> the Subject. Here's how it works, in PolicyContextGeneric:
>>
>> 1. the principal-role map specified above is fed in.
>> 2. the role-permission map specified by the DD or annotations is fed in
>> 3. these are combined to form a principal-permission map as the app starts
>> up
>> 4. when you test a permission (either through container access control or an
>> isUserInRole/isCallerInRole call) we run through the Subject's principals,
>> get the PermissionCollection for that principal, and see if it implies the
>> permission desired.
>>
>> One thing to note about this is that geronimo needs to know about the role
>> and permission you're going to check. So the role has to be declared
>> somewhere. I'm less sure about the role-ref permission...
>> for web apps there is an implicit role-ref permission set up mapping the
>> role to itself for any role without an explicit role-ref. I don't recall
>> how ejbs work, I kinda think that you have to declare all the roles you are
>> going to test with a role-ref.
>>
>>>
>>> I can see how this would be the case, though the following must
>>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>>> isCallerInRole("Lamp Room"). They all return false.
>>>
>>> If I have a method annotated with @RolesAllowed({"Personnel User"}),
>>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>>> InterfaceType typee) return TRUE.
>>> Though, GeronimoSecurityService.isCallerInRole(String role) returns
>>> FALSE when I query isCallerInRole("Personnel User").
>>
>> I think this might support my idea that you have to explicitly set up a
>> role-ref for any role you mean to test in an ejb.
>>>
>>> I assume somewhere the AccessControlContext isn't populated correctly?
>>> I'm not really sure how this should work, so if someone can tell me
>>> how this all fits together I can have a look.
>>>
>>
>> Let me know if the above doesn't answer your questions
>>
>> thanks
>> david jencks
>>
>>> Quintin Beukes
>>
>>
>

Re: Serious Problem with Roles

2009-11-16T10:04:26Z

Oh yes :<

I was so focussed on my initial problem that I forgot about the
workings of isCallerInRole(). You have to do @DeclareRoles({..}) at
the class level. I actually do this everywhere I call
isCallerInRole(). It was just in this case where I'm trying to
determine the call's roles. The subject wasn't working (I now know
it's obvious, as a role isn't a principal), so I tried to do
isCallerInRole() without using it properly.

I have a big problem though.

Is there any way at all to get a list of roles for a user as mapped in
the deployment descriptor? Even if I have to query the Geronimo API.
Portability when it comes to security is really not a big issue for me
as I feel JavaEE's security is vague in any case. Besides, where ever
I break portability I do so through interfaces and implementations
with some "container validation". So if someone following me tries to
port he'll get a "friendly" message stating he needs to make his own
implementation.

Quintin Beukes

On Mon, Nov 16, 2009 at 7:29 PM, David Jencks <david_jencks@...> wrote:

> Hi Quintin,
>
> On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:
>
>> Hey,
>>
>> I basically have a bunch of roles which should each be mapped to
>> different combinations of a user's "GroupPrincipals". Something like
>> this:
>>
>> <sec:role role-name="Lamp Room">
>> <sec:principal
>> class
>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>> name="Lamp Room"/>
>> </sec:role>
>> <sec:role role-name="VDS User">
>> <sec:principal
>> class
>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>> name="Lamp Room"/>
>> </sec:role>
>> <sec:role role-name="Personnel User">
>> <sec:principal
>> class
>> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
>> name="Lamp Room"/>
>> </sec:role>
>>
>> This means that named roles are all assigned to a user of group "Lamp
>> Room".
>>
>> Though doing the following I don't see these "virtual roles", only the
>> actual group.
>> Subject subject = ContextManager.getCurrentCaller();
>> Set<Principal> principals = subject.getPrincipals();
>
> roles are just names, not principals, so there's no way you'll see them in
> the Subject. Here's how it works, in PolicyContextGeneric:
>
> 1. the principal-role map specified above is fed in.
> 2. the role-permission map specified by the DD or annotations is fed in
> 3. these are combined to form a principal-permission map as the app starts
> up
> 4. when you test a permission (either through container access control or an
> isUserInRole/isCallerInRole call) we run through the Subject's principals,
> get the PermissionCollection for that principal, and see if it implies the
> permission desired.
>
> One thing to note about this is that geronimo needs to know about the role
> and permission you're going to check. So the role has to be declared
> somewhere. I'm less sure about the role-ref permission...
> for web apps there is an implicit role-ref permission set up mapping the
> role to itself for any role without an explicit role-ref. I don't recall
> how ejbs work, I kinda think that you have to declare all the roles you are
> going to test with a role-ref.
>
>>
>> I can see how this would be the case, though the following must
>> definitely work: isCallerInRole("Personnel Admin") or EVEN
>> isCallerInRole("Lamp Room"). They all return false.
>>
>> If I have a method annotated with @RolesAllowed({"Personnel User"}),
>> then GeronimoSecurityService.isCallerAuthorized(Method method,
>> InterfaceType typee) return TRUE.
>> Though, GeronimoSecurityService.isCallerInRole(String role) returns
>> FALSE when I query isCallerInRole("Personnel User").
>
> I think this might support my idea that you have to explicitly set up a
> role-ref for any role you mean to test in an ejb.
>>
>> I assume somewhere the AccessControlContext isn't populated correctly?
>> I'm not really sure how this should work, so if someone can tell me
>> how this all fits together I can have a look.
>>
>
> Let me know if the above doesn't answer your questions
>
> thanks
> david jencks
>
>> Quintin Beukes
>
>

Re: JNDI lookup fails with Hibernate + application-scoped datasource

2009-11-16T09:56:20Z

On Nov 15, 2009, at 8:37 PM, Bevon wrote:

>
> Hi David,
> Thanks for your prompt reply. I tried digging into what the actual
> JNDI
> name was for the data source as you suggested and also went with the
> standard Geronimo JNDI as well (as opposed to the EJB JNDI). Here’s
> what I
> found:
>
> In both the Hibernate-JPA and Hibernate-Core case, the data source
> showed
> (in the Geronimo console’s JNDI Viewer) as:
> jca:/default/Psop_EAR50_Test/JCAManagedConnectionFactory/jdbc/psop/
> derbyDs1
>
> The fact that it's the same in both cases makes sense, since I'm
> declaring
> the data source at the application level and it doesn't change based
> on what
> EJB module I'm using. If I look at the Database Pools view in the
> console,
> I see my data source with "jdbc/psop/derbyDs1" as its name and
> deployed as
> "default/Psop_EAR_50_Test/1.0/car". Again, the same for both cases
> and as
> expected.
>
> Based on what you stated earlier, in the Hibernate-JPA case, Geronimo
> doesn't use JNDI, it just uses the name to lookup the data source.
> And in
> the Hibernate-Core case, Hibernate uses JNDI to do the lookup.
>
> I guess my next question is -- is there a way to provide a "better"
> JNDI
> name for a data source in Geronimo? I'd think maybe in the
> application
> metadata somwhere (application.xml, geronimo-application.xml or the
> vendor-specific deployment plan for the database pool). The reason
> I ask
> is:
> 1) The JNDI name is... unwieldy and non-obvious (ie. it's not
> obvious that
> "jdbc/psop/derbyDs1" is registered in JNDI as "jca:/default/...." and
> 2) It contains the EAR name in it, which I'd rather not have
> hardcoded into
> my EJB module's metadata (for ease of portability reasons).

I am a definite opponent of using global jndi for anything partly for
these kind or reasons. In a global jndi name you need a lot of
context info to assure that there won't be naming collisions when you
deploy 57 datasources named "myDS" for your 114 different independent
apps. That's why the ear name gets into the global jndi name, and why
it will stay there.

That being said you can modify the global jndi name format with a
template in var/config/config-substitutions.properties. I done't
advise it however.

I would try to declare a resource-ref in each of your ejb jars and
look up the java:comp/env/<res-ref-name> string in hibernate. This
will work as long as all calls into hibernate come from javaee
components such as ejbs (or on threads whose call stack goes through
such a component). This has a little more configuration but doesn't
need the context info you are objecting to in the global name.

hope this helps
david jencks

>
> In any case, changing the data source JNDI name in Hibernate
> configuration
> file gets around the publishing errors:
> hibernate.cfg.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
> Configuration DTD 3.0//EN"
> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
> <hibernate-configuration>
> <session-factory name="jdbc/psop/hibernateSf1">
>
> 
> <property
> name="hibernate.connection.datasource">jca:/default/Psop_EAR50_Test/
> JCAManagedConnectionFactory/jdbc/psop/derbyDs1</property>
>
> 
> <property
> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .manager_lookup_class
> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
> property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .factory_class">org.hibernate.transaction.JTATransactionFactory</
> property>
>
> 
> <property name="hibernate.show_sql">true</property>
> <property name="hibernate.format_sql">true</property>
>
> 
> <mapping
> resource="META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml"/>
> </session-factory>
> </hibernate-configuration>
>
>
> Thanks in advance,
> Bevon
>
>
>
>
> djencks wrote:
>>
>> Hi Bevon,
>>
>> I haven't looked through all the files you post but want to give a
>> couple hints, maybe you can easily track down what is going on.
>>
>> In Geronimo, the jta-datasource and non-jta-datasource values don't
>> refer to anything in jndi, they basically look up components
>> registered in the geronimo kernel. The JPA architecture has the
>> container (geronimo's jpa support) setting up an object that includes
>> these datasources and the rest of the info from the persistence.xml,
>> suitably resolved. So, you don't need to declare any resource-refs
>> in
>> your ejb jar anywhere to use jpa.
>>
>> For non-jpa hibernate, IIUC your explanation, jndi is really used to
>> find the datasource(s). I'm not clear on exactly what is getting
>> looked up.... I strongly advise finding out. I also suggest using
>> the
>> standard geronimo jndi rather than the openejb jndi context which is
>> unlikely to have any datasources in it since it is for looking up
>> ejbs. I'd hope that if you _don't_ set the hibernate property it
>> would just use
>> new InitialContext() which ought to work.
>>
>> Finally, hibernate might be trying to look up a java:comp/env jndi
>> name defined by a resource ref in the ejb jar or some completely
>> specified string for a global jndi name. In the latter case, you'll
>> want to check the geronimo.log to make sure you know exactly what the
>> global jndi name for your datasource actually is.... it gets logged
>> as
>> the datasource starts.
>>
>> hope this helps, and if you want to update our docs when you get it
>> working that would be great!
>>
>> thanks
>> david jencks
>>
>> On Nov 14, 2009, at 11:59 AM, Bevon wrote:
>>
>>>
>>> First, my apologies in advance is this should be posted on a
>>> Hibernate board.
>>> But this seems more of a configuration issue specific to Geronimo
>>> so...
>>>
>>> Geronimo: v2.1.4
>>> Hibernate core: v3.3.2
>>> Derby Network Server: v10.4.2
>>>
>>> I was able to get Hibernate working as my JPA provider (instead of
>>> OpenJPA)
>>> for my EJB3 module. However, as an academic/learning exercise, I
>>> have been
>>> trying to get Hibernate core working as my persistence layer for my
>>> EJB3
>>> module. The problem I'm seeing is that during the Hibernate
>>> Configuration.buildSessionFactory() call, a JNDI exception is thrown
>>> stating
>>> that the datasource could not be found.
>>>
>>>
>>> I have an application-scoped managed datasource declared for my
>>> EAR as
>>> follows:
>>> application.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns="http://java.sun.com/xml/ns/javaee"
>>>
>>> xmlns:application="http://java.sun.com/xml/ns/javaee/
>>> application_5.xsd"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>>> http://java.sun.com/xml/ns/javaee/application_5.xsd"
>>> id="Application_ID"
>>> version="5">
>>> <display-name>PsopEAR5_Test</display-name>
>>> <module>
>>> <connector>Derby/tranql-connector-derby-client-local-1.4.rar</
>>> connector>
>>> </module>
>>> <module>
>>> <web>
>>> <web-uri>Psop_Servlet25_Jsp21.war</web-uri>
>>> <context-root>Psop_Servlet25_Jsp21</context-root>
>>> </web>
>>> </module>
>>> <module>
>>> <ejb>Psop_Ejb30_Hibernate33.jar</ejb>
>>> </module>
>>> </application>
>>>
>>>
>>> geronimo-application.xml:
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <app:application
>>> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
>>>
>>> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
>>> "
>>>
>>> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
>>>
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
>>>
>>> xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
>>> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2
>>> "
>>> xmlns:pers="http://java.sun.com/xml/ns/persistence"
>>> xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1
>>> "
>>> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0
>>> "
>>>
>>> xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
>>> application-name="PsopEAR5_Test">
>>> <dep:environment>
>>> <dep:moduleId>
>>> <dep:groupId>default</dep:groupId>
>>> <dep:artifactId>PsopEAR5_Test</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>car</dep:type>
>>> </dep:moduleId>
>>> <dep:dependencies />
>>> </dep:environment>
>>> <app:module>
>>> 
>>>
>>> <app:connector>Derby/tranql-connector-derby-client-local-1.4.rar</
>>> app:connector>
>>>
>>> 
>>> <app:alt-dd>Derby/derby-network-server-plan.xml</app:alt-dd>
>>> </app:module>
>>> </app:application>
>>>
>>>
>>> derby-network-server-plan.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/
>>> connector-1.2">
>>> <dep:environment
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
>>> <dep:moduleId>
>>> <dep:groupId>console.dbpool</dep:groupId>
>>> <dep:artifactId>jdbc_psop_derbyDs1</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>rar</dep:type>
>>> </dep:moduleId>
>>> <dep:dependencies>
>>> <dep:dependency>
>>> <dep:groupId>org.apache.geronimo.configs</dep:groupId>
>>> <dep:artifactId>system-database</dep:artifactId>
>>> <dep:version>2.1.4</dep:version>
>>> <dep:type>car</dep:type>
>>> </dep:dependency>
>>> </dep:dependencies>
>>> </dep:environment>
>>> <resourceadapter>
>>> <outbound-resourceadapter>
>>> <connection-definition>
>>>
>>> <connectionfactory-interface>javax.sql.DataSource</
>>> connectionfactory-
>>> interface>
>>> <connectiondefinition-instance>
>>> <name>jdbc/psop/derbyDs1</name>
>>> <config-property-setting
>>> name="DatabaseName">E:\PSOP\Databases\Derby\PSOP_DATABASE</config-
>>> property-setting>
>>> <config-property-setting
>>> name="Password">app</config-property-setting>
>>> <config-property-setting
>>> name="UserName">app</config-property-setting>
>>> <config-property-setting name="LoginTimeout"/>
>>> <connectionmanager>
>>> <local-transaction/>
>>> <single-pool>
>>> <max-size>10</max-size>
>>> <min-size>0</min-size>
>>> <match-one/>
>>> </single-pool>
>>> </connectionmanager>
>>> </connectiondefinition-instance>
>>> </connection-definition>
>>> </outbound-resourceadapter>
>>> </resourceadapter>
>>> </connector>
>>>
>>>
>>> My EJB3 module metadata is as follows:
>>> ejb-jar.xml (essentially empty since I'm using EJB3 annotations):
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns="http://java.sun.com/xml/ns/javaee"
>>> xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>>> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>>> version="3.0">
>>> <description>PSOP model implemented with EJB 3.0. PSOP
>>> persistence
>>> implemented with Hibernate 3.3 (native).</description>
>>> <display-name>Psop_Ejb30_Hibernate33</display-name>
>>> </ejb-jar>
>>>
>>>
>>> openejb-jar.xml (all of the dependency jars were copied into the
>>> Geronimo
>>> repository):
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> <openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-
>>> jar-2.2"
>>> xmlns:naming="http://geronimo.apache.org/xml/ns/
>>> naming-1.2"
>>> xmlns:sec="http://geronimo.apache.org/xml/ns/
>>> security-2.0"
>>> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2
>>> ">
>>> <sys:environment>
>>> <sys:moduleId>
>>> <sys:groupId>default</sys:groupId>
>>> <sys:artifactId>Psop_Ejb30_Hibernate33</sys:artifactId>
>>> <sys:version>1.0</sys:version>
>>> <sys:type>car</sys:type>
>>> </sys:moduleId>
>>> <sys:dependencies>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>core</sys:artifactId>
>>> <sys:version>3.3</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>antlr</sys:artifactId>
>>> <sys:version>2.7.6</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>commons-collections</sys:artifactId>
>>> <sys:version>3.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>dom4j</sys:artifactId>
>>> <sys:version>1.6.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>javassist</sys:artifactId>
>>> <sys:version>3.9.0.GA</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>jta</sys:artifactId>
>>> <sys:version>1.1</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>psop_hibernate</sys:groupId>
>>> <sys:artifactId>GeronimoTransactionManager</
>>> sys:artifactId>
>>> <sys:version>1.0</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> <sys:dependency>
>>> <sys:groupId>org.slf4j</sys:groupId>
>>> <sys:artifactId>slf4j-api</sys:artifactId>
>>> <sys:version>1.4.3</sys:version>
>>> <sys:type>jar</sys:type>
>>> </sys:dependency>
>>> </sys:dependencies>
>>> </sys:environment>
>>> </openejb-jar>
>>>
>>>
>>> hibernate.cfg.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
>>> Configuration DTD 3.0//EN"
>>> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
>>> <hibernate-configuration>
>>> <session-factory name="jdbc/psop/hibernateSf1">
>>>
>>> 
>>> <property
>>> name="hibernate.connection.datasource">jdbc/psop/derbyDs1</property>
>>>
>>> 
>>> <property
>>> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</
>>> property>
>>>
>>> 
>>> <property
>>> name
>>> =
>>> "hibernate
>>> .transaction
>>> .manager_lookup_class
>>> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
>>> property>
>>>
>>> 
>>> <property
>>> name
>>> =
>>> "hibernate
>>> .transaction
>>> .factory_class">org.hibernate.transaction.JTATransactionFactory</
>>> property>
>>>
>>> 
>>> <property name="hibernate.show_sql">true</property>
>>> <property name="hibernate.format_sql">true</property>
>>>
>>> 
>>> <mapping
>>> resource="META-INF/mappings/com/psop/model/hibernate/
>>> PlayerHibernateEntity.hbm.xml"/>
>>> </session-factory>
>>> </hibernate-configuration>
>>>
>>>
>>>
>>>
>>> Here is the code that tries to build the SessionFactory:
>>> Configuration hibernateConfiguration = new
>>> Configuration().configure(
>>> "/META-INF/hibernate.cfg.xml" );
>>> hibernateConfiguration.setProperty(
>>> org.hibernate.cfg.Environment.JNDI_CLASS,
>>> "org.apache.openejb.client.RemoteInitialContextFactory" ) );
>>> hibernateConfiguration
>>> .setProperty( org.hibernate.cfg.Environment.JNDI_URL,
>>> "ejbd://localhost:4201" );
>>>
>>> sessionFactorySingleInstance =
>>> hibernateConfiguration.buildSessionFactory();
>>> // throws JNDI exception
>>> // as a test, if I do a JNDI lookup on "jdbc/psop/derbyDs1", I get
>>> the same
>>> exception
>>>
>>>
>>> Here is the exception that occurs during publishing (I'm using
>>> Eclipse
>>> Ganymede with GEP):
>>> javax.naming.NameNotFoundException: /jdbc/psop/derbyDs1 does not
>>> exist in
>>> the system. Check that the app was successfully deployed.
>>> at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:
>>> 277)
>>> at javax.naming.InitialContext.lookup(Unknown Source)
>>> at
>>> com
>>> .psop
>>> .model
>>> .ejb
>>> .config
>>> .EjbHibernateModelConfig
>>> .initializeSessionFactory(EjbHibernateModelConfig.java:234)
>>> at
>>> com
>>> .psop
>>> .model
>>> .ejb
>>> .config
>>> .EjbHibernateModelConfig
>>> .initializeModel(EjbHibernateModelConfig.java:292)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at
>>> org.apache.openejb.core.interceptor.ReflectionInvocationContext
>>> $Invocation.invoke(ReflectionInvocationContext.java:158)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core
>>> .interceptor
>>> .ReflectionInvocationContext
>>> .proceed(ReflectionInvocationContext.java:141)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
>>> 210)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
>>> 188)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .core.stateless.StatelessContainer.invoke(StatelessContainer.java:
>>> 165)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .server
>>> .ejbd
>>> .EjbRequestHandler
>>> .doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238)
>>> at
>>> org
>>> .apache
>>> .openejb
>>> .server
>>> .ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:
>>> 129)
>>> at
>>> org
>>> .apache
>>> .openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164)
>>> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
>>> 122)
>>> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
>>> 84)
>>> at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:
>>> 60)
>>> at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:78)
>>> at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:
>>> 101)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>>> Source)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>> Source)
>>> at java.lang.Thread.run(Unknown Source)
>>>
>>>
>>>
>>> Geronimo log (I don't see any binding of the datasource to JNDI
>>> here):
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default
>>> Stateless Container, type=Container, provider-id=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default
>>> Stateful Container, type=Container, provider-id=Default Stateful
>>> Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default BMP
>>> Container, type=Container, provider-id=Default BMP Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring
>>> Service(id=Default CMP
>>> Container, type=Container, provider-id=Default CMP Container)
>>> 2009-11-14 14:30:06,903 INFO [config] Configuring app:
>>> default/PsopEAR5_Test/1.0/car
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateFinder:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateDestroyer:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateCreator:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator)
>>> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
>>> ejb/psop/ejbHibernateModelConfig:
>>> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig)
>>> 2009-11-14 14:30:06,919 INFO [config] Loaded Module:
>>> default/PsopEAR5_Test/1.0/car
>>> 2009-11-14 14:30:07,810 INFO [KernelContextGBean] bound gbean
>>> default/PsopEAR5_Test/1.0/car?J2EEApplication=default/PsopEAR5_Test/
>>> 1.0/car,JCAConnectionFactory=jdbc/psop/derbyDs1,JCAResource=Derby/
>>> tranql-connector-derby-client-local-1.4.rar,ResourceAdapter=Derby/
>>> tranql-connector-derby-client-
>>> local-1.4.rar,ResourceAdapterModule=Derby/tranql-connector-derby-
>>> client-local-1.4.rar,j2eeType=JCAManagedConnectionFactory,name=jdbc/
>>> psop/derbyDs1
>>> at name default/PsopEAR5_Test/JCAManagedConnectionFactory/jdbc/psop/
>>> derbyDs1
>>> 2009-11-14 14:30:07,810 INFO [startup] Assembling app: C:\Documents
>>> and
>>> Settings\Bevon Palod\Local
>>> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateFinderRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateDestroyerRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateCreatorRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator)
>>> 2009-11-14 14:30:07,872 INFO [startup]
>>> Jndi(name=ejb/psop/ejbHibernateModelConfigRemote) -->
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateFinder,
>>> ejb-name=ejb/psop/ejbHibernateFinder, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateDestroyer,
>>> ejb-name=ejb/psop/ejbHibernateDestroyer, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateCreator,
>>> ejb-name=ejb/psop/ejbHibernateCreator, container=Default Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Created
>>> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
>>> ejbHibernateModelConfig,
>>> ejb-name=ejb/psop/ejbHibernateModelConfig, container=Default
>>> Stateless
>>> Container)
>>> 2009-11-14 14:30:07,872 INFO [startup] Deployed
>>> Application(path=C:\Documents and Settings\Bevon Palod\Local
>>> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar)
>>> 2009-11-14 14:30:08,013 INFO [OpenEJB] invoking method create on
>>> Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig
>>> 2009-11-14 14:30:08,013 INFO [OpenEJB] finished invoking method
>>> create
>>> 2009-11-14 14:30:08,013 INFO [Transaction] TX Required: Started
>>> transaction
>>> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>>> 2009-11-14 14:30:08,091 INFO [Environment] Hibernate 3.3.2.GA
>>> 2009-11-14 14:30:08,091 INFO [Environment] hibernate.properties not
>>> found
>>> 2009-11-14 14:30:08,106 INFO [Environment] Bytecode provider name :
>>> javassist
>>> 2009-11-14 14:30:08,122 INFO [Environment] using JDK 1.4
>>> java.sql.Timestamp
>>> handling
>>> 2009-11-14 14:30:08,356 INFO [Configuration] configuring from
>>> resource:
>>> /META-INF/hibernate.cfg.xml
>>> 2009-11-14 14:30:08,356 INFO [Configuration] Configuration
>>> resource:
>>> /META-INF/hibernate.cfg.xml
>>> 2009-11-14 14:30:08,497 INFO [Configuration] Reading mappings from
>>> resource
>>> : META-INF/mappings/com/psop/model/hibernate/
>>> PlayerHibernateEntity.hbm.xml
>>> 2009-11-14 14:30:08,606 INFO [HbmBinder] Mapping class:
>>> com.psop.model.hibernate.PlayerHibernateEntity -> PLAYERS
>>> 2009-11-14 14:30:08,685 INFO [Configuration] Configured
>>> SessionFactory:
>>> jdbc/psop/hibernateSf1
>>> 2009-11-14 14:30:08,685 INFO [Transaction] TX Required: Committing
>>> transaction
>>> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>>>
>>>
>>> I do not see this exception when I make use of Hibernate
>>> Annotations +
>>> EnitityManager and stick with JPA-only API/annotations in my code.
>>> In terms
>>> of configuration, the EAR metadata is exactly the same (save for
>>> swapping
>>> the EJB3 modules). The EJB3 module metadata has two differences:
>>> 1. I've got a persistence.xml instead of hibernate.cfg.xml.
>>> 2. I've added the Hibernate Annotations + EntityManager
>>> dependencies to my
>>> openejb-jar.xml (won't bother pasting it again here).
>>>
>>> persistence.xml:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <persistence xmlns="http://java.sun.com/xml/ns/persistence"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/
>>> persistence
>>> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
>>> version="1.0" >
>>> <persistence-unit name="Psop_Ejb30_Jpa10" transaction-type="JTA">
>>> <description>Hibernate v3.3 JPA provider</description>
>>> <provider>org.hibernate.ejb.HibernatePersistence</provider>
>>> <jta-data-source>jdbc/psop/derbyDs1</jta-data-source>
>>> <class>com.psop.model.jpa.PlayerJpaEntity</class>
>>> <properties>
>>> <property
>>> name="hibernate.transaction.manager_lookup_class"
>>> value="org.hibernate.transaction.GeronimoTransactionManagerLookup"/>
>>> <property name="hibernate.show_sql" value="true"/>
>>> <property name="hibernate.format_sql" value="true"/>
>>> <property name="hibernate.dialect"
>>> value="org.hibernate.dialect.DerbyDialect"/>
>>> </properties>
>>> </persistence-unit>
>>> </persistence>
>>>
>>>
>>> My best guess -- I'm doing something wrong or it's a faulty
>>> assumption that
>>> my datasource will automagically be registered in JNDI (as it is
>>> with JPA).
>>>
>>> Please bear with me as I'm a newbie. I've been banging on Geronimo
>>> for just
>>> about a month and have been at Hibernate for maybe a week. If
>>> someone could
>>> shed some light on this problem or perhaps point me to some
>>> documentation
>>> (yes, I've read the Hibernate to Geronimo migration docs, yes, I've
>>> googled,
>>> yes, I did a keyword search on this forum for "Hibernate
>>> datasource").
>>>
>>> Many thanks in advance!!!
>>> Bevon
>>> --
>>> View this message in context:
>>> http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26353366.html
>>> Sent from the Apache Geronimo - Users mailing list archive at
>>> Nabble.com.
>>>
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26366792.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>

Re: Serious Problem with Roles

2009-11-16T09:29:51Z

Hi Quintin,

On Nov 16, 2009, at 8:41 AM, Quintin Beukes wrote:

> Hey,
>
> I basically have a bunch of roles which should each be mapped to
> different combinations of a user's "GroupPrincipals". Something like
> this:
>
> <sec:role role-name="Lamp Room">
> <sec:principal
> class
> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
> name="Lamp Room"/>
> </sec:role>
> <sec:role role-name="VDS User">
> <sec:principal
> class
> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
> name="Lamp Room"/>
> </sec:role>
> <sec:role role-name="Personnel User">
> <sec:principal
> class
> ="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
> name="Lamp Room"/>
> </sec:role>
>
> This means that named roles are all assigned to a user of group
> "Lamp Room".
>
> Though doing the following I don't see these "virtual roles", only the
> actual group.
> Subject subject = ContextManager.getCurrentCaller();
> Set<Principal> principals = subject.getPrincipals();

roles are just names, not principals, so there's no way you'll see
them in the Subject. Here's how it works, in PolicyContextGeneric:

1. the principal-role map specified above is fed in.
2. the role-permission map specified by the DD or annotations is fed in
3. these are combined to form a principal-permission map as the app
starts up
4. when you test a permission (either through container access control
or an isUserInRole/isCallerInRole call) we run through the Subject's
principals, get the PermissionCollection for that principal, and see
if it implies the permission desired.

One thing to note about this is that geronimo needs to know about the
role and permission you're going to check. So the role has to be
declared somewhere. I'm less sure about the role-ref permission...
for web apps there is an implicit role-ref permission set up mapping
the role to itself for any role without an explicit role-ref. I don't
recall how ejbs work, I kinda think that you have to declare all the
roles you are going to test with a role-ref.

>
> I can see how this would be the case, though the following must
> definitely work: isCallerInRole("Personnel Admin") or EVEN
> isCallerInRole("Lamp Room"). They all return false.
>
> If I have a method annotated with @RolesAllowed({"Personnel User"}),
> then GeronimoSecurityService.isCallerAuthorized(Method method,
> InterfaceType typee) return TRUE.
> Though, GeronimoSecurityService.isCallerInRole(String role) returns
> FALSE when I query isCallerInRole("Personnel User").

I think this might support my idea that you have to explicitly set up
a role-ref for any role you mean to test in an ejb.
>
> I assume somewhere the AccessControlContext isn't populated correctly?
> I'm not really sure how this should work, so if someone can tell me
> how this all fits together I can have a look.
>

Let me know if the above doesn't answer your questions

thanks
david jencks

> Quintin Beukes

Serious Problem with Roles

2009-11-16T08:41:33Z

Hey,

I basically have a bunch of roles which should each be mapped to
different combinations of a user's "GroupPrincipals". Something like
this:

<sec:role role-name="Lamp Room">
<sec:principal
class="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
name="Lamp Room"/>
</sec:role>
<sec:role role-name="VDS User">
<sec:principal
class="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
name="Lamp Room"/>
</sec:role>
<sec:role role-name="Personnel User">
<sec:principal
class="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"
name="Lamp Room"/>
</sec:role>

This means that named roles are all assigned to a user of group "Lamp Room".

Though doing the following I don't see these "virtual roles", only the
actual group.
Subject subject = ContextManager.getCurrentCaller();
Set<Principal> principals = subject.getPrincipals();

I can see how this would be the case, though the following must
definitely work: isCallerInRole("Personnel Admin") or EVEN
isCallerInRole("Lamp Room"). They all return false.

If I have a method annotated with @RolesAllowed({"Personnel User"}),
then GeronimoSecurityService.isCallerAuthorized(Method method,
InterfaceType typee) return TRUE.
Though, GeronimoSecurityService.isCallerInRole(String role) returns
FALSE when I query isCallerInRole("Personnel User").

I assume somewhere the AccessControlContext isn't populated correctly?
I'm not really sure how this should work, so if someone can tell me
how this all fits together I can have a look.

Quintin Beukes

Re: Unsubscribe

2009-11-16T07:15:30Z

To unsubscribe, send an email to user-unsubscribe@....

--kevan

On Nov 14, 2009, at 8:28 PM, José Arcángel Salazar Delgado wrote:

>

Re: JNDI lookup fails with Hibernate + application-scoped datasource

2009-11-15T20:37:36Z

Hi David,
Thanks for your prompt reply. I tried digging into what the actual JNDI name was for the data source as you suggested and also went with the standard Geronimo JNDI as well (as opposed to the EJB JNDI). Here’s what I found:

In both the Hibernate-JPA and Hibernate-Core case, the data source showed (in the Geronimo console’s JNDI Viewer) as:
jca:/default/Psop_EAR50_Test/JCAManagedConnectionFactory/jdbc/psop/derbyDs1

The fact that it's the same in both cases makes sense, since I'm declaring the data source at the application level and it doesn't change based on what EJB module I'm using. If I look at the Database Pools view in the console, I see my data source with "jdbc/psop/derbyDs1" as its name and deployed as "default/Psop_EAR_50_Test/1.0/car". Again, the same for both cases and as expected.

Based on what you stated earlier, in the Hibernate-JPA case, Geronimo doesn't use JNDI, it just uses the name to lookup the data source. And in the Hibernate-Core case, Hibernate uses JNDI to do the lookup.

I guess my next question is -- is there a way to provide a "better" JNDI name for a data source in Geronimo? I'd think maybe in the application metadata somwhere (application.xml, geronimo-application.xml or the vendor-specific deployment plan for the database pool). The reason I ask is:
1) The JNDI name is... unwieldy and non-obvious (ie. it's not obvious that "jdbc/psop/derbyDs1" is registered in JNDI as "jca:/default/...." and
2) It contains the EAR name in it, which I'd rather not have hardcoded into my EJB module's metadata (for ease of portability reasons).

In any case, changing the data source JNDI name in Hibernate configuration file gets around the publishing errors:
hibernate.cfg.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory name="jdbc/psop/hibernateSf1">


<property name="hibernate.connection.datasource">jca:/default/Psop_EAR50_Test/JCAManagedConnectionFactory/jdbc/psop/derbyDs1</property>


<property name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>


<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.GeronimoTransactionManagerLookup</property>


<property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>


<property name="hibernate.show_sql">true</property>
<property name="hibernate.format_sql">true</property>


<mapping resource="META-INF/mappings/com/psop/model/hibernate/PlayerHibernateEntity.hbm.xml"/>
</session-factory>
</hibernate-configuration>

Thanks in advance,
Bevon

djencks wrote:

Hi Bevon,

I haven't looked through all the files you post but want to give a
couple hints, maybe you can easily track down what is going on.

In Geronimo, the jta-datasource and non-jta-datasource values don't
refer to anything in jndi, they basically look up components
registered in the geronimo kernel. The JPA architecture has the
container (geronimo's jpa support) setting up an object that includes
these datasources and the rest of the info from the persistence.xml,
suitably resolved. So, you don't need to declare any resource-refs in
your ejb jar anywhere to use jpa.

For non-jpa hibernate, IIUC your explanation, jndi is really used to
find the datasource(s). I'm not clear on exactly what is getting
looked up.... I strongly advise finding out. I also suggest using the
standard geronimo jndi rather than the openejb jndi context which is
unlikely to have any datasources in it since it is for looking up
ejbs. I'd hope that if you _don't_ set the hibernate property it
would just use
new InitialContext() which ought to work.

Finally, hibernate might be trying to look up a java:comp/env jndi
name defined by a resource ref in the ejb jar or some completely
specified string for a global jndi name. In the latter case, you'll
want to check the geronimo.log to make sure you know exactly what the
global jndi name for your datasource actually is.... it gets logged as
the datasource starts.

hope this helps, and if you want to update our docs when you get it
working that would be great!

thanks
david jencks

On Nov 14, 2009, at 11:59 AM, Bevon wrote:

>
> First, my apologies in advance is this should be posted on a
> Hibernate board.
> But this seems more of a configuration issue specific to Geronimo
> so...
>
> Geronimo: v2.1.4
> Hibernate core: v3.3.2
> Derby Network Server: v10.4.2
>
> I was able to get Hibernate working as my JPA provider (instead of
> OpenJPA)
> for my EJB3 module. However, as an academic/learning exercise, I
> have been
> trying to get Hibernate core working as my persistence layer for my
> EJB3
> module. The problem I'm seeing is that during the Hibernate
> Configuration.buildSessionFactory() call, a JNDI exception is thrown
> stating
> that the datasource could not be found.
>
>
> I have an application-scoped managed datasource declared for my EAR as
> follows:
> application.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://java.sun.com/xml/ns/javaee"
>
> xmlns:application="http://java.sun.com/xml/ns/javaee/
> application_5.xsd"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/application_5.xsd"
> id="Application_ID"
> version="5">
> <display-name>PsopEAR5_Test</display-name>
> <module>
> <connector>Derby/tranql-connector-derby-client-local-1.4.rar</
> connector>
> </module>
> <module>
> <web>
> <web-uri>Psop_Servlet25_Jsp21.war</web-uri>
> <context-root>Psop_Servlet25_Jsp21</context-root>
> </web>
> </module>
> <module>
> <ejb>Psop_Ejb30_Hibernate33.jar</ejb>
> </module>
> </application>
>
>
> geronimo-application.xml:
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <app:application
> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
>
> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
> "
>
> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
>
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
>
> xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2
> "
> xmlns:pers="http://java.sun.com/xml/ns/persistence"
> xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1
> "
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0
> "
>
> xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
> application-name="PsopEAR5_Test">
> <dep:environment>
> <dep:moduleId>
> <dep:groupId>default</dep:groupId>
> <dep:artifactId>PsopEAR5_Test</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>car</dep:type>
> </dep:moduleId>
> <dep:dependencies />
> </dep:environment>
> <app:module>
> 
>
> <app:connector>Derby/tranql-connector-derby-client-local-1.4.rar</
> app:connector>
>
> 
> <app:alt-dd>Derby/derby-network-server-plan.xml</app:alt-dd>
> </app:module>
> </app:application>
>
>
> derby-network-server-plan.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/
> connector-1.2">
> <dep:environment
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
> <dep:moduleId>
> <dep:groupId>console.dbpool</dep:groupId>
> <dep:artifactId>jdbc_psop_derbyDs1</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>rar</dep:type>
> </dep:moduleId>
> <dep:dependencies>
> <dep:dependency>
> <dep:groupId>org.apache.geronimo.configs</dep:groupId>
> <dep:artifactId>system-database</dep:artifactId>
> <dep:version>2.1.4</dep:version>
> <dep:type>car</dep:type>
> </dep:dependency>
> </dep:dependencies>
> </dep:environment>
> <resourceadapter>
> <outbound-resourceadapter>
> <connection-definition>
>
> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-
> interface>
> <connectiondefinition-instance>
> <name>jdbc/psop/derbyDs1</name>
> <config-property-setting
> name="DatabaseName">E:\PSOP\Databases\Derby\PSOP_DATABASE</config-
> property-setting>
> <config-property-setting
> name="Password">app</config-property-setting>
> <config-property-setting
> name="UserName">app</config-property-setting>
> <config-property-setting name="LoginTimeout"/>
> <connectionmanager>
> <local-transaction/>
> <single-pool>
> <max-size>10</max-size>
> <min-size>0</min-size>
> <match-one/>
> </single-pool>
> </connectionmanager>
> </connectiondefinition-instance>
> </connection-definition>
> </outbound-resourceadapter>
> </resourceadapter>
> </connector>
>
>
> My EJB3 module metadata is as follows:
> ejb-jar.xml (essentially empty since I'm using EJB3 annotations):
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
> version="3.0">
> <description>PSOP model implemented with EJB 3.0. PSOP persistence
> implemented with Hibernate 3.3 (native).</description>
> <display-name>Psop_Ejb30_Hibernate33</display-name>
> </ejb-jar>
>
>
> openejb-jar.xml (all of the dependency jars were copied into the
> Geronimo
> repository):
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:naming="http://geronimo.apache.org/xml/ns/
> naming-1.2"
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2
> ">
> <sys:environment>
> <sys:moduleId>
> <sys:groupId>default</sys:groupId>
> <sys:artifactId>Psop_Ejb30_Hibernate33</sys:artifactId>
> <sys:version>1.0</sys:version>
> <sys:type>car</sys:type>
> </sys:moduleId>
> <sys:dependencies>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>core</sys:artifactId>
> <sys:version>3.3</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>antlr</sys:artifactId>
> <sys:version>2.7.6</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>commons-collections</sys:artifactId>
> <sys:version>3.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>dom4j</sys:artifactId>
> <sys:version>1.6.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>javassist</sys:artifactId>
> <sys:version>3.9.0.GA</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>jta</sys:artifactId>
> <sys:version>1.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>GeronimoTransactionManager</
> sys:artifactId>
> <sys:version>1.0</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>org.slf4j</sys:groupId>
> <sys:artifactId>slf4j-api</sys:artifactId>
> <sys:version>1.4.3</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> </sys:dependencies>
> </sys:environment>
> </openejb-jar>
>
>
> hibernate.cfg.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
> Configuration DTD 3.0//EN"
> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
> <hibernate-configuration>
> <session-factory name="jdbc/psop/hibernateSf1">
>
> 
> <property
> name="hibernate.connection.datasource">jdbc/psop/derbyDs1</property>
>
> 
> <property
> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .manager_lookup_class
> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
> property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .factory_class">org.hibernate.transaction.JTATransactionFactory</
> property>
>
> 
> <property name="hibernate.show_sql">true</property>
> <property name="hibernate.format_sql">true</property>
>
> 
> <mapping
> resource="META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml"/>
> </session-factory>
> </hibernate-configuration>
>
>
>
>
> Here is the code that tries to build the SessionFactory:
> Configuration hibernateConfiguration = new Configuration().configure(
> "/META-INF/hibernate.cfg.xml" );
> hibernateConfiguration.setProperty(
> org.hibernate.cfg.Environment.JNDI_CLASS,
> "org.apache.openejb.client.RemoteInitialContextFactory" ) );
> hibernateConfiguration
> .setProperty( org.hibernate.cfg.Environment.JNDI_URL,
> "ejbd://localhost:4201" );
>
> sessionFactorySingleInstance =
> hibernateConfiguration.buildSessionFactory();
> // throws JNDI exception
> // as a test, if I do a JNDI lookup on "jdbc/psop/derbyDs1", I get
> the same
> exception
>
>
> Here is the exception that occurs during publishing (I'm using Eclipse
> Ganymede with GEP):
> javax.naming.NameNotFoundException: /jdbc/psop/derbyDs1 does not
> exist in
> the system. Check that the app was successfully deployed.
> at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:277)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> com
> .psop
> .model
> .ejb
> .config
> .EjbHibernateModelConfig
> .initializeSessionFactory(EjbHibernateModelConfig.java:234)
> at
> com
> .psop
> .model
> .ejb
> .config
> .EjbHibernateModelConfig
> .initializeModel(EjbHibernateModelConfig.java:292)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.openejb.core.interceptor.ReflectionInvocationContext
> $Invocation.invoke(ReflectionInvocationContext.java:158)
> at
> org
> .apache
> .openejb
> .core
> .interceptor
> .ReflectionInvocationContext
> .proceed(ReflectionInvocationContext.java:141)
> at
> org
> .apache
> .openejb
> .core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
> 210)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
> 188)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer.invoke(StatelessContainer.java:165)
> at
> org
> .apache
> .openejb
> .server
> .ejbd
> .EjbRequestHandler
> .doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238)
> at
> org
> .apache
> .openejb
> .server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:
> 129)
> at
> org
> .apache
> .openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164)
> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
> 122)
> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
> 84)
> at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:
> 60)
> at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:78)
> at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:101)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> Geronimo log (I don't see any binding of the datasource to JNDI here):
> 2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default
> Stateless Container, type=Container, provider-id=Default Stateless
> Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default
> Stateful Container, type=Container, provider-id=Default Stateful
> Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring
> Service(id=Default BMP
> Container, type=Container, provider-id=Default BMP Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring
> Service(id=Default CMP
> Container, type=Container, provider-id=Default CMP Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring app:
> default/PsopEAR5_Test/1.0/car
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateFinder:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateDestroyer:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateCreator:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateModelConfig:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig)
> 2009-11-14 14:30:06,919 INFO [config] Loaded Module:
> default/PsopEAR5_Test/1.0/car
> 2009-11-14 14:30:07,810 INFO [KernelContextGBean] bound gbean
> default/PsopEAR5_Test/1.0/car?J2EEApplication=default/PsopEAR5_Test/
> 1.0/car,JCAConnectionFactory=jdbc/psop/derbyDs1,JCAResource=Derby/
> tranql-connector-derby-client-local-1.4.rar,ResourceAdapter=Derby/
> tranql-connector-derby-client-
> local-1.4.rar,ResourceAdapterModule=Derby/tranql-connector-derby-
> client-local-1.4.rar,j2eeType=JCAManagedConnectionFactory,name=jdbc/
> psop/derbyDs1
> at name default/PsopEAR5_Test/JCAManagedConnectionFactory/jdbc/psop/
> derbyDs1
> 2009-11-14 14:30:07,810 INFO [startup] Assembling app: C:\Documents
> and
> Settings\Bevon Palod\Local
> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateFinderRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateDestroyerRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateCreatorRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateModelConfigRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder,
> ejb-name=ejb/psop/ejbHibernateFinder, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer,
> ejb-name=ejb/psop/ejbHibernateDestroyer, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator,
> ejb-name=ejb/psop/ejbHibernateCreator, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig,
> ejb-name=ejb/psop/ejbHibernateModelConfig, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Deployed
> Application(path=C:\Documents and Settings\Bevon Palod\Local
> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar)
> 2009-11-14 14:30:08,013 INFO [OpenEJB] invoking method create on
> Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig
> 2009-11-14 14:30:08,013 INFO [OpenEJB] finished invoking method
> create
> 2009-11-14 14:30:08,013 INFO [Transaction] TX Required: Started
> transaction
> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
> 2009-11-14 14:30:08,091 INFO [Environment] Hibernate 3.3.2.GA
> 2009-11-14 14:30:08,091 INFO [Environment] hibernate.properties not
> found
> 2009-11-14 14:30:08,106 INFO [Environment] Bytecode provider name :
> javassist
> 2009-11-14 14:30:08,122 INFO [Environment] using JDK 1.4
> java.sql.Timestamp
> handling
> 2009-11-14 14:30:08,356 INFO [Configuration] configuring from
> resource:
> /META-INF/hibernate.cfg.xml
> 2009-11-14 14:30:08,356 INFO [Configuration] Configuration resource:
> /META-INF/hibernate.cfg.xml
> 2009-11-14 14:30:08,497 INFO [Configuration] Reading mappings from
> resource
> : META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml
> 2009-11-14 14:30:08,606 INFO [HbmBinder] Mapping class:
> com.psop.model.hibernate.PlayerHibernateEntity -> PLAYERS
> 2009-11-14 14:30:08,685 INFO [Configuration] Configured
> SessionFactory:
> jdbc/psop/hibernateSf1
> 2009-11-14 14:30:08,685 INFO [Transaction] TX Required: Committing
> transaction
> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>
>
> I do not see this exception when I make use of Hibernate Annotations +
> EnitityManager and stick with JPA-only API/annotations in my code.
> In terms
> of configuration, the EAR metadata is exactly the same (save for
> swapping
> the EJB3 modules). The EJB3 module metadata has two differences:
> 1. I've got a persistence.xml instead of hibernate.cfg.xml.
> 2. I've added the Hibernate Annotations + EntityManager
> dependencies to my
> openejb-jar.xml (won't bother pasting it again here).
>
> persistence.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence xmlns="http://java.sun.com/xml/ns/persistence"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
> version="1.0" >
> <persistence-unit name="Psop_Ejb30_Jpa10" transaction-type="JTA">
> <description>Hibernate v3.3 JPA provider</description>
> <provider>org.hibernate.ejb.HibernatePersistence</provider>
> <jta-data-source>jdbc/psop/derbyDs1</jta-data-source>
> <class>com.psop.model.jpa.PlayerJpaEntity</class>
> <properties>
> <property name="hibernate.transaction.manager_lookup_class"
> value="org.hibernate.transaction.GeronimoTransactionManagerLookup"/>
> <property name="hibernate.show_sql" value="true"/>
> <property name="hibernate.format_sql" value="true"/>
> <property name="hibernate.dialect"
> value="org.hibernate.dialect.DerbyDialect"/>
> </properties>
> </persistence-unit>
> </persistence>
>
>
> My best guess -- I'm doing something wrong or it's a faulty
> assumption that
> my datasource will automagically be registered in JNDI (as it is
> with JPA).
>
> Please bear with me as I'm a newbie. I've been banging on Geronimo
> for just
> about a month and have been at Hibernate for maybe a week. If
> someone could
> shed some light on this problem or perhaps point me to some
> documentation
> (yes, I've read the Hibernate to Geronimo migration docs, yes, I've
> googled,
> yes, I did a keyword search on this forum for "Hibernate datasource").
>
> Many thanks in advance!!!
> Bevon
> --
> View this message in context: http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26353366.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>

Geronimo book now available - Apache Geronimo 2.1: Quick Reference

2009-11-15T19:59:26Z

Hi All,

The book titled "Apache Geronimo 2.1: Quick Reference" authored by Manu T. George and myself is released by Packt Publishing and is now available. Please see [1].

Thanks and best regards,
Vamsi
Committer and Member of Apache Geronimo PMC
Committer on Apache Tuscany

[1] http://www.packtpub.com/apache-geronimo-2-2-quick-reference/book

Re: Geronimo 2.2 Release Status

2009-11-15T16:32:47Z

I have no idea about the Geronimo release plans. I've copied the Geronimo users list for further info.

On Sun, Nov 15, 2009 at 4:51 PM, frapien <frank.pientka@...> wrote:

How are the plans? Will Geronimo 2.2 get out this year?
Are there any open isues? Releaseplan speaks from Proposed Release date:
3Q2009
http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html
Thanks for information
Frank
--
View this message in context: http://old.nabble.com/Geronimo-2.2-Release-Status-tp26362898p26362898.html
Sent from the Camel - Users mailing list archive at Nabble.com.

--
Cheers,
Jon

Camel in Action: http://manning.com/ibsen
Blog: http://janstey.blogspot.com

Re: JNDI lookup fails with Hibernate + application-scoped datasource

2009-11-15T00:17:30Z

Hi Bevon,

I haven't looked through all the files you post but want to give a
couple hints, maybe you can easily track down what is going on.

In Geronimo, the jta-datasource and non-jta-datasource values don't
refer to anything in jndi, they basically look up components
registered in the geronimo kernel. The JPA architecture has the
container (geronimo's jpa support) setting up an object that includes
these datasources and the rest of the info from the persistence.xml,
suitably resolved. So, you don't need to declare any resource-refs in
your ejb jar anywhere to use jpa.

For non-jpa hibernate, IIUC your explanation, jndi is really used to
find the datasource(s). I'm not clear on exactly what is getting
looked up.... I strongly advise finding out. I also suggest using the
standard geronimo jndi rather than the openejb jndi context which is
unlikely to have any datasources in it since it is for looking up
ejbs. I'd hope that if you _don't_ set the hibernate property it
would just use
new InitialContext() which ought to work.

Finally, hibernate might be trying to look up a java:comp/env jndi
name defined by a resource ref in the ejb jar or some completely
specified string for a global jndi name. In the latter case, you'll
want to check the geronimo.log to make sure you know exactly what the
global jndi name for your datasource actually is.... it gets logged as
the datasource starts.

hope this helps, and if you want to update our docs when you get it
working that would be great!

thanks
david jencks

On Nov 14, 2009, at 11:59 AM, Bevon wrote:

>
> First, my apologies in advance is this should be posted on a
> Hibernate board.
> But this seems more of a configuration issue specific to Geronimo
> so...
>
> Geronimo: v2.1.4
> Hibernate core: v3.3.2
> Derby Network Server: v10.4.2
>
> I was able to get Hibernate working as my JPA provider (instead of
> OpenJPA)
> for my EJB3 module. However, as an academic/learning exercise, I
> have been
> trying to get Hibernate core working as my persistence layer for my
> EJB3
> module. The problem I'm seeing is that during the Hibernate
> Configuration.buildSessionFactory() call, a JNDI exception is thrown
> stating
> that the datasource could not be found.
>
>
> I have an application-scoped managed datasource declared for my EAR as
> follows:
> application.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://java.sun.com/xml/ns/javaee"
>
> xmlns:application="http://java.sun.com/xml/ns/javaee/
> application_5.xsd"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/application_5.xsd"
> id="Application_ID"
> version="5">
> <display-name>PsopEAR5_Test</display-name>
> <module>
> <connector>Derby/tranql-connector-derby-client-local-1.4.rar</
> connector>
> </module>
> <module>
> <web>
> <web-uri>Psop_Servlet25_Jsp21.war</web-uri>
> <context-root>Psop_Servlet25_Jsp21</context-root>
> </web>
> </module>
> <module>
> <ejb>Psop_Ejb30_Hibernate33.jar</ejb>
> </module>
> </application>
>
>
> geronimo-application.xml:
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <app:application
> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
>
> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
> "
>
> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
>
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
>
> xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2
> "
> xmlns:pers="http://java.sun.com/xml/ns/persistence"
> xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1
> "
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0
> "
>
> xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
> application-name="PsopEAR5_Test">
> <dep:environment>
> <dep:moduleId>
> <dep:groupId>default</dep:groupId>
> <dep:artifactId>PsopEAR5_Test</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>car</dep:type>
> </dep:moduleId>
> <dep:dependencies />
> </dep:environment>
> <app:module>
> 
>
> <app:connector>Derby/tranql-connector-derby-client-local-1.4.rar</
> app:connector>
>
> 
> <app:alt-dd>Derby/derby-network-server-plan.xml</app:alt-dd>
> </app:module>
> </app:application>
>
>
> derby-network-server-plan.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/
> connector-1.2">
> <dep:environment
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
> <dep:moduleId>
> <dep:groupId>console.dbpool</dep:groupId>
> <dep:artifactId>jdbc_psop_derbyDs1</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>rar</dep:type>
> </dep:moduleId>
> <dep:dependencies>
> <dep:dependency>
> <dep:groupId>org.apache.geronimo.configs</dep:groupId>
> <dep:artifactId>system-database</dep:artifactId>
> <dep:version>2.1.4</dep:version>
> <dep:type>car</dep:type>
> </dep:dependency>
> </dep:dependencies>
> </dep:environment>
> <resourceadapter>
> <outbound-resourceadapter>
> <connection-definition>
>
> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-
> interface>
> <connectiondefinition-instance>
> <name>jdbc/psop/derbyDs1</name>
> <config-property-setting
> name="DatabaseName">E:\PSOP\Databases\Derby\PSOP_DATABASE</config-
> property-setting>
> <config-property-setting
> name="Password">app</config-property-setting>
> <config-property-setting
> name="UserName">app</config-property-setting>
> <config-property-setting name="LoginTimeout"/>
> <connectionmanager>
> <local-transaction/>
> <single-pool>
> <max-size>10</max-size>
> <min-size>0</min-size>
> <match-one/>
> </single-pool>
> </connectionmanager>
> </connectiondefinition-instance>
> </connection-definition>
> </outbound-resourceadapter>
> </resourceadapter>
> </connector>
>
>
> My EJB3 module metadata is as follows:
> ejb-jar.xml (essentially empty since I'm using EJB3 annotations):
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
> version="3.0">
> <description>PSOP model implemented with EJB 3.0. PSOP persistence
> implemented with Hibernate 3.3 (native).</description>
> <display-name>Psop_Ejb30_Hibernate33</display-name>
> </ejb-jar>
>
>
> openejb-jar.xml (all of the dependency jars were copied into the
> Geronimo
> repository):
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:naming="http://geronimo.apache.org/xml/ns/
> naming-1.2"
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2
> ">
> <sys:environment>
> <sys:moduleId>
> <sys:groupId>default</sys:groupId>
> <sys:artifactId>Psop_Ejb30_Hibernate33</sys:artifactId>
> <sys:version>1.0</sys:version>
> <sys:type>car</sys:type>
> </sys:moduleId>
> <sys:dependencies>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>core</sys:artifactId>
> <sys:version>3.3</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>antlr</sys:artifactId>
> <sys:version>2.7.6</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>commons-collections</sys:artifactId>
> <sys:version>3.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>dom4j</sys:artifactId>
> <sys:version>1.6.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>javassist</sys:artifactId>
> <sys:version>3.9.0.GA</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>jta</sys:artifactId>
> <sys:version>1.1</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>psop_hibernate</sys:groupId>
> <sys:artifactId>GeronimoTransactionManager</
> sys:artifactId>
> <sys:version>1.0</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> <sys:dependency>
> <sys:groupId>org.slf4j</sys:groupId>
> <sys:artifactId>slf4j-api</sys:artifactId>
> <sys:version>1.4.3</sys:version>
> <sys:type>jar</sys:type>
> </sys:dependency>
> </sys:dependencies>
> </sys:environment>
> </openejb-jar>
>
>
> hibernate.cfg.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate
> Configuration DTD 3.0//EN"
> "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
> <hibernate-configuration>
> <session-factory name="jdbc/psop/hibernateSf1">
>
> 
> <property
> name="hibernate.connection.datasource">jdbc/psop/derbyDs1</property>
>
> 
> <property
> name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .manager_lookup_class
> ">org.hibernate.transaction.GeronimoTransactionManagerLookup</
> property>
>
> 
> <property
> name
> =
> "hibernate
> .transaction
> .factory_class">org.hibernate.transaction.JTATransactionFactory</
> property>
>
> 
> <property name="hibernate.show_sql">true</property>
> <property name="hibernate.format_sql">true</property>
>
> 
> <mapping
> resource="META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml"/>
> </session-factory>
> </hibernate-configuration>
>
>
>
>
> Here is the code that tries to build the SessionFactory:
> Configuration hibernateConfiguration = new Configuration().configure(
> "/META-INF/hibernate.cfg.xml" );
> hibernateConfiguration.setProperty(
> org.hibernate.cfg.Environment.JNDI_CLASS,
> "org.apache.openejb.client.RemoteInitialContextFactory" ) );
> hibernateConfiguration
> .setProperty( org.hibernate.cfg.Environment.JNDI_URL,
> "ejbd://localhost:4201" );
>
> sessionFactorySingleInstance =
> hibernateConfiguration.buildSessionFactory();
> // throws JNDI exception
> // as a test, if I do a JNDI lookup on "jdbc/psop/derbyDs1", I get
> the same
> exception
>
>
> Here is the exception that occurs during publishing (I'm using Eclipse
> Ganymede with GEP):
> javax.naming.NameNotFoundException: /jdbc/psop/derbyDs1 does not
> exist in
> the system. Check that the app was successfully deployed.
> at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:277)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at
> com
> .psop
> .model
> .ejb
> .config
> .EjbHibernateModelConfig
> .initializeSessionFactory(EjbHibernateModelConfig.java:234)
> at
> com
> .psop
> .model
> .ejb
> .config
> .EjbHibernateModelConfig
> .initializeModel(EjbHibernateModelConfig.java:292)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.openejb.core.interceptor.ReflectionInvocationContext
> $Invocation.invoke(ReflectionInvocationContext.java:158)
> at
> org
> .apache
> .openejb
> .core
> .interceptor
> .ReflectionInvocationContext
> .proceed(ReflectionInvocationContext.java:141)
> at
> org
> .apache
> .openejb
> .core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
> 210)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer._invoke(StatelessContainer.java:
> 188)
> at
> org
> .apache
> .openejb
> .core.stateless.StatelessContainer.invoke(StatelessContainer.java:165)
> at
> org
> .apache
> .openejb
> .server
> .ejbd
> .EjbRequestHandler
> .doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238)
> at
> org
> .apache
> .openejb
> .server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:
> 129)
> at
> org
> .apache
> .openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164)
> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
> 122)
> at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
> 84)
> at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:
> 60)
> at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:78)
> at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:101)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> Geronimo log (I don't see any binding of the datasource to JNDI here):
> 2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default
> Stateless Container, type=Container, provider-id=Default Stateless
> Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default
> Stateful Container, type=Container, provider-id=Default Stateful
> Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring
> Service(id=Default BMP
> Container, type=Container, provider-id=Default BMP Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring
> Service(id=Default CMP
> Container, type=Container, provider-id=Default CMP Container)
> 2009-11-14 14:30:06,903 INFO [config] Configuring app:
> default/PsopEAR5_Test/1.0/car
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateFinder:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateDestroyer:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateCreator:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator)
> 2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb
> ejb/psop/ejbHibernateModelConfig:
> EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig)
> 2009-11-14 14:30:06,919 INFO [config] Loaded Module:
> default/PsopEAR5_Test/1.0/car
> 2009-11-14 14:30:07,810 INFO [KernelContextGBean] bound gbean
> default/PsopEAR5_Test/1.0/car?J2EEApplication=default/PsopEAR5_Test/
> 1.0/car,JCAConnectionFactory=jdbc/psop/derbyDs1,JCAResource=Derby/
> tranql-connector-derby-client-local-1.4.rar,ResourceAdapter=Derby/
> tranql-connector-derby-client-
> local-1.4.rar,ResourceAdapterModule=Derby/tranql-connector-derby-
> client-local-1.4.rar,j2eeType=JCAManagedConnectionFactory,name=jdbc/
> psop/derbyDs1
> at name default/PsopEAR5_Test/JCAManagedConnectionFactory/jdbc/psop/
> derbyDs1
> 2009-11-14 14:30:07,810 INFO [startup] Assembling app: C:\Documents
> and
> Settings\Bevon Palod\Local
> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateFinderRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateDestroyerRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateCreatorRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator)
> 2009-11-14 14:30:07,872 INFO [startup]
> Jndi(name=ejb/psop/ejbHibernateModelConfigRemote) -->
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateFinder,
> ejb-name=ejb/psop/ejbHibernateFinder, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateDestroyer,
> ejb-name=ejb/psop/ejbHibernateDestroyer, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateCreator,
> ejb-name=ejb/psop/ejbHibernateCreator, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Created
> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/
> ejbHibernateModelConfig,
> ejb-name=ejb/psop/ejbHibernateModelConfig, container=Default Stateless
> Container)
> 2009-11-14 14:30:07,872 INFO [startup] Deployed
> Application(path=C:\Documents and Settings\Bevon Palod\Local
> Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar)
> 2009-11-14 14:30:08,013 INFO [OpenEJB] invoking method create on
> Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig
> 2009-11-14 14:30:08,013 INFO [OpenEJB] finished invoking method
> create
> 2009-11-14 14:30:08,013 INFO [Transaction] TX Required: Started
> transaction
> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
> 2009-11-14 14:30:08,091 INFO [Environment] Hibernate 3.3.2.GA
> 2009-11-14 14:30:08,091 INFO [Environment] hibernate.properties not
> found
> 2009-11-14 14:30:08,106 INFO [Environment] Bytecode provider name :
> javassist
> 2009-11-14 14:30:08,122 INFO [Environment] using JDK 1.4
> java.sql.Timestamp
> handling
> 2009-11-14 14:30:08,356 INFO [Configuration] configuring from
> resource:
> /META-INF/hibernate.cfg.xml
> 2009-11-14 14:30:08,356 INFO [Configuration] Configuration resource:
> /META-INF/hibernate.cfg.xml
> 2009-11-14 14:30:08,497 INFO [Configuration] Reading mappings from
> resource
> : META-INF/mappings/com/psop/model/hibernate/
> PlayerHibernateEntity.hbm.xml
> 2009-11-14 14:30:08,606 INFO [HbmBinder] Mapping class:
> com.psop.model.hibernate.PlayerHibernateEntity -> PLAYERS
> 2009-11-14 14:30:08,685 INFO [Configuration] Configured
> SessionFactory:
> jdbc/psop/hibernateSf1
> 2009-11-14 14:30:08,685 INFO [Transaction] TX Required: Committing
> transaction
> org.apache.geronimo.transaction.manager.TransactionImpl@188807b
>
>
> I do not see this exception when I make use of Hibernate Annotations +
> EnitityManager and stick with JPA-only API/annotations in my code.
> In terms
> of configuration, the EAR metadata is exactly the same (save for
> swapping
> the EJB3 modules). The EJB3 module metadata has two differences:
> 1. I've got a persistence.xml instead of hibernate.cfg.xml.
> 2. I've added the Hibernate Annotations + EntityManager
> dependencies to my
> openejb-jar.xml (won't bother pasting it again here).
>
> persistence.xml:
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence xmlns="http://java.sun.com/xml/ns/persistence"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
> version="1.0" >
> <persistence-unit name="Psop_Ejb30_Jpa10" transaction-type="JTA">
> <description>Hibernate v3.3 JPA provider</description>
> <provider>org.hibernate.ejb.HibernatePersistence</provider>
> <jta-data-source>jdbc/psop/derbyDs1</jta-data-source>
> <class>com.psop.model.jpa.PlayerJpaEntity</class>
> <properties>
> <property name="hibernate.transaction.manager_lookup_class"
> value="org.hibernate.transaction.GeronimoTransactionManagerLookup"/>
> <property name="hibernate.show_sql" value="true"/>
> <property name="hibernate.format_sql" value="true"/>
> <property name="hibernate.dialect"
> value="org.hibernate.dialect.DerbyDialect"/>
> </properties>
> </persistence-unit>
> </persistence>
>
>
> My best guess -- I'm doing something wrong or it's a faulty
> assumption that
> my datasource will automagically be registered in JNDI (as it is
> with JPA).
>
> Please bear with me as I'm a newbie. I've been banging on Geronimo
> for just
> about a month and have been at Hibernate for maybe a week. If
> someone could
> shed some light on this problem or perhaps point me to some
> documentation
> (yes, I've read the Hibernate to Geronimo migration docs, yes, I've
> googled,
> yes, I did a keyword search on this forum for "Hibernate datasource").
>
> Many thanks in advance!!!
> Bevon
> --
> View this message in context: http://old.nabble.com/JNDI-lookup-fails-with-Hibernate-%2B-application-scoped-datasource-tp26353366s134p26353366.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>

Unsubscribe

2009-11-14T17:28:39Z

JNDI lookup fails with Hibernate + application-scoped datasource

2009-11-14T11:59:14Z

First, my apologies in advance is this should be posted on a Hibernate board. But this seems more of a configuration issue specific to Geronimo so...

Geronimo: v2.1.4
Hibernate core: v3.3.2
Derby Network Server: v10.4.2

I was able to get Hibernate working as my JPA provider (instead of OpenJPA) for my EJB3 module. However, as an academic/learning exercise, I have been trying to get Hibernate core working as my persistence layer for my EJB3 module. The problem I'm seeing is that during the Hibernate Configuration.buildSessionFactory() call, a JNDI exception is thrown stating that the datasource could not be found.

I have an application-scoped managed datasource declared for my EAR as follows:
application.xml:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
id="Application_ID"
version="5">
<display-name>PsopEAR5_Test</display-name>
<module>
<connector>Derby/tranql-connector-derby-client-local-1.4.rar</connector>
</module>
<module>
<web>
<web-uri>Psop_Servlet25_Jsp21.war</web-uri>
<context-root>Psop_Servlet25_Jsp21</context-root>
</web>
</module>
<module>
<ejb>Psop_Ejb30_Hibernate33.jar</ejb>
</module>
</application>

geronimo-application.xml:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<app:application xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"
xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"
xmlns:pers="http://java.sun.com/xml/ns/persistence"
xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1"
application-name="PsopEAR5_Test">
<dep:environment>
<dep:moduleId>
<dep:groupId>default</dep:groupId>
<dep:artifactId>PsopEAR5_Test</dep:artifactId>
<dep:version>1.0</dep:version>
<dep:type>car</dep:type>
</dep:moduleId>
<dep:dependencies />
</dep:environment>
<app:module>

<app:connector>Derby/tranql-connector-derby-client-local-1.4.rar</app:connector>


<app:alt-dd>Derby/derby-network-server-plan.xml</app:alt-dd>
</app:module>
</app:application>

derby-network-server-plan.xml:
<?xml version="1.0" encoding="UTF-8"?>
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2">
<dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
<dep:moduleId>
<dep:groupId>console.dbpool</dep:groupId>
<dep:artifactId>jdbc_psop_derbyDs1</dep:artifactId>
<dep:version>1.0</dep:version>
<dep:type>rar</dep:type>
</dep:moduleId>
<dep:dependencies>
<dep:dependency>
<dep:groupId>org.apache.geronimo.configs</dep:groupId>
<dep:artifactId>system-database</dep:artifactId>
<dep:version>2.1.4</dep:version>
<dep:type>car</dep:type>
</dep:dependency>
</dep:dependencies>
</dep:environment>
<resourceadapter>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
<connectiondefinition-instance>
<name>jdbc/psop/derbyDs1</name>
<config-property-setting name="DatabaseName">E:\PSOP\Databases\Derby\PSOP_DATABASE</config-property-setting>
<config-property-setting name="Password">app</config-property-setting>
<config-property-setting name="UserName">app</config-property-setting>
<config-property-setting name="LoginTimeout"/>
<connectionmanager>
<local-transaction/>
<single-pool>
<max-size>10</max-size>
<min-size>0</min-size>
<match-one/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
</connector>

My EJB3 module metadata is as follows:
ejb-jar.xml (essentially empty since I'm using EJB3 annotations):
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
<description>PSOP model implemented with EJB 3.0. PSOP persistence implemented with Hibernate 3.3 (native).</description>
<display-name>Psop_Ejb30_Hibernate33</display-name>
</ejb-jar>

openejb-jar.xml (all of the dependency jars were copied into the Geronimo repository):
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.2"
xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2">
<sys:environment>
<sys:moduleId>
<sys:groupId>default</sys:groupId>
<sys:artifactId>Psop_Ejb30_Hibernate33</sys:artifactId>
<sys:version>1.0</sys:version>
<sys:type>car</sys:type>
</sys:moduleId>
<sys:dependencies>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>core</sys:artifactId>
<sys:version>3.3</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>antlr</sys:artifactId>
<sys:version>2.7.6</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>commons-collections</sys:artifactId>
<sys:version>3.1</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>dom4j</sys:artifactId>
<sys:version>1.6.1</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>javassist</sys:artifactId>
<sys:version>3.9.0.GA</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>jta</sys:artifactId>
<sys:version>1.1</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>psop_hibernate</sys:groupId>
<sys:artifactId>GeronimoTransactionManager</sys:artifactId>
<sys:version>1.0</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
<sys:dependency>
<sys:groupId>org.slf4j</sys:groupId>
<sys:artifactId>slf4j-api</sys:artifactId>
<sys:version>1.4.3</sys:version>
<sys:type>jar</sys:type>
</sys:dependency>
</sys:dependencies>
</sys:environment>
</openejb-jar>

hibernate.cfg.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory name="jdbc/psop/hibernateSf1">


<property name="hibernate.connection.datasource">jdbc/psop/derbyDs1</property>


<property name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property>


<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.GeronimoTransactionManagerLookup</property>


<property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>


<property name="hibernate.show_sql">true</property>
<property name="hibernate.format_sql">true</property>


<mapping resource="META-INF/mappings/com/psop/model/hibernate/PlayerHibernateEntity.hbm.xml"/>
</session-factory>
</hibernate-configuration>

Here is the code that tries to build the SessionFactory:
Configuration hibernateConfiguration = new Configuration().configure( "/META-INF/hibernate.cfg.xml" );
hibernateConfiguration.setProperty( org.hibernate.cfg.Environment.JNDI_CLASS, "org.apache.openejb.client.RemoteInitialContextFactory" ) );
hibernateConfiguration.setProperty( org.hibernate.cfg.Environment.JNDI_URL, "ejbd://localhost:4201" );

sessionFactorySingleInstance = hibernateConfiguration.buildSessionFactory(); // throws JNDI exception
// as a test, if I do a JNDI lookup on "jdbc/psop/derbyDs1", I get the same exception

Here is the exception that occurs during publishing (I'm using Eclipse Ganymede with GEP):
javax.naming.NameNotFoundException: /jdbc/psop/derbyDs1 does not exist in the system. Check that the app was successfully deployed.
at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:277)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.psop.model.ejb.config.EjbHibernateModelConfig.initializeSessionFactory(EjbHibernateModelConfig.java:234)
at com.psop.model.ejb.config.EjbHibernateModelConfig.initializeModel(EjbHibernateModelConfig.java:292)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:67)
at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:210)
at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:188)
at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:165)
at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:238)
at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:129)
at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:164)
at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:122)
at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84)
at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60)
at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:78)
at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:101)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Geronimo log (I don't see any binding of the datasource to JNDI here):
2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default Stateless Container, type=Container, provider-id=Default Stateless Container)
2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default Stateful Container, type=Container, provider-id=Default Stateful Container)
2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default BMP Container, type=Container, provider-id=Default BMP Container)
2009-11-14 14:30:06,903 INFO [config] Configuring Service(id=Default CMP Container, type=Container, provider-id=Default CMP Container)
2009-11-14 14:30:06,903 INFO [config] Configuring app: default/PsopEAR5_Test/1.0/car
2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb ejb/psop/ejbHibernateFinder: EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateFinder)
2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb ejb/psop/ejbHibernateDestroyer: EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateDestroyer)
2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb ejb/psop/ejbHibernateCreator: EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateCreator)
2009-11-14 14:30:06,919 INFO [OpenEJB] Auto-deploying ejb ejb/psop/ejbHibernateModelConfig: EjbDeployment(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig)
2009-11-14 14:30:06,919 INFO [config] Loaded Module: default/PsopEAR5_Test/1.0/car
2009-11-14 14:30:07,810 INFO [KernelContextGBean] bound gbean default/PsopEAR5_Test/1.0/car?J2EEApplication=default/PsopEAR5_Test/1.0/car,JCAConnectionFactory=jdbc/psop/derbyDs1,JCAResource=Derby/tranql-connector-derby-client-local-1.4.rar,ResourceAdapter=Derby/tranql-connector-derby-client-local-1.4.rar,ResourceAdapterModule=Derby/tranql-connector-derby-client-local-1.4.rar,j2eeType=JCAManagedConnectionFactory,name=jdbc/psop/derbyDs1 at name default/PsopEAR5_Test/JCAManagedConnectionFactory/jdbc/psop/derbyDs1
2009-11-14 14:30:07,810 INFO [startup] Assembling app: C:\Documents and Settings\Bevon Palod\Local Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar
2009-11-14 14:30:07,872 INFO [startup] Jndi(name=ejb/psop/ejbHibernateFinderRemote) --> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateFinder)
2009-11-14 14:30:07,872 INFO [startup] Jndi(name=ejb/psop/ejbHibernateDestroyerRemote) --> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateDestroyer)
2009-11-14 14:30:07,872 INFO [startup] Jndi(name=ejb/psop/ejbHibernateCreatorRemote) --> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateCreator)
2009-11-14 14:30:07,872 INFO [startup] Jndi(name=ejb/psop/ejbHibernateModelConfigRemote) --> Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig)
2009-11-14 14:30:07,872 INFO [startup] Created Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateFinder, ejb-name=ejb/psop/ejbHibernateFinder, container=Default Stateless Container)
2009-11-14 14:30:07,872 INFO [startup] Created Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateDestroyer, ejb-name=ejb/psop/ejbHibernateDestroyer, container=Default Stateless Container)
2009-11-14 14:30:07,872 INFO [startup] Created Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateCreator, ejb-name=ejb/psop/ejbHibernateCreator, container=Default Stateless Container)
2009-11-14 14:30:07,872 INFO [startup] Created Ejb(deployment-id=Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig, ejb-name=ejb/psop/ejbHibernateModelConfig, container=Default Stateless Container)
2009-11-14 14:30:07,872 INFO [startup] Deployed Application(path=C:\Documents and Settings\Bevon Palod\Local Settings\Temp\geronimo-deploymentUtil3743899707090395072.jar)
2009-11-14 14:30:08,013 INFO [OpenEJB] invoking method create on Psop_Ejb30_Hibernate33.jar/ejb/psop/ejbHibernateModelConfig
2009-11-14 14:30:08,013 INFO [OpenEJB] finished invoking method create
2009-11-14 14:30:08,013 INFO [Transaction] TX Required: Started transaction org.apache.geronimo.transaction.manager.TransactionImpl@188807b
2009-11-14 14:30:08,091 INFO [Environment] Hibernate 3.3.2.GA
2009-11-14 14:30:08,091 INFO [Environment] hibernate.properties not found
2009-11-14 14:30:08,106 INFO [Environment] Bytecode provider name : javassist
2009-11-14 14:30:08,122 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
2009-11-14 14:30:08,356 INFO [Configuration] configuring from resource: /META-INF/hibernate.cfg.xml
2009-11-14 14:30:08,356 INFO [Configuration] Configuration resource: /META-INF/hibernate.cfg.xml
2009-11-14 14:30:08,497 INFO [Configuration] Reading mappings from resource : META-INF/mappings/com/psop/model/hibernate/PlayerHibernateEntity.hbm.xml
2009-11-14 14:30:08,606 INFO [HbmBinder] Mapping class: com.psop.model.hibernate.PlayerHibernateEntity -> PLAYERS
2009-11-14 14:30:08,685 INFO [Configuration] Configured SessionFactory: jdbc/psop/hibernateSf1
2009-11-14 14:30:08,685 INFO [Transaction] TX Required: Committing transaction org.apache.geronimo.transaction.manager.TransactionImpl@188807b

I do not see this exception when I make use of Hibernate Annotations + EnitityManager and stick with JPA-only API/annotations in my code. In terms of configuration, the EAR metadata is exactly the same (save for swapping the EJB3 modules). The EJB3 module metadata has two differences:
1. I've got a persistence.xml instead of hibernate.cfg.xml.
2. I've added the Hibernate Annotations + EntityManager dependencies to my openejb-jar.xml (won't bother pasting it again here).

persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0" >
<persistence-unit name="Psop_Ejb30_Jpa10" transaction-type="JTA">
<description>Hibernate v3.3 JPA provider</description>
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>jdbc/psop/derbyDs1</jta-data-source>
<class>com.psop.model.jpa.PlayerJpaEntity</class>
<properties>
<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.GeronimoTransactionManagerLookup"/>
<property name="hibernate.show_sql" value="true"/>
<property name="hibernate.format_sql" value="true"/>
<property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect"/>
</properties>
</persistence-unit>
</persistence>

My best guess -- I'm doing something wrong or it's a faulty assumption that my datasource will automagically be registered in JNDI (as it is with JPA).

Please bear with me as I'm a newbie. I've been banging on Geronimo for just about a month and have been at Hibernate for maybe a week. If someone could shed some light on this problem or perhaps point me to some documentation (yes, I've read the Hibernate to Geronimo migration docs, yes, I've googled, yes, I did a keyword search on this forum for "Hibernate datasource").

Many thanks in advance!!!
Bevon

Re: 2.2 in production

2009-11-14T05:07:19Z

Great, thanks again!

We've had many more updates of our servers since I last reported and WADI failover handling has proven stable so far.

Trygve

On Sat, Nov 14, 2009 at 7:59 AM, Gianny Damour <gianny.damour@...> wrote:

Hi Trygve,

Thanks for your test.

These warnings indicate that a session replication message was not acknowledged within a 2000ms timeframe. The message has not been lost and will be processed by back-up nodes as expected.

Kevan, I just deployed release 2.1.2 of WADI for geronimo 2.2.

Thanks,
Gianny

On 09/11/2009, at 11:38 PM, Trygve Hardersen wrote:

Hello again

The system has now been running for a few days and I've not seen the hang on startup so I believe the issue has been resolved. Great!

I am still seeing some warnings like this:

10:58:49,250 WARN [UpdateReplicationCommand] Update has not been properly cascaded due to a communication failure. If a targeted node has been lost, state will be re-balanced automatically.
org.codehaus.wadi.servicespace.ServiceInvocationException: org.codehaus.wadi.group.MessageExchangeException: No correlated messages received within [2000]ms
at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory$ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:209)
at org.codehaus.wadi.replication.storage.ReplicaStorage$$EnhancerByCGLIB$$4372d264.mergeUpdate(<generated>)
at org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.cascadeUpdate(UpdateReplicationCommand.java:93)
at org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.run(UpdateReplicationCommand.java:86)
at org.codehaus.wadi.replication.manager.basic.SyncReplicationManager.update(SyncReplicationManager.java:138)
at org.codehaus.wadi.replication.manager.basic.LoggingReplicationManager.update(LoggingReplicationManager.java:100)
at org.codehaus.wadi.core.session.AbstractReplicableSession.onEndProcessing(AbstractReplicableSession.java:49)
at org.codehaus.wadi.core.session.AtomicallyReplicableSession.onEndProcessing(AtomicallyReplicableSession.java:58)
at org.apache.geronimo.clustering.wadi.WADISessionAdaptor.onEndAccess(WADISessionAdaptor.java:77)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionManager.complete(ClusteredSessionManager.java:60)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:198)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.doHandle(ClusteredSessionHandler.java:59)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler$ActualHandler.handle(ClusteredSessionHandler.java:66)
at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler$WebClusteredInvocation.invokeLocally(AbstractClusteredPreHandler.java:71)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation.access$000(WADIClusteredPreHandler.java:52)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation$1.doFilter(WADIClusteredPreHandler.java:64)
at org.codehaus.wadi.web.impl.WebInvocation.invoke(WebInvocation.java:116)
at org.codehaus.wadi.core.contextualiser.MemoryContextualiser.handleLocally(MemoryContextualiser.java:71)
at org.codehaus.wadi.core.contextualiser.AbstractExclusiveContextualiser.handle(AbstractExclusiveContextualiser.java:94)
at org.codehaus.wadi.core.contextualiser.AbstractMotingContextualiser.contextualise(AbstractMotingContextualiser.java:37)
at org.codehaus.wadi.core.manager.StandardManager.processStateful(StandardManager.java:154)
at org.codehaus.wadi.core.manager.StandardManager.contextualise(StandardManager.java:146)
at org.codehaus.wadi.core.manager.ClusteredManager.contextualise(ClusteredManager.java:81)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation.invoke(WADIClusteredPreHandler.java:72)
at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler.handle(AbstractClusteredPreHandler.java:39)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.handle(ClusteredSessionHandler.java:51)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(TwistyWebAppContext.java:41)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(TwistyWebAppContext.java:66)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58)
at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle(TwistyWebAppContext.java:60)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.codehaus.wadi.group.MessageExchangeException: No correlated messages received within [2000]ms
at org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous(AbstractDispatcher.java:174)
at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invokeOnPeers(BasicServiceInvoker.java:90)
at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invoke(BasicServiceInvoker.java:69)
at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory$ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:193)
... 49 more

Not sure if I should worry about that.

Many thanks for your help!

Trygve

On Tue, Nov 3, 2009 at 4:35 PM, Trygve Hardersen <trygve@...> wrote:

On Mon, Nov 2, 2009 at 5:39 PM, Kevan Miller <kevan.miller@...> wrote:

Thanks Gianny. I'd like to see this included in the Geronimo 2.2 release. Can we look for a new WADI release, soon? Once we know the problem is fixed?

Trygve, the sooner we get confirmation that your issue is resolved, the sooner we can start finalizing the 2.2 release.

--kevan

I've now built Geronimo using the 2.2-SNAPSHOT of WADI and installed it on our test environment. No obvious issues so I'll go ahead and deploy this to production either later this evening (EU time) or tomorrow. Then it needs to run for a few days before I can confirm if the issue has really been resolved.

BTW I got this on our test system:

AS-000:
16:23:17,773 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.
16:23:17,897 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

AS-001:
16:23:18,446 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.
16:23:18,456 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

And then:

AS-000
16:30:02,576 INFO [ChannelInterceptorBase] memberDisappeared:tcp://{-64, -88, 1, 61}:4000
16:30:02,577 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
16:30:02,600 INFO [SimpleStateManager]
=============================
New Partition Balancing
Partition Balancing
Size [24]
Partition[0] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[1] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[2] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[3] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[4] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[5] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[6] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[7] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[8] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[9] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[10] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[11] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[12] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[13] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[14] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[15] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[16] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[17] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[18] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[19] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[20] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[21] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[22] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
Partition[23] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
=============================

16:30:02,888 WARN [TcpFailureDetector] Member added, even though we werent notified:org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=2221072,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]
16:30:02,889 INFO [ChannelInterceptorBase] memberAdded:tcp://{-64, -88, 1, 61}:4000

AS-001
Nothing....

There is practically no load on this network. Anyway I'll try this with load and see what happens.

Many thanks again!

Trygve

Re: 2.2 in production

2009-11-13T22:57:31Z

Hi Trygve,

Thanks for your test.

These warnings indicate that a session replication message was not
acknowledged within a 2000ms timeframe. The message has not been lost
and will be processed by back-up nodes as expected.

Kevan, I just deployed release 2.1.2 of WADI for geronimo 2.2.

Thanks,
Gianny

On 09/11/2009, at 11:38 PM, Trygve Hardersen wrote:

> Hello again
>
> The system has now been running for a few days and I've not seen
> the hang on startup so I believe the issue has been resolved. Great!
>
> I am still seeing some warnings like this:
>
> 10:58:49,250 WARN [UpdateReplicationCommand] Update has not been
> properly cascaded due to a communication failure. If a targeted
> node has been lost, state will be re-balanced automatically.
> org.codehaus.wadi.servicespace.ServiceInvocationException:
> org.codehaus.wadi.group.MessageExchangeException: No correlated
> messages received within [2000]ms
> at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory
> $ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:209)
> at org.codehaus.wadi.replication.storage.ReplicaStorage$
> $EnhancerByCGLIB$$4372d264.mergeUpdate(<generated>)
> at
> org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.c
> ascadeUpdate(UpdateReplicationCommand.java:93)
> at
> org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.r
> un(UpdateReplicationCommand.java:86)
> at
> org.codehaus.wadi.replication.manager.basic.SyncReplicationManager.upd
> ate(SyncReplicationManager.java:138)
> at
> org.codehaus.wadi.replication.manager.basic.LoggingReplicationManager.
> update(LoggingReplicationManager.java:100)
> at
> org.codehaus.wadi.core.session.AbstractReplicableSession.onEndProcessi
> ng(AbstractReplicableSession.java:49)
> at
> org.codehaus.wadi.core.session.AtomicallyReplicableSession.onEndProces
> sing(AtomicallyReplicableSession.java:58)
> at
> org.apache.geronimo.clustering.wadi.WADISessionAdaptor.onEndAccess
> (WADISessionAdaptor.java:77)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionManager.complete
> (ClusteredSessionManager.java:60)
> at org.mortbay.jetty.servlet.SessionHandler.handle
> (SessionHandler.java:198)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.doHandle
> (ClusteredSessionHandler.java:59)
> at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler
> $ActualHandler.handle(ClusteredSessionHandler.java:66)
> at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler
> $WebClusteredInvocation.invokeLocally
> (AbstractClusteredPreHandler.java:71)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation.access$000(WADIClusteredPreHandler.java:
> 52)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation$1.doFilter(WADIClusteredPreHandler.java:
> 64)
> at org.codehaus.wadi.web.impl.WebInvocation.invoke
> (WebInvocation.java:116)
> at
> org.codehaus.wadi.core.contextualiser.MemoryContextualiser.handleLocal
> ly(MemoryContextualiser.java:71)
> at
> org.codehaus.wadi.core.contextualiser.AbstractExclusiveContextualiser.
> handle(AbstractExclusiveContextualiser.java:94)
> at
> org.codehaus.wadi.core.contextualiser.AbstractMotingContextualiser.con
> textualise(AbstractMotingContextualiser.java:37)
> at org.codehaus.wadi.core.manager.StandardManager.processStateful
> (StandardManager.java:154)
> at org.codehaus.wadi.core.manager.StandardManager.contextualise
> (StandardManager.java:146)
> at org.codehaus.wadi.core.manager.ClusteredManager.contextualise
> (ClusteredManager.java:81)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation.invoke(WADIClusteredPreHandler.java:72)
> at
> org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler.handle(
> AbstractClusteredPreHandler.java:39)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.handle
> (ClusteredSessionHandler.java:51)
> at org.mortbay.jetty.handler.ContextHandler.handle
> (ContextHandler.java:765)
> at org.mortbay.jetty.webapp.WebAppContext.handle
> (WebAppContext.java:417)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access
> $101(TwistyWebAppContext.java:41)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext
> $TwistyHandler.handle(TwistyWebAppContext.java:66)
> at
> org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
> (ThreadClassloaderHandler.java:46)
> at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle
> (InstanceContextHandler.java:58)
> at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle
> (UserTransactionHandler.java:48)
> at
> org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle
> (ComponentContextHandler.java:47)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle
> (TwistyWebAppContext.java:60)
> at org.mortbay.jetty.handler.ContextHandlerCollection.handle
> (ContextHandlerCollection.java:230)
> at org.mortbay.jetty.handler.HandlerCollection.handle
> (HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle
> (HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at org.mortbay.jetty.HttpConnection.handleRequest
> (HttpConnection.java:534)
> at org.mortbay.jetty.HttpConnection$RequestHandler.content
> (HttpConnection.java:879)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at org.mortbay.io.nio.SelectChannelEndPoint.run
> (SelectChannelEndPoint.java:409)
> at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
> at org.apache.geronimo.pool.ThreadPool
> $ContextClassLoaderRunnable.run(ThreadPool.java:344)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.codehaus.wadi.group.MessageExchangeException: No
> correlated messages received within [2000]ms
> at
> org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous
> (AbstractDispatcher.java:174)
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invokeOnPeers
> (BasicServiceInvoker.java:90)
> at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invoke
> (BasicServiceInvoker.java:69)
> at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory
> $ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:193)
> ... 49 more
>
> Not sure if I should worry about that.
>
> Many thanks for your help!
>
> Trygve
>
>
> On Tue, Nov 3, 2009 at 4:35 PM, Trygve Hardersen <trygve@...>
> wrote:
>
>
> On Mon, Nov 2, 2009 at 5:39 PM, Kevan Miller
> <kevan.miller@...> wrote:
>
> Thanks Gianny. I'd like to see this included in the Geronimo 2.2
> release. Can we look for a new WADI release, soon? Once we know the
> problem is fixed?
>
> Trygve, the sooner we get confirmation that your issue is resolved,
> the sooner we can start finalizing the 2.2 release.
>
> --kevan
>
> I've now built Geronimo using the 2.2-SNAPSHOT of WADI and
> installed it on our test environment. No obvious issues so I'll go
> ahead and deploy this to production either later this evening (EU
> time) or tomorrow. Then it needs to run for a few days before I can
> confirm if the issue has really been resolved.
>
> BTW I got this on our test system:
>
> AS-000:
> 16:23:17,773 INFO [TcpFailureDetector] Received memberDisappeared
> [org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88,
> 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10
> 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5
> 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95
> 87 65 68 ...(10)}, ]] message. Will verify.
> 16:23:17,897 INFO [TcpFailureDetector] Verification complete.
> Member still alive[org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000,
> alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79
> -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={},
> domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
>
> AS-001:
> 16:23:18,446 INFO [TcpFailureDetector] Received memberDisappeared
> [org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88,
> 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91
> -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19
> 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65
> 95 87 65 68 ...(10)}, ]] message. Will verify.
> 16:23:18,456 INFO [TcpFailureDetector] Verification complete.
> Member still alive[org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000,
> alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85
> 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)},
> command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
>
> And then:
>
> AS-000
> 16:30:02,576 INFO [ChannelInterceptorBase] memberDisappeared:tcp://
> {-64, -88, 1, 61}:4000
> 16:30:02,577 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 16:30:02,600 INFO [SimpleStateManager]
> =============================
> New Partition Balancing
> Partition Balancing
> Size [24]
> Partition[0] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[1] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[2] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[3] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[4] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[5] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[6] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[7] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[8] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[9] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[10] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[11] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[12] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[13] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[14] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[15] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[16] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[17] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[18] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[19] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[20] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[21] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[22] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> Partition[23] owned by [TribesPeer [AS-000; tcp://
> 192.168.1.60:4000]]; version [3]; mergeVersion [0]
> =============================
>
> 16:30:02,888 WARN [TcpFailureDetector] Member added, even though
> we werent notified:org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000,
> alive=2221072,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79
> -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={},
> domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]
> 16:30:02,889 INFO [ChannelInterceptorBase] memberAdded:tcp://{-64,
> -88, 1, 61}:4000
>
> AS-001
> Nothing....
>
> There is practically no load on this network. Anyway I'll try this
> with load and see what happens.
>
> Many thanks again!
>
> Trygve
>