Hi Trygve,
A new WADI release, 2.1.1, has been cut which fixes the race
condition I was referring to in my previous email. Let me know if you
see other problems with.
Thanks,
Gianny
On 16/01/2009, at 4:31 AM, Trygve Hardersen wrote:
I can confirm that this solves the shutdown problem. After some
initial testing I'm not seeing other issues either, though I've not
stressed the servers yet.
I'm building a slightly customized Geronimo 2.2-SNAPSHOT so I just
updated wadiVersion to 2.2-SNAPSHOT in the main POM. I had to checkout
and build WADI trunk because some of the required dependencies could
not be found in the codehaus snapshots repository.
Many thanks for all your help, appreciate it!
Trygve
On Thu, Jan 15, 2009 at 3:20 PM, Trygve Hardersen <[email protected]>
wrote:
Cool, thanks for the quick fix.
I'm seeing other issues that look like race condititions to me, but
I've yet to find a consistent pattern.
I'll test this and let you know how it goes.
Trygve
On Thu, Jan 15, 2009 at 2:31 PM, Gianny Damour
<[email protected]> wrote:
Hi Trygve,
This was a bug and it is now fixed; I also changed the log level
as ERROR
was indeed inappropriate.
You will need to get a snapshot version of wadi-core as this was
a problem
with WADI which was not properly re-initiating replicas when
sessions were
evacuated from a node shutting down to all the remaining nodes.
I will
review more closely the re-initialisation of replicas in the case
of normal
shutdown over the week-end as there is still a problem in a very
specific
race condition (I do not think that you will be able to observe it).
You can get the snapshot there:
http://snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-
core/2.2-SNAPSHOT/wadi-core-2.2-20090115.131018-1.jar
The simplest thing is to replace
repository/org/codehaus/wadi/wadi-core/2.1/wadi-core-2.1.jar
with this snapshot version. You can also install this artefact in
your repo
with a version number higher than 2.1. and it will be transparently
picked-up instead of 2.1.
I will need to cut a release of WADI very soon as these fixes
need to be
included in G 2.2. So, you should not have to use this snapshot
for more
than 3-4 days.
Thanks,
Gianny
