[JBoss JIRA] Created: (AS7-1355) Review jboss-app.xml handling
by Darran Lofthouse (JIRA)
Review jboss-app.xml handling
-----------------------------
Key: AS7-1355
URL: https://issues.jboss.org/browse/AS7-1355
Project: Application Server 7
Issue Type: Task
Components: EE
Reporter: Darran Lofthouse
Assignee: David Lloyd
Fix For: 7.1.0.Alpha1
The jboss-app.xml descriptor needs a schema appropriate for AS7 - initially the first missing piece of config is the support for security-domain - the jboss-app.xml descriptor should avoid overlap with jboss-deployment-structure.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBAS-9243) Management Port sharing port 8080
by Jim Tyrrell (JIRA)
Management Port sharing port 8080
---------------------------------
Key: JBAS-9243
URL: https://issues.jboss.org/browse/JBAS-9243
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Beta2
Reporter: Jim Tyrrell
While it is great and there are many good reason to have a management console on a different port then the standard 8080 web ports, it should be possible to use port 8080 or equivalent for a management console and another port needing to be open should not be required, but can be a selectable feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-3001) HC Reload operation variety that does not restart servers
by Kabir Khan (Created) (JIRA)
HC Reload operation variety that does not restart servers
---------------------------------------------------------
Key: AS7-3001
URL: https://issues.jboss.org/browse/AS7-3001
Project: Application Server 7
Issue Type: Feature Request
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: 7.1.0.Final
bstansberry: I have that reload op that restarts everything, that's a 3rd case
[15:40] bstansberry: the final variant is something like adding a param to the HC reload op such that it doesn't stop servers
[15:40] bstansberry: it just reloads itself and the servers somehow sync back up
[15:40] bstansberry: which is meant to work but, well, who knows
[15:41] kkhan: Yeah, we had some stuff for that
[15:42] bstansberry: that can be nice for scenarios like
[15:43] bstansberry: DC dies and can't be revived for some reason
[15:43] bstansberry: :reload HC into admin-only but don't restart servers
[15:43] bstansberry: tweak config to make the HC master, get the domain.xml in place
[15:43] bstansberry: :reload again out of admin-only, servers reconnect, we have a new DC
[15:44] bstansberry: that's a pretty convoluted case though, so we can defer to Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (AS7-1467) Socketbinding :write-attribute(name=includes, value=[]) fails with "no attribute named includes", but :read-resource shows it
by Heiko Rupp (JIRA)
Socketbinding :write-attribute(name=includes,value=[]) fails with "no attribute named includes", but :read-resource shows it
----------------------------------------------------------------------------------------------------------------------------
Key: AS7-1467
URL: https://issues.jboss.org/browse/AS7-1467
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
[domain@localhost:9999 socket-binding-group=standard-sockets] :read-resource
{
"outcome" => "success",
"result" => {
"default-interface" => "public",
"includes" => [],
"name" => "standard-sockets",
"socket-binding" => {
"jmx-connector-registry" => undefined,
}
}
}
[domain@localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=lala)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "Wrong type for includes. Expected [LIST] but was STRING"},
"rolled-back" => true
}
[domain@localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=[])
{
"outcome" => "failed",
"result" => {"server-groups" => [("main-server-group" => {"master" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "No known attribute called includes",
"rolled-back" => true
}
}})]},
"failure-description" => "Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
[domain@localhost:9999 socket-binding-group=standard-sockets] :read-children-types
{
"outcome" => "success",
"result" => ["socket-binding"]
}
[domain@localhost:9999 socket-binding-group=standard-sockets]
Also read-attribute works:
[domain@localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=includes)
{
"outcome" => "success",
"result" => []
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years