[JBoss JIRA] Closed: (JBESB-429) Clustering: load balancing
by Kurt Stam (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-429?page=all ]
Kurt Stam closed JBESB-429.
---------------------------
Fix Version/s: (was: 5.0)
Resolution: Done
Works now for any protocol, as long as the target service is Stateless. Maybe have to come back to the handling of stateful services for 5.0.
You can plug in two different loadbalance strategies: RandomRobin or RoundRobin , or you can plugin your own load balance strategy. Note that FirstAvailable is NOT a load-balance strategy, but a fail-over strategy only.
> Clustering: load balancing
> --------------------------
>
> Key: JBESB-429
> URL: http://jira.jboss.com/jira/browse/JBESB-429
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Reporter: Mark Little
> Assigned To: Kurt Stam
> Fix For: 4.2
>
>
> Load-balancing across like services deployed across multiple JVMs.
--
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, 8 months
[JBoss JIRA] Created: (JBESB-623) Bring Hudson CI builds inline with current CI builds
by Kevin Conner (JIRA)
Bring Hudson CI builds inline with current CI builds
----------------------------------------------------
Key: JBESB-623
URL: http://jira.jboss.com/jira/browse/JBESB-623
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Reporter: Kevin Conner
Assigned To: Prabhat Jha
The CI build has beem migrated to Hudson but there are a number of outstanding issued to be addressed before it will replace the current CI builds in Newcastle.
Current issues are as follows
- Hudson should start a build as soon as possible after modifications have been made to the repository.
At present the Newcastle CI build checks every 15 mins for modifications, initiating a build when the
repository has been updated
- Emails should be sent on every build, whether successful or not and contain the following information
List of modifications identified
Contents of Emma coverage reports
- Hudson builds must be reliable.
One issue identified so far is a transient clash on port 8888.
--
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, 8 months