[JBoss JIRA] (WFLY-3816) ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
by Yannick Lorenzati (JIRA)
Yannick Lorenzati created WFLY-3816:
---------------------------------------
Summary: ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
Key: WFLY-3816
URL: https://issues.jboss.org/browse/WFLY-3816
Project: WildFly
Issue Type: Bug
Affects Versions: 8.1.0.Final, JBoss AS7 7.2.0.Final
Environment: Linux / Aix ; IBM JDK 1.6
Reporter: Yannick Lorenzati
Assignee: Jason Greene
Priority: Minor
I use Jboss AS 7.2.0 with IBM JDK 1.6
One of my applications try to load the security provider com.ibm.crypto.provider.IBMJCE but I got an ClassNotFoundException.
I think it’s because in the ibm.jdk module.xml we need to add the package of the security provider like this
<module xmlns="urn:jboss:module:1.1" name="ibm.jdk">
<resources>
</resources>
<dependencies>
<system export="true">
<paths>
<path name="com/ibm"/>
<path name="com/ibm/jvm"/>
<path name="com/ibm/jvm/io"/>
<path name="com/ibm/jvm/util"/>
<path name="com/ibm/match"/>
<path name="com/ibm/misc"/>
<path name="com/ibm/net"/>
<path name="com/ibm/nio"/>
<path name="com/ibm/nio/ch"/>
<path name="com/ibm/security/auth"/>
<path name="com/ibm/security/bootstrap"/>
<path name="com/ibm/security/auth/module"/>
<path name="com/ibm/security/util"/>
</paths>
</system>
</dependencies>
</module>
We need to add this
<path name="com/ibm/crypto"/>
<path name="com/ibm/crypto/provider"/>
Can't do a pull request at work, but i hope this help
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3815) Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3815?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-3815:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1103052
> Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3815
> URL: https://issues.jboss.org/browse/WFLY-3815
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Reporter: Dominik Pospisil
> Assignee: Dominik Pospisil
>
> java.lang.Exception: Http request failed.
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:423)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.testRollbackAcrossGroupsRolloutPlan(RolloutPlanTestCase.java:322)
> ...
> Caused by: java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:201)
> at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:50)
> at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:80)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:420)
> ... 43 more
> Standard Output
> [Host Controller] [0m[0m14:49:48,985 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> [Server:main-two] 14:49:49,579 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:49,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,586 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:49,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,696 INFO [org.jboss.web] (ServerService Thread Pool -- 73) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-one] 14:49:49,710 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 73) RolloutServlet initialized: 1401389389710
> [Server:main-three] 14:49:49,791 INFO [org.jboss.web] (ServerSe[Server:main-two] 14:49:49,762 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-two] 14:49:49,788 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 58) RolloutServlet initialized: 1401389389786
> [Server:test-one] 14:49:49,784 INFO [org.jboss.web] (ServerService Thread Pool -- 21) JBAS018210: Register web context: /RolloutPlanTestCase
> rvice Thread Pool -- 67) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-three] 14:49:49,804 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 67) RolloutServlet initialized: 1401389389803
> [Server:test-one] 14:49:49,820 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 21) RolloutServlet initialized: 1401389389820
> [Server:other-two] 14:49:49,891 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:49:50,826 INFO [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:other-two] 14:49:50,845 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 71) RolloutServlet initialized: 1401389390845
> [Server:main-two] 14:49:51,172 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:51,174 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:51,169 INF[Server:other-two] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> O [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:11,333 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:test-one] 14:50:11,346 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-three] 14:50:11,376 INFO [org.jboss.web] (ServerService Thread Pool -- 69) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-two] 14:50:11,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 62ms
> [Server:test-one] 14:50:11,397 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 59ms
> [Server:main-three] 14:50:11,548 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 175ms
> [Server:other-two] 14:50:11,634 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:other-two] 14:50:11,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 132ms
> [Server:main-one] 14:50:11,748 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-one] 14:50:11,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 385ms
> [Server:main-three] 14:50:12,225 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/main-three/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-three] 14:50:12,226 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:50:12,217 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/test-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:test-one] 14:50:12,218 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:12,218 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-two/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-two] 14:50:12,219 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:50:12,221 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-one] 14:50:12,223 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:50:12,237 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/other-two/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:other-two] 14:50:12,252 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Host Controller] [0m[0m14:50:12,261 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> ERROR [org.jboss.as.cli.CommandContext] {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"test-binding\")
> ]' not found"},
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3815) Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
by Dominik Pospisil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3815?page=com.atlassian.jira.plugin.... ]
Dominik Pospisil updated WFLY-3815:
-----------------------------------
Description:
java.lang.Exception: Http request failed.
at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:423)
at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.testRollbackAcrossGroupsRolloutPlan(RolloutPlanTestCase.java:322)
...
Caused by: java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:201)
at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:50)
at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:80)
at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:420)
... 43 more
Standard Output
[Host Controller] [0m[0m14:49:48,985 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
[Server:main-two] 14:49:49,579 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:test-one] 14:49:49,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:main-one] 14:49:49,586 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:main-three] 14:49:49,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:main-one] 14:49:49,696 INFO [org.jboss.web] (ServerService Thread Pool -- 73) JBAS018210: Register web context: /RolloutPlanTestCase
[Server:main-one] 14:49:49,710 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 73) RolloutServlet initialized: 1401389389710
[Server:main-three] 14:49:49,791 INFO [org.jboss.web] (ServerSe[Server:main-two] 14:49:49,762 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /RolloutPlanTestCase
[Server:main-two] 14:49:49,788 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 58) RolloutServlet initialized: 1401389389786
[Server:test-one] 14:49:49,784 INFO [org.jboss.web] (ServerService Thread Pool -- 21) JBAS018210: Register web context: /RolloutPlanTestCase
rvice Thread Pool -- 67) JBAS018210: Register web context: /RolloutPlanTestCase
[Server:main-three] 14:49:49,804 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 67) RolloutServlet initialized: 1401389389803
[Server:test-one] 14:49:49,820 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 21) RolloutServlet initialized: 1401389389820
[Server:other-two] 14:49:49,891 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:other-two] 14:49:50,826 INFO [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018210: Register web context: /RolloutPlanTestCase
[Server:other-two] 14:49:50,845 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 71) RolloutServlet initialized: 1401389390845
[Server:main-two] 14:49:51,172 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
[Server:test-one] 14:49:51,174 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
[Server:main-one] 14:49:51,169 INF[Server:other-two] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
[Server:main-three] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
O [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
[Server:main-two] 14:50:11,333 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018224: Unregister web context: /RolloutPlanTestCase
[Server:test-one] 14:50:11,346 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister web context: /RolloutPlanTestCase
[Server:main-three] 14:50:11,376 INFO [org.jboss.web] (ServerService Thread Pool -- 69) JBAS018224: Unregister web context: /RolloutPlanTestCase
[Server:main-two] 14:50:11,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 62ms
[Server:test-one] 14:50:11,397 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 59ms
[Server:main-three] 14:50:11,548 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 175ms
[Server:other-two] 14:50:11,634 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
[Server:other-two] 14:50:11,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 132ms
[Server:main-one] 14:50:11,748 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
[Server:main-one] 14:50:11,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 385ms
[Server:main-three] 14:50:12,225 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/main-three/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
[Server:main-three] 14:50:12,226 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:test-one] 14:50:12,217 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/test-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
[Server:test-one] 14:50:12,218 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:main-two] 14:50:12,218 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-two/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
[Server:main-two] 14:50:12,219 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:main-one] 14:50:12,221 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
[Server:main-one] 14:50:12,223 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Server:other-two] 14:50:12,237 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/other-two/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
[Server:other-two] 14:50:12,252 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
[Host Controller] [0m[0m14:50:12,261 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
ERROR [org.jboss.as.cli.CommandContext] {
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[
(\"socket-binding-group\" => \"standard-sockets\"),
(\"socket-binding\" => \"test-binding\")
]' not found"},
"rolled-back" => true
}
> Rare fail of org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase due to TimeoutException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3815
> URL: https://issues.jboss.org/browse/WFLY-3815
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Reporter: Dominik Pospisil
> Assignee: Dominik Pospisil
>
> java.lang.Exception: Http request failed.
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:423)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.testRollbackAcrossGroupsRolloutPlan(RolloutPlanTestCase.java:322)
> ...
> Caused by: java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:201)
> at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:50)
> at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:80)
> at org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.checkURL(RolloutPlanTestCase.java:420)
> ... 43 more
> Standard Output
> [Host Controller] [0m[0m14:49:48,985 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> [Server:main-two] 14:49:49,579 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:49,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,586 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:49,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:49,696 INFO [org.jboss.web] (ServerService Thread Pool -- 73) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-one] 14:49:49,710 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 73) RolloutServlet initialized: 1401389389710
> [Server:main-three] 14:49:49,791 INFO [org.jboss.web] (ServerSe[Server:main-two] 14:49:49,762 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-two] 14:49:49,788 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 58) RolloutServlet initialized: 1401389389786
> [Server:test-one] 14:49:49,784 INFO [org.jboss.web] (ServerService Thread Pool -- 21) JBAS018210: Register web context: /RolloutPlanTestCase
> rvice Thread Pool -- 67) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:main-three] 14:49:49,804 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 67) RolloutServlet initialized: 1401389389803
> [Server:test-one] 14:49:49,820 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 21) RolloutServlet initialized: 1401389389820
> [Server:other-two] 14:49:49,891 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:49:50,826 INFO [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018210: Register web context: /RolloutPlanTestCase
> [Server:other-two] 14:49:50,845 INFO [org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestServlet] (ServerService Thread Pool -- 71) RolloutServlet initialized: 1401389390845
> [Server:main-two] 14:49:51,172 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:test-one] 14:49:51,174 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-one] 14:49:51,169 INF[Server:other-two] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-three] 14:49:51,180 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> O [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "RolloutPlanTestCase.war" (runtime-name : "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:11,333 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:test-one] 14:50:11,346 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-three] 14:50:11,376 INFO [org.jboss.web] (ServerService Thread Pool -- 69) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-two] 14:50:11,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 62ms
> [Server:test-one] 14:50:11,397 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 59ms
> [Server:main-three] 14:50:11,548 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 175ms
> [Server:other-two] 14:50:11,634 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:other-two] 14:50:11,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 132ms
> [Server:main-one] 14:50:11,748 INFO [org.jboss.web] (ServerService Thread Pool -- 78) JBAS018224: Unregister web context: /RolloutPlanTestCase
> [Server:main-one] 14:50:11,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment RolloutPlanTestCase.war (runtime-name: RolloutPlanTestCase.war) in 385ms
> [Server:main-three] 14:50:12,225 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/main-three/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-three] 14:50:12,226 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:test-one] 14:50:12,217 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/test-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:test-one] 14:50:12,218 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-two] 14:50:12,218 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-two/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-two] 14:50:12,219 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:main-one] 14:50:12,221 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/servers/main-one/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:main-one] 14:50:12,223 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Server:other-two] 14:50:12,237 INFO [org.jboss.as.repository] (host-controller-connection-threads - 1) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/slave/data/servers/other-two/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content
> [Server:other-two] 14:50:12,252 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018558: Undeployed "RolloutPlanTestCase.war" (runtime-name: "RolloutPlanTestCase.war")
> [Host Controller] [0m[0m14:50:12,261 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014901: Content removed from location /mnt/hudson_workspace/workspace/eap-6x-as-testsuite-RHEL-matrix-OracleJDK7/378ed68b/jboss-eap-6.3-src/testsuite/domain/target/domains/CLITestSuite/master/data/content/65/679323a365c7fcc3e6453a9fa3e114cfcd7ecb/content[0m
> ERROR [org.jboss.as.cli.CommandContext] {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"test-binding\")
> ]' not found"},
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1878) Multicast discovery does not work on JDK8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1878?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1878:
--------------------------------
So if we had {{IP_MULTICAST_ALL}} set to 1, we'd get the old behavior ?
Do you know when socket option {{IP_MULTICAST_ALL}} will be supported ? JDK 8 ? (I checked; it is not in JDK 7).
In [1] I'll need to set socket option {{IP_MULTICAST_TTL}}, so I might as well also set the {{IP_MULTICAST_ALL}} option, when supported.
The question is, should 1 be the default ? I actually think that we should only receive traffic on interfaces on which we joined a multicast group, so 0 is just fine IMO.
[1] https://issues.jboss.org/browse/JGRP-1880
> Multicast discovery does not work on JDK8
> -----------------------------------------
>
> Key: JGRP-1878
> URL: https://issues.jboss.org/browse/JGRP-1878
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.12, 3.5
> Environment: OpenJDK8, OracleJDK8u40
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 3.2.14, 3.6
>
> Attachments: mcast.java
>
>
> Multicast discovery does not work on JDK8 when using different bind IP addresses. This blocks EAP certification on JDK8.
> Steps to reproduce with draw, switch to JDK8:
> {noformat}
> export IP_ADDR=127.0.0.1
> ./draw.sh
> export IP_ADDR=192.168.1.10
> ./draw.sh
> {noformat}
> Everything works when binding to the same IP address or using JDK 6 or 7. Possibly a JDK8 bug..
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1881) TimeService: provide time on request
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1881?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1881:
---------------------------
Description:
Currently the TimeService registers a task that runs every (say) 500 ms. It gets the current time and updates a field. Threads which get the time from the TimeService get the value of that field, so {{System.currentTimeMillis()}} is not called too much.
However, when no thread needs to get the time for a period of time, the TimeService nevertheless calls {{System.currentTimeMillis()}} every 500 ms, and we have an additional task in the timer.
h5. SOLUTION
* Remove that task which periodically gets the current time
* Add a {{timestamp}} field ({{System.nanoTime()}}) which gets set when {{System.currentTimeMillis()}} is called
* Add a field {{current_time}} which is set by {{System.currentTimeMillis()}}
* When a thread wants to get the current time from the TimeService, it compares the current time with the timestamp and, if 500 ms have elapsed, calls {{System.currentTimeMillis()}}, sets the timestamp and current_time fields and returns the time
* If the time elapsed since the last update is less than 500 ms, it returns {{current_time}}
There has to be synchronization around getting the current time ({{System.currentTimeMillis()}}), but this could be done with a CAS and a busy loop.
was:
Currently the TimeService registers a task that runs every (say) 500 ms. It gets the current time and updates a field. Threads which get the time from the TimeService get the value of that field, so {{System.currentTimeMillis()}} is not called too much.
However, when no thread needs to get the time for a period of time, the TimeService nevertheless calls {{System.currentTimeMillis()}} every 500 ms, and we have an additional task in the time.
h5. SOLUTION
* Remove that task which periodically gets the current time
* Add a {{timestamp}} field ({{System.nanoTime()}}) which gets set when {{System.currentTimeMillis()}} is called
* Add a field {{current_time}} which is set by {{System.currentTimeMillis()}}
* When a thread wants to get the current time from the TimeService, it compares the current time with the timestamp and, if 500 ms have elapsed, calls {{System.currentTimeMillis()}}, sets the timestamp and current_time fields and returns the time
* If the time elapsed since the last update is less than 500 ms, it returns {{current_time}}
There has to be synchronization around getting the current time ({{System.currentTimeMillis()}}), but this could be done with a CAS and a busy loop.
> TimeService: provide time on request
> ------------------------------------
>
> Key: JGRP-1881
> URL: https://issues.jboss.org/browse/JGRP-1881
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6
>
>
> Currently the TimeService registers a task that runs every (say) 500 ms. It gets the current time and updates a field. Threads which get the time from the TimeService get the value of that field, so {{System.currentTimeMillis()}} is not called too much.
> However, when no thread needs to get the time for a period of time, the TimeService nevertheless calls {{System.currentTimeMillis()}} every 500 ms, and we have an additional task in the timer.
> h5. SOLUTION
> * Remove that task which periodically gets the current time
> * Add a {{timestamp}} field ({{System.nanoTime()}}) which gets set when {{System.currentTimeMillis()}} is called
> * Add a field {{current_time}} which is set by {{System.currentTimeMillis()}}
> * When a thread wants to get the current time from the TimeService, it compares the current time with the timestamp and, if 500 ms have elapsed, calls {{System.currentTimeMillis()}}, sets the timestamp and current_time fields and returns the time
> * If the time elapsed since the last update is less than 500 ms, it returns {{current_time}}
> There has to be synchronization around getting the current time ({{System.currentTimeMillis()}}), but this could be done with a CAS and a busy loop.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1881) TimeService: provide time on request
by Bela Ban (JIRA)
Bela Ban created JGRP-1881:
------------------------------
Summary: TimeService: provide time on request
Key: JGRP-1881
URL: https://issues.jboss.org/browse/JGRP-1881
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.6
Currently the TimeService registers a task that runs every (say) 500 ms. It gets the current time and updates a field. Threads which get the time from the TimeService get the value of that field, so {{System.currentTimeMillis()}} is not called too much.
However, when no thread needs to get the time for a period of time, the TimeService nevertheless calls {{System.currentTimeMillis()}} every 500 ms, and we have an additional task in the time.
h5. SOLUTION
* Remove that task which periodically gets the current time
* Add a {{timestamp}} field ({{System.nanoTime()}}) which gets set when {{System.currentTimeMillis()}} is called
* Add a field {{current_time}} which is set by {{System.currentTimeMillis()}}
* When a thread wants to get the current time from the TimeService, it compares the current time with the timestamp and, if 500 ms have elapsed, calls {{System.currentTimeMillis()}}, sets the timestamp and current_time fields and returns the time
* If the time elapsed since the last update is less than 500 ms, it returns {{current_time}}
There has to be synchronization around getting the current time ({{System.currentTimeMillis()}}), but this could be done with a CAS and a busy loop.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-585) inconsistent behavior of & bitwise operator
by Rahul Singh (JIRA)
[ https://issues.jboss.org/browse/DROOLS-585?page=com.atlassian.jira.plugin... ]
Rahul Singh updated DROOLS-585:
-------------------------------
Description:
inconsistent behavior of & bitwise operator
after writing a rule given below
no-loop
when
f: Person(
((101 & age) != 0)
)
then
f.setFound(true);
end
after calling this several times say 100 it gives inconsistent result. Similar behavior is observed if we place bitwise '&' with bitwise '|'
was:
inconsistent behavior of & bitwise operator
after writing a rule given below
no-loop
when
f: Person(
((101 & age) != 0)
)
then
f.setFound(true);
end
after calling this several times say 100 it gives in consistent result. Similar behavior is observed if we place bitwise '&' with bitwise '|'
> inconsistent behavior of & bitwise operator
> -------------------------------------------
>
> Key: DROOLS-585
> URL: https://issues.jboss.org/browse/DROOLS-585
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.6.0.Final
> Reporter: Rahul Singh
> Assignee: Mark Proctor
>
> inconsistent behavior of & bitwise operator
> after writing a rule given below
> no-loop
> when
> f: Person(
> ((101 & age) != 0)
> )
> then
> f.setFound(true);
> end
> after calling this several times say 100 it gives inconsistent result. Similar behavior is observed if we place bitwise '&' with bitwise '|'
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1877) System.nanoTime() may be in the future
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1877?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1877:
--------------------------------
Oh, no, can't interrupt the current thread, or else this would result in a busy loop: if {{done}} is false and we have
{code:java}
catch(InterruptedException e) {
Thread.currentThread().interrupt();
}
{code}
, the loop would continue until {{done}} was false or {{wait_time}} <= 0.
Calling {{cond.wait(wait_time)}} would not wait, but throw an InterruptedException again. This would busy-loop until {{wait_time}} was <= 0.
It is OK to swallow the InterruptedException as the wait is only supposed to return from the loop when one or both conditions are met. If the stack is stopped, then cleanup code makes sure that all pending waits are stopped by setting {{done}} to true.
> System.nanoTime() may be in the future
> --------------------------------------
>
> Key: JGRP-1877
> URL: https://issues.jboss.org/browse/JGRP-1877
> Project: JGroups
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
> Code like the one below might fail:
> {code:title=Responses.waitFor()|borderStyle=solid}
> public boolean waitFor(long timeout) {
> long wait_time;
> final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
> lock.lock();
> try {
> while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
> try {
> cond.await(wait_time,TimeUnit.NANOSECONDS);
> }
> catch(InterruptedException e) {
> }
> }
> return done;
> }
> finally {
> lock.unlock();
> }
> }
> {code}
> Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month