zkn ha scritto:
Yes, the new jar together with the environment.xml change fixed the
problem. Now james starts normally without any delay.
Thank you!
Thanks to you for reporting the problem and the help in testing :-)
I hope James PMC will want to include this fix in the next 2.3.1. Stay
tuned.
Stefano
On 05.04.2007, at 20:13, Stefano Bagnara wrote:
Finally I managed to recreate the problematic environment here (james
2.3.0 and a lot of files inside the apps/james/var folder and I
reproduced it and debugged it.
Unfortunately the environment.xml changes were not enough alone, and I
had to change some phoenix internals to make it works.
I attached a binary jar of phoenix-engine.jar that you should replace
to your own (probably it is both in bin/lib and lib folders). This
works together with the environment.xml change:
----
<?xml version="1.0"?>
<server>
<classloaders default="default" version="1.0">
<classloader name="default" parent="*system*">
<entry location="./SAR-INF/classes" />
<fileset dir="./SAR-INF/lib">
<include name="*.jar" />
</fileset>
</classloader>
<predefined name="*system*" />
</classloaders>
<logs version="1.1">
...
----
Can you try it so we can confirm it actually fix your problem and we
can decide wether to include the fix in the next release or not?
Thank you,
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
