]
Jeff Mesnil commented on AS7-5357:
----------------------------------
The initial message packet size is a runtime read-only attribute.
However there is a bug in the domain mode that make it pass for a configuration attribute
(AS7-5366)
If you talk directly to the server, the property looks fine:
{noformat}
[domain@localhost:9999 /]
/host=master/server=server-one/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Defines a connection factory.",
"attributes" => {
...
"initial-message-packet-size" => {
"description" => "The initial size of messages created
through this factory.",
"type" => INT,
"nillable" => false,
"unit" => "BYTES",
"access-type" => "read-only",
"storage" => "runtime"
}
},
"operations" => undefined,
"children" => {}
}
}
[domain@localhost:9999 /]
/host=master/server=server-one/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
...
"initial-message-packet-size" => 1500,
...
}
}
{noformat}
Read-Only Property Without Value - Initial Message Package Size
---------------------------------------------------------------
Key: AS7-5357
URL:
https://issues.jboss.org/browse/AS7-5357
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Stefan Negrea
Assignee: Jeff Mesnil
Labels: rhq
Initial-message-packet-size property of a connection-factory does not have a value for
profiles even though it is read-only. The expectation is that server returns the default
value. The example below uses the full profile but the issue is applicable to all other
profiles that have the messaging subsystem.
Property: initial-message-packet-size
Path:
/profile=full/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory
Sample CLI output:
[domain@localhost:9999 /] cd
profile=full/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory
[domain@localhost:9999 connection-factory=RemoteConnectionFactory]
:read-resource-description
{
"outcome" => "success",
"result" => {
......
"initial-message-packet-size" => {
"description" => "The initial size of messages created
through this factory.",
"type" => INT,
"nillable" => false,
"unit" => "BYTES",
"access-type" => "read-only",
"storage" => "configuration"
}
"operations" => undefined,
"children" => {}
}
}
[domain@localhost:9999 connection-factory=RemoteConnectionFactory]
:read-resource(include-runtime=true,include-defaults=true)
{
"outcome" => "success",
"result" => {
"auto-group" => false,
"block-on-acknowledge" => false,
"block-on-durable-send" => true,
"block-on-non-durable-send" => false,
"cache-large-message-client" => false,
"call-timeout" => 30000L,
"client-failure-check-period" => 30000,
"client-id" => undefined,
"compress-large-messages" => false,
"confirmation-window-size" => -1,
"connection-load-balancing-policy-class-name" =>
"org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy",
"connection-ttl" => "60000",
"connector" => {"netty" => undefined},
"consumer-max-rate" => -1,
"consumer-window-size" => 1048576,
"discovery-group-name" => undefined,
"discovery-initial-wait-timeout" => undefined,
"dups-ok-batch-size" => 1048576,
"entries" =>
["java:jboss/exported/jms/RemoteConnectionFactory"],
"factory-type" => undefined,
"failover-on-initial-connection" => false,
"failover-on-server-shutdown" => undefined,
"group-id" => undefined,
"ha" => false,
"max-retry-interval" => "2000",
"min-large-message-size" => 102400,
"pre-acknowledge" => false,
"producer-max-rate" => -1,
"producer-window-size" => 65536,
"reconnect-attempts" => 0,
"retry-interval" => 2000L,
"retry-interval-multiplier" => "1.0",
"scheduled-thread-pool-max-size" => 5,
"thread-pool-max-size" => 30,
"transaction-batch-size" => 1048576,
"use-global-pools" => true
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: