I figured out. It's due to old version of Python interpreter bundled with
open office. I upgraded to Python version 2.6.6 and it works fine. Thanks
for the help.
Rajika
On Wed, Dec 15, 2010 at 8:33 PM, Rajika Kumarasiri wrote:
> Do you see anything suspicious? I'll also upgrade to version 2.6.6
Are you referring to qpid-2979? Not sure what you're asking...
-Steve
--
Steve Huston, Riverace Corporation
Total Lifecycle Support for Your Networked Applications
http://www.riverace.com
> -Original Message-
> From: pete.carapet...@gmail.com
> [mailto:pete.carapet...@gmail.com] On Beh
On Thu, Dec 16, 2010 at 5:45 AM, Pete Carapetyan
wrote:
> Still not sure what this means from the java side. Suggestions?
>
Can you try telnet and see if actually a server socket is listening on the
port ?
Rajika
>
> On Wed, Dec 15, 2010 at 4:29 PM, Adam Kaminiecki
> wrote:
> > ok will try to
Still not sure what this means from the java side. Suggestions?
On Wed, Dec 15, 2010 at 4:29 PM, Adam Kaminiecki wrote:
> ok will try to turn on trace
> but --auth no for now resolve my problem. Thanks a lot.
>
>
> regards,
> Adam
>
> W dniu 2010-12-15 22:53, Steve Huston pisze:
>>
>> Hi Adam,
>>
ok will try to turn on trace
but --auth no for now resolve my problem. Thanks a lot.
regards,
Adam
W dniu 2010-12-15 22:53, Steve Huston pisze:
Hi Adam,
I have little simillar problem with qpid 0.8
I'm using C# client
connections = new Client();
connections.ExceptionRais
Hi Adam,
> I have little simillar problem with qpid 0.8
>
> I'm using C# client
>
> connections = new Client();
>
> connections.ExceptionRaised +=
> ConnectionsExceptionRaised;
> connections.ConnectionLost +=
> ConnectionsConnectionLost;
> co
Hi,
I have little simillar problem with qpid 0.8
I'm using C# client
connections = new Client();
connections.ExceptionRaised += ConnectionsExceptionRaised;
connections.ConnectionLost += ConnectionsConnectionLost;
connections.Connect(host, port, "
Hi I've never used qpid before so I'm attempting to run the java
examples. My broker says it is running fine, and I can fire up the
examples fine from either from within my IDE or with the example
script, but either way I am getting this when I fire up the Hello
client example.
javax.jms.JMSExcept
Greetings
Be careful with transactions. It brings you to drop the performance down
up to 300 times!
I have posted my performance test results and code some weeks ago.
Regards,
Boris
Marnie McCormack
15.12.2010 09:55
Please respond to
users@qpid.apache.org
To
users@qpid.apache.org
cc
Subj
Do you see anything suspicious? I'll also upgrade to version 2.6.6 of Python
and see how it goes.
Rajika
On Wed, Dec 15, 2010 at 8:06 AM, Rajika Kumarasiri wrote:
>
>
> On Wed, Dec 15, 2010 at 1:46 AM, Jonathan Robie > wrote:
>
>> What does your PYTHONPATH look like?
>>
>
> [raj...@localhost p
All right, I've created https://issues.apache.org/jira/browse/QPID-2979
(hopefully correctly)
Ibisek
__
> Od: "Steve Huston"
> Komu:
> Datum: 15.12.2010 14:58
> Předmět: RE: Error creating connection: The following SASL mechanisms
On Wed, 2010-12-15 at 13:18 +, Gordon Sim wrote:
> On 12/15/2010 01:07 PM, Bruno Matos wrote:
> > The connection ID can be
> > something generated in broker side, a hash a sequence number generator
> > or something like that.
>
> Out of curiosity, how would that be used?
>
:)
Would be used
On 12/15/2010 01:57 PM, Steve Huston wrote:
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
For now it would probably be simplest to not use auth=no, and simply
setup a trivial user database with guest as the only user.
(I don't know anything yet about how the broker on wind
Good morning.
> -Original Message-
> From: Gordon Sim [mailto:g...@redhat.com]
>
> On 12/15/2010 12:57 PM, junkmai...@centrum.cz wrote:
> >
> > All right, will see what the 0.9 brings.
Could you please enter a JIRA for this issue? Else 0.9 won't bring
anything ;-)
> For now it would pr
On 12/15/2010 01:07 PM, Bruno Matos wrote:
The connection ID can be
something generated in broker side, a hash a sequence number generator
or something like that.
Out of curiosity, how would that be used?
-
Apache Qpid - AMQP
On Wed, 2010-12-15 at 13:00 +, Gordon Sim wrote:
> On 12/14/2010 09:41 AM, Bruno Matos wrote:
> > On Mon, 2010-12-13 at 12:09 +, Bruno Matos wrote:
> >> Hi,
> >>
> >> There is any way to associate a message with the connection ID used to
> >> publish it?
> >>
> >
> > Hi,
> >
> > Sorry for t
On 12/14/2010 09:41 AM, Bruno Matos wrote:
On Mon, 2010-12-13 at 12:09 +, Bruno Matos wrote:
Hi,
There is any way to associate a message with the connection ID used to
publish it?
Hi,
Sorry for the leak of information.
What I need is to add the connection ID to every message that arriv
On 12/15/2010 12:57 PM, junkmai...@centrum.cz wrote:
All right, will see what the 0.9 brings.
For now it would probably be simplest to not use auth=no, and simply
setup a trivial user database with guest as the only user.
(I don't know anything yet about how the broker on windows manages
u
All right, will see what the 0.9 brings.
Thank you for the interaction!
Ibisek
__
> Od: "Gordon Sim"
> Komu: users@qpid.apache.org
> Datum: 15.12.2010 13:49
> Předmět: Re: Error creating connection: The following SASL mechanisms [PLAI
On 12/15/2010 10:48 AM, junkmai...@centrum.cz wrote:
I am getting this:
C:Program Filesapache-qpidc-0.8bin>qpidd --auth no --log-enable info+
--log-enable trace+:amqp_0_10
2010-12-15 11:42:48 info Management enabled
2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
2010-12-1
Hi Gordon,
I am getting this:
C:Program Filesapache-qpidc-0.8bin>qpidd --auth no --log-enable info+
--log-enable trace+:amqp_0_10
2010-12-15 11:42:48 info Management enabled
2010-12-15 11:42:48 notice SASL disabled: No Authentication Performed
2010-12-15 11:42:48 info Policy file not specified.
On 12/15/2010 10:03 AM, junkmai...@centrum.cz wrote:
I am trying to reach a qpidd broker started with the --auth no option from a
Java client (both version 0.8) and am receiving the following exception:
javax.jms.JMSException: Error creating connection: The following SASL
mechanisms [PLAIN] sp
On 12/15/2010 08:01 AM, gcutuli wrote:
can someone help me in understanding the usage of the class
"FailoverUpdates" provided by Qpid Messaging API ?
AMQP 0-10 defines a 'failover' exchange type. A client can bind a queue
to that exchange and subscribe to it in order to maintain a current list
Hi guys,
I am trying to reach a qpidd broker started with the --auth no option from a
Java client (both version 0.8) and am receiving the following exception:
javax.jms.JMSException: Error creating connection: The following SASL
mechanisms [PLAIN] specified by the client are not supported by t
Dear all,
can someone help me in understanding the usage of the class
"FailoverUpdates" provided by Qpid Messaging API ?
Thanks in advance.
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/About-failoverUpdates-tp5837418p5837418.html
Sent from the Apache Qpid users
25 matches
Mail list logo