You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by zeeman <ha...@fastmail.us> on 2013/02/26 23:32:47 UTC
Tomee Parallel Deployment
Hi all,
I have a WAR that gets deployed to Tomee. To handle site's downtime
gracefully. I wanted to use Tomcat parallel deployment feature, so I can use
a maintenance war to show instead of real site's WAR. When I deployed
ROOT##001.war to tomee I get below error:
SEVERE: Unable to deploy collapsed ear in war
StandardEngine[Catalina].StandardHost[localhost].StandardContext[##001]
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:841)
at
org.apache.openejb.config.AutoConfig.resolveDestinationLinks(AutoConfig.java:582)
at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:183)
at
org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:338)
at
org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:827)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:974)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:901)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:118)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:662)
Caused by: java.net.URISyntaxException: Illegal character in fragment at
index 1: ##001
at java.net.URI$Parser.fail(URI.java:2810)
at java.net.URI$Parser.checkChars(URI.java:2983)
at java.net.URI$Parser.parse(URI.java:3029)
at java.net.URI.<init>(URI.java:577)
at java.net.URI.create(URI.java:839)
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[##0
01]]
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:662)
Caused by: org.apache.tomee.catalina.TomEERuntimeException:
java.lang.IllegalArgumentException
at
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:989)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:901)
at
org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:118)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
Caused by: java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:841)
at
org.apache.openejb.config.AutoConfig.resolveDestinationLinks(AutoConfig.java:582)
at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:183)
at
org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:338)
at
org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:827)
at
org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:974)
... 17 more
Caused by: java.net.URISyntaxException: Illegal character in fragment at
index 1: ##001
at java.net.URI$Parser.fail(URI.java:2810)
at java.net.URI$Parser.checkChars(URI.java:2983)
at java.net.URI$Parser.parse(URI.java:3029)
at java.net.URI.<init>(URI.java:577)
at java.net.URI.create(URI.java:839)
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
The fix was integrated to xbean. Didnt try but it should.
Le 10 mars 2013 08:34, "zeeman" <ha...@fastmail.us> a écrit :
> Hey,
>
> What about now? Is the fix in Tomee 1.6 snapshot?
> BTW I'll be running the WAR on Linux (prod) not Windows (dev).
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661378.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
Hey,
What about now? Is the fix in Tomee 1.6 snapshot?
BTW I'll be running the WAR on Linux (prod) not Windows (dev).
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661378.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
not yet, XBEAN guys will valid the patch under windows tomorrow only
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/6 zeeman <ha...@fastmail.us>
> hi,
>
> Is the fix available part of 1.6 snapshot if I get latest now?
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661310.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
hi,
Is the fix available part of 1.6 snapshot if I get latest now?
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661310.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
You can have a look to http://httpd.apache.org/docs/trunk/mod/mod_proxy.html
Le 27 févr. 2013 21:33, "zeeman" <ha...@fastmail.us> a écrit :
> Can you point me to some documentation for the features you mentioned? My
> app
> runs on AWS and if these features make sense I'll be more than happy to try
> them.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661064.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
Can you point me to some documentation for the features you mentioned? My app
runs on AWS and if these features make sense I'll be more than happy to try
them.
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661064.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
but with last versions you have graceful shutdown and dynamic cluster
membering...was just a pointer
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/27 zeeman <ha...@fastmail.us>
> You mean run apache httpd as proxy infront of Tomee? I have been avoid this
> option as it complicates deployments and require extra resources on
> machines.
>
> I run tomee without any proxies on port 8080, forward port 80 to 8080 for
> security. This has been working well. Less moving parts and simpler.
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661056.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
You mean run apache httpd as proxy infront of Tomee? I have been avoid this
option as it complicates deployments and require extra resources on
machines.
I run tomee without any proxies on port 8080, forward port 80 to 8080 for
security. This has been working well. Less moving parts and simpler.
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661056.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
PS: maybe look httpd new features too, for switching it can be fine
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/27 zeeman <ha...@fastmail.us>
> You understood me correctly. Looks like we should be fine. Parallel
> deployment is an awesome feature. It saves us from dealing with DNS changes
> and having multiple nodes for maintenance time.
>
> I'll update this thread next week to see if the fix is included in Tomee
> snapshot. Can you please update the xbean bug you created once everything
> is
> set? Thanks!
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661054.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
You understood me correctly. Looks like we should be fine. Parallel
deployment is an awesome feature. It saves us from dealing with DNS changes
and having multiple nodes for maintenance time.
I'll update this thread next week to see if the fix is included in Tomee
snapshot. Can you please update the xbean bug you created once everything is
set? Thanks!
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661054.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
I can't say for monday but i hope in the week
for the workflow if i understood you do:
-> webapp0 v0 -> webapp1 (with very few features) v0 -> remove webapp0 v0
-> webapp0 v1
this one works. If the remove phase is not done you have no guarantee at
all (of course it can all be done the tomee running ;).
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/27 zeeman <ha...@fastmail.us>
> So next week Mon you think patch will be in? So I know when to ask QA to
> test
> again with Tomee snapshot.
>
> Thanks for the suggestion.
>
> I'm actually never deploying the same webapp war twice (different
> versions).
> There is always one webapp war, then I deploy a maintenance war (no EJBs
> just a servlet filter) with a higher version as root context, so new users
> get a message saying the site is under maintenance and it handles HTTP 503
> status for bots/search engines.
>
> When maintenance is done, a new webapp war is deployed and all previous
> wars
> are removed. I think this keep it simple and prevent issues you mentioned.
>
> Do you see anything wrong with this approach?
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661050.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
So next week Mon you think patch will be in? So I know when to ask QA to test
again with Tomee snapshot.
Thanks for the suggestion.
I'm actually never deploying the same webapp war twice (different versions).
There is always one webapp war, then I deploy a maintenance war (no EJBs
just a servlet filter) with a higher version as root context, so new users
get a message saying the site is under maintenance and it handles HTTP 503
status for bots/search engines.
When maintenance is done, a new webapp war is deployed and all previous wars
are removed. I think this keep it simple and prevent issues you mentioned.
Do you see anything wrong with this approach?
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661050.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
the jar path is ....<war name>/.../jar name so the jar name is impacted by
it
locally it passes but i patched xbean as mentionned (hope it will be
included next week)
that said think a bit more to this feature and i think you don't want to
use it:
1) ejb can be share (jndi names) accross the instance so it will fail (jndi
name already bound)
2) it deploy version N+1 the undeploy version N -> so the version N can't
start anything unique at JVM level (start a server for instance/block a
port)
3) same kind of issue with resources.xml
4) if the deployment of v N+1 fails v N is undeployed (IIRC)
etc...
this is a wrong good idea IMO because easily breakable with updates
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/27 zeeman <ha...@fastmail.us>
> Hi,
>
> The ## is in the WAR file name, none of the jars have # in their names.
> Just
> to be sure.
>
> Would it be possible to get it fixed? When Can I try a new build? Many prod
> deployments will use parallel deployment and blocked by this. Thanks!
>
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661048.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: Tomee Parallel Deployment
Posted by zeeman <ha...@fastmail.us>.
Hi,
The ## is in the WAR file name, none of the jars have # in their names. Just
to be sure.
Would it be possible to get it fixed? When Can I try a new build? Many prod
deployments will use parallel deployment and blocked by this. Thanks!
--
View this message in context: http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037p4661048.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Tomee Parallel Deployment
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
that's linked to https://issues.apache.org/jira/browse/XBEAN-241 + some
minor other changes
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/26 zeeman <ha...@fastmail.us>
> Hi all,
>
> I have a WAR that gets deployed to Tomee. To handle site's downtime
> gracefully. I wanted to use Tomcat parallel deployment feature, so I can
> use
> a maintenance war to show instead of real site's WAR. When I deployed
> ROOT##001.war to tomee I get below error:
>
>
> SEVERE: Unable to deploy collapsed ear in war
> StandardEngine[Catalina].StandardHost[localhost].StandardContext[##001]
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:841)
> at
>
> org.apache.openejb.config.AutoConfig.resolveDestinationLinks(AutoConfig.java:582)
> at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:183)
> at
>
> org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:338)
> at
>
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:827)
> at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:974)
> at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:901)
> at
>
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:118)
> at
>
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at
>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
>
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 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:662)
> Caused by: java.net.URISyntaxException: Illegal character in fragment at
> index 1: ##001
> at java.net.URI$Parser.fail(URI.java:2810)
> at java.net.URI$Parser.checkChars(URI.java:2983)
> at java.net.URI$Parser.parse(URI.java:3029)
> at java.net.URI.<init>(URI.java:577)
> at java.net.URI.create(URI.java:839)
>
>
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[##0
> 01]]
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at
>
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 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:662)
> Caused by: org.apache.tomee.catalina.TomEERuntimeException:
> java.lang.IllegalArgumentException
> at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:989)
> at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:901)
> at
>
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:118)
> at
>
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at
>
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at
>
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
> Caused by: java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:841)
> at
>
> org.apache.openejb.config.AutoConfig.resolveDestinationLinks(AutoConfig.java:582)
> at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:183)
> at
>
> org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:338)
> at
>
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:827)
> at
>
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:974)
> ... 17 more
> Caused by: java.net.URISyntaxException: Illegal character in fragment at
> index 1: ##001
> at java.net.URI$Parser.fail(URI.java:2810)
> at java.net.URI$Parser.checkChars(URI.java:2983)
> at java.net.URI$Parser.parse(URI.java:3029)
> at java.net.URI.<init>(URI.java:577)
> at java.net.URI.create(URI.java:839)
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Tomee-Parallel-Deployment-tp4661037.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>