Re: Stating Qpid on Windows

Ok, thanks it's working:) but now how can i check connections,queues etc? and how can i stop it?? W dniu 2010-12-02 21:30, Steve Huston pisze: Hi Adam, I have a problem with starting Qpid server on Windows. I'm trying to run it as administrator but get error Cannot create directory \temp\qu

RE: Stating Qpid on Windows

Hi Adam, > I have a problem with starting Qpid server on Windows. I'm trying to > run it as administrator but get error > Cannot create directory \temp\qupid > > Where I need to change path for data?? You can use the --data-dir option (see qpidd --help) -Steve -- Steve Huston, Riverace Corp

Stating Qpid on Windows

Hi, I have a problem with starting Qpid server on Windows. I'm trying to run it as administrator but get error Cannot create directory \temp\qupid Where I need to change path for data?? Regards, Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and i

Timer callback overran

Greetings. Could you please help me with the following warning message on c++ qpid broker 0.7 verson? We use java client in this example. 2010-12-02 19:25:05 warning Timer callback overran by 2ms [taking 21000ns] 2010-12-02 19:25:05 warning Timer callback overran by 2ms [taking 4000ns] 2010-12-0

Re: error Could not accept socket: Too many open files

Thank you for the good explanation. How is it possible to research the issue with ulimits? How can I determine, why my system use more than 1024 open file descritors/sockets? I know the queue count, and I suppose I can monitor (with qpid-stat) the connections to the broker. In general I use about

Re: How to handle large messages in Qpid Java client

Forwarding to dev list ! On Thu, Dec 2, 2010 at 3:28 PM, Lahiru Gunathilake wrote: > FYI, I try to monitor all the reads from the socket InputStream from the > client and I can see that Client is reading a curupted message, so > I guarantee that there's no issue in Client side IoSendere and IoRec

Re: How to handle large messages in Qpid Java client

FYI, I try to monitor all the reads from the socket InputStream from the client and I can see that Client is reading a curupted message, so I guarantee that there's no issue in Client side IoSendere and IoReceiver classes. I think the issue is with the broker IoReceiver or Sending, we found that t