[JBoss JIRA] Updated: (JBCLUSTER-25) HA JMS
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-25?page=all ]
Brian Stansberry updated JBCLUSTER-25:
--------------------------------------
Fix Version/s: Q1Y8
(was: Q2Y7)
> HA JMS
> ------
>
> Key: JBCLUSTER-25
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-25
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Brian Stansberry
> Fix For: Q1Y8
>
>
> Currently JBossMQ is using HA-Singleton for limited high availbility. There is no fail over for state, per se.
> We don't have plan to enhance any HA in JBossMQ (4.0x release).
> Ovidiu's new messaging system has a built-in high-availbility capability in there through the servless nature of the system. So when his new system is ready for JMS, this piece should be built in.
> Remaining issues are to integrate with the current clustering framework.
--
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
18 years, 6 months
[JBoss JIRA] Closed: (JBCLUSTER-102) How to run jbento2
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-102?page=all ]
Brian Stansberry closed JBCLUSTER-102.
--------------------------------------
Resolution: Out of Date
> How to run jbento2
> ------------------
>
> Key: JBCLUSTER-102
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-102
> Project: JBoss Clustering
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Ben Wang
>
> Under atl lab, jbento account, I have created jebnto2 so we can run it accordingly.
> 1. Machines: dev02, dev03 are for jboss instanaces, dev14 (actually dev14-priv) is for the driver. Note that there is no apache load balancing yet. So it will just hit dev02.
> 2. Jboss is sym link as jboss4-4 and jboss4-3 on home dir.
> 3. jboss has sync and async config names under respective /tmp/jbento dir
> 4. Check run.sh and shutdown.sh for the binding.
> 5. Use sh driver.sh Repo to run jbento2. Check either JBento-Result or Work for results. Looks for analyzer.txt under report dir.
> 6. To modify, use loop.conf and jboss4.sh under Repo/conf dir.
--
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
18 years, 6 months