[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jetty-users] Configuring Transaction Manager JOTM in jetty-env.xml - javax.naming.InvalidNameException: A flat name can only have a single component
|
Hi,
I want to configure a database connection with a transaction manager in
jetty-env.xml. But I do not succeed. My jetty-env.xml is:
It seems that
<New id="jotm" class="org.objectweb.jotm.Jotm">
<Arg type="boolean">True</Arg>
<Arg type="boolean">False</Arg>
<Call id="tm" name="getTransactionManager"></Call>
<Call id="ut" name="getUserTransaction"></Call>
</New>
causes the trouble. Whenever I leave it away the XML can be loaded.
<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
"http://jetty.mortbay.org/configure.dtd">
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<New class="org.eclipse.jetty.plus.jndi.Resource">
<Arg>jdbc/MyDataSource</Arg>
<Arg>
<New id="myds" class="org.apache.commons.dbcp.BasicDataSource">
<Set name="DriverClassName">org.hsqldb.jdbcDriver</Set>
<Set name="Url">jdbc:hsqldb:mem:.</Set>
<Set name="Username">sa</Set>
<Set name="Password"></Set>
</New>
</Arg>
</New>
<New id="jotm" class="org.objectweb.jotm.Jotm">
<Arg type="boolean">True</Arg>
<Arg type="boolean">False</Arg>
<Call id="tm" name="getTransactionManager"></Call>
<Call id="ut" name="getUserTransaction"></Call>
</New>
<New class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg>
<Arg>javax.transaction.TransactionManager</Arg>
<Arg>
<Ref id="ut"/>
</Arg>
</New>
<New id="tx" class="org.eclipse.jetty.plus.jndi.Transaction">
<Arg><Ref id="ut"/></Arg>
</New>
</Configure>
Starting jetty 7.4.0.v20110414 ...
2011-05-19 18:56:16.500:INFO::jetty-7.4.0.v20110414
18:56:23,703 INFO jotm(118) - JOTM started with a local transaction
factory which is not bound.
18:56:23,703 INFO jotm(130) - CAROL initialization
18:56:23,718 INFO ConfigurationRepository(320) - No protocols were
defined for property 'carol.protocols', trying with default protocol =
'jrmp'.
18:56:24,859 INFO jta(173) - JOTM 2.0.10
2011-05-19 18:56:25.031:WARN::Config error at <New
class="org.eclipse.jetty.plus.jndi.Resource">| <Arg/>|
<Arg>javax.transaction.TransactionManager</Arg>|
<Arg>| <Ref id="ut"/>| </Arg>| </New>
java.lang.reflect.InvocationTargetException
2011-05-19 18:56:25.046:WARN::Failed startup of context
o.m.j.p.JettyWebAppContext{/jms,file:/D:/Projects/M_at_School-Control/Code/asyncjms/jms_queue_async_client/src/main/webapp/},file:/D:/Projects/M_at_School-Control/Code/asyncjms/jms_queue_async_client/src/main/webapp/
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:775)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:377)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:311)
at
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:273)
at
org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118)
at
org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:414)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1153)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:587)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:436)
at
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:180)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:164)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:93)
at org.eclipse.jetty.server.Server.doStart(Server.java:253)
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:67)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:468)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:408)
at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:589)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by:
javax.naming.InvalidNameException: A flat name can only have a single
component
at javax.naming.NameImpl.addAll(NameImpl.java:621)
at javax.naming.CompoundName.addAll(CompoundName.java:442)
at
org.eclipse.jetty.plus.jndi.NamingEntryUtil.makeNamingEntryName(NamingEntryUtil.java:160)
at org.eclipse.jetty.plus.jndi.NamingEntry.save(NamingEntry.java:184)
at org.eclipse.jetty.plus.jndi.Resource.<init>(Resource.java:33)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:775)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:377)
at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:311)
at
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:273)
at
org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118)
at
org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:414)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1153)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:587)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:436)
at
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:180)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:164)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:226)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:93)
at org.eclipse.jetty.server.Server.doStart(Server.java:253)
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:67)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:468)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:408)
at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:589)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
2011-05-19 18:56:25.265:INFO::Started
SelectChannelConnector@0.0.0.0:9090 STARTING
Started Jetty Server
Starting scanner at interval of 10 seconds.
Thanks,
Karsten
--
Karsten Ohme
T-Systems Multimedia Solutions GmbH
Portal Technologies, Applications & Appliances
Hausanschrift: Riesaer Strasse 5, 01129 Dresden
Postanschrift: Postfach 10 02 24, 01072 Dresden
Telefon: +49 351 28 20 - 2123
Mobil: +49 160 90 54 76 80
Fax: +49 171 351 28 20 - 5116
E-Mail: karsten.ohme@xxxxxxxxxxxxx
Aufsichtsrat: Ulrich Meister (Vorsitzender)
Geschäftsführung: Peter Klingenburg, Dr. Jens Nebendahl
Handelsregister: Amtsgericht Dresden HRB 11433
Sitz der Gesellschaft: Dresden
Ust-IdNr.: DE 811 807 949