subject:"\[VOTE\] Release Apache Tomcat 6.0.52"

Re: [CANCEL][VOTE] Release Apache Tomcat 6.0.52

2017-04-02 Thread Violeta Georgieva

Hi,

2017-03-28 22:38 GMT+03:00 Violeta Georgieva :
>
> The proposed Apache Tomcat 6.0.52 release is now available for voting.
>
> Note: This is the last Tomcat 6 release.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1129/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/
>
> The proposed 6.0.52 release is:
> [X] Broken - do not release
> [ ] Stable - go ahead and release as 6.0.52 Stable

I'm cancelling the vote because of the issue reported by Rainer.

Regards,
Violeta

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-04-01 Thread Rainer Jung


Am 31.03.2017 um 20:39 schrieb Violeta Georgieva:

Hi,

2017-03-31 20:53 GMT+03:00 Rainer Jung :


Am 31.03.2017 um 16:09 schrieb Violeta Georgieva:


Hi,

2017-03-31 0:55 GMT+03:00 Rainer Jung :





I do not see problems on Windows OS, I'm going to test on Ubuntu
One question: Do you experience this issue only with 6.0.52? What about
0.6.51?



I have to try it. It did not happen in 6.0.50. I'll try with 51 and let

you know but probably only tomorrow.

I succeeded to reproduce it on Windows and Ubuntu.
It is happening only with this version 6.0.52.

I'm working on a patch.


Thanks, great. I can of course retest once you have a proposed patch for 
either 6.0.x or tcnative.


Regards,

Rainer


Regards,
Violeta


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-31 Thread Violeta Georgieva

Hi,

2017-03-31 20:53 GMT+03:00 Rainer Jung :
>
> Am 31.03.2017 um 16:09 schrieb Violeta Georgieva:
>>
>> Hi,
>>
>> 2017-03-31 0:55 GMT+03:00 Rainer Jung :
>>>
>>>
>>
>> I do not see problems on Windows OS, I'm going to test on Ubuntu
>> One question: Do you experience this issue only with 6.0.52? What about
>> 0.6.51?
>
>
> I have to try it. It did not happen in 6.0.50. I'll try with 51 and let
you know but probably only tomorrow.

I succeeded to reproduce it on Windows and Ubuntu.
It is happening only with this version 6.0.52.

I'm working on a patch.

Regards,
Violeta

>> Thanks a lot,
>
>
> Thanks to you!
>
>
> Rainer
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-31 Thread Rainer Jung


Am 31.03.2017 um 16:09 schrieb Violeta Georgieva:

Hi,

2017-03-31 0:55 GMT+03:00 Rainer Jung :




I do not see problems on Windows OS, I'm going to test on Ubuntu
One question: Do you experience this issue only with 6.0.52? What about
0.6.51?


I have to try it. It did not happen in 6.0.50. I'll try with 51 and let 
you know but probably only tomorrow.



Thanks a lot,


Thanks to you!

Rainer

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-31 Thread Violeta Georgieva

Hi,

2017-03-31 0:55 GMT+03:00 Rainer Jung :
>

I do not see problems on Windows OS, I'm going to test on Ubuntu
One question: Do you experience this issue only with 6.0.52? What about
0.6.51?

Thanks a lot,
Violeta

