[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]
by Tobi Tobias (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ]
Tobi Tobias updated WFCORE-1330:
--------------------------------
Attachment: server.log
> Deployment error after reboot [WFLYSRV0137]
> -------------------------------------------
>
> Key: WFCORE-1330
> URL: https://issues.jboss.org/browse/WFCORE-1330
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.2.Final
> Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65
> Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance.
> Reporter: Tobi Tobias
> Assignee: ehsavoie Hugonnet
> Priority: Critical
> Attachments: server.log
>
>
> I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE).
> After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred.
> But if I restart the server now, I get following error message:
> 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot.
> The only way to fix the configuration is to manually remove the deployments from the standalone.xml.
> But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]
by Tobi Tobias (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ]
Tobi Tobias commented on WFCORE-1330:
-------------------------------------
I could successfully nailed the problem down to a server log. Please see attached log file.
I deployed two applications. Both have their own datasource. Both apps worked fine.
After deployment I requested a server shutdown via jboss-cli. -> worked fine
Then, I started the server again. The first log entries where "Removing content..." and then the server couldn't finish booting because of missing exactly these deployments.
> Deployment error after reboot [WFLYSRV0137]
> -------------------------------------------
>
> Key: WFCORE-1330
> URL: https://issues.jboss.org/browse/WFCORE-1330
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.2.Final
> Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65
> Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance.
> Reporter: Tobi Tobias
> Assignee: ehsavoie Hugonnet
> Priority: Critical
>
> I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE).
> After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred.
> But if I restart the server now, I get following error message:
> 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot.
> The only way to fix the configuration is to manually remove the deployments from the standalone.xml.
> But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5566) org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5566?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-5566:
------------------------------------
Assignee: Richard Achmatowicz (was: Paul Ferraro)
> org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed
> --------------------------------------------------------------------------------
>
> Key: WFLY-5566
> URL: https://issues.jboss.org/browse/WFLY-5566
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Ivan Straka
> Assignee: Richard Achmatowicz
> Labels: clustering_revalidate
>
> There is org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed failing with exception:
> {code:java}
> Error Message
> expected:<500> but was:<200>
> Stacktrace
> java.lang.AssertionError: expected:<500> but was:<200>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed(XSiteSimpleTestCase.java:202)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-4786 at 1/27/16 11:51 AM:
----------------------------------------------------------------
Managed to reproduce alright. Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distributable fail on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
The test logic was introduced for WFLY-2774 via commit:
c3902e26957f607983d81c7a8f3f18e358acf743
was (Author: rhusar):
Managed to reproduce alright. Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distributable fails on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
which was introduced in WFLY-2774 via commit id:
c3902e26957f607983d81c7a8f3f18e358acf743
> Clustering integration tests fails once -Dnode0 and -Dnode1 are used
> --------------------------------------------------------------------
>
> Key: WFLY-4786
> URL: https://issues.jboss.org/browse/WFLY-4786
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.Alpha3
> Reporter: Petr Kremensky
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Beta2
>
> Attachments: maven.logs, results.zip, testsuite.clustering.logs.zip
>
>
> Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-...
> * build 5 binds to localhost (no -Dnode*)
> * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2
> Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-4786 at 1/27/16 11:50 AM:
----------------------------------------------------------------
Managed to reproduce alright. Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distributable fails on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
which was introduced in WFLY-2774 via commit id:
c3902e26957f607983d81c7a8f3f18e358acf743
was (Author: rhusar):
Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distributable fails on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
which was introduced in WFLY-2774 via commit id:
c3902e26957f607983d81c7a8f3f18e358acf743
> Clustering integration tests fails once -Dnode0 and -Dnode1 are used
> --------------------------------------------------------------------
>
> Key: WFLY-4786
> URL: https://issues.jboss.org/browse/WFLY-4786
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.Alpha3
> Reporter: Petr Kremensky
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Beta2
>
> Attachments: maven.logs, results.zip, testsuite.clustering.logs.zip
>
>
> Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-...
> * build 5 binds to localhost (no -Dnode*)
> * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2
> Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-4786) Clustering integration tests fails once -Dnode0 and -Dnode1 are used
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4786?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-4786 at 1/27/16 11:42 AM:
----------------------------------------------------------------
Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distributable fails on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
which was introduced in WFLY-2774 via commit id:
c3902e26957f607983d81c7a8f3f18e358acf743
was (Author: rhusar):
Current list of failures is:
{noformat}
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<2ss7WTESS7lVo3Is6zP9Lq6HGLrsV7rMfbHJjIYV=node-1>
CoarseWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<Frmey6bDfZCM7e-2ScAc7AnFI6CSdk3NaaVyVZOL=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<HqqvZ0a_ACDXWc0RDmYyCON3cEZL3h7mf1KfpO2n=node-1>
GranularWebFailoverTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<oqVW8pfo_r1ZeaL-zyVMaIJ40uWrOF_Xin3lKeNp=node-1>
NonDistributableTestCase.test:127 expected:<2> but was:<1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover:103->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ia8teO0bP1vW5DM0pqEevfUE-brgUsdmBJlMnejs=node-1>
ReplicationForNegotiationAuthenticatorTestCase>ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover:83->ClusteredWebFailoverAbstractCase.testFailover:164 expected null, but was:<ULQ3vjz743vvjnLJE7nLQDNTNeDJ2p02NS6qRGp0=node-1>
{noformat}
Out of total tests run: 54, Failures: 7, Errors: 0, Skipped: 3
All except for the non-distrubutable fails on line
org/jboss/as/test/clustering/cluster/web/ClusteredWebFailoverAbstractCase.java:164
which was introduced in WFLY-2774 via commit id:
c3902e26957f607983d81c7a8f3f18e358acf743
> Clustering integration tests fails once -Dnode0 and -Dnode1 are used
> --------------------------------------------------------------------
>
> Key: WFLY-4786
> URL: https://issues.jboss.org/browse/WFLY-4786
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.Alpha3
> Reporter: Petr Kremensky
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Beta2
>
> Attachments: maven.logs, results.zip, testsuite.clustering.logs.zip
>
>
> Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-...
> * build 5 binds to localhost (no -Dnode*)
> * build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2
> Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1043) Remove deprecated knowledge-api-legacy5-adapter module
by Petr Široký (JIRA)
Petr Široký created DROOLS-1043:
-----------------------------------
Summary: Remove deprecated knowledge-api-legacy5-adapter module
Key: DROOLS-1043
URL: https://issues.jboss.org/browse/DROOLS-1043
Project: Drools
Issue Type: Task
Components: core engine
Affects Versions: 6.4.0.Beta1, 6.3.0.Final
Reporter: Petr Široký
Assignee: Petr Široký
Module {{knowledge-api-legacy5-adapter}} was meant as bridge between versions 5 and 6. For 7 it should be removed as it is no longer needed and adds additional maintenance costs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months