RE: Incompatible code with NSS when buidling Qpid C++ Broker
Hello Steve, I am willing to help close this issue as I am currently compiling on SunOS. What do you need me to do? As I mentioned before, applying the proposed patch works (It fixes the compilation issue raised but of course there are other issues I am facing now).But, I couldn't find any jira issue with the patch attached. Regards,Adel Boutros,www.murex.com > From: shus...@riverace.com > To: users@qpid.apache.org > Subject: RE: Incompatible code with NSS when buidling Qpid C++ Broker > Date: Wed, 6 Apr 2016 23:11:35 + > > Offhand, there would be two reasons I can see... > > 1. The original poster didn't reply to the request to test the patch - Ken > said he couldn't test it > 2. There was no JIRA entered for it with the patch included > > -Steve > > > -Original Message- > > From: Adel Boutros [mailto:adelbout...@live.com] > > Sent: Wednesday, April 06, 2016 9:27 AM > > To: users@qpid.apache.org > > Subject: Incompatible code with NSS when buidling Qpid C++ Broker > > > > Hello, > > While building Qpid C++ Broker on SunOS, I encountered an error which has > > to do with NSS specific code. > > After checking this link (http://qpid.2158936.n2.nabble.com/NSS-lt-v3-14- > > and-qpidc-broker-build-td7622467.html) and applying the proposed patch, > > the file compiled correctly. > > Is there a reason this patch is not yet accepted and committed? > > Regards, > > Adel Boutroswww.murex.com > > > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org >
Re: Reactor Heartbeat [was: RE: Rapid generation of IOExceptions on Proton-J client recv() when HornetQ stopped/becomes unavailable]
Hi Matthew, I think your initial issue here is likely that HornetQ is neither requesting clients send it heartbeats, or supporting sending heartbeats to them if it so requested. It is however separately enforcing a timeout in its IO layer. I say that based on the heartbeat handling only quite recently being fixed in ActiveMQ Artemis, which is based on the previously donated HornetQ codebase. In AMQP 1.0 each side announces their own independent timeout requirements to the other side, with each then doing what they need to satisfy the peers requirements, either through normal messaging activity or by explicit heartbeat/empty frames in its absense. The proton engine satisfies/enforces these requirements via the transport tick method, as it seems you might be aware, which checks that requested heartbeats have been received and required heartbeats get sent, returning when it next needs to be called to keep on top of that. The reactor takes care of calling tick itself as far as I am aware and that being the case you also calling it should have no real effect on overall behaviour, which seems to be what you observed. In any case, if the broker has indeed not advertised an idleTimeout, the tick() will not produce heartbeat/empty frames because it has effectively been told it doesn't need to. It might be possible to tinker via reflection to trick it into thinking it should be. You also mention sending an empty frame, can you elaborate more on what you are doing exactly? If you look at the protocol trace (envieonment variable PN_TRACE_FRM=true) do you actually see it sending anything? The heartbeating stuff is all hidden behind tick(), so are you achieving that via reflection? Robbie On 6 April 2016 at 10:20, Matthew Karlsen wrote: > Hello All, > > After being directed towards the Proton-J reactor (away from the messenger), > I have been experimenting with reactor. I modified the supplied reactor > examples to send/recv to/from a queue on HornetQ fairly quickly. > > However, I appear to be having less success implementing a > heartbeat/keep-alive (HornetQ 2.4.0 will disconnect after a one minute > default if it does not receive data from the client). > > I have scheduled a regular event using [ e.getReactor().schedule(1, > this); ] with a view to implementing a heartbeat. I then override > onTimerTask() and call tick() or send an empty frame within onTimerTask() > then re-schedule another call of onTimerTask() -- I have tried several > permutations. > > However, whether I use tick(), or send an empty frame, it does not seem to > maintain the connection. > > I was wondering: > 1) Are there any better approaches? > 2) What is the "correct" approach/location for using tick()? > > Thank you & regards, > Matthew > > > > -Original Message- > From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] > Sent: 18 March 2016 17:59 > To: users@qpid.apache.org > Subject: Re: Rapid generation of IOExceptions on Proton-J client recv() when > HornetQ stopped/becomes unavailable > > On 18 March 2016 at 12:15, Matthew Karlsen wrote: >> Hello All, >> >> We have a queue running in HornetQ 2.4.0 (embedded within Wildfly), with a >> Proton-J 0.12.0 client periodically connecting to this queue. >> >> If HornetQ stops or becomes unavailable when the Proton-J client is running, >> the Proton-J client continually generates exceptions similar to that below >> (very rapidly). >> >> The issue is that the IOException generated exception is handled in >> MessengerImpl's processActive() by generating an "Error processing >> connection" message in the logs, rather than recv() throwing an exception >> and hence the higher level program logic is unable to react to the problem. >> >> Is this a bug or am I missing something important? >> >> Thank you, >> Matthew >> >> java.io.IOException: An existing connection was forcibly closed by the >> remote host >> at sun.nio.ch.SocketDispatcher.read0(Native Method) >> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) >> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) >> at sun.nio.ch.IOUtil.read(IOUtil.java:197) >> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) >> at >> org.apache.qpid.proton.driver.impl.ConnectorImpl.read(ConnectorImpl.java:129) >> at >> org.apache.qpid.proton.driver.impl.ConnectorImpl.process(ConnectorImpl.java:94) >> at >> org.apache.qpid.proton.messenger.impl.MessengerImpl.processActive(MessengerImpl.java:738) >> at >> org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:895) >> at >> org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:844) >> at >> org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:446) >> at >> org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:451) >> ... >> at java.lang.Thre
RE: Incompatible code with NSS when buidling Qpid C++ Broker
It would be great if you can raise a JIRA and attach your patch against the current trunk/head/master. Thanks, -Steve > -Original Message- > From: Adel Boutros [mailto:adelbout...@live.com] > Sent: Thursday, April 07, 2016 4:01 AM > To: users@qpid.apache.org > Subject: RE: Incompatible code with NSS when buidling Qpid C++ Broker > > Hello Steve, > I am willing to help close this issue as I am currently compiling on SunOS. > What do you need me to do? > As I mentioned before, applying the proposed patch works (It fixes the > compilation issue raised but of course there are other issues I am facing > now).But, I couldn't find any jira issue with the patch attached. > Regards,Adel Boutros,www.murex.com > > > From: shus...@riverace.com > > To: users@qpid.apache.org > > Subject: RE: Incompatible code with NSS when buidling Qpid C++ Broker > > Date: Wed, 6 Apr 2016 23:11:35 + > > > > Offhand, there would be two reasons I can see... > > > > 1. The original poster didn't reply to the request to test the patch - > > Ken said he couldn't test it 2. There was no JIRA entered for it with > > the patch included > > > > -Steve > > > > > -Original Message- > > > From: Adel Boutros [mailto:adelbout...@live.com] > > > Sent: Wednesday, April 06, 2016 9:27 AM > > > To: users@qpid.apache.org > > > Subject: Incompatible code with NSS when buidling Qpid C++ Broker > > > > > > Hello, > > > While building Qpid C++ Broker on SunOS, I encountered an error > > > which has to do with NSS specific code. > > > After checking this link > > > (http://qpid.2158936.n2.nabble.com/NSS-lt-v3-14- > > > and-qpidc-broker-build-td7622467.html) and applying the proposed > > > patch, the file compiled correctly. > > > Is there a reason this patch is not yet accepted and committed? > > > Regards, > > > Adel Boutroswww.murex.com > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For > > additional commands, e-mail: users-h...@qpid.apache.org > > > - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[VOTE] Release Qpid JMS client 0.9.0
Hi folks, I have put together a spin for a 0.9.0 Qpid JMS client release, please test it and vote accordingly. The source and binary archives can be grabbed from here: https://dist.apache.org/repos/dist/dev/qpid/jms/0.9.0-rc1/ Those files and the other maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1069 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1069 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 0.9.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
c++ (and other bindings) auto close behavior for handlers?
Currently proton-C and the various bindings do *not* auto-close contained objects when the container closes. I.e. closing a connection does not close its sessions, closing a session does not close its links etc. Also closing a transport does not automatically close its connection. I believe there are some reconnect use-cases that require this, e.g. if the transport closes unexpectedly you want to keep the connection and its children around so you can use them to re-build connection state on a new transport. However in the majority of cases it is a huge pain. Look at the existing broker.cpp example, `remove_stale_consumers`. The example isn't even complete: you must implement transport_close, connection_close, link_close (or in C++ sender_close and receiver_close) AND session_close (forgotten in the broker.cpp example) to clean up link resources correctly. I'd like to find a way to automate this that doesn't break the reconnect cases. Ideally I'd like it to be the default behavior unless a reconnect handler is in play. Can that be done with the existing event set or do we need new events? Cheers, Alan. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Anyone have an example of using message setProperty()?
At client site. Need a clear example of the usage of setProperty() Thanks for your help it is appreciated! Paul This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: Anyone have an example of using message setProperty()?
On 04/07/2016 04:55 PM, Flores, Paul A. wrote: At client site. Need a clear example of the usage of setProperty() Can you provide a bit more context on what code you are referring to and what you want to accomplish? Thanks for your help it is appreciated! Paul This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
java broker startup properties file
Hi, Is there any way to start qpid-java-0.28 broker using .properties file or .xml or .yaml file instead of .json file? or what are the other ways to pass override properties instead of JSON config file? Thanks, Ram
Re: java broker startup properties file
Firstly, 0.28 is quite old now - I would recommend updating to v6.0.1 if you can. Secondly I'm not sure I understand your question - are you asking about overriding particular properties, or the storage format for the broker configuration - these are two different things. In terms of properties / context overrides this can be specified using a properties file (at least in v6 - I forget exactly how it worked on 0.28). In terms of the configuration, JSON is currently the only text based format supported. You can use a database for the broker config storage, there are built in mechanisms to support Derby, BDB, and generic JDBC config stores. May I ask what advantage you would get by using YAML or properties files instead of JSON? -- Rob On 7 April 2016 at 22:43, rammohan ganapavarapu wrote: > Hi, > > Is there any way to start qpid-java-0.28 broker using .properties file or > .xml or .yaml file instead of .json file? or what are the other ways to > pass override properties instead of JSON config file? > > > Thanks, > Ram >
Re: java broker startup properties file
Rob,
Does v6.0.1 support Anonymous or no authentication? last time when i try to
use .32 it was not working with Anonymous.
Sorry i was not clear in my previous email, i was taking about properties
file not broker storage format, the use case is if i wanted to override
some of these properties and i have my own custom tool/script that goes
through the properties files and replace with the override i defined, so i
want to use the same tool/script for qpid config as well. My tool only
support key:value but if we have json array it wont work. So if i want to
pass overrides as "-prop" command line arguments what are the properties
that java qpid support as command line?
Below if my config, is it possible to pass all these as command line
arguments?
{
"authenticationproviders" : [ {
"id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
"name" : "Anonymous",
"type" : "Anonymous"
} ],
"defaultVirtualHost" : "default",
"id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
"modelVersion" : "1.3",
"name" : "Broker",
"plugins" : [ {
"id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
"name" : "httpManagement",
"pluginType" : "MANAGEMENT-HTTP"
}, {
"id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
"name" : "jmxManagement",
"pluginType" : "MANAGEMENT-JMX"
} ],
"ports" : [ {
"authenticationProvider" : "Anonymous",
"id" : "99e13356-080a-4abe-852e-8c452149cdae",
"name" : "JMX_CONNECTOR",
"port" : "9099",
"protocols" : [ "JMX_RMI" ]
}, {
"authenticationProvider" : "Anonymous",
"id" : "12813407-62ae-429f-8bee-75802f3b6553",
"name" : "RMI_REGISTRY",
"port" : "8999",
"protocols" : [ "RMI" ]
}, {
"authenticationProvider" : "Anonymous",
"id" : "3b107675-edd7-40a3-86c2-3113b46157f9",
"name" : "AMQP",
"port" : "5672"
}, {
"authenticationProvider" : "Anonymous",
"id" : "6dff5ecf-1a4b-46ad-b93d-f2606b5e4f6e",
"name" : "HTTP",
"port" : "10001",
"protocols" : [ "HTTP" ]
} ],
"storeVersion" : 1,
"virtualhosts" : [ {
"createdTime" : 1439482250329,
"id" : "eef20ba0-33d3-4b37-93a7-fe2b34e54503",
"name" : "default",
"storePath" : "/ebs//derbystore/default",
"storeType" : "DERBY",
"type" : "STANDARD"
} ]
}
One more question or may be clarification is,
*-sp (--store-path) is the path of config file that will generated by qpidd
from the initial config right? what is the use of store-path?*
*Thanks,*
*Ram*
On Thu, Apr 7, 2016 at 3:02 PM, Rob Godfrey wrote:
> Firstly, 0.28 is quite old now - I would recommend updating to v6.0.1 if
> you can.
>
> Secondly I'm not sure I understand your question - are you asking about
> overriding particular properties, or the storage format for the broker
> configuration - these are two different things. In terms of properties /
> context overrides this can be specified using a properties file (at least
> in v6 - I forget exactly how it worked on 0.28). In terms of the
> configuration, JSON is currently the only text based format supported. You
> can use a database for the broker config storage, there are built in
> mechanisms to support Derby, BDB, and generic JDBC config stores.
>
> May I ask what advantage you would get by using YAML or properties files
> instead of JSON?
>
> -- Rob
>
> On 7 April 2016 at 22:43, rammohan ganapavarapu
> wrote:
>
> > Hi,
> >
> > Is there any way to start qpid-java-0.28 broker using .properties file or
> > .xml or .yaml file instead of .json file? or what are the other ways to
> > pass override properties instead of JSON config file?
> >
> >
> > Thanks,
> > Ram
> >
>
Re: java broker startup properties file
On 7 April 2016 at 23:16, rammohan ganapavarapu
wrote:
> Rob,
>
> Does v6.0.1 support Anonymous or no authentication? last time when i try to
> use .32 it was not working with Anonymous.
>
Yes, Anonymous is supported. Which AMQP protocol are you using (0-9-1,
0-10, or 1.0)... I would expect that Anonymous should work on 0.32 however
I think in 0.32 the "no authentication layer at all" option for AMQP 1.0
probably didn't work (this is different to an authentication layer which
allows anonymous).
>
> Sorry i was not clear in my previous email, i was taking about properties
> file not broker storage format, the use case is if i wanted to override
> some of these properties and i have my own custom tool/script that goes
> through the properties files and replace with the override i defined, so i
> want to use the same tool/script for qpid config as well. My tool only
> support key:value but if we have json array it wont work. So if i want to
> pass overrides as "-prop" command line arguments what are the properties
> that java qpid support as command line?
>
> Below if my config, is it possible to pass all these as command line
> arguments?
>
> {
> "authenticationproviders" : [ {
> "id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
> "name" : "Anonymous",
> "type" : "Anonymous"
> } ],
> "defaultVirtualHost" : "default",
> "id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
> "modelVersion" : "1.3",
> "name" : "Broker",
> "plugins" : [ {
> "id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
> "name" : "httpManagement",
> "pluginType" : "MANAGEMENT-HTTP"
> }, {
> "id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
> "name" : "jmxManagement",
> "pluginType" : "MANAGEMENT-JMX"
> } ],
> "ports" : [ {
> "authenticationProvider" : "Anonymous",
> "id" : "99e13356-080a-4abe-852e-8c452149cdae",
> "name" : "JMX_CONNECTOR",
> "port" : "9099",
> "protocols" : [ "JMX_RMI" ]
> }, {
> "authenticationProvider" : "Anonymous",
> "id" : "12813407-62ae-429f-8bee-75802f3b6553",
> "name" : "RMI_REGISTRY",
> "port" : "8999",
> "protocols" : [ "RMI" ]
> }, {
> "authenticationProvider" : "Anonymous",
> "id" : "3b107675-edd7-40a3-86c2-3113b46157f9",
> "name" : "AMQP",
> "port" : "5672"
> }, {
> "authenticationProvider" : "Anonymous",
> "id" : "6dff5ecf-1a4b-46ad-b93d-f2606b5e4f6e",
> "name" : "HTTP",
> "port" : "10001",
> "protocols" : [ "HTTP" ]
> } ],
> "storeVersion" : 1,
> "virtualhosts" : [ {
> "createdTime" : 1439482250329,
> "id" : "eef20ba0-33d3-4b37-93a7-fe2b34e54503",
> "name" : "default",
> "storePath" : "/ebs//derbystore/default",
> "storeType" : "DERBY",
> "type" : "STANDARD"
> } ]
> }
>
>
>
In 6.0 you can replace any value in the JSON with a reference to a
property, for example
"name" : "${myPortName}",
this will then interpolate the value from the property, so if you set the
property myPortName to "RobsPort" that will be the value used. Type
conversions will be performed, so if the required value is an integer it
will convert to an integer. If the value required is a list then you can
use a String representation of a list in Json format.
You can set the properties individually, or you can pass in a properties
file using -props or --system-properties-file (so if you have a properties
file already maybe you can just pass this in).
> One more question or may be clarification is,
>
>
> *-sp (--store-path) is the path of config file that will generated by qpidd
> from the initial config right? what is the use of store-path?*
>
>
That is correct. Some people just like to have config files in a
non-default location :-)
Hope this helps,
Rob
> *Thanks,*
>
> *Ram*
>
> On Thu, Apr 7, 2016 at 3:02 PM, Rob Godfrey
> wrote:
>
> > Firstly, 0.28 is quite old now - I would recommend updating to v6.0.1 if
> > you can.
> >
> > Secondly I'm not sure I understand your question - are you asking about
> > overriding particular properties, or the storage format for the broker
> > configuration - these are two different things. In terms of properties /
> > context overrides this can be specified using a properties file (at least
> > in v6 - I forget exactly how it worked on 0.28). In terms of the
> > configuration, JSON is currently the only text based format supported.
> You
> > can use a database for the broker config storage, there are built in
> > mechanisms to support Derby, BDB, and generic JDBC config stores.
> >
> > May I ask what advantage you would get by using YAML or properties files
> > instead of JSON?
> >
> > -- Rob
> >
> > On 7 April 2016 at 22:43, rammohan ganapavarapu >
> > wrote:
> >
> > > Hi,
> > >
> > > Is there any way to start qpid-java-0.28 broker using .properties file
> or
> > > .xml or .yaml file instead of .json file? or what are the other ways to
> > > pass override properties instead of JSON config file?
> > >
> > >
> > > Thanks,
> > > Ram
> > >
Re: java broker startup properties file
This looks like a client error to me... the line which says:
Client restricted itself to : PLAIN
Out of interest what happens if you remove the &sasl_mechs='ANONYMOUS' from
your connection URL? Without any sort of restriction I'd expect the client
to do the right thing.
I need to get to sleep now (1am here :-) )... I'll have deeper look in the
morning.
-- Rob
On 7 April 2016 at 23:51, rammohan ganapavarapu
wrote:
> Rob,
>
> thanks for the explanation, do you have a sample --system-properties-file?
> that i can take a look?
>
> Also i just tried 6.0.1 but my client/app is throwing this error, i am not
> a developer, i am ops guy and i dont want to change the existing code but
> wanted to make java qpid work. This is the error i am getting with 6.0.1v..
>
> 2016-04-07 22:32:36,726
> QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> to Connection : 0 Host = qphost01
>
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> error Unknown virtualhost '' username=null
> 2016-04-07 22:32:36,731
> QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> to Connection : 0 Host = qphost01
>
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> error Client and broker have no SASL mechanisms in common. Broker allows :
> ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5,
> AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : PLAIN
> username=guest
>
>
> And here is my sasl mechanism.
>
> curl -s 0:10001/service/sasl
> {
> "user" : "ANONYMOUS",
> "mechanisms" : [ "ANONYMOUS" ]
>
> Same SASL with 0.28 works fine with my app but 6.0.1 is not working.
>
>
> Thanks,
> Ram
>
>
>
> On Thu, Apr 7, 2016 at 3:39 PM, Rob Godfrey
> wrote:
>
> > On 7 April 2016 at 23:16, rammohan ganapavarapu >
> > wrote:
> >
> > > Rob,
> > >
> > > Does v6.0.1 support Anonymous or no authentication? last time when i
> try
> > to
> > > use .32 it was not working with Anonymous.
> > >
> >
> > Yes, Anonymous is supported. Which AMQP protocol are you using (0-9-1,
> > 0-10, or 1.0)... I would expect that Anonymous should work on 0.32
> however
> > I think in 0.32 the "no authentication layer at all" option for AMQP 1.0
> > probably didn't work (this is different to an authentication layer which
> > allows anonymous).
> >
> >
> > >
> > > Sorry i was not clear in my previous email, i was taking about
> properties
> > > file not broker storage format, the use case is if i wanted to override
> > > some of these properties and i have my own custom tool/script that
> goes
> > > through the properties files and replace with the override i defined,
> so
> > i
> > > want to use the same tool/script for qpid config as well. My tool only
> > > support key:value but if we have json array it wont work. So if i want
> to
> > > pass overrides as "-prop" command line arguments what are the
> properties
> > > that java qpid support as command line?
> > >
> > > Below if my config, is it possible to pass all these as command line
> > > arguments?
> > >
> > > {
> > > "authenticationproviders" : [ {
> > > "id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
> > > "name" : "Anonymous",
> > > "type" : "Anonymous"
> > > } ],
> > > "defaultVirtualHost" : "default",
> > > "id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
> > > "modelVersion" : "1.3",
> > > "name" : "Broker",
> > > "plugins" : [ {
> > > "id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
> > > "name" : "httpManagement",
> > > "pluginType" : "MANAGEMENT-HTTP"
> > > }, {
> > > "id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
> > > "name" : "jmxManagement",
> > > "pluginType" : "MANAGEMENT-JMX"
> > > } ],
> > > "ports" : [ {
> > > "authenticationProvider" : "Anonymous",
> > > "id" : "99e13356-080a-4abe-852e-8c452149cdae",
> > > "name" : "JMX_CONNECTOR",
> > > "port" : "9099",
> > > "protocols" : [ "JMX_RMI" ]
> > > }, {
> > > "authenticationProvider" : "Anonymous",
> > > "id" : "12813407-62ae-429f-8bee-75802f3b6553",
> > > "name" : "RMI_REGISTRY",
> > > "port" : "8999",
> > > "protocols" : [ "RMI" ]
> > > }, {
> > > "authenticationProvider" : "Anonymous",
> > > "id" : "3b107675-edd7-40a3-86c2-3113b46157f9",
> > > "name" : "AMQP",
> > > "port" : "5672"
> > > }, {
> > > "authenticationProvider" : "Anonymous",
> > > "id" : "6dff5ecf-1a4b-46ad-b93d-f2606b5e4f6e",
> > > "name" : "HTTP",
> > > "port" : "10001",
> > > "protocols" : [ "HTTP" ]
> > > } ],
> > > "storeVersion" : 1,
> > > "virtualhosts" : [ {
> > > "createdTime" : 1439482250329,
> > > "id" : "eef20ba0-33d3-4b37-93a7-fe2b34e54503",
> > > "name" : "default",
Re: [VOTE] Release Qpid JMS client 0.9.0
+1 * Checked the signatures and sums * Built the src and ran all tests * Ran the example against an ActiveMQ 5 broker * Ran the AMQP test suite in ActiveMQ 5 using the staged artifact * Checked the LICENSE and NOTICE files * Reviewed the Documentation file On 04/07/2016 01:04 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.9.0 Qpid JMS client release, please test it and vote accordingly. The source and binary archives can be grabbed from here: https://dist.apache.org/repos/dist/dev/qpid/jms/0.9.0-rc1/ Those files and the other maven artifacts are also staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1069 Regards, Robbie P.S. If you want to test it out using maven (e.g with the examples src, or your own things), you can temporarily add this to your poms to access the staging repo: staging https://repository.apache.org/content/repositories/orgapacheqpid-1069 The dependency for the client itself would then be: org.apache.qpid qpid-jms-client 0.9.0 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: java broker startup properties file
Rob,
thanks for the explanation, do you have a sample --system-properties-file?
that i can take a look?
Also i just tried 6.0.1 but my client/app is throwing this error, i am not
a developer, i am ops guy and i dont want to change the existing code but
wanted to make java qpid work. This is the error i am getting with 6.0.1v..
2016-04-07 22:32:36,726
QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
to Connection : 0 Host = qphost01
url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
error Unknown virtualhost '' username=null
2016-04-07 22:32:36,731
QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
to Connection : 0 Host = qphost01
url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
error Client and broker have no SASL mechanisms in common. Broker allows :
ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5,
AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : PLAIN
username=guest
And here is my sasl mechanism.
curl -s 0:10001/service/sasl
{
"user" : "ANONYMOUS",
"mechanisms" : [ "ANONYMOUS" ]
Same SASL with 0.28 works fine with my app but 6.0.1 is not working.
Thanks,
Ram
On Thu, Apr 7, 2016 at 3:39 PM, Rob Godfrey wrote:
> On 7 April 2016 at 23:16, rammohan ganapavarapu
> wrote:
>
> > Rob,
> >
> > Does v6.0.1 support Anonymous or no authentication? last time when i try
> to
> > use .32 it was not working with Anonymous.
> >
>
> Yes, Anonymous is supported. Which AMQP protocol are you using (0-9-1,
> 0-10, or 1.0)... I would expect that Anonymous should work on 0.32 however
> I think in 0.32 the "no authentication layer at all" option for AMQP 1.0
> probably didn't work (this is different to an authentication layer which
> allows anonymous).
>
>
> >
> > Sorry i was not clear in my previous email, i was taking about properties
> > file not broker storage format, the use case is if i wanted to override
> > some of these properties and i have my own custom tool/script that goes
> > through the properties files and replace with the override i defined, so
> i
> > want to use the same tool/script for qpid config as well. My tool only
> > support key:value but if we have json array it wont work. So if i want to
> > pass overrides as "-prop" command line arguments what are the properties
> > that java qpid support as command line?
> >
> > Below if my config, is it possible to pass all these as command line
> > arguments?
> >
> > {
> > "authenticationproviders" : [ {
> > "id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
> > "name" : "Anonymous",
> > "type" : "Anonymous"
> > } ],
> > "defaultVirtualHost" : "default",
> > "id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
> > "modelVersion" : "1.3",
> > "name" : "Broker",
> > "plugins" : [ {
> > "id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
> > "name" : "httpManagement",
> > "pluginType" : "MANAGEMENT-HTTP"
> > }, {
> > "id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
> > "name" : "jmxManagement",
> > "pluginType" : "MANAGEMENT-JMX"
> > } ],
> > "ports" : [ {
> > "authenticationProvider" : "Anonymous",
> > "id" : "99e13356-080a-4abe-852e-8c452149cdae",
> > "name" : "JMX_CONNECTOR",
> > "port" : "9099",
> > "protocols" : [ "JMX_RMI" ]
> > }, {
> > "authenticationProvider" : "Anonymous",
> > "id" : "12813407-62ae-429f-8bee-75802f3b6553",
> > "name" : "RMI_REGISTRY",
> > "port" : "8999",
> > "protocols" : [ "RMI" ]
> > }, {
> > "authenticationProvider" : "Anonymous",
> > "id" : "3b107675-edd7-40a3-86c2-3113b46157f9",
> > "name" : "AMQP",
> > "port" : "5672"
> > }, {
> > "authenticationProvider" : "Anonymous",
> > "id" : "6dff5ecf-1a4b-46ad-b93d-f2606b5e4f6e",
> > "name" : "HTTP",
> > "port" : "10001",
> > "protocols" : [ "HTTP" ]
> > } ],
> > "storeVersion" : 1,
> > "virtualhosts" : [ {
> > "createdTime" : 1439482250329,
> > "id" : "eef20ba0-33d3-4b37-93a7-fe2b34e54503",
> > "name" : "default",
> > "storePath" : "/ebs//derbystore/default",
> > "storeType" : "DERBY",
> > "type" : "STANDARD"
> > } ]
> > }
> >
> >
> >
> In 6.0 you can replace any value in the JSON with a reference to a
> property, for example
>
> "name" : "${myPortName}",
>
> this will then interpolate the value from the property, so if you set the
> property myPortName to "RobsPort" that will be the value used. Type
> conversions will be performed, so if the required value is an integer it
> will convert to an integer. If the value required is a list then you can
> use a String representation of a list in Json format.
>
> You can set the properties individually, or you can pass i
Re: java broker startup properties file
Rob,
Thank you, one more question on -icp and -sp, so what if i have updated icp
with some property change and restarted broker with icp (every time i
restart broker i am using initial config
"/opt/qpid-java-broker/bin/qpid-server -icp
/opt/qpid-java-broker/etc/config.json" not sure if its is right way or
not), does it automatically update config file in -sp? i my case it did not
updated the config file in store-path upon restart. What will happened if i
have differences in initial config file that i use to start broker and the
config file under store-path?
Thanks,
Ram
On Thu, Apr 7, 2016 at 3:59 PM, Rob Godfrey wrote:
> This looks like a client error to me... the line which says:
>
> Client restricted itself to : PLAIN
>
> Out of interest what happens if you remove the &sasl_mechs='ANONYMOUS' from
> your connection URL? Without any sort of restriction I'd expect the client
> to do the right thing.
>
> I need to get to sleep now (1am here :-) )... I'll have deeper look in the
> morning.
>
> -- Rob
>
> On 7 April 2016 at 23:51, rammohan ganapavarapu
> wrote:
>
> > Rob,
> >
> > thanks for the explanation, do you have a sample
> --system-properties-file?
> > that i can take a look?
> >
> > Also i just tried 6.0.1 but my client/app is throwing this error, i am
> not
> > a developer, i am ops guy and i dont want to change the existing code but
> > wanted to make java qpid work. This is the error i am getting with
> 6.0.1v..
> >
> > 2016-04-07 22:32:36,726
> > QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> > S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> > to Connection : 0 Host = qphost01
> >
> >
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> > error Unknown virtualhost '' username=null
> > 2016-04-07 22:32:36,731
> > QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> > S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> > to Connection : 0 Host = qphost01
> >
> >
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> > error Client and broker have no SASL mechanisms in common. Broker allows
> :
> > ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5,
> > AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : PLAIN
> > username=guest
> >
> >
> > And here is my sasl mechanism.
> >
> > curl -s 0:10001/service/sasl
> > {
> > "user" : "ANONYMOUS",
> > "mechanisms" : [ "ANONYMOUS" ]
> >
> > Same SASL with 0.28 works fine with my app but 6.0.1 is not working.
> >
> >
> > Thanks,
> > Ram
> >
> >
> >
> > On Thu, Apr 7, 2016 at 3:39 PM, Rob Godfrey
> > wrote:
> >
> > > On 7 April 2016 at 23:16, rammohan ganapavarapu <
> rammohanga...@gmail.com
> > >
> > > wrote:
> > >
> > > > Rob,
> > > >
> > > > Does v6.0.1 support Anonymous or no authentication? last time when i
> > try
> > > to
> > > > use .32 it was not working with Anonymous.
> > > >
> > >
> > > Yes, Anonymous is supported. Which AMQP protocol are you using (0-9-1,
> > > 0-10, or 1.0)... I would expect that Anonymous should work on 0.32
> > however
> > > I think in 0.32 the "no authentication layer at all" option for AMQP
> 1.0
> > > probably didn't work (this is different to an authentication layer
> which
> > > allows anonymous).
> > >
> > >
> > > >
> > > > Sorry i was not clear in my previous email, i was taking about
> > properties
> > > > file not broker storage format, the use case is if i wanted to
> override
> > > > some of these properties and i have my own custom tool/script that
> > goes
> > > > through the properties files and replace with the override i defined,
> > so
> > > i
> > > > want to use the same tool/script for qpid config as well. My tool
> only
> > > > support key:value but if we have json array it wont work. So if i
> want
> > to
> > > > pass overrides as "-prop" command line arguments what are the
> > properties
> > > > that java qpid support as command line?
> > > >
> > > > Below if my config, is it possible to pass all these as command line
> > > > arguments?
> > > >
> > > > {
> > > > "authenticationproviders" : [ {
> > > > "id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
> > > > "name" : "Anonymous",
> > > > "type" : "Anonymous"
> > > > } ],
> > > > "defaultVirtualHost" : "default",
> > > > "id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
> > > > "modelVersion" : "1.3",
> > > > "name" : "Broker",
> > > > "plugins" : [ {
> > > > "id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
> > > > "name" : "httpManagement",
> > > > "pluginType" : "MANAGEMENT-HTTP"
> > > > }, {
> > > > "id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
> > > > "name" : "jmxManagement",
> > > > "pluginType" : "MANAGEMENT-JMX"
> > > > } ],
> > > > "ports" : [ {
> > > > "authenticationProvider" : "Anonymous",
> > > > "id" : "99e13356-080
Re: java broker startup properties file
Rob,
Please also share --system-properties-file sample file.
Thanks,
Ram
On Thu, Apr 7, 2016 at 3:51 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:
> Rob,
>
> thanks for the explanation, do you have a sample --system-properties-file?
> that i can take a look?
>
> Also i just tried 6.0.1 but my client/app is throwing this error, i am not
> a developer, i am ops guy and i dont want to change the existing code but
> wanted to make java qpid work. This is the error i am getting with 6.0.1v..
>
> 2016-04-07 22:32:36,726
> QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> to Connection : 0 Host = qphost01
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> error Unknown virtualhost '' username=null
> 2016-04-07 22:32:36,731
> QPIDConnectionManager-80478ba7-b31e-483a-823e-f726104ac1db ERROR
> S.QUEUECLIENTSERVICE - ConnectionImpl.openConnection() : Error connecting
> to Connection : 0 Host = qphost01
> url=amqp://null:@qphost011460067563391/?brokerlist='tcp://localhost:5672?connecttimeout='5000'&sasl_mechs='ANONYMOUS''
> error Client and broker have no SASL mechanisms in common. Broker allows :
> ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5,
> AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : PLAIN
> username=guest
>
>
> And here is my sasl mechanism.
>
> curl -s 0:10001/service/sasl
> {
> "user" : "ANONYMOUS",
> "mechanisms" : [ "ANONYMOUS" ]
>
> Same SASL with 0.28 works fine with my app but 6.0.1 is not working.
>
>
> Thanks,
> Ram
>
>
>
> On Thu, Apr 7, 2016 at 3:39 PM, Rob Godfrey
> wrote:
>
>> On 7 April 2016 at 23:16, rammohan ganapavarapu
>> wrote:
>>
>> > Rob,
>> >
>> > Does v6.0.1 support Anonymous or no authentication? last time when i
>> try to
>> > use .32 it was not working with Anonymous.
>> >
>>
>> Yes, Anonymous is supported. Which AMQP protocol are you using (0-9-1,
>> 0-10, or 1.0)... I would expect that Anonymous should work on 0.32 however
>> I think in 0.32 the "no authentication layer at all" option for AMQP 1.0
>> probably didn't work (this is different to an authentication layer which
>> allows anonymous).
>>
>>
>> >
>> > Sorry i was not clear in my previous email, i was taking about
>> properties
>> > file not broker storage format, the use case is if i wanted to override
>> > some of these properties and i have my own custom tool/script that goes
>> > through the properties files and replace with the override i defined,
>> so i
>> > want to use the same tool/script for qpid config as well. My tool only
>> > support key:value but if we have json array it wont work. So if i want
>> to
>> > pass overrides as "-prop" command line arguments what are the
>> properties
>> > that java qpid support as command line?
>> >
>> > Below if my config, is it possible to pass all these as command line
>> > arguments?
>> >
>> > {
>> > "authenticationproviders" : [ {
>> > "id" : "7050933f-3485-4866-95d2-1f1b258ea3ac",
>> > "name" : "Anonymous",
>> > "type" : "Anonymous"
>> > } ],
>> > "defaultVirtualHost" : "default",
>> > "id" : "c433a66c-e6dc-4c48-be01-268295f580bc",
>> > "modelVersion" : "1.3",
>> > "name" : "Broker",
>> > "plugins" : [ {
>> > "id" : "58889cb7-9b9b-4866-bab2-4cfd63266dbf",
>> > "name" : "httpManagement",
>> > "pluginType" : "MANAGEMENT-HTTP"
>> > }, {
>> > "id" : "67282f5e-ebab-4341-9ff5-27a58fd2df89",
>> > "name" : "jmxManagement",
>> > "pluginType" : "MANAGEMENT-JMX"
>> > } ],
>> > "ports" : [ {
>> > "authenticationProvider" : "Anonymous",
>> > "id" : "99e13356-080a-4abe-852e-8c452149cdae",
>> > "name" : "JMX_CONNECTOR",
>> > "port" : "9099",
>> > "protocols" : [ "JMX_RMI" ]
>> > }, {
>> > "authenticationProvider" : "Anonymous",
>> > "id" : "12813407-62ae-429f-8bee-75802f3b6553",
>> > "name" : "RMI_REGISTRY",
>> > "port" : "8999",
>> > "protocols" : [ "RMI" ]
>> > }, {
>> > "authenticationProvider" : "Anonymous",
>> > "id" : "3b107675-edd7-40a3-86c2-3113b46157f9",
>> > "name" : "AMQP",
>> > "port" : "5672"
>> > }, {
>> > "authenticationProvider" : "Anonymous",
>> > "id" : "6dff5ecf-1a4b-46ad-b93d-f2606b5e4f6e",
>> > "name" : "HTTP",
>> > "port" : "10001",
>> > "protocols" : [ "HTTP" ]
>> > } ],
>> > "storeVersion" : 1,
>> > "virtualhosts" : [ {
>> > "createdTime" : 1439482250329,
>> > "id" : "eef20ba0-33d3-4b37-93a7-fe2b34e54503",
>> > "name" : "default",
>> > "storePath" : "/ebs//derbystore/default",
>> > "storeType" : "DERBY",
>> > "type" : "STANDARD"
>> > } ]
>> > }
>> >
>> >
>> >
>> In 6.0 you can replace any value in the JSON with a reference to a
>> property, for example
>>
>> "name" : "${myPortName}",
>>
>> this will then interpolate the value from the property, so if you set th
