Forgot to mention also that the regular python qpid.messaging library works fine, but I actually have a need to use the c bindings.
On Fri, Feb 10, 2012 at 11:11 AM, Brandon Pedersen <[email protected]> wrote: > On Fri, Feb 10, 2012 at 10:40 AM, Robbie Gemmell > <[email protected]> wrote: >> Hi Brandon, >> >> The python client is admitedly mostly used with the C++ broker >> currently, but there shouldnt be anything inherantly stopping its use >> with the Java broker given they both speak AMQP 0-10, and we would >> want to resolve it if there is. We do run the Python client tests and >> python based AMQP 0-10 broker tests against the Java broker on CI >> instances on a daily basis now (though my memory is fuzzy on if or how >> long we had before the 0.14 release initially branched ). > > I just want to point out that I am using the C bindings in Python, not > the basic qpid.messaging Python library > >> If you can possibly send the code you are having issue using (or a >> stripped down example based on it if its in any way sensitive), I will >> take a look if there is anything I can spot either in there or on the >> broker side while running it. > > Here is a very stripped down example that produces the problem: > from cqpid import Connection > conn = Connection("localhost", username="admin", password="admin", > reconnect=True) > conn.open() > session = conn.session() > >> With regards to the brokers log output, did you happen to turn on >> debug logging for analysis, or possibly somehow havent provided the >> default logging config we ship in the package? Almost none of that >> output should be displayed by default. > > Yes, I used the debug.log4j.xml so I could see if there were any > problems and pasted it here since I thought it might help. > > Thanks, > > -Brandon > >> Regards, >> Robbie >> >> On 10 February 2012 06:20, Brandon Pedersen <[email protected]> wrote: >>> Hi, I am currently using the C++ broker with the python cqpid client >>> and it is running smoothly. However, after reading through this >>> http://qpid.2158936.n2.nabble.com/DerbyDB-vs-BerkeleyDB-using-the-Java-Broker-tp7056640p7155540.html >>> I thought it would be best to switch to the Java broker instead. I am >>> currently using 0.12 but am testing out the 0.14 java broker (though >>> the same problem I am having exists with 0.12). When I try to use the >>> cqpid client with the Java broker it does not work. My python program >>> spits out a ton of messages like "warning Connection >>> [127.0.0.1:48782-localhost:5672] closed" and basically hangs...I have >>> to force kill it. And on the server it outputs the following over and >>> over again: >>> >>> 2012-02-08 22:22:53,592 INFO [IoReceiver - /127.0.0.1:33357] >>> logging.Log4jMessageLogger (Log4jMessageLogger.java:72) - >>> [con:458(/127.0.0.1:33357)] CON-1001 : Open : Protocol Version : 0-10 >>> 2012-02-08 22:22:53,592 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - RECV: [conn:5dfa490] AMQP.1 0-10 >>> 2012-02-08 22:22:53,593 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - SEND: [conn:5dfa490] AMQP.1 0-10 >>> 2012-02-08 22:22:53,593 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - SEND: [conn:5dfa490] ch=0 >>> ConnectionStart(serverProperties={qpid.federation_tag=957f527c-dfa5-4192-8160-9f092b31b303}, >>> mechanisms=[AMQPLAIN, PLAIN, CRAM-MD5], locales=[en_US]) >>> 2012-02-08 22:22:53,593 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - FLUSH: [conn:5dfa490] >>> 2012-02-08 22:22:53,594 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - RECV: [conn:5dfa490] ch=0 >>> ConnectionStartOk(clientProperties={qpid.client_pid=18119, >>> qpid.client_ppid=28800, qpid.client_process=python, >>> qpid.session_flow=1}, mechanism=, response=[B@1dacecf3, locale=en_US) >>> 2012-02-08 22:22:53,594 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - SEND: [conn:5dfa490] ch=0 >>> ConnectionTune(channelMax=256, maxFrameSize=65535, heartbeatMin=0, >>> heartbeatMax=0) >>> 2012-02-08 22:22:53,594 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - FLUSH: [conn:5dfa490] >>> 2012-02-08 22:22:53,595 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - RECV: [conn:5dfa490] ch=0 >>> ConnectionTuneOk(channelMax=256, maxFrameSize=65535, heartbeat=0) >>> 2012-02-08 22:22:53,595 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - RECV: [conn:5dfa490] ch=0 >>> ConnectionOpen(virtualHost=, capabilities=[], insist=true) >>> 2012-02-08 22:22:53,596 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - SEND: [conn:5dfa490] ch=0 >>> ConnectionOpenOk(knownHosts=[]) >>> 2012-02-08 22:22:53,596 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - FLUSH: [conn:5dfa490] >>> 2012-02-08 22:22:53,597 INFO [IoReceiver - /127.0.0.1:33357] >>> logging.Log4jMessageLogger (Log4jMessageLogger.java:72) - >>> [con:458(/127.0.0.1:33357)] CON-1001 : Open : Client ID : null : >>> Protocol Version : 0-10 >>> 2012-02-08 22:22:53,597 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - RECV: [conn:5dfa490] ch=1 >>> SessionAttach(name=[B@64836727) >>> 2012-02-08 22:22:53,597 DEBUG [IoReceiver - /127.0.0.1:33357] >>> util.Logger (Logger.java:54) - connection closed: conn:5dfa490 >>> >>> Any idea what might be wrong here? Is this a bug or am I potentially >>> doing something wrong? >>> >>> Thanks, >>> >>> -Brandon >>> >>> --------------------------------------------------------------------- >>> Apache Qpid - AMQP Messaging Implementation >>> Project: http://qpid.apache.org >>> Use/Interact: mailto:[email protected] >>> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