> Using gdb I see:
>
> Case 1:
>
> #7  impl_pollset_remove (pollset=0xeebf68, descriptor=0xb377f6a4) at
poll/unix/port.c:283
> fd = 
> ep = 
> rv = 0
> res = 
> err = 0
> found = 
> #8  0xfaddfcdc in apr_pollset_remove (pollset=0xeebf68,
descriptor=descriptor@entry=0xb377f6a4) at poll/unix/pollset.c:343
> No locals.
> #9  0xfaed4b88 in Java_org_apache_tomcat_jni_Poll_maintain (e=0x659884,
o=, pollset=, set=0xb377f82c,
remove=) at src/poll.c:484
> fd = {p = 0x0, desc_type = APR_POLL_SOCKET, reqevents = 5,
rtnevents = 0, desc = {f = 0x0, s = 0x0}, client_data = 0xe527b8}
> s = 
> p = 0x1157648
> i = 0
> num = 1
> now = 
> ep = 
> ip = 
>
> (gdb) print *pollset
> $1 = {pool = 0xeebf28, nelts = 0, nalloc = 8193, flags = 6, wakeup_pipe =
{0x1157558, 0x11575a8}, wakeup_pfd = {p = 0xeebf28, desc_type =
APR_POLL_FILE, reqevents = 1,
> rtnevents = -16516, desc = {f = 0x1157558, s = 0x1157558},
client_data = 0xeebf7c}, p = 0xeebfa0, provider = 0xfadf8838}
> (gdb) print *descriptor
> $2 = {p = 0x0, desc_type = APR_POLL_SOCKET, reqevents = 5, rtnevents = 0,
desc = {f = 0x0, s = 0x0}, client_data = 0xe527b8}
> (gdb) print *pollset->pool
> $3 = {parent = 0x6557d0, child = 0x0, sibling = 0x0, ref = 0x13b8c60,
cleanups = 0x1157638, free_cleanups = 0x0, allocator = 0x319d68,
subprocesses = 0x0, abort_fn = 0,
>   user_data = 0x0, tag = 0x0, active = 0xde0a50, self = 0xeebf10,
self_first_avail = 0xeebf68 "", pre_cleanups = 0x0}
>
>
> So we crash here:
>
> 282 if (descriptor->desc_type == APR_POLL_SOCKET) {
> => 283 fd = descriptor->desc.s->socketdes;
> 284 }
> ...
>
> because descriptor->desc.s is NULL.
>
>
> Case 2:
>
> #8  0xfadd8980 in allocator_free (node=0xb8f170, allocator=0x2d8238) at
memory/unix/apr_pools.c:370
> freelist = 0x0
> max_index = 
> max_free_index = 
> next = 
> index = 
> current_free_index = 
> #9  apr_pool_destroy (pool=0xb8f188) at memory/unix/apr_pools.c:856
> active = 0xb8f170
> allocator = 0x2d8238
>
> (gdb) print *node
> $2 = {next = 0x0, ref = 0xb8f170, index = 0, free_index = 1465,
first_avail = 0x0, endp = 0xb91170 ""}
> (gdb) print *allocator
> $1 = {max_index = 7756680, max_free_index = 1601139303,
current_free_index = 0, mutex = 0x6368655f, owner = 0x0, free =
{0x61745f6a, 0x0, 0x72726f72, 0x5f737472, 0x6572726f,
> 0x7200, 0x4, 0x7a8, 0x, 0x0, 0x6, 0xb91b20, 0x7,
0x765b88, 0x, 0x0, 0x9, 0x, 0x, 0xa}}
> (gdb) print *allocator->mutex
> Cannot access memory at address 0x6368655f
>
>
> So we crash here:
>
>  369 if (allocator->mutex)
> =>  370 apr_thread_mutex_lock(allocator->mutex);
>
> since the mutex is already invalid.
>
>
> Case 3:
>
> #8  0xfadd8980 in allocator_free (node=0x5bd138, allocator=0xd7f138) at
memory/unix/apr_pools.c:370
> freelist = 0x0
> max_index = 
> max_free_index = 
> next = 
> index = 
> current_free_index = 
> #9  apr_pool_destroy (pool=0x5bd150) at memory/unix/apr_pools.c:856
> active = 0x5bd138
> allocator = 0xd7f138
>
> (gdb) print *node
> $1 = {next = 0x6d1bd8, ref = 0x5bd138, index = 0, free_index = 65,
first_avail = 0xf24cf8 "", endp = 0x5bf138 ""}
> (gdb) print *allocator
> $2 = {max_index = 16381824, max_free_index = 1601139303,
current_free_index = 6773064, mutex = 0x6368655f, owner = 0x87cf60, free =
{0x61745f6a, 0x0, 0x72726f72, 0x5f737472,
> 0x6572726f, 0x72000c0c, 0xc0c0c01, 0x30, 0x1010100, 0x0, 0x0,
0x675948, 0x59b70002, 0x706e10, 0x1204b600, 0x0, 0x5b60006, 0xb700072a,
0x1bb50008, 0xd7f130}}
> (gdb) print *allocator->mutex
> Cannot access memory at address 0x6368655f
>
>
> So the same as Case 2.
>
>
> Case 4:
>
> Not easily analyzable with gdb.
>
> Regards,
>
> Rainer
>
>
>
>
> Am 30.03.2017 um 23:37 schrieb Rainer Jung:
>>
>> Am 28.03.2017 um 21:38 schrieb Violeta Georgieva:
>>>
>>> The proposed Apache Tomcat 6.0.52 release is now available for voting.
>>>
>>> Note: This is the last Tomcat 6 release.
>>>
>>> It can be obtained from:
>>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
>>> The Maven staging repo is:
>>> https://repository.apache.org/content/repositories/orgapachetomcat-1129/
>>> The svn tag is:
>>> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/
>>>
>>> The proposed 6.0.52 release is:
>>> [ ] Broken - do not release
>>> [ ] Stable - go ahead and release as 6.0.52 Stable
>>
>>
>> I see JVM crashes in APR:
>>
>> org.apache.catalina.connector.TestSendFile
>>  testSendFile
>> org.apache.catalina.core.TestApplicationContext
>>

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-30 Thread Rainer Jung


Using gdb I see:

Case 1:

#7  impl_pollset_remove (pollset=0xeebf68, descriptor=0xb377f6a4) at 
poll/unix/port.c:283

fd = 
ep = 
rv = 0
res = 
err = 0
found = 
#8  0xfaddfcdc in apr_pollset_remove (pollset=0xeebf68, 
descriptor=descriptor@entry=0xb377f6a4) at poll/unix/pollset.c:343

No locals.
#9  0xfaed4b88 in Java_org_apache_tomcat_jni_Poll_maintain (e=0x659884, 
o=, pollset=, set=0xb377f82c, 
remove=) at src/poll.c:484
fd = {p = 0x0, desc_type = APR_POLL_SOCKET, reqevents = 5, 
rtnevents = 0, desc = {f = 0x0, s = 0x0}, client_data = 0xe527b8}

s = 
p = 0x1157648
i = 0
num = 1
now = 
ep = 
ip = 

(gdb) print *pollset
$1 = {pool = 0xeebf28, nelts = 0, nalloc = 8193, flags = 6, wakeup_pipe 
= {0x1157558, 0x11575a8}, wakeup_pfd = {p = 0xeebf28, desc_type = 
APR_POLL_FILE, reqevents = 1,
rtnevents = -16516, desc = {f = 0x1157558, s = 0x1157558}, 
client_data = 0xeebf7c}, p = 0xeebfa0, provider = 0xfadf8838}

(gdb) print *descriptor
$2 = {p = 0x0, desc_type = APR_POLL_SOCKET, reqevents = 5, rtnevents = 
0, desc = {f = 0x0, s = 0x0}, client_data = 0xe527b8}

(gdb) print *pollset->pool
$3 = {parent = 0x6557d0, child = 0x0, sibling = 0x0, ref = 0x13b8c60, 
cleanups = 0x1157638, free_cleanups = 0x0, allocator = 0x319d68, 
subprocesses = 0x0, abort_fn = 0,
  user_data = 0x0, tag = 0x0, active = 0xde0a50, self = 0xeebf10, 
self_first_avail = 0xeebf68 "", pre_cleanups = 0x0}



So we crash here:

282 if (descriptor->desc_type == APR_POLL_SOCKET) {
=> 283 fd = descriptor->desc.s->socketdes;
284 }
...

because descriptor->desc.s is NULL.


Case 2:

#8  0xfadd8980 in allocator_free (node=0xb8f170, allocator=0x2d8238) at 
memory/unix/apr_pools.c:370

freelist = 0x0
max_index = 
max_free_index = 
next = 
index = 
current_free_index = 
#9  apr_pool_destroy (pool=0xb8f188) at memory/unix/apr_pools.c:856
active = 0xb8f170
allocator = 0x2d8238

(gdb) print *node
$2 = {next = 0x0, ref = 0xb8f170, index = 0, free_index = 1465, 
first_avail = 0x0, endp = 0xb91170 ""}

(gdb) print *allocator
$1 = {max_index = 7756680, max_free_index = 1601139303, 
current_free_index = 0, mutex = 0x6368655f, owner = 0x0, free = 
{0x61745f6a, 0x0, 0x72726f72, 0x5f737472, 0x6572726f,
0x7200, 0x4, 0x7a8, 0x, 0x0, 0x6, 0xb91b20, 0x7, 
0x765b88, 0x, 0x0, 0x9, 0x, 0x, 0xa}}

(gdb) print *allocator->mutex
Cannot access memory at address 0x6368655f


So we crash here:

 369 if (allocator->mutex)
=>  370 apr_thread_mutex_lock(allocator->mutex);

since the mutex is already invalid.


Case 3:

#8  0xfadd8980 in allocator_free (node=0x5bd138, allocator=0xd7f138) at 
memory/unix/apr_pools.c:370

freelist = 0x0
max_index = 
max_free_index = 
next = 
index = 
current_free_index = 
#9  apr_pool_destroy (pool=0x5bd150) at memory/unix/apr_pools.c:856
active = 0x5bd138
allocator = 0xd7f138

(gdb) print *node
$1 = {next = 0x6d1bd8, ref = 0x5bd138, index = 0, free_index = 65, 
first_avail = 0xf24cf8 "", endp = 0x5bf138 ""}

(gdb) print *allocator
$2 = {max_index = 16381824, max_free_index = 1601139303, 
current_free_index = 6773064, mutex = 0x6368655f, owner = 0x87cf60, free 
= {0x61745f6a, 0x0, 0x72726f72, 0x5f737472,
0x6572726f, 0x72000c0c, 0xc0c0c01, 0x30, 0x1010100, 0x0, 0x0, 
0x675948, 0x59b70002, 0x706e10, 0x1204b600, 0x0, 0x5b60006, 0xb700072a, 
0x1bb50008, 0xd7f130}}

(gdb) print *allocator->mutex
Cannot access memory at address 0x6368655f


So the same as Case 2.


Case 4:

Not easily analyzable with gdb.

Regards,

Rainer



Am 30.03.2017 um 23:37 schrieb Rainer Jung:

Am 28.03.2017 um 21:38 schrieb Violeta Georgieva:

The proposed Apache Tomcat 6.0.52 release is now available for voting.

Note: This is the last Tomcat 6 release.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1129/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/

The proposed 6.0.52 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 6.0.52 Stable


I see JVM crashes in APR:

org.apache.catalina.connector.TestSendFile
 testSendFile
org.apache.catalina.core.TestApplicationContext
 testGetRequestDispatcherNullPath02
org.apache.catalina.core.TestApplicationHttpRequest testMergeQueryString02
org.apache.catalina.startup.TestTomcat testSingleWebapp

all result in:

Caused an ERROR
Forked Java VM exited abnormally. Please note the time in the report
does not reflect the time until the VM exit.
junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
Please note the time in the report does not reflect the time until the
VM exit.

I'd say they happen during shutdown.

Here are

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-30 Thread Rainer Jung


Am 28.03.2017 um 21:38 schrieb Violeta Georgieva:

The proposed Apache Tomcat 6.0.52 release is now available for voting.

Note: This is the last Tomcat 6 release.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1129/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/

The proposed 6.0.52 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 6.0.52 Stable


I see JVM crashes in APR:

org.apache.catalina.connector.TestSendFile
 testSendFile
org.apache.catalina.core.TestApplicationContext
 testGetRequestDispatcherNullPath02
org.apache.catalina.core.TestApplicationHttpRequest testMergeQueryString02
org.apache.catalina.startup.TestTomcat testSingleWebapp

all result in:

Caused an ERROR
Forked Java VM exited abnormally. Please note the time in the report 
does not reflect the time until the VM exit.
junit.framework.AssertionFailedError: Forked Java VM exited abnormally. 
Please note the time in the report does not reflect the time until the 
VM exit.


I'd say they happen during shutdown.

Here are the stacks of the crashing threads:

Crash 1:

...
 --- called from signal handler with signal 11 (SIGSEGV) ---
 faddfdb0 impl_pollset_remove (eebf68, b377f6a4, 1585, d7403c92, 
eebfa0, eebf68) + 1c

 faddfcd4 apr_pollset_remove (eebf68, b377f6a4, 54bf0, 51add715, 0, 0) + 10
 faed4b80 Java_org_apache_tomcat_jni_Poll_maintain (1, 0, 659884, 
1157648, b377f82c, 0) + 160

 f8c0c280 * org/apache/tomcat/jni/Poll.maintain(J[JZ)I+-27472
 f8c0c224 * org/apache/tomcat/jni/Poll.maintain(J[JZ)I+0
 f8c058b8 * org/apache/tomcat/util/net/AprEndpoint$Poller.run()V+659 
(line 1612)

...

or from the hs_err file:

Current thread (0x006597c8):  JavaThread 
"http-127.0.0.1-auto-1-Poller-0" daemon [_thread_in_native, id=14]


C  [libapr-1.so.0+0x1fdb0]
C  [libapr-1.so.0+0x1fcdc]  apr_pollset_remove+0x18
C  [libtcnative-1.so.0.2.12+0x14b88] 
Java_org_apache_tomcat_jni_Poll_maintain+0x168

j  org.apache.tomcat.jni.Poll.maintain(J[JZ)I+38064
j  org.apache.tomcat.jni.Poll.maintain(J[JZ)I+0
j  org.apache.tomcat.util.net.AprEndpoint$Poller.run()V+659

Log:

[junit] Running org.apache.catalina.connector.TestSendFile
[junit] Mar 30, 2017 12:40:13 PM 
org.apache.catalina.startup.LoggingBaseTest setUp

[junit] INFO: Starting test case [testSendFile]
[junit] Created file:/var/tmp/testSendFile-1490870414108-0.txt with 
10 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414168-1.txt with 
20 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414185-2.txt with 
30 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414210-3.txt with 
40 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414222-4.txt with 
50 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414236-5.txt with 
60 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414254-6.txt with 
70 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414356-7.txt with 
80 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414376-8.txt with 
90 bytes.
[junit] Created file:/var/tmp/testSendFile-1490870414443-9.txt with 
100 bytes.
[junit] Mar 30, 2017 12:40:14 PM 
org.apache.catalina.core.AprLifecycleListener init
[junit] INFO: Loaded APR based Apache Tomcat Native library 1.2.12 
using APR version 1.5.2.
[junit] Mar 30, 2017 12:40:14 PM 
org.apache.catalina.core.AprLifecycleListener init
[junit] INFO: APR capabilities: IPv6 [true], sendfile [true], 
accept filters [false], random [true].
[junit] Mar 30, 2017 12:40:14 PM 
org.apache.catalina.core.AprLifecycleListener initializeSSL
[junit] INFO: OpenSSL successfully initialized with version OpenSSL 
1.0.2k  26 Jan 2017
[junit] Mar 30, 2017 12:40:15 PM 
org.apache.coyote.http11.Http11AprProtocol init
[junit] INFO: Initializing Coyote HTTP/1.1 on 
http-127.0.0.1-auto-1-56737
[junit] Mar 30, 2017 12:40:15 PM 
org.apache.catalina.core.StandardService start

[junit] INFO: Starting service Tomcat
[junit] Mar 30, 2017 12:40:15 PM 
org.apache.catalina.core.StandardEngine start

[junit] INFO: Starting Servlet Engine: Apache Tomcat/6.0.52
[junit] Mar 30, 2017 12:40:17 PM 
org.apache.coyote.http11.Http11AprProtocol start

[junit] INFO: Starting Coyote HTTP/1.1 on http-127.0.0.1-auto-1-56737
[junit] Server Wrote 10 bytes in 8 ms.
[junit] Client received 10 bytes in 238 ms.
[junit] #
[junit] # An unexpected error has been detected by HotSpot Virtual 
Machine:

[junit] #
[junit] #  SIGSEGV (0xb) at pc=0xfaddfdb0, pid=24546, tid=14
[junit] #
[junit] # Java VM: Java HotSpot(TM) Server VM (1.5.0_22-b03 mixed mode)
[junit] # Problematic frame:
[junit] # C  [libapr-1.so.0+0x1fdb0]
[junit] #
[junit] # An error report file with more

Re: [VOTE] Release Apache Tomcat 6.0.52

2017-03-30 Thread Violeta Georgieva

2017-03-28 22:38 GMT+03:00 Violeta Georgieva :
>
> The proposed Apache Tomcat 6.0.52 release is now available for voting.
>
> Note: This is the last Tomcat 6 release.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1129/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/
>
> The proposed 6.0.52 release is:
> [ ] Broken - do not release
[X] Stable - go ahead and release as 6.0.52 Stable

Regards,
Violeta

[VOTE] Release Apache Tomcat 6.0.52

2017-03-28 Thread Violeta Georgieva

The proposed Apache Tomcat 6.0.52 release is now available for voting.

Note: This is the last Tomcat 6 release.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-6/v6.0.52/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1129/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_52/

The proposed 6.0.52 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 6.0.52 Stable

Regards,
Violeta

Re: [CANCEL][VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

Re: [VOTE] Release Apache Tomcat 6.0.52

[VOTE] Release Apache Tomcat 6.0.52

9 matches

Site Navigation

Mail list logo

Footer information