Thank you Rob!
On Oct 9, 2016 9:13 AM, "Rob Godfrey" <[email protected]> wrote:
> In general context variables are used in two ways:
>
> 1) where the configuration file (or initial configuration) explicitly
> uses a value of the for "${prop_name}"
> 2) where the code defines a default value for an attribute in terms of
> a property (for instance the alertRepeatGap property of queues is
> defined to default to ${queue.alertRepeatGap} which is specified as
> having a default value of 3000
>
> For 6.1 we have added a feature to the REST apidocs which displays the
> context variables defined in a given object type. Unfortunately this
> feature is not present in 6.0.x. However you can fairly easily see
> all the defined context variables simply by using the REST api to
> retrieve the details of the broker and looking at the context
> attribute. For instance on my local broker I can run
> http://localhost:8888/api/latest/broker and in the results I see:
>
> "context" : {
> "java.vm.version" : "24.0-b56",
> "virtualhost.storeTransactionIdleTimeoutWarn" : "180000",
> "port.http.maximumQueuedRequests" : "1000",
> "rvm_version" : "1.24.7 (stable)",
> "XPC_FLAGS" : "0x0",
> "queue.holdOnPublishEnabled" : "false",
> "qpid.broker.bdbTotalCacheSize" : "102943948",
> "line.separator" : "\n",
> "qpid.port.protocol_handshake_timeout" : "2000",
> ...
>
> as you can tell these are a mixture of qpid defined context variables,
> and context defined by the environment (java.vm.version, rpm_version,
> XPC_FLAGS, and line.separator are environment and not Qpid defined).
> If you ignore the environment context then you can see all the context
> variables which your Qpid version defines in code.
>
> There is nothing defined for authentication provider. The approach
> you describe in your other e-mail is the correct one, unfortunately
> there is a bug which is stopping this from working. However I've
> already created a fix for that bug which we should be able to put into
> 6.0.5 which you can use as a drop-in replacement for 6.0.2.
>
> Hope this helps,
> Rob
>
> On 8 October 2016 at 20:22, rammohan ganapavarapu
> <[email protected]> wrote:
> > Hi,
> >
> > I am trying to find what are the available properties that can use at
> > broker start up. I know below are available but any undocumented
> properties
> > that i can pass at the time of startup?
> >
> > qpid.amqp_port=5672
> > qpid.http_port=10002
> > qpid.jmx_port=8999
> > qpid.rmi_port=9099
> >
> > and config.json will be like
> >
> > "ports" : [ {
> > "port" : "${qpid.amqp_port}",
> > "port" : "${qpid.http_port}",
> > "port" : "${qpid.jmx_port}"
> > "port" : "${qpid.rmi_port}"
> >
> >
> >
> > is there any property available for "authenticationProvider" so that i
> can
> > use it as variable in config file?
> >
> > like "authenticationProvider" : "${my_authenticationProvider}"
> >
> >
> > Thanks,
> > Ram
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
