You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Bill Barker <bi...@apache.org> on 2011/04/01 12:54:27 UTC
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
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 general@gump.apache.org.
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 Timed Out'.
For reference only, the following projects are affected by this:
- tomcat-trunk-test : Java Servlet 3.0, Java Server Pages 2.2 & Expression Languag...
Full details are available at:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were provided:
-DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar.
-DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz.
-DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz.
-DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home.
-INFO- Failed with reason build timed out
-INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs
The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html
Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 60 mins
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-01042011.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-01042011-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-01042011-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-01042011.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/srv/gump/public/worksp
ace/apache-commons/dbcp -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-*[0-9T].jar -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-01042011.jar test
[Working Directory: /srv/gump/public/workspace/tomcat-trunk]
CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv
/gump/public/workspace/tomcat-trunk/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.
jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-01042011.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-01042011.jar:/srv/gump/public/workspace/junit/dist/junit-01042011.jar
---------------------------------------------
[junit] INFO: No global web.xml found
[junit] Apr 1, 2011 10:53:33 AM org.apache.coyote.AbstractProtocolHandler start
[junit] INFO: Starting ProtocolHandler ["http-bio-8004"]
[junit] Apr 1, 2011 10:53:33 AM org.apache.coyote.AbstractProtocolHandler pause
[junit] INFO: Pausing ProtocolHandler ["http-bio-8004"]
[junit] Apr 1, 2011 10:53:34 AM org.apache.catalina.core.StandardService stopInternal
[junit] INFO: Stopping service Tomcat
[junit] Apr 1, 2011 10:53:34
[junit] AM org.apache.coyote.AbstractProtocolHandler stop
[junit] INFO: Stopping ProtocolHandler ["http-bio-8004"]
[junit] Apr 1, 2011 10:53:34 AM org.
[junit] apache.coyote.AbstractProtocolHandler destroy
[junit] INFO: Destroying ProtocolHandler ["http-bio-8004"]
[junit] Apr 1, 2011 10:53:34 AM org.apa
[junit] che.coyote.AbstractProtocolHandler init
[junit] INFO: Initializing ProtocolHandler ["http-bio-8005"]
[junit] Apr 1, 2011 10:53:34 AM org.apache.
[junit] catalina.core.StandardService startInternal
[junit] INFO: Starting service Tomcat
[junit] Apr 1, 2011 10:53:34 AM org.apache.catalina.core.Stand
[junit] ardEngine startInternal
[junit] INFO: Starting Servlet Engine: Apache Tomcat/7.0.12-dev
[junit] Apr 1, 2011 10:53:34 AM org.apache.catalina.star
[junit] tup.ContextConfig webConfig
[junit] INFO: No global web.xml found
[junit] Apr 1, 2011 10:53:34 AM org.apache.coyote.AbstractProtocolHandler star
[junit] t
[junit] INFO: Starting ProtocolHandler ["http-bio-8005"]
[junit] Apr 1, 2011 10:53:35 AM org.apache.coyote.AbstractProtocolHandler pause
[junit] INFO: Pausing ProtocolHandler ["http-bio-8005"]
[junit] Apr 1, 2011 10:53:36 AM org.apache.catalina.core.StandardService stopInternal
[junit] INFO: Stopping service Tomcat
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 92.119 sec
[junit] Apr 1, 2011 10:53:36 AM org.apache.coyote.AbstractProtocolHandler stop
[junit] INFO: Stopping ProtocolHandler ["http-bio-8005"]
[junit] Apr 1, 2
[junit] 011 10:53:36 AM org.apache.coyote.AbstractProtocolHandler destroy
[junit] INFO: Destroying ProtocolHandler ["http-bio-8005"]
[junit] Running org.apache.naming.resources.TestDirContextURLStreamHandlerFactory
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.
[junit] 059 sec
[junit] Running org.apache.naming.resources.TestNamingContext
[junit] Apr 1, 2011 10:53:38 AM org.apache.coyote.AbstractProtocolHandler init
[junit] INFO: Initializing ProtocolHandler ["http-bio-8001"]
[junit] Apr
[junit] 1, 2011 10:53:38 AM org.apache.catalina.core.StandardService startInternal
[junit] INFO: Starting service Tomcat
[junit] Apr 1, 2011 10:53:38 AM
[junit] org.apache.catalina.core.StandardEngine startInternal
[junit] INFO: Starting Servlet Engine: Apache Tomcat/7.0.12-dev
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/rss.xml
- Atom: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/atom.xml
============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 06000601042011, vmgump.apache.org:vmgump:06000601042011
Gump E-mail Identifier (unique within run) #13.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk)
failed
Posted by Mark Thomas <ma...@apache.org>.
On 01/04/2011 15:01, Konstantin Kolinko wrote:
> 2011/4/1 Mark Thomas <ma...@apache.org>:
>> On 01/04/2011 14:37, Konstantin Kolinko wrote:
>>> 2011/4/1 Mark Thomas <ma...@apache.org>:
>>
>>>> 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,
>
> 6u24 as well, probably. It is the latest,
> http://www.oracle.com/technetwork/java/javase/downloads/index.html
> and u25 is in early access,
> http://jdk6.java.net/6uNea.html
Sorry - 6u24 - I was typing too quickly.
Mark
>
>> 8-core machine.
>>
>>> Running the tests several days ago I once saw hanging in the
>>> org.apache.tomcat.jni.Library.terminate(Native Method)
>>>
>>> call during shutdown. That is with APR connector, native 1.1.20 /
>>> win32. That happened only once and was not reproducible ever since.
>>
>> Haven't seen that one yet.
>>
>> I am just testing a work-around for the hanging on shutdown issue. It
>> seems to be OK at the moment. I'll commit it if the unit tests all pass.
>>
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/4/1 Mark Thomas <ma...@apache.org>:
> On 01/04/2011 14:37, Konstantin Kolinko wrote:
>> 2011/4/1 Mark Thomas <ma...@apache.org>:
>
>>> 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,
6u24 as well, probably. It is the latest,
http://www.oracle.com/technetwork/java/javase/downloads/index.html
and u25 is in early access,
http://jdk6.java.net/6uNea.html
> 8-core machine.
>
>> Running the tests several days ago I once saw hanging in the
>> org.apache.tomcat.jni.Library.terminate(Native Method)
>>
>> call during shutdown. That is with APR connector, native 1.1.20 /
>> win32. That happened only once and was not reproducible ever since.
>
> Haven't seen that one yet.
>
> I am just testing a work-around for the hanging on shutdown issue. It
> seems to be OK at the moment. I'll commit it if the unit tests all pass.
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk)
failed
Posted by Mark Thomas <ma...@apache.org>.
On 01/04/2011 14:37, Konstantin Kolinko wrote:
> 2011/4/1 Mark Thomas <ma...@apache.org>:
>> 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,
8-core machine.
> Running the tests several days ago I once saw hanging in the
> org.apache.tomcat.jni.Library.terminate(Native Method)
>
> call during shutdown. That is with APR connector, native 1.1.20 /
> win32. That happened only once and was not reproducible ever since.
Haven't seen that one yet.
I am just testing a work-around for the hanging on shutdown issue. It
seems to be OK at the moment. I'll commit it if the unit tests all pass.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/4/4 Rainer Jung <ra...@kippdata.de>:
> 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<kn...@gmail.com>:
>>>> 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 [SHA1PRNG] took [69,367]
>>>> milliseconds.
>>
>>>> and so on in the next runs.
>>
>>>> That explains the slowness. It is good that we have this logging now.
>>
>>> I know there was some related discussion on the users list, but just
>>> in case it didn't become clear from that.
>>
>>> There is a bug in the Oracle JVM. Initialization of random number
>>> generation on Linux can block for a long time, because even if
>>> configured for using /dev/urandom it will use /dev/random. 1.6.0_24
>>> even seems to be preconfigured for using /dev/urandom on Linux, but it
>>> dows not work due to an implementation bug.
>>
>> vmgump is on 6b20 and I don't think there is anything more recent
>> available for Ubuntu 10.4 (unless we fiddle with package sources, I
>> guess).
>
> Sorry, I didn't want to indicate it is a 1.6.0_24 problem only. It's just
> that I checked the default only for 1.6.0_24. The issue is open at Oracle
> for a longer.
>
>> But you seem to be correct this is a Linux issue. On FreeBSD[1] I see
>> 140 ms.
>
> It is also not strictly reproducable in the sense that fst startup means you
> don't have the problem. You can check via open files or similar, if
> /dev/random or /dev/urandom is being used. Even when /dev/random is used due
> t the bug, sometimes there is enough entropy, sometimes not. I usually run
> into the problem when trying to start two instances in parallel. One starts
> up fast, the other blocks.
>
>>> Workaround: You can still use the system property "java.security.egd"
>>> to switch to /dev/urandom, but you have to use a value that is
>>> semantically equivalent to /dev/urandom but not stringwise
>>> identical.
>>
>> You can set system properties via<sysproperty> inside the Gump
>> descriptor and if you use
>>
>> <sysproperty name="ant.build.clonevm" value="true"/>
>>
>> Ant will make sure any system property will be passed to a new Java VM
>> that is forked as well[2] (as long as forking uses Ant's mechanisms,
>> that is).
>
> Good thing. Konstantin already added a jvmarg to our local build.xml, I
> guess it will work in Gump but also when testing standalone.
>
> It might be a nice default setting for the ASF gump, because more projects
> might run into the same unpleasant issue.
>
>> Stefan
>>
>> [1]
>> http://gump.zones.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.txt
>>
>> [2] http://ant.apache.org/manual/clonevm.html
>
> Regards,
>
> Rainer
>
With my changes to our build.xml this problem is now fixed.
https://svn.apache.org/viewvc?view=revision&revision=1088467
The last Gump run for tomcat-trunk-test was successful,
BIO + NIO tests completed in 21 mins 16 secs
Regarding tomcat-trunk-validate, the current status is
http://marc.info/?l=gump&m=130189110920329&w=2
My plan is to apply the workaround suggested by Stefan in that thread.
I tried an alternative way, but that failed as well as before.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk)
failed
Posted by Rainer Jung <ra...@kippdata.de>.
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<kn...@gmail.com>:
>>> 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 [SHA1PRNG] took [69,367] milliseconds.
>
>>> and so on in the next runs.
>
>>> That explains the slowness. It is good that we have this logging now.
>
>> I know there was some related discussion on the users list, but just
>> in case it didn't become clear from that.
>
>> There is a bug in the Oracle JVM. Initialization of random number
>> generation on Linux can block for a long time, because even if
>> configured for using /dev/urandom it will use /dev/random. 1.6.0_24
>> even seems to be preconfigured for using /dev/urandom on Linux, but it
>> dows not work due to an implementation bug.
>
> vmgump is on 6b20 and I don't think there is anything more recent
> available for Ubuntu 10.4 (unless we fiddle with package sources, I
> guess).
Sorry, I didn't want to indicate it is a 1.6.0_24 problem only. It's
just that I checked the default only for 1.6.0_24. The issue is open at
Oracle for a longer.
> But you seem to be correct this is a Linux issue. On FreeBSD[1] I see
> 140 ms.
It is also not strictly reproducable in the sense that fst startup means
you don't have the problem. You can check via open files or similar, if
/dev/random or /dev/urandom is being used. Even when /dev/random is used
due t the bug, sometimes there is enough entropy, sometimes not. I
usually run into the problem when trying to start two instances in
parallel. One starts up fast, the other blocks.
>> Workaround: You can still use the system property "java.security.egd"
>> to switch to /dev/urandom, but you have to use a value that is
>> semantically equivalent to /dev/urandom but not stringwise
>> identical.
>
> You can set system properties via<sysproperty> inside the Gump
> descriptor and if you use
>
> <sysproperty name="ant.build.clonevm" value="true"/>
>
> Ant will make sure any system property will be passed to a new Java VM
> that is forked as well[2] (as long as forking uses Ant's mechanisms,
> that is).
Good thing. Konstantin already added a jvmarg to our local build.xml, I
guess it will work in Gump but also when testing standalone.
It might be a nice default setting for the ASF gump, because more
projects might run into the same unpleasant issue.
> Stefan
>
> [1] http://gump.zones.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.txt
>
> [2] http://ant.apache.org/manual/clonevm.html
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2011-04-03, Rainer Jung wrote:
> On 02.04.2011 01:20, Konstantin Kolinko wrote:
>> 2011/4/1 Konstantin Kolinko<kn...@gmail.com>:
>> 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 [SHA1PRNG] took [69,367] milliseconds.
>> and so on in the next runs.
>> That explains the slowness. It is good that we have this logging now.
> I know there was some related discussion on the users list, but just
> in case it didn't become clear from that.
> There is a bug in the Oracle JVM. Initialization of random number
> generation on Linux can block for a long time, because even if
> configured for using /dev/urandom it will use /dev/random. 1.6.0_24
> even seems to be preconfigured for using /dev/urandom on Linux, but it
> dows not work due to an implementation bug.
vmgump is on 6b20 and I don't think there is anything more recent
available for Ubuntu 10.4 (unless we fiddle with package sources, I
guess).
But you seem to be correct this is a Linux issue. On FreeBSD[1] I see
140 ms.
> Workaround: You can still use the system property "java.security.egd"
> to switch to /dev/urandom, but you have to use a value that is
> semantically equivalent to /dev/urandom but not stringwise
> identical.
You can set system properties via <sysproperty> inside the Gump
descriptor and if you use
<sysproperty name="ant.build.clonevm" value="true"/>
Ant will make sure any system property will be passed to a new Java VM
that is forked as well[2] (as long as forking uses Ant's mechanisms,
that is).
Stefan
[1] http://gump.zones.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.txt
[2] http://ant.apache.org/manual/clonevm.html
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk)
failed
Posted by Rainer Jung <ra...@kippdata.de>.
On 02.04.2011 01:20, Konstantin Kolinko wrote:
> 2011/4/1 Konstantin Kolinko<kn...@gmail.com>:
> 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 [SHA1PRNG] took [69,367] milliseconds.
>
> and so on in the next runs.
>
> That explains the slowness. It is good that we have this logging now.
I know there was some related discussion on the users list, but just in
case it didn't become clear from that.
There is a bug in the Oracle JVM. Initialization of random number
generation on Linux can block for a long time, because even if
configured for using /dev/urandom it will use /dev/random. 1.6.0_24 even
seems to be preconfigured for using /dev/urandom on Linux, but it dows
not work due to an implementation bug.
Workaround: You can still use the system property "java.security.egd" to
switch to /dev/urandom, but you have to use a value that is semantically
equivalent to /dev/urandom but not stringwise identical. So instead of
the value proposed usually:
-Djava.security.egd=file:/dev/urandom
You can use
-Djava.security.egd=file:/dev//urandom
or
-Djava.security.egd=file:/dev/./urandom
Looking at the JVM sources one can see the reason. On Linux, when
configuring exactly for /dev/random or /dev/urandom, the JVM prefers to
use a so-called native random number generator. It initializes the
native generator with the default constructor, that always uses /dev/random.
When switching from file:/dev/urandom to something equivalent but not
identical, you finally get what you were looking for.
Oracle thinks it is not a bug, but from the bug report comments it seems
they haven’t actually looked at their code and are still only arguing
about /dev/urandom not being secure.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/4/1 Konstantin Kolinko <kn...@gmail.com>:
> 2011/4/1 Mark Thomas <ma...@apache.org>:
>> 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
>> DedicatedThreadExecutor. Taking a look now...
>>
>
> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
> Start: Fri, 01 Apr 2011 09:54:25 (UTC)
> Elapsed: 60 mins
>
> From quick glance I do not see hangs there.
>
> Last output is
>
> [junit] Running org.apache.naming.resources.TestNamingContext
> ...
> [junit] Apr 1, 2011 10:53:38 AM
> [junit] org.apache.catalina.core.StandardEngine startInternal
> [junit] INFO: Starting Servlet Engine: Apache Tomcat/7.0.12-dev
>
> The whole hour since 09:54 Tomcat was running the tests. And it is
> just the bio connector. The time used to run up to TestNamingContext
> test is about 80% of the test run for a single connector.
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 [SHA1PRNG] took [69,367] milliseconds.
and so on in the next runs.
That explains the slowness. It is good that we have this logging now.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/4/1 Mark Thomas <ma...@apache.org>:
> 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
> DedicatedThreadExecutor. Taking a look now...
>
http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html
Start: Fri, 01 Apr 2011 09:54:25 (UTC)
Elapsed: 60 mins
>From quick glance I do not see hangs there.
Last output is
[junit] Running org.apache.naming.resources.TestNamingContext
...
[junit] Apr 1, 2011 10:53:38 AM
[junit] org.apache.catalina.core.StandardEngine startInternal
[junit] INFO: Starting Servlet Engine: Apache Tomcat/7.0.12-dev
The whole hour since 09:54 Tomcat was running the tests. And it is
just the bio connector. The time used to run up to TestNamingContext
test is about 80% of the test run for a single connector.
> Tomcat hangs during shutdown.
I did not observe any issues with DedicatedThreadExecutor. All runs OK
for me. (three connectors, Win32, JDK 6u24).
Running the tests several days ago I once saw hanging in the
org.apache.tomcat.jni.Library.terminate(Native Method)
call during shutdown. That is with APR connector, native 1.1.20 /
win32. That happened only once and was not reproducible ever since.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk)
failed
Posted by Mark Thomas <ma...@apache.org>.
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
DedicatedThreadExecutor. Taking a look now...
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org