|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [jbehave-dev] [jira] (JBEHAVE-927) Disable Tim... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-927) Disabl... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-927) Disabl... Sebastian Sickelmann (JIRA)
The specific assumption should work (at least for the ibm-jvm and sun-jvm since version 5)
http://docs.oracle.com/javase/6/docs/technotes/guides/jpda/conninv.html#Invocation
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaha%2Fjpdebuga.htm
Yes i can manually set timeout to MAX_VALUE but it's a "trick" which i usually implement
to support the "not so smart part(Mr. Hyde)" inside me. Normally i implement this
trick in a smart moment(Dr. Jekyll) with the foreseen that i(Mr.Hyde) missed the
change and check MAX_VALUE into version control and head-up the build-server/test-server
in the datacenter during nightly-build/test.