[JBoss JIRA] (WFCORE-205) ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-205?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-205:
------------------------------------
Bugzilla Update: (was: Perform)
> ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-205
> URL: https://issues.jboss.org/browse/WFCORE-205
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha10
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha11
>
>
> ManagedDMRContentTypeResource.content is used for generating an overall hash for the stored content, but it does not use consistent ordering (i.e. it needs to be a LinkedHashMap or perhaps a TreeMap.) The result is when another node in the domain receives an update it may calculate a different overall hash.
> This is surfacing as failures in https://bugzilla.redhat.com/show_bug.cgi?id=1078062 when the master and slave are running on different JVM releases. Different VM releases often have different ordering behavior when iterating over the unordered collections.
> I believe this is unlikely to result in real-world problems since any backup will persist its own version of the hash to its local copy of domain.xml, so there won't be any mismatch. The importance of the overall hash is that it allows the process to find the content in the repo when it is added.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3974) Move 'Channel end notification received, closing channel' to DEBUG
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3974?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3974:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1153281|https://bugzilla.redhat.com/show_bug.cgi?id=1153281] from POST to MODIFIED
> Move 'Channel end notification received, closing channel' to DEBUG
> ------------------------------------------------------------------
>
> Key: WFLY-3974
> URL: https://issues.jboss.org/browse/WFLY-3974
> Project: WildFly
> Issue Type: Enhancement
> Components: Naming
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 9.0.0.Beta1
>
>
> When a remote jms queue is located the following is seen:
> 2014-09-25 16:48:29,327 INFO [org.jboss.as.naming] (Remoting "jeev6dev01_200" task-1) JBAS011806: Notification de fin de canal reçue, fermeture du canal Channel ID 0cb79bd5 (inbound) of Remoting connection 53a1933a to /10.23.132.245:57733
> This is due to org.jboss.as.naming.NamingLogger where the following is used:
> @LogMessage(level=Logger.Level.INFO)
> @Message(id=11806, value="Channel end notification received, closing channel %s")
> public abstract void closingChannelOnChannelEnd(Channel paramChannel);
> Changin this to
> @LogMessage(level=Logger.Level.DEBUG)
> Would ensure that an INFO log event is not seen every time a jms message is sent to the server.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-205) ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-205?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-205:
------------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1078062|https://bugzilla.redhat.com/show_bug.cgi?id=1078062] from POST to MODIFIED
> ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-205
> URL: https://issues.jboss.org/browse/WFCORE-205
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha10
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> ManagedDMRContentTypeResource.content is used for generating an overall hash for the stored content, but it does not use consistent ordering (i.e. it needs to be a LinkedHashMap or perhaps a TreeMap.) The result is when another node in the domain receives an update it may calculate a different overall hash.
> This is surfacing as failures in https://bugzilla.redhat.com/show_bug.cgi?id=1078062 when the master and slave are running on different JVM releases. Different VM releases often have different ordering behavior when iterating over the unordered collections.
> I believe this is unlikely to result in real-world problems since any backup will persist its own version of the hash to its local copy of domain.xml, so there won't be any mismatch. The importance of the overall hash is that it allows the process to find the content in the repo when it is added.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-4025) Log Viewer [Download] does not work
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4025?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-4025:
---------------------------------
Assignee: James Perkins (was: Jason Greene)
> Log Viewer [Download] does not work
> -----------------------------------
>
> Key: WFLY-4025
> URL: https://issues.jboss.org/browse/WFLY-4025
> Project: WildFly
> Issue Type: Bug
> Components: Logging, Web Console
> Affects Versions: 8.1.0.Final
> Reporter: Robert Smith
> Assignee: James Perkins
>
> We are running a domain mode configuration using Wildfly 8.1.0.Final 'Kenny'. The Log Viewer allows us to [View] logs but the download button does nothing. No error is reported in the server.log when pressing the button and the log file is not downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-4025) Log Viewer [Download] does not work
by Robert Smith (JIRA)
Robert Smith created WFLY-4025:
----------------------------------
Summary: Log Viewer [Download] does not work
Key: WFLY-4025
URL: https://issues.jboss.org/browse/WFLY-4025
Project: WildFly
Issue Type: Bug
Affects Versions: 8.1.0.Final
Reporter: Robert Smith
Assignee: Jason Greene
We are running a domain mode configuration using Wildfly 8.1.0.Final 'Kenny'. The Log Viewer allows us to [View] logs but the download button does nothing. No error is reported in the server.log when pressing the button and the log file is not downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months