On 21/08/2013 15:43, Mark Thomas wrote:
> On 21/08/2013 14:20, Nick Williams wrote:
>>
>> On Aug 21, 2013, at 6:14 AM, Mark Thomas wrote:
>>
>>> I'm not exactly sure what the problem is. It looks like the WebSocket
>>> SCI is being registered twice or is running twice but I can't reproduce
>>> the
On 21/08/2013 14:20, Nick Williams wrote:
>
> On Aug 21, 2013, at 6:14 AM, Mark Thomas wrote:
>
>> I'm not exactly sure what the problem is. It looks like the WebSocket
>> SCI is being registered twice or is running twice but I can't reproduce
>> the problem. Anyone got any ideas?
>>
>> Currently
On Aug 21, 2013, at 6:14 AM, Mark Thomas wrote:
> I'm not exactly sure what the problem is. It looks like the WebSocket
> SCI is being registered twice or is running twice but I can't reproduce
> the problem. Anyone got any ideas?
>
> Currently, my plan is to add some logging to the SCI registra
I'm not exactly sure what the problem is. It looks like the WebSocket
SCI is being registered twice or is running twice but I can't reproduce
the problem. Anyone got any ideas?
Currently, my plan is to add some logging to the SCI registration code
to see what triggers each registration of each SCI
On 30/03/2012 19:41, Mark Thomas wrote:
> The Maven publishing for the new JARs still needs to be fixed.
Done.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apa
Costin broke the unit tests for Gump when the jni classes were moved to
a separate JAR. I've hopefully fixed this so we should be good to go
with the next Gump run.
The Maven publishing for the new JARs still needs to be fixed.
Mark
---
On 21/02/2012 14:49, Konstantin Kolinko wrote:
> Note that Buildbot fails as well.
>
> The error is in TestWebSocket,
> [[[
> Testcase: testSimple took 3.875 sec
> FAILED
> null
> junit.framework.AssertionFailedError
> at
> org.apache.catalina.websocket.TestWebSocket.readMessage(TestW
Note that Buildbot fails as well.
The error is in TestWebSocket,
[[[
Testcase: testSimple took 3.875 sec
FAILED
null
junit.framework.AssertionFailedError
at
org.apache.catalina.websocket.TestWebSocket.readMessage(TestWebSocket.java:149)
at
org.apache.catalina.websocket.Te
2012/1/24 Bill Barker :
> Full details are available at:
>
> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
>
The only failed test is TEST-org.apache.catalina.mbeans.TestRegistration.BIO
[1]
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/g
On 13/01/2012 12:06, Rainer Jung wrote:
> On 10.01.2012 16:28, Rainer Jung wrote:
>
> The below observation seems to be fixed now, after Mark's enhancements
> to Realms and the unit tests.
Most likely, it was moving the destruction of the ContainerBase objects
to ContainerBase.destroy() that fixe
On 10.01.2012 16:28, Rainer Jung wrote:
The below observation seems to be fixed now, after Mark's enhancements
to Realms and the unit tests.
Regards,
Rainer
One observation, unrelated to the failure we were discussion above: if I
dump all MBeans out of curiousity in the middle of TestRegist
On 10.01.2012 11:57, Konstantin Kolinko wrote:
2012/1/10 Rainer Jung:
On 10.01.2012 05:27, Konstantin Kolinko wrote:
2012/1/10 Konstantin Kolinko:
2012/1/9 Konstantin Kolinko:
2012/1/7 Rainer Jung:
Maybe enable the accesslog during testing with test.accesslog=true,
so one
can check afte
2012/1/10 Rainer Jung :
> On 10.01.2012 05:27, Konstantin Kolinko wrote:
>>
>> 2012/1/10 Konstantin Kolinko:
>>>
>>> 2012/1/9 Konstantin Kolinko:
>>
>> 2012/1/7 Rainer Jung:
>>>
>>>
>>> Maybe enable the accesslog during testing with test.accesslog=true,
>>> so one
>>> ca
On 10.01.2012 05:27, Konstantin Kolinko wrote:
2012/1/10 Konstantin Kolinko:
2012/1/9 Konstantin Kolinko:
2012/1/7 Rainer Jung:
Maybe enable the accesslog during testing with test.accesslog=true, so one
can check after the next failure whether the contents agree with your
assumption. Not sure
2012/1/10 Konstantin Kolinko :
> 2012/1/9 Konstantin Kolinko :
2012/1/7 Rainer Jung :
>
> Maybe enable the accesslog during testing with test.accesslog=true, so one
> can check after the next failure whether the contents agree with your
> assumption. Not sure, whether Gump offe
2012/1/9 Konstantin Kolinko :
>>> 2012/1/7 Rainer Jung :
Maybe enable the accesslog during testing with test.accesslog=true, so one
can check after the next failure whether the contents agree with your
assumption. Not sure, whether Gump offers access to the access log for
c
>> 2012/1/7 Rainer Jung :
>>>
>>> Maybe enable the accesslog during testing with test.accesslog=true, so one
>>> can check after the next failure whether the contents agree with your
>>> assumption. Not sure, whether Gump offers access to the access log for
>>> checking.
>>
>> +1, but needs some fi
On 07/01/2012 15:49, Konstantin Kolinko wrote:
> 2012/1/7 Mark Thomas :
>> On 07/01/2012 03:57, Bill Barker wrote:
>>> Gump Run 1107012012, vmgump.apache.org:vmgump:1107012012
>>> Gump E-mail Identifier (unique within run) #27.
>>>
>>> --
>>> Apache Gump
>>> http://gump.apache.org/ [Instanc
2012/1/7 Mark Thomas :
> On 07/01/2012 03:57, Bill Barker wrote:
>> Gump Run 1107012012, vmgump.apache.org:vmgump:1107012012
>> Gump E-mail Identifier (unique within run) #27.
>>
>> --
>> Apache Gump
>> http://gump.apache.org/ [Instance: vmgump]
>
> This is odd.
>
> Here is an extract from
On 07.01.2012 10:10, Mark Thomas wrote:
On 07/01/2012 03:57, Bill Barker wrote:
Gump Run 1107012012, vmgump.apache.org:vmgump:1107012012
Gump E-mail Identifier (unique within run) #27.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
This is odd.
Here is an extract from the
On 07/01/2012 03:57, Bill Barker wrote:
> Gump Run 1107012012, vmgump.apache.org:vmgump:1107012012
> Gump E-mail Identifier (unique within run) #27.
>
> --
> Apache Gump
> http://gump.apache.org/ [Instance: vmgump]
This is odd.
Here is an extract from the test log [1] (this will disappea
Only one test failed:
TEST-org.apache.catalina.mbeans.TestRegistration.BIO.txt.html
[[[
Testsuite: org.apache.catalina.mbeans.TestRegistration
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 1.716 sec
- Standard Error -
Jan 5, 2012 3:36:03 AM org.apache.coyote.Abstr
This one is something new
Using BIO
Testsuite: org.apache.catalina.mbeans.TestRegistration
The log is short, so I'll cite it as a whole.
[[[
Testsuite: org.apache.catalina.mbeans.TestRegistration
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 1.67 sec
- Standard Error ---
2011/10/15 Bill Barker :
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test has an issue affecting its co
2011/9/27 Bill Barker :
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test has an issue affecting its com
Comet is failing for NIO:
Testcase: testCometConnectorStop took 6.092 sec
FAILED
null
junit.framework.AssertionFailedError
at
org.apache.catalina.comet.TestCometProcessor.testCometConnectorStop(TestCometProcessor.java:164)
which means the reader thread is getting an exception. Sam
2011/9/12 Bill Barker :
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test has an issue affecting its com
On 11.09.2011 16:07, Rainer Jung wrote:
> One test failure remaining (only trunk):
>
> Testsuite: org.apache.catalina.core.TestAsyncContextImpl2
> Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.047 sec
>
> Testcase: initializationError took 0.005 sec
> Caused an ERROR
> No runnable
On 11.09.2011 14:53, Rainer Jung wrote:
> Lookslike this helps:
>
> Index: java/org/apache/catalina/core/DefaultInstanceManager.java
> ===
> --- java/org/apache/catalina/core/DefaultInstanceManager.java
> (revision 1168558)
> +++ java
Lookslike this helps:
Index: java/org/apache/catalina/core/DefaultInstanceManager.java
===
--- java/org/apache/catalina/core/DefaultInstanceManager.java
(revision 1168558)
+++ java/org/apache/catalina/core/DefaultInstanceManager.java
For trunk (!) the test failures on Gump are:
[junit] Running org.apache.catalina.core.TestAsyncContextImpl
[junit] Tests run: 32, Failures: 22, Errors: 0, Time elapsed: 60.667 sec
[junit] Running org.apache.catalina.core.TestStandardContextResources
[junit] Tests run: 4, Failures:
I found this test error last night too.
There are 3 tests in the Testfile.
The second fails 90% of executions. If the first test (sorry can't check the
name now) is set to ignore the second (now failing test) succeed every on
run.
2011/7/28 Mark Thomas
> On 28/07/2011 10:58, Konstantin Kolinko
On 28/07/2011 10:58, Konstantin Kolinko wrote:
> 2011/7/28 Bill Barker :
>> Project tomcat-trunk-test has an issue affecting its community integration.
>> This issue affects 1 projects,
>> and has been outstanding for 2 runs.
>> The current state of this project is 'Failed', with reason 'Build Fai
2011/7/28 Bill Barker :
> Project tomcat-trunk-test has an issue affecting its community integration.
> This issue affects 1 projects,
> and has been outstanding for 2 runs.
> The current state of this project is 'Failed', with reason 'Build Failed'.
> For reference only, the following projects ar
On 02/07/2011 09:52, Bill Barker wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test ha
On 01/07/2011 09:09, Bill Barker wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test ha
This is still the Comet test. I've just fixed a line-ending issue that
should enable this to get further next time.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomc
On 15.06.2011 14:49, Mark Thomas wrote:
> On 15/06/2011 13:29, Konstantin Kolinko wrote:
>> The failure happened in
>> [junit] Test org.apache.catalina.core.TestAsyncContextImpl FAILED
>>
>> when running with NIO. Running the same test with BIO was OK. The log
>> file from the test is [1].
>>
>>
On 15.06.2011 14:49, Mark Thomas wrote:
> On 15/06/2011 13:29, Konstantin Kolinko wrote:
>> The failure happened in
>> [junit] Test org.apache.catalina.core.TestAsyncContextImpl FAILED
>>
>> when running with NIO. Running the same test with BIO was OK. The log
>> file from the test is [1].
>>
>>
On 15/06/2011 13:29, Konstantin Kolinko wrote:
> The failure happened in
> [junit] Test org.apache.catalina.core.TestAsyncContextImpl FAILED
>
> when running with NIO. Running the same test with BIO was OK. The log
> file from the test is [1].
>
> [1]:
> http://vmgump.apache.org/gump/public/to
The failure happened in
[junit] Test org.apache.catalina.core.TestAsyncContextImpl FAILED
when running with NIO. Running the same test with BIO was OK. The log
file from the test is [1].
[1]:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_file/TEST-org.apache.catalina
2011/4/17 Bill Barker :
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at gene...@gump.apache.org.
>
> Project tomcat-trunk-test has an issue affecting its com
2011/4/4 Rainer Jung :
> On 04.04.2011 11:34, Stefan Bodewig wrote:
>>
>> On 2011-04-03, Rainer Jung wrote:
>>
>>> On 02.04.2011 01:20, Konstantin Kolinko wrote:
2011/4/1 Konstantin Kolinko:
In the recent run:
>>
[junit] Apr 1, 2011 9:53:27 PM
org.apache.catalina.util.
On 04.04.2011 11:34, Stefan Bodewig wrote:
On 2011-04-03, Rainer Jung wrote:
On 02.04.2011 01:20, Konstantin Kolinko wrote:
2011/4/1 Konstantin Kolinko:
In the recent run:
[junit] Apr 1, 2011 9:53:27 PM
org.apache.catalina.util.SessionIdGenerator createSecureRandom
[junit] INFO:
On 2011-04-03, Rainer Jung wrote:
> On 02.04.2011 01:20, Konstantin Kolinko wrote:
>> 2011/4/1 Konstantin Kolinko:
>> In the recent run:
>> [junit] Apr 1, 2011 9:53:27 PM
>> org.apache.catalina.util.SessionIdGenerator createSecureRandom
>> [junit] INFO: Creation of SecureRandom instance
On 02.04.2011 01:20, Konstantin Kolinko wrote:
2011/4/1 Konstantin Kolinko:
In the recent run:
[junit] Apr 1, 2011 9:53:27 PM
org.apache.catalina.util.SessionIdGenerator createSecureRandom
[junit] INFO: Creation of SecureRandom instance fo
[junit] r session ID generation using [SH
2011/4/1 Konstantin Kolinko :
> 2011/4/1 Mark Thomas :
>> On 01/04/2011 10:54, Bill Barker wrote:
>>
>>> Full details are available at:
>>>
>>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
>>
>> I'm seeing a slightly different issue when I run the unit tests.
On 01/04/2011 15:01, Konstantin Kolinko wrote:
> 2011/4/1 Mark Thomas :
>> On 01/04/2011 14:37, Konstantin Kolinko wrote:
>>> 2011/4/1 Mark Thomas :
>>
Tomcat hangs during shutdown.
>>>
>>> I did not observe any issues with DedicatedThreadExecutor. All runs OK
>>> for me. (three connectors, W
2011/4/1 Mark Thomas :
> On 01/04/2011 14:37, Konstantin Kolinko wrote:
>> 2011/4/1 Mark Thomas :
>
>>> Tomcat hangs during shutdown.
>>
>> I did not observe any issues with DedicatedThreadExecutor. All runs OK
>> for me. (three connectors, Win32, JDK 6u24).
>
> I'm seeing random hangs will all th
On 01/04/2011 14:37, Konstantin Kolinko wrote:
> 2011/4/1 Mark Thomas :
>> Tomcat hangs during shutdown.
>
> I did not observe any issues with DedicatedThreadExecutor. All runs OK
> for me. (three connectors, Win32, JDK 6u24).
I'm seeing random hangs will all three connectors. Win64, JDK 6u26,
2011/4/1 Mark Thomas :
> On 01/04/2011 10:54, Bill Barker wrote:
>
>> Full details are available at:
>>
>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
>
> I'm seeing a slightly different issue when I run the unit tests. Tomcat
> hangs during shutdown. It look
On 01/04/2011 10:54, Bill Barker wrote:
> Full details are available at:
>
> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
I'm seeing a slightly different issue when I run the unit tests. Tomcat
hangs during shutdown. It looks to be hanging in the
DedicatedTh
52 matches
Mail list logo
