[JBoss JIRA] (WFCORE-1620) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
by James Perkins (JIRA)
James Perkins created WFCORE-1620:
-------------------------------------
Summary: Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
Key: WFCORE-1620
URL: https://issues.jboss.org/browse/WFCORE-1620
Project: WildFly Core
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
[Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
{quote}
The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
{quote}
Analysis will need to be done to ensure this works as expected before the fork is no longer required.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1528:
-------------------------------------
Release Notes Text: (was: Re-resolving. If we make further changes in thread management that can come via a separate issue and would not be necessary to consider this specific problem as being fixed.)
Re-resolving. If we make further changes in thread management that can come via a separate issue and would not be necessary to consider this specific problem as being fixed.
> EAP 7 with secured management become unavailable after ~8 days
> --------------------------------------------------------------
>
> Key: WFCORE-1528
> URL: https://issues.jboss.org/browse/WFCORE-1528
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 2.1.0.Final
> Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication
> Reporter: Simeon Pinder
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 2.2.0.CR2, 3.0.0.Alpha3
>
>
> Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode.
> Issue discovered by JON QE after testing for 8 days with SSL.
> JON QE did not see the same issue when running identical test against EAP 6.
> Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted.
> See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details.
> JON team would like some evaluation done to determine:
> i)if this is EAP 7 issue or
> ii)somehow just a JON issue
> iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle.
> This issue could affect GA release schedules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ]
Brian Stansberry resolved WFCORE-1528.
--------------------------------------
Release Notes Text: Re-resolving. If we make further changes in thread management that can come via a separate issue and would not be necessary to consider this specific problem as being fixed.
Resolution: Done
> EAP 7 with secured management become unavailable after ~8 days
> --------------------------------------------------------------
>
> Key: WFCORE-1528
> URL: https://issues.jboss.org/browse/WFCORE-1528
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 2.1.0.Final
> Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication
> Reporter: Simeon Pinder
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 3.0.0.Alpha3, 2.2.0.CR2
>
>
> Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode.
> Issue discovered by JON QE after testing for 8 days with SSL.
> JON QE did not see the same issue when running identical test against EAP 6.
> Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted.
> See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details.
> JON team would like some evaluation done to determine:
> i)if this is EAP 7 issue or
> ii)somehow just a JON issue
> iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle.
> This issue could affect GA release schedules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6773) Provide ability to start/stop Data Source creation without restart of server
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-6773?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-6773:
-------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
> Provide ability to start/stop Data Source creation without restart of server
> ----------------------------------------------------------------------------
>
> Key: WFLY-6773
> URL: https://issues.jboss.org/browse/WFLY-6773
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Ramesh Reddy
> Assignee: Stefano Maestri
>
> Currently in WF 10, where a data source is created / removed using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF.
> h3. Why We need it?
> In Teiid, it is common practice to add/remove data sources dynamically and restarting server will affect performance and usability severely.
> * Because delete/re-add is in Teiid's workflow to manage a data sources and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
> * Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
> * Every time data source starts we fetch metadata from the source, this is very expensive operation.
> * With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
> * This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
> As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
> h3. Proposed Solution
> [~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
> Based on this the conclusion is that Data Sources, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new DS is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
> h3. Workarounds Considered
> Since this highly dependent on configuration based data source creation, we can opt to a deployment based data source creation (-ds.xml), however GSS is quick to dismiss this as this not supported feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6774) Provide ability to start/stop Resource Adapter creation/deletion without restart of server
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-6774?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-6774:
-------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
> Provide ability to start/stop Resource Adapter creation/deletion without restart of server
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-6774
> URL: https://issues.jboss.org/browse/WFLY-6774
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Affects Versions: 9.0.0.Final, 10.0.0.Final
> Reporter: Ramesh Reddy
> Assignee: Stefano Maestri
>
> Currently in WF 10, when a resource adapter is created / deleted using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF. We need ability *avoid* the restart of the server
> h3. Why We need it?
> In Teiid, it is common practice to add/remove resource adapters dynamically and restarting server will affect performance and usability severely.
> * Because delete/re-add is in Teiid's workflow to manage a resource adapters and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
> * Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
> * Every time resource adapter starts we fetch metadata from the source, this is very expensive operation.
> * With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
> * This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
> As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
> h3. Proposed Solution
> [~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
> Based on this the conclusion is that resource adapters, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new RA is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
> h3. Workarounds Considered
> Teiid currently deploy the RAR files in module format (due to product requirements) if allowed this can be changed to deploy .rar files, which is suggested as alternative. This does require lot of code changes and not approved path. Aslo, only half solution as WFLY-6773 we would still need.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6774) Provide ability to start/stop Resource Adapter creation/deletion without restart of server
by Ramesh Reddy (JIRA)
Ramesh Reddy created WFLY-6774:
----------------------------------
Summary: Provide ability to start/stop Resource Adapter creation/deletion without restart of server
Key: WFLY-6774
URL: https://issues.jboss.org/browse/WFLY-6774
Project: WildFly
Issue Type: Enhancement
Components: JCA
Affects Versions: 10.0.0.Final, 9.0.0.Final
Reporter: Ramesh Reddy
Assignee: Jesper Pedersen
Currently in WF 10, when a resource adapter is created / deleted using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF. We need ability *avoid* the restart of the server
h3. Why We need it?
In Teiid, it is common practice to add/remove resource adapters dynamically and restarting server will affect performance and usability severely.
* Because delete/re-add is in Teiid's workflow to manage a resource adapters and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
* Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
* Every time resource adapter starts we fetch metadata from the source, this is very expensive operation.
* With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
* This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
h3. Proposed Solution
[~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
Based on this the conclusion is that resource adapters, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new RA is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
h3. Workarounds Considered
Teiid currently deploy the RAR files in module format (due to product requirements) if allowed this can be changed to deploy .rar files, which is suggested as alternative. This does require lot of code changes and not approved path. Aslo, only half solution as WFLY-6773 we would still need.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6773) Provide ability to start/stop Data Source creation without restart of server
by Ramesh Reddy (JIRA)
Ramesh Reddy created WFLY-6773:
----------------------------------
Summary: Provide ability to start/stop Data Source creation without restart of server
Key: WFLY-6773
URL: https://issues.jboss.org/browse/WFLY-6773
Project: WildFly
Issue Type: Enhancement
Components: JCA
Affects Versions: 10.0.0.Final
Reporter: Ramesh Reddy
Assignee: Jesper Pedersen
Currently in WF 10, where a data source is created / removed using the CLI the "reload-status" is set to "requires restart", based how the resource is expected to be managed in WF.
h3. Why We need it?
In Teiid, it is common practice to add/remove data sources dynamically and restarting server will affect performance and usability severely.
* Because delete/re-add is in Teiid's workflow to manage a data sources and when we have to restart we loose the whole state of the virtual database. That means we need re-establish runtime status. For example, all the existing sessions will be killed.
* Runtime environment are often shared, that could kill other person's tasks in flight leaving them hanging with errors.
* Every time data source starts we fetch metadata from the source, this is very expensive operation.
* With multi-source feature, it is a feature that user dynamically brings in/out sources as they show up on their dashboard, it would be not possible to support this feature.
* This is a change of behavior from earlier versions of the EAP, our users and customers rely on this feature
As per Teiid project is concerned, we consider this is regression on WF and thus a bug.
h3. Proposed Solution
[~brian.stansberry] suggested the WF management practices here in this document https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Apply...
Based on this the conclusion is that Data Sources, is developed under "all-services" paradigm, not under "resource-services" paradigm, where a explicit header from client to whether to restart or not can avoid having to "reload" the server when a new DS is added or removed. We understand the nature of service dependencies in WF, and how this can affect the other dependent services, but we verified that Teiid will not have those side effects as we designed. Since these sources are effectively exclusively defined for Teiid should not interfere with others. Also, since the request is explicit, should not affect current behavior.
h3. Workarounds Considered
Since this highly dependent on configuration based data source creation, we can opt to a deployment based data source creation (-ds.xml), however GSS is quick to dismiss this as this not supported feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6772) Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6772?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6772:
---------------------------------
Priority: Minor (was: Major)
> Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-6772
> URL: https://issues.jboss.org/browse/WFLY-6772
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 10.1.0.Final
>
>
> 172 runs / 5 failures / 0 ignored Success rate: 97.1%
> org.jboss.as.test.clustering.cluster.web (1)
> ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover — Muted on 07 Jun 16 14:48 by Tomaz Cerar
>
> First failure: pull/1628 #2988 Changes (73) 22 Jun 16 16:47
> java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:207)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:103)
> https://ci.wildfly.org/viewLog.html?buildId=19454&tab=buildResultsDiv&bui...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6772) Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6772?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6772:
---------------------------------
Affects Version/s: 10.0.0.Final
> Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-6772
> URL: https://issues.jboss.org/browse/WFLY-6772
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 10.1.0.Final
>
>
> 172 runs / 5 failures / 0 ignored Success rate: 97.1%
> org.jboss.as.test.clustering.cluster.web (1)
> ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover — Muted on 07 Jun 16 14:48 by Tomaz Cerar
>
> First failure: pull/1628 #2988 Changes (73) 22 Jun 16 16:47
> java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:207)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:103)
> https://ci.wildfly.org/viewLog.html?buildId=19454&tab=buildResultsDiv&bui...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months