[JBoss JIRA] Created: (JBAS-4908) Update sample-bindings.xml to reflect use of -beans.xml instead of -service.xml for clustering services.
2:21 p.m.
Update sample-bindings.xml to reflect use of -beans.xml instead of -service.xml for
clustering services.
--------------------------------------------------------------------------------------------------------
Key: JBAS-4908
URL: http://jira.jboss.com/jira/browse/JBAS-4908
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
The current file assumes things like HA-JNDI are mbeans.
--
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
2:18 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4908) Support vertical clustering port replacement for cluster services
[ http://jira.jboss.com/jira/browse/JBAS-4908?page=all ]
Brian Stansberry updated JBAS-4908:
-----------------------------------
Summary: Support vertical clustering port replacement for cluster services
(was: Update sample-bindings.xml to reflect use of -beans.xml instead of -service.xml for
clustering services.)
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta4)
Description: You can vertically cluster AS instances either by multihoming your
machine and passing different values to -b when starting JBoss, or by ensuring each AS
uses distinct ports for all services that open ports. AS 4.x supports the latter via the
ServiceBindingManager service, which does not work with pojo services (i.e. those that are
not deployed via the ServiceController). A number of clustering services that open ports
have been converted in AS 5 into pojo services, so the old ServiceBindingManager approach
no longer works. Need to find a solution for this. (was: The current file assumes things
like HA-JNDI are mbeans.)
Support vertical clustering port replacement for cluster services
-----------------------------------------------------------------
Key: JBAS-4908
URL: http://jira.jboss.com/jira/browse/JBAS-4908
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
You can vertically cluster AS instances either by multihoming your machine and passing
different values to -b when starting JBoss, or by ensuring each AS uses distinct ports for
all services that open ports. AS 4.x supports the latter via the ServiceBindingManager
service, which does not work with pojo services (i.e. those that are not deployed via the
ServiceController). A number of clustering services that open ports have been converted
in AS 5 into pojo services, so the old ServiceBindingManager approach no longer works.
Need to find a solution for this.
--
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
2:27 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4908) Support vertical clustering port replacement for cluster services
[ http://jira.jboss.com/jira/browse/JBAS-4908?page=all ]
Brian Stansberry updated JBAS-4908:
-----------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128642
Support vertical clustering port replacement for cluster services
-----------------------------------------------------------------
Key: JBAS-4908
URL: http://jira.jboss.com/jira/browse/JBAS-4908
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
You can vertically cluster AS instances either by multihoming your machine and passing
different values to -b when starting JBoss, or by ensuring each AS uses distinct ports for
all services that open ports. AS 4.x supports the latter via the ServiceBindingManager
service, which does not work with pojo services (i.e. those that are not deployed via the
ServiceController). A number of clustering services that open ports have been converted
in AS 5 into pojo services, so the old ServiceBindingManager approach no longer works.
Need to find a solution for this.
--
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
11:24 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4908) Support vertical clustering port replacement for cluster services
[ http://jira.jboss.com/jira/browse/JBAS-4908?page=all ]
Brian Stansberry updated JBAS-4908:
-----------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
(was: JBossAS-5.0.0.CR1)
Support vertical clustering port replacement for cluster services
-----------------------------------------------------------------
Key: JBAS-4908
URL: http://jira.jboss.com/jira/browse/JBAS-4908
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: JBossAS-5.0.0.CR2
You can vertically cluster AS instances either by multihoming your machine and passing
different values to -b when starting JBoss, or by ensuring each AS uses distinct ports for
all services that open ports. AS 4.x supports the latter via the ServiceBindingManager
service, which does not work with pojo services (i.e. those that are not deployed via the
ServiceController). A number of clustering services that open ports have been converted
in AS 5 into pojo services, so the old ServiceBindingManager approach no longer works.
Need to find a solution for this.
--
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
7:41 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-4908) Support vertical clustering port replacement for cluster services
[
https://jira.jboss.org/jira/browse/JBAS-4908?page=com.atlassian.jira.plug...
]
Brian Stansberry closed JBAS-4908.
----------------------------------
Resolution: Done
Although JBAS-5192 is still open, that's because a couple non-clustering services are
still working to complete integration with it. The new ServiceBindingManager handles the
clustering services. I'd like to revert the subtask work and reconvert them from
-service.xml to -jboss-beans.xml, but don't see that happening for 5.0.0.
Support vertical clustering port replacement for cluster services
-----------------------------------------------------------------
Key: JBAS-4908
URL: https://jira.jboss.org/jira/browse/JBAS-4908
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Critical
Fix For: JBossAS-5.0.0.CR2
You can vertically cluster AS instances either by multihoming your machine and passing
different values to -b when starting JBoss, or by ensuring each AS uses distinct ports for
all services that open ports. AS 4.x supports the latter via the ServiceBindingManager
service, which does not work with pojo services (i.e. those that are not deployed via the
ServiceController). A number of clustering services that open ports have been converted
in AS 5 into pojo services, so the old ServiceBindingManager approach no longer works.
Need to find a solution for this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6536
days inactive
6846
days old
4 comments
1 participants
participants (1)
-
Brian Stansberry (JIRA)