[JBoss JIRA] Updated: (JBAS-1832) Improving JBoss WebConsole's snapshots
by gunter zeilinger (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1832?page=all ]
gunter zeilinger updated JBAS-1832:
-----------------------------------
Attachment: jboss-4.2.2.GA-bin-patch.zip
jboss-4.2.2.GA-src-patch.zip
jboss-4.2.2.GA-src-patch.diff
Attached patch for JBossAS-4.2.2.GA additionally add support to JBoss Web Console to persist created snapshots.
To apply on binary JBossAS-4.2.2.GA distribution
> unzip jboss-4.2.2.GA-bin-patch.zip
in your server configuration directory (e.g: jboss-4.2.2.GA/server/default ).
jboss-4.2.2.GA-src-patch.zip contains the modified and added sources, jboss-4.2.2.GA-src-patch.diff the diff against http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_2_GA.
> Improving JBoss WebConsole's snapshots
> --------------------------------------
>
> Key: JBAS-1832
> URL: http://jira.jboss.com/jira/browse/JBAS-1832
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX/Web Console
> Affects Versions: JBossAS-4.0.0 Final
> Environment: Not relevant
> Reporter: Mathieu Bourrier
> Assigned To: Jon Prindiville
> Priority: Minor
> Attachments: jboss-4.2.2.GA-bin-patch.zip, jboss-4.2.2.GA-src-patch.diff, jboss-4.2.2.GA-src-patch.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The snapshots in the Webconsole cannot be started automatically on startup, as the Recording field isn't an attribute.
> 2 classes need to be modified, and the changes are quite small.
> Given topic describes changes to be made in order to manage it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JGRP-794) FD_SOCK: un-suspected members are not added back to pingable_mbrs
by Bela Ban (JIRA)
FD_SOCK: un-suspected members are not added back to pingable_mbrs
-----------------------------------------------------------------
Key: JGRP-794
URL: http://jira.jboss.com/jira/browse/JGRP-794
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6.4, 2.7
[Bruce Schuchardt]
I had a test run where a member was suspected by FD_SOCK, but replied to an
ARE_YOU_DEAD message. The process was then immediately killed by the test
but was never suspected again.
FD_SOCK.run() removes suspected members from pingable_mbrs so they won't be
ping targets. When a member is unsuspected, it needs to be put back in
pingable_mbrs in the correct place and the pinger thread needs to be started
or interrupted. Otherwise no-one will be watching the unsuspected member
until the next view change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months