December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-325) Allow socket-binding-group-refType to override default-interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-325?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-325: --------------------------------------- Assignee: Emmanuel Hugonnet > Allow socket-binding-group-refType to override default-interface > ---------------------------------------------------------------- > > Key: WFCORE-325 > URL: https://issues.jboss.org/browse/WFCORE-325 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Todd Trimmer > Assignee: Emmanuel Hugonnet > Priority: Optional > Labels: configuration, domain, host-controller > > I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports. > Under my proposal, the host.xml could thus more easily be written like this: > ... > <interfaces> > <interface name="public"> > <inet-address value="10.10.10.1" /> > </interface> > <interface name="public-two"> > <inet-address value="10.10.10.2" /> > </interface> > </interfaces> > ... > <servers> > <server name="server-one" group="prod-server-group" auto-start="true"> > <jvm name="jvm6g" /> > </server> > <server name="server-two" group="prod-server-group" auto-start="false"> > <jvm name="jvm2g" /> > <socket-binding-group ref="standard-sockets" default-interface="public-two" /> > </server> > </servers> > ... > This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-353) CLI command for executing the deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-353?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-353: --------------------------------------- Assignee: Emmanuel Hugonnet > CLI command for executing the deployment scanner > ------------------------------------------------ > > Key: WFCORE-353 > URL: https://issues.jboss.org/browse/WFCORE-353 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management, Server > Reporter: Ben Schofield > Assignee: Emmanuel Hugonnet > Priority: Minor > > provide a CLI command that will run the deployment scanner even if the deployment scanner is turned off. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-239) Socket binding remove does not respect allow-resource-service-restart

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-239?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-239: --------------------------------------- Assignee: Emmanuel Hugonnet > Socket binding remove does not respect allow-resource-service-restart > --------------------------------------------------------------------- > > Key: WFCORE-239 > URL: https://issues.jboss.org/browse/WFCORE-239 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Stuart Douglas > Assignee: Emmanuel Hugonnet > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-289) Emit notifications for servers in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-289?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-289: ----------------------------------------- It's easier to implement with these notifications coming from server-config=YYY but it would be nicer to have them from /host=XXX/server=YYY on both the HC process and, perhaps, on the server itself. Although having them on the server itself needs thought, as the notification should likely be different, and oriented toward that server's own point-of-view and not that of a controlling HC. Anyway, it's nicer to have the HC ones in /host=XXX/server=YYY as that is the resource that represents the server. The server-config resource is just a chunk of configuration data. It has start/stop ops, but really that just because in the past we hadn't figured out how to have those ops on the server resource itself, so we stuck them on the next best spot. Let's try and not go down that path again. > Emit notifications for servers in domain mode > --------------------------------------------- > > Key: WFCORE-289 > URL: https://issues.jboss.org/browse/WFCORE-289 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > emit notifications related to server lifecycle in domain mode: > * server-started > * server-stopped > * server-restarted > * server-destroyed > * server-killed > These notifications should be emitted from the corresponding server-config resource (under /host=XXX/server-config=YYY) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4121) Wrong LDAP host used in AdvancedLdapLoginModuleTestCase