[JBoss JIRA] (WFLY-5387) Upgrade Narayana to 5.2.4.Final
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5387?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5387:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Upgrade Narayana to 5.2.4.Final
> -------------------------------
>
> Key: WFLY-5387
> URL: https://issues.jboss.org/browse/WFLY-5387
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Transactions
> Affects Versions: 10.0.0.CR1
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 10.0.0.Final
>
>
> Includes miscellaneous bug fixes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5176) Some tests end with Security Exception after login with security manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5176?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5176:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Some tests end with Security Exception after login with security manager
> ------------------------------------------------------------------------
>
> Key: WFLY-5176
> URL: https://issues.jboss.org/browse/WFLY-5176
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Ondrej Kotek
> Fix For: 10.0.0.Final
>
>
> *Description of problem:*
> Some tests end with Security Exception after login with security manager.
> *Affected tests found so far:*
> * org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase
> * org.jboss.as.test.integration.ejb.security.AuthenticationTestCase
> * org.jboss.as.test.integration.ejb.security.EJBInWarDefaultSecurityDomainTestCase#testSecurityOnBeanInAbsenceOfExplicitSecurityDomain
> * org.jboss.as.test.integration.ejb.security.LifecycleTestCase
> * org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase#testDDOverride
> * org.jboss.as.test.integration.ejb.security.asynchronous.AsynchronousSecurityTestCase
> * org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsDefaultAllowedTestCase
> * org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsTestCase
> * org.jboss.as.test.integration.ejb.security.rolelink.SecurityRoleLinkTestCase#testIsCallerInRole
> * org.jboss.as.test.integration.ejb.security.runas.RunAsTestCase
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=AnnotationAuthorizationTestCase
> *Actual results:*
> {noformat}
> javax.security.auth.login.LoginException: Security Exception
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:841)
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> at javax.security.auth.login.LoginContext.login(LoginContext.java:588)
> at org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase.testRolesAllowedOverriden_User2(AnnotationAuthorizationTestCase.java:187)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4960) Discard interceptors during messaging migration
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4960?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-4960:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Discard interceptors during messaging migration
> -----------------------------------------------
>
> Key: WFLY-4960
> URL: https://issues.jboss.org/browse/WFLY-4960
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Affects Versions: 10.0.0.Alpha5
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.Final
>
>
> the messaging subsystem :migrate operation must discard any incoming or outgoing interceptors that are defined for hornetq-server resources.
> The base type of interceptors have changed in Artemis (at least their packages) and HornetQ-based interceptors will not be loaded by Artemis.
> Discard them during the :migrate operation with a warning that their base type must be changed and they must be provided in their own module (once WFLY-4867 is done)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5183) VaultSystemPropertyOnServerStartTestCase ends with "Internal Server Error" with security manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5183?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5183:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> VaultSystemPropertyOnServerStartTestCase ends with "Internal Server Error" with security manager
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-5183
> URL: https://issues.jboss.org/browse/WFLY-5183
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Ondrej Kotek
> Fix For: 10.0.0.Final
>
>
> *Description of problem:*
> VaultSystemPropertyOnServerStartTestCase ends with "Internal Server Error" with security manager
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.noSmoke -Dts.manualmode -Dtest=VaultSystemPropertyOnServerStartTestCase
> *Actual results:*
> {noformat}
> java.util.concurrent.ExecutionException: java.io.IOException: HTTP Status 500 Response: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: HTTP Status 500 Response: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.jboss.as.test.integration.common.HttpRequest.execute(HttpRequest.java:51)
> at org.jboss.as.test.integration.common.HttpRequest.get(HttpRequest.java:81)
> at org.jboss.as.test.manualmode.security.VaultSystemPropertyOnServerStartTestCase.testVaultedSystemPropertyOnStart(VaultSystemPropertyOnServerStartTestCase.java:94)
> Caused by: java.io.IOException: HTTP Status 500 Response: <html><head><title>Error</title></head><body>Internal Server Error</body></html>
> at org.jboss.as.test.integration.common.HttpRequest.processResponse(HttpRequest.java:156)
> at org.jboss.as.test.integration.common.HttpRequest.access$000(HttpRequest.java:45)
> at org.jboss.as.test.integration.common.HttpRequest$1.call(HttpRequest.java:78)
> at org.jboss.as.test.integration.common.HttpRequest$1.call(HttpRequest.java:73)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5334) Update to HAL 2.8.9.Final
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5334?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5334:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Update to HAL 2.8.9.Final
> -------------------------
>
> Key: WFLY-5334
> URL: https://issues.jboss.org/browse/WFLY-5334
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Web Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 10.0.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5517) Tests from RTS module fails with security manager
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5517?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5517:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Tests from RTS module fails with security manager
> -------------------------------------------------
>
> Key: WFLY-5517
> URL: https://issues.jboss.org/browse/WFLY-5517
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Gytis Trikleris
> Fix For: 10.0.0.Final
>
> Attachments: rts.module.txt
>
>
> *Description of problem:*
> Tests from RTS module fails with security manager
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.rts
> *Actual results:*
> See attached file
> *Expected results:*
> No errors
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5528) "WFLYCTL0171: unsatisfied dependencies" when removing a modified XA datasource
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5528?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5528:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> "WFLYCTL0171: unsatisfied dependencies" when removing a modified XA datasource
> ------------------------------------------------------------------------------
>
> Key: WFLY-5528
> URL: https://issues.jboss.org/browse/WFLY-5528
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 9.0.1.Final, 10.0.0.CR2
> Reporter: Peter Palaga
> Assignee: Stefano Maestri
> Priority: Critical
> Fix For: 10.0.0.Final
>
>
> Please note that the present scenario ends with a similar error message and has the same workaround as WFLY-5527.
> Steps to reproduce:
> (1) Create an XA Datasource:
> {code}
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs")
> ],
> "jndi-name" => "java:/testXaDs",
> "driver-name" => "h2",
> "xa-datasource-class" => "org.h2.jdbcx.JdbcDataSource",
> "user-name" => "sa",
> "password" => "sa",
> "new-connection-sql" => undefined,
> "url-delimiter" => undefined,
> "url-selector-strategy-class-name" => undefined,
> "use-java-context" => undefined,
> "max-pool-size" => undefined,
> "min-pool-size" => undefined,
> "initial-pool-size" => undefined,
> "pool-prefill" => undefined,
> "pool-use-strict-min" => undefined,
> "interleaving" => undefined,
> "capacity-incrementer-class" => undefined,
> "capacity-decrementer-class" => undefined,
> "no-tx-separate-pool" => undefined,
> "pad-xid" => undefined,
> "same-rm-override" => undefined,
> "wrap-xa-resource" => undefined,
> "security-domain" => undefined,
> "reauth-plugin-class-name" => undefined,
> "flush-strategy" => undefined,
> "allow-multiple-users" => undefined,
> "connection-listener-class" => undefined,
> "prepared-statements-cache-size" => undefined,
> "share-prepared-statements" => undefined,
> "track-statements" => undefined,
> "allocation-retry" => undefined,
> "allocation-retry-wait-millis" => undefined,
> "blocking-timeout-wait-millis" => undefined,
> "idle-timeout-minutes" => undefined,
> "query-timeout" => undefined,
> "use-try-lock" => undefined,
> "set-tx-query-timeout" => undefined,
> "transaction-isolation" => undefined,
> "check-valid-connection-sql" => undefined,
> "exception-sorter-class-name" => undefined,
> "stale-connection-checker-class-name" => undefined,
> "valid-connection-checker-class-name" => undefined,
> "background-validation-millis" => undefined,
> "background-validation" => undefined,
> "use-fast-fail" => undefined,
> "validate-on-match" => undefined,
> "xa-resource-timeout" => undefined,
> "spy" => undefined,
> "use-ccm" => undefined,
> "enabled" => undefined,
> "connectable" => undefined,
> "statistics-enabled" => undefined,
> "tracking" => undefined,
> "recovery-username" => undefined,
> "recovery-password" => undefined,
> "recovery-security-domain" => undefined,
> "recovery-plugin-class-name" => undefined,
> "no-recovery" => undefined,
> "url-property" => undefined,
> "reauth-plugin-properties" => undefined,
> "exception-sorter-properties" => undefined,
> "stale-connection-checker-properties" => undefined,
> "valid-connection-checker-properties" => undefined,
> "recovery-plugin-properties" => undefined,
> "connection-listener-property" => undefined,
> "capacity-incrementer-properties" => undefined,
> "capacity-decrementer-properties" => undefined
> },
> {
> "operation" => "add",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs"),
> ("xa-datasource-properties" => "URL")
> ],
> "value" => "jdbc:h2:mem:test"
> }
> ]
> }
> {code}
> (2) Update its {{"jndi-name"}}
> {code}
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "write-attribute",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs")
> ],
> "name" => "jndi-name",
> "value" => "java:/testXaDs_changed"
> }
> ]
> }
> {code}
> This composite operation succeeds.
> (3) Remove the XA Datasource:
> {code}
> {
> "operation" => "remove",
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "testXaDs")
> ]
> }
> {code}
> NOT OK: the operation fails:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.data-source.reference-factory.testXaDs was depended upon by service jboss.naming.context.java.testXaDs
> Service jboss.xa-data-source-config.testXaDs was depended upon by service jboss.data-source.java:/testXaDs",
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
> EXPECTED: the operation should succeed
> Workaround: When the same request is sent once again, the second invocation succeeds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5083) [Migration operation] group-address/group-port/local-bind-address/local-bind-port in broadcast-group are not migrated
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5083?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5083:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> [Migration operation] group-address/group-port/local-bind-address/local-bind-port in broadcast-group are not migrated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5083
> URL: https://issues.jboss.org/browse/WFLY-5083
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Beta1
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.Final
>
>
> If broadcast group with local-bind-address,local-bind-port, group-address and group-port then those parameters are not migrated properly:
> For example HornetQ configuration:
> {code}
> <broadcast-group name="groupA">
> <local-bind-address>localhost</local-bind-address>
> <local-bind-port>12345</local-bind-port>
> <group-address>224.0.1.105</group-address>
> <group-port>23456</group-port>
> <broadcast-period>${broadcast.period:2500}</broadcast-period>
> <connector-ref>netty</connector-ref>
> <connector-ref>netty-throughput</connector-ref>
> </broadcast-group>
> {code}
> is migrated to Artemis like:
> {code}
> <broadcast-group name="groupA" connectors="netty netty-throughput" broadcast-period="${broadcast.period:2500}"/>
> {code}
> With such a configuration server cannot be started. There is no warning pointing to this problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5030) Intermittent failure of deployment containing two datasources in -ds.xml
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5030?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5030:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Intermittent failure of deployment containing two datasources in -ds.xml
> ------------------------------------------------------------------------
>
> Key: WFLY-5030
> URL: https://issues.jboss.org/browse/WFLY-5030
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Beta1
> Reporter: Jan Blizňák
> Assignee: Stefano Maestri
> Fix For: 10.0.0.Final
>
> Attachments: one-datasource.jar, two-datasources.jar
>
>
> Running smoke runs of JBossWS in EAP7, I occasionally hit test failure of WSRMStoreFeatureTestCase (from JBossWS testsuite). The testcase uses deployment that should add some datasources, but deploying ends up with:
> {code}
> org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/rmclientdb.statistics: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/deployment=*/subsystem=datasources/data-source=*/statistics=jdbc'
> at org.jboss.as.controller.registry.NodeSubregistry.register(NodeSubregistry.java:86)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:180)
> at org.jboss.as.connector.services.datasources.statistics.DataSourceStatisticsService.start(DataSourceStatisticsService.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> {code}
> After some debugging, the problematic scenario seems to be:
> 1) there is a deployment (jar/war, doesn't matter) containing -ds.xml configuration file
> 2) this file contains definition of at least two datasources to be added
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5134) Error creating Batch JDBC storage in domain
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5134?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-5134:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many of these so I am not checking the history properly. From the lastModified date of this issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc. for this exercise). If that is incorrect please adjust as needed.
> Error creating Batch JDBC storage in domain
> -------------------------------------------
>
> Key: WFLY-5134
> URL: https://issues.jboss.org/browse/WFLY-5134
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 10.0.0.Beta1
> Environment: Oracle, DB2, Derby, Sybase, Firebird, and SQL Server databases
> Reporter: Jan Martiska
> Assignee: Cheng Fang
> Fix For: 10.0.0.Final
>
>
> When multiple servers (eg. a server-group in a JBoss domain) attempt to create a JDBC Batch repository at once, and they share a common database, they race in creating the database tables, because sometimes instance A will create the table PARTITION_EXECUTION after instance B invokes the check whether this table exists (this check is used to decide whether all tables need to be created) - therefore B will decide to create all tables too.
> If the database doesn't support the IF NOT EXISTS clause in CREATE TABLE (db2, oracle, sybase..), it will probably lead to a failure like 'table already exists', which in turn rolls back the creation of the JDBC store on all nodes in the domain, including those where the schema creation succeeded or was skipped. The tables remain physically in the database.
> This is similar to WFLY-5061, but this time, it is caused by having multiple servers in a domain.
> Sharing a common database in domain mode should work because it is useful for restarting failed jobs on different nodes if one node crashes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months