Apache Qpid : System Properties
This page last changed on Aug 12, 2009 by aidan.
Explanation of System properties used in QpidThis page documents the various System Properties that are currently used in the Qpid Java code base.
Client PropertiesSTRICT_AMQPType : boolean Features disabled by STRICT_AMQP
This is associated with property STRICT_AMQP_FATAL STRICT_AMQP_FATALType : boolean This will cause any attempt to utilise an enhanced feature to throw and UnsupportedOperationException. When set to false then the exception will not occur but the feature will be disabled. e.g. IMMEDIATE_PREFETCHType : boolean The default with AMQP is to start prefetching messages. However, with certain 3rd party Java tools, such as Mule this can cause a problem. Mule will create a consumer but never consume from it so any any prefetched messages will be stuck until that session is closed. This property is used to re-instate the default AMQP behaviour. The default Qpid behaviour is to prevent prefetch occurring, by starting the connection Flow Controlled, until a request for a message is made on the consumer either via a receive() or setting a message listener. amqj.default_syncwrite_timeoutType : long amq.dynamicsaslregistrar.propertiesType : String amqj.heartbeat.timeoutFactorType : float amqj.tcpNoDelayType : boolean amqj.sendBufferSizeType : integer amqj.receiveBufferSizeType : integer amqj.protocolprovider.classType : String amqj.protocol.logging.levelType : boolean jboss.hostUsed by the JBossConnectionFactoryInitialiser to specify the host to connect to perform JNDI lookups. jboss.portUsed by the JBossConnectionFactoryInitialiser to specify the port to connect to perform JNDI lookups. amqj.MaximumStateWaitDefault : 30000 Management PropertiessecurityDefault: null jmxconnectorDefault: null timeoutDefault: 5000 Properties used in ExamplesarchivepathUsed in : FileMessageDispatcher |
![]() |
Document generated by Confluence on May 26, 2010 10:34 |