Jetty

JNDI features may be enabled only for one application

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Not A Bug
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    JDK 1.6.0_10
    Jetty 7 Pre 5
    Win XP 32, Win Vista x64
  • Number of attachments :
    2

Description

It looks like JNDI works correctly only for one web application .
Steps to reproduce:
1. Try to enable jetty-plus that deploys applications from webapps-plus
2. Put 2 applications to webapps-plus (just a WEB-INF with minimal web.xml, no JNDI references)
3. Restart Jetty
4. The following is shown when second application is started:

2009-03-04 17:06:06.097::WARN: Failed startup of context org.mortbay.jetty.weba
pp.WebAppContext@754fc

{/app-b,C:\jetty/webapps-plus/app-b}

javax.naming.NamingException: This context is immutable; remaining name 'env'
at org.mortbay.naming.NamingContext.createSubcontext(NamingContext.java:
434)
at org.mortbay.naming.NamingContext.createSubcontext(NamingContext.java:
517)
at org.mortbay.jetty.plus.webapp.EnvConfiguration.createEnvContext(EnvCo
nfiguration.java:58)
at org.mortbay.jetty.plus.webapp.EnvConfiguration.configureDefaults(EnvC
onfiguration.java:101)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.jav
a:1195)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:
548)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348
)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection
.java:151)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHan
dlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection
.java:151)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:
130)
at org.mortbay.jetty.Server.doStart(Server.java:222)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:982)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.start.Main.invokeMain(Main.java:218)
at org.mortbay.start.Main.start(Main.java:564)

The same happens when deploying application via context-s, in this case declaring
<Set name="configurationClasses">
<Array id="plusConfig" type="java.lang.String">
...
</Array>
</Set>

in 2 contexts definition causes the very same bug

  1. File
    test-files.tar
    05/Mar/09 5:24 AM
    120 kB
    Jan Bartel
  2. File
    test-files-jotm.tar
    05/Mar/09 8:15 AM
    130 kB
    Jan Bartel

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jan Bartel added a comment -

Valery,

I can't reproduce this problem with jetty-7.0.pre5. I've attached a tarball with the standard jetty jndi test webapp duplicated so there are 2 instances of it, with its config files appropriately modified. Note that as the standard jndi test webapp uses some jndi entries that are server wide, I've moved them out into the etc/jetty.xml, which I've also included. Can you untar this and test it? It should just overlay onto your existing jetty-7.0.pre5 installation.

thanks
Jan

Show
Jan Bartel added a comment - Valery, I can't reproduce this problem with jetty-7.0.pre5. I've attached a tarball with the standard jetty jndi test webapp duplicated so there are 2 instances of it, with its config files appropriately modified. Note that as the standard jndi test webapp uses some jndi entries that are server wide, I've moved them out into the etc/jetty.xml, which I've also included. Can you untar this and test it? It should just overlay onto your existing jetty-7.0.pre5 installation. thanks Jan
Hide
Permalink
Valery Silaev added a comment -

Jan,

I've tried your code with clean Jetty7 Pre5 install.
I'm using JOTM, so I had to remove Atomikos entries from necessary configuration files, and can confirm that both applications works fine.

However, when I'm enabling JOTM back in jetty.xml (even without using it), then error is reproduced. The following is my JOTM config in jetty.xml:
======
<!-- Configure a Jotm instance which provides a javax.transaction.TransactionManager -->
<!-- and a javax.transaction.UserTransaction implementation. -->
<New id="jotm" class="org.objectweb.jotm.Jotm">
<Arg type="boolean">True</Arg>
<Arg type="boolean">True</Arg>
<Call id="tm" name="getTransactionManager"/>
<Call id="ut" name="getUserTransaction"/>
</New>

<!-- bind the transaction manager so the StandardXADataSource can find it -->
<!-- Note: we also need to set the name of the transaction manager on the data source itself so it knows what to look for -->
<!-- Alternatively, Stephen Winall says you can bind the UserTransaction, "ut", to javax.naming.TransactionManager which the StandardXAPoolDataSource seems to always look for -->
<New class="org.mortbay.jetty.plus.naming.Resource">
<Arg>/javax.transaction.TransactionManager</Arg>
<Arg><Ref id="tm" /></Arg>
</New>

<New class="org.mortbay.jetty.plus.naming.Resource">
<Arg>java:comp/UserTransaction</Arg>
<Arg><Ref id="ut" /></Arg>
</New>

<!-- Set up the UserTransaction impl from JOTM as the transaction manager for jetty6 -->
<New id="tx" class="org.mortbay.jetty.plus.naming.Transaction">
<Arg>
<Ref id="ut"/>
</Arg>
</New>
=====
Could you comment on config correctness or verify Jetty with JOTM?

Show
Valery Silaev added a comment - Jan, I've tried your code with clean Jetty7 Pre5 install. I'm using JOTM, so I had to remove Atomikos entries from necessary configuration files, and can confirm that both applications works fine. However, when I'm enabling JOTM back in jetty.xml (even without using it), then error is reproduced. The following is my JOTM config in jetty.xml: ====== <!-- Configure a Jotm instance which provides a javax.transaction.TransactionManager --> <!-- and a javax.transaction.UserTransaction implementation. --> <New id="jotm" class="org.objectweb.jotm.Jotm"> <Arg type="boolean">True</Arg> <Arg type="boolean">True</Arg> <Call id="tm" name="getTransactionManager"/> <Call id="ut" name="getUserTransaction"/> </New> <!-- bind the transaction manager so the StandardXADataSource can find it --> <!-- Note: we also need to set the name of the transaction manager on the data source itself so it knows what to look for --> <!-- Alternatively, Stephen Winall says you can bind the UserTransaction, "ut", to javax.naming.TransactionManager which the StandardXAPoolDataSource seems to always look for --> <New class="org.mortbay.jetty.plus.naming.Resource"> <Arg>/javax.transaction.TransactionManager</Arg> <Arg><Ref id="tm" /></Arg> </New> <New class="org.mortbay.jetty.plus.naming.Resource"> <Arg>java:comp/UserTransaction</Arg> <Arg><Ref id="ut" /></Arg> </New> <!-- Set up the UserTransaction impl from JOTM as the transaction manager for jetty6 --> <New id="tx" class="org.mortbay.jetty.plus.naming.Transaction"> <Arg> <Ref id="ut"/> </Arg> </New> ===== Could you comment on config correctness or verify Jetty with JOTM?
Hide
Permalink
Jan Bartel added a comment -

Sheesh, JOTM is really difficult to set up! Anyway, here's the setup. I'll document this on the jetty wiki JOTM page.

regards
Jan

Show
Jan Bartel added a comment - Sheesh, JOTM is really difficult to set up! Anyway, here's the setup. I'll document this on the jetty wiki JOTM page. regards Jan
Hide
Permalink
Jan Bartel added a comment -

Valery, I've closed the issue, hopefully the config files I sent you will sort you out.
cheers
Jan

Show
Jan Bartel added a comment - Valery, I've closed the issue, hopefully the config files I sent you will sort you out. cheers Jan
Hide
Permalink
Valery Silaev added a comment -

Jan,

Verified – your JOTM configuration works perfectly, no more JNDI-related bugs.
So the issue was indeed caused by the fact that JOTM configuration for Jetty 6 may not be re-applied to Jetty 7 "as is"

Thank you for support.

Show
Valery Silaev added a comment - Jan, Verified – your JOTM configuration works perfectly, no more JNDI-related bugs. So the issue was indeed caused by the fact that JOTM configuration for Jetty 6 may not be re-applied to Jetty 7 "as is" Thank you for support.

People

  • Assignee:
    Jan Bartel
    Reporter:
    Valery Silaev
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: