Found two bugs in v3tp2.
1) Grizzlyproxy bug?
When starting v3tp2 there no check if the ports specified in server.xml are
already in use. Server starts with no errors being thrown (whereas v2ur2
will correctly state " Domain domain1 failed to startup. There is a conflict
on port 8080. Please check the server log for more details.)
While updating might wanna check also if there are no port conflict on any
of the other ports - v2ur2 only complains about port 8080, while actually
all ports needed (4848, 8181 and 8686 are in already in use)
2) context root on port 4848?
context root for admin console should be / on port 4848, whereas in v3tp2
one would have to specify /admin in the url.
As I said these exist in v3tp2. Will only file bug report if exists in
nightly build / build from trunk. No time today though. Maybe someone else
cares to check already ? (-> survivant , your build should be finished by
now? ;)
Wim
-----Original Message-----
From: Survivant 00 [mailto:survivant00_at_gmail.com]
Sent: donderdag 21 augustus 2008 15:45
To: quality_at_glassfish.dev.java.net
Subject: Re: where are the v3 prelude nightly builds ?
good question.
now I'm building it myself from the trunk. take 15 min to build.
mvn -U -cpu clean install
2008/8/21 Wim Verreycken <wim_at_pizzastop.be>
Thanks,
Wim