0004215: Conflict between jersey and resin (and again, with example war)

(0004819)
olaf2010
11-04-10 11:30

Jersey does not use its init process with a "thread local" variable anymore. Since resin (and other container) do the init stuff in a different thread.

So, instead they store their stuff now in a JNDI context named:

"/com.sun.jersey.config/CDIExtension"

This causes trouble:

[10-11-04 19:22:01.920] {resin-16} javax.naming.NameNotFoundException: /com.sun.jersey.config/CDIExtension
                                       at com.caucho.naming.ContextImpl.rebind(ContextImpl.java:525)
                                       at javax.naming.InitialContext.rebind(InitialContext.java:408)
                                       at com.sun.jersey.server.impl.cdi.CDIExtension.initialize(CDIExtension.java:189)
                                       at com.sun.jersey.server.impl.cdi.CDIExtension.beforeBeanDiscovery(CDIExtension.java:257)

I have changed the name to "com.sun.jersey.config/CDIExtension", same exception.

As soon as i change the name to "CDIExtension" only, it works.

Can it be, that com.caucho.naming.ContextImpl.rebind(ContextImpl.java:525) has a problem with slashes in the name?

(0004820)
olaf2010
11-04-10 11:43

Ok, it seems, in JNDI the "/" character is special and needs to be quoted, if used. I guess then, this is a jersey bug at all.

Nonetheless the exception from resin is confusing, since its not a "NameNotFoundException", its rather the name itself, which is broken.

(0004821)
olaf2010
11-04-10 11:45

And finally, jersey project seems to be locked now. I can not even file a bug/patch there. Hm

(0004824)
ferg
11-09-10 16:34

The slash in JNDI isn't illegal, exactly. It's like a directory, and the application is supposed to create the parent context/directory.

It would be easy for us to change that behavior to automatically create the directory, but we'd need to double check the JNDI (or see if there's some reason that jersey is trying to create that context and we're not allowing it.)

(0004826)
olaf2010
11-10-10 04:07

Jersey has finally moved and i can submit bugs there

- http://java.net/jira/browse/JERSEY-601 [^]

They have an CDIExtension, which has a method:

void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event) {...}

Thats also where they store the CDIExtension instance in the JNDI context. This is their second try to workaround for something else, that doesnt work:

They tried to lookup CDIExtension in:

Object beanManager = ic.lookup("java:comp/BeanManager");

The beanManager itself is not null, but there is never an instance of CDIExtension.

(0004832)
ferg
11-12-10 10:57

That definitely looks like a Jersey bug.

From the JNDI JavaDoc: rebind() "Binds a name to an object, overwriting any existing binding. All intermediate contexts and the target context (that named by all but terminal atomic component of the name) must already exist."

The error is because Jersey never creates the "com.sun.jersey.config" component (and I can't really change Resin to use a non-conforming JNDI context.)

There is a workaround for Jersey, though. Set the following system-property in the resin.xml:

<resin ...>
...
<system-property
com.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager="true"/>

(0004834)
olaf2010
11-12-10 16:15

Thank you for the advice. But this creates the "original" NPE for which they have had to create the JNDI workaround (or former thread-local). They cant find for any obscure reason their "CDIExtension" instance in the BeanManager. So they go the way over JNDI and save the instance in that "beforeBeanDiscovery" method. Where they fail with resin, due to this rebind things.

Well, ok, i will try to change the source code, so that /com.sun.jersey.config/CDIExtension will be created as necessary. Maybe they like what they see. So far no reaction on my report there.

(0004835)
ferg
11-12-10 18:23

Please try 4.0.13, because 4.0.10 is old and the 4.0.13 release is more recent than the snapshot.

(0004836)
olaf2010
11-13-10 08:41

Good news.

With resin 4.0.13 it works again, when setting the system property:

com.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager="true"

With resin 4.0.10 it does not work. I just checked once more.

Whatever changes you guys did: Thank you.

(0004840)
ferg
11-15-10 09:12

thanks for the update. I'm closing this as fixed.

Notes
(0004819) olaf2010 11-04-10 11:30	Jersey does not use its init process with a "thread local" variable anymore. Since resin (and other container) do the init stuff in a different thread. So, instead they store their stuff now in a JNDI context named: "/com.sun.jersey.config/CDIExtension" This causes trouble: [10-11-04 19:22:01.920] {resin-16} javax.naming.NameNotFoundException: /com.sun.jersey.config/CDIExtension at com.caucho.naming.ContextImpl.rebind(ContextImpl.java:525) at javax.naming.InitialContext.rebind(InitialContext.java:408) at com.sun.jersey.server.impl.cdi.CDIExtension.initialize(CDIExtension.java:189) at com.sun.jersey.server.impl.cdi.CDIExtension.beforeBeanDiscovery(CDIExtension.java:257) I have changed the name to "com.sun.jersey.config/CDIExtension", same exception. As soon as i change the name to "CDIExtension" only, it works. Can it be, that com.caucho.naming.ContextImpl.rebind(ContextImpl.java:525) has a problem with slashes in the name?

(0004820) olaf2010 11-04-10 11:43	Ok, it seems, in JNDI the "/" character is special and needs to be quoted, if used. I guess then, this is a jersey bug at all. Nonetheless the exception from resin is confusing, since its not a "NameNotFoundException", its rather the name itself, which is broken.

(0004821) olaf2010 11-04-10 11:45	And finally, jersey project seems to be locked now. I can not even file a bug/patch there. Hm

(0004824) ferg 11-09-10 16:34	The slash in JNDI isn't illegal, exactly. It's like a directory, and the application is supposed to create the parent context/directory. It would be easy for us to change that behavior to automatically create the directory, but we'd need to double check the JNDI (or see if there's some reason that jersey is trying to create that context and we're not allowing it.)

(0004826) olaf2010 11-10-10 04:07	Jersey has finally moved and i can submit bugs there - http://java.net/jira/browse/JERSEY-601 [^] They have an CDIExtension, which has a method: void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event) {...} Thats also where they store the CDIExtension instance in the JNDI context. This is their second try to workaround for something else, that doesnt work: They tried to lookup CDIExtension in: Object beanManager = ic.lookup("java:comp/BeanManager"); The beanManager itself is not null, but there is never an instance of CDIExtension.

(0004832) ferg 11-12-10 10:57	That definitely looks like a Jersey bug. From the JNDI JavaDoc: rebind() "Binds a name to an object, overwriting any existing binding. All intermediate contexts and the target context (that named by all but terminal atomic component of the name) must already exist." The error is because Jersey never creates the "com.sun.jersey.config" component (and I can't really change Resin to use a non-conforming JNDI context.) There is a workaround for Jersey, though. Set the following system-property in the resin.xml: <resin ...> ... <system-property com.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager="true"/>

(0004834) olaf2010 11-12-10 16:15	Thank you for the advice. But this creates the "original" NPE for which they have had to create the JNDI workaround (or former thread-local). They cant find for any obscure reason their "CDIExtension" instance in the BeanManager. So they go the way over JNDI and save the instance in that "beforeBeanDiscovery" method. Where they fail with resin, due to this rebind things. Well, ok, i will try to change the source code, so that /com.sun.jersey.config/CDIExtension will be created as necessary. Maybe they like what they see. So far no reaction on my report there.

(0004835) ferg 11-12-10 18:23	Please try 4.0.13, because 4.0.10 is old and the 4.0.13 release is more recent than the snapshot.

(0004836) olaf2010 11-13-10 08:41	Good news. With resin 4.0.13 it works again, when setting the system property: com.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager="true" With resin 4.0.10 it does not work. I just checked once more. Whatever changes you guys did: Thank you.

(0004840) ferg 11-15-10 09:12	thanks for the update. I'm closing this as fixed.

Issue History
Date Modified	Username	Field	Change
09-16-10 06:48	olaf2010	New Issue
11-04-10 11:30	olaf2010	Note Added: 0004819
11-04-10 11:43	olaf2010	Note Added: 0004820
11-04-10 11:45	olaf2010	Note Added: 0004821
11-09-10 16:34	ferg	Note Added: 0004824
11-10-10 04:07	olaf2010	Note Added: 0004826
11-12-10 10:57	ferg	Note Added: 0004832
11-12-10 16:15	olaf2010	Note Added: 0004834
11-12-10 18:23	ferg	Note Added: 0004835
11-13-10 08:41	olaf2010	Note Added: 0004836
11-15-10 09:12	ferg	Note Added: 0004840
11-15-10 09:12	ferg	Assigned To	=> ferg
11-15-10 09:12	ferg	Status	new => closed
11-15-10 09:12	ferg	Resolution	open => fixed
11-15-10 09:12	ferg	Fixed in Version	=> 4.0.13

Relationships