[
https://issues.jboss.org/browse/AS7-5441?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil resolved AS7-5441.
------------------------------
Fix Version/s: 7.2.0.Alpha1
Resolution: Done
the underlying issue (AS7-5107) has been fixed and the guilty attributes are correctly
checking whether there is an alternative attribute already set
{noformat}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory] pwd
/subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:read-attribute(name=connector)
{
"outcome" => "success",
"result" => {"in-vm" => undefined}
}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:read-attribute(name=discovery-group-name)
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:write-attribute(name=discovery-group-name,value=blabla)
{
"outcome" => "failed",
"failure-description" => "JBAS011630: Alternative attribute of
(discovery-group-name) is already defined.",
"rolled-back" => true
}
{noformat}
Input for HQ that the api accepts makes the server crash on reload or
restart
-----------------------------------------------------------------------------
Key: AS7-5441
URL:
https://issues.jboss.org/browse/AS7-5441
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Heiko Rupp
Assignee: Jeff Mesnil
Priority: Critical
Labels: rhq
Fix For: 7.2.0.Alpha1
The following will get the server to not reload/restart. Even if the input is considered
valid by the server. Needs a -full.xml configuration to include HornetQ.
[standalone@localhost:9999 connection-factory=InVmConnectionFactory] pwd
/subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:read-attribute(name=connector)
{
"outcome" => "success",
"result" => {"in-vm" => undefined}
}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:read-attribute(name=discovery-group-name)
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
:write-attribute(name=discovery-group-name,value=blabla)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory] /:reload
{"outcome" => "success"}
[standalone@localhost:9999 connection-factory=InVmConnectionFactory]
/:read-attribute(name=name)
Failed to perform read-operation-description to validate the request:
java.net.ConnectException: JBAS012144: Konnte keine Verbindung mit remote://localhost:9999
herstellen. Timeout der Verbindung
AS7 console log shows
10:03:49,540 ERROR [org.jboss.as.server] JBAS015956: Exception aufgetreten während des
Hochfahrens: org.jboss.as.controller.persistence.ConfigurationPersistenceException:
JBAS014676: Parsen der Konfiguration fehlgeschlagen
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141)
[jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.server.ServerService.boot(ServerService.java:270)
[jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156)
[jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0-b24]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[275,25]
Message: JBAS011646: Ungültiges Element connectors: kann nict verwendet werden, wenn
discovery-group-ref verwendet wird
at
org.jboss.as.messaging.MessagingSubsystemParser.checkOtherElementIsNotAlreadyDefined(MessagingSubsystemParser.java:2357)
at
org.jboss.as.messaging.Messaging12SubsystemParser.createConnectionFactory(Messaging12SubsystemParser.java:75)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira