Can't build proton-c undefined symbols ERR_get_error etc

Hi all We are having problems building proton-c on our dev boxes (Red Hat Enterprise Linux Server release 5.3 (Tikanga)). I've done a git bisect and discovered that it was Andrew's commit last Wednesday (rev 1417553) that has introduced/exposed the issue. Before that point, we could build withou

Re: Can't build proton-c undefined symbols ERR_get_error etc

Hi Andrew, Thanks for the rapid response. I confirm that the workaroud you suggest works successfully. Here are the details: > Could you run "make VERBOSE=1" and post the final link line (only). /usr/bin/cmake -E cmake_link_script CMakeFiles/qpid-proton.dir/link.txt --verbose=1 /usr/bin/gcc -f

Changing the Proton build system to accommodate jni bindings

We are currently in the process of implementing the proton-jni binding for the proton-c library that implements the Java Proton-API, allow Java users to choose the C based proton stack if they wish. This work is being performed on the jni-branch under PROTON-192 (for the JNI work) and PROTON-194 (f

Re: Changing the Proton build system to accommodate jni bindings

>> What are people's views on the relative priority of these requirements? >> Are there any I've missed? I think answering these questions is a >> prerequisite for agreeing the technical solution. With the aim of stimulating discussion regarding our requirements and to reach a consensus, I've cla

Re: Question about proton-c message id API

On 23 January 2013 15:40, Rafael Schloming wrote: > Yeah, it appears to be a bug. I checked in a potential fix on trunk. Give > it a shot and see if it's still an issue. > > --Rafael Thanks, that has indeed addressed the issue. The Message system tests which previously failed now run cleanly aga

Building proton-c: cc1: error: unrecognized command line option "-Wvla" (RHEL 5.3)

Hi all, I'm getting a problem building proton-c since rev 1441872 (Sunday 2013-02-03). It looks like the introduction of the flag -Wvla has caused the problem. I've included full details below. Do we have a statement regarding the minumum versions of Proton's build and runtime dependencies? Kin

Re: Building proton-c: cc1: error: unrecognized command line option "-Wvla" (RHEL 5.3)

On 5 February 2013 17:38, Cliff Jansen wrote: > Hmmm. You raise a good point. > > On the one hand, we want people to be policed by these flags if they > are contributing to the proton-c work. However, we don't want proton > to be difficult to build for anybody else. > > I will raise a JIRA to ha

Proton CI jobs on Apache Jenkins (PROTON-196)

Just to let you know we now have the following jobs configured on the Apache Jenkins CI instances: Builds proton-c and executes the Python system tests: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-c/ Builds proton-j and executes the Python/Java system tests: https://builds.apache

Re: [proton-j] MessengerFactory

Hi Rajith > I was wondering what is the mechanism recommended for obtaining a > MessengerFactory instance (other than directly instantiating it). Take a look at ProtonFactoryLoader and the factories themselves: EngineFactory, MessengerFactory, MessageFactory etc. ProtonFactoryLoader is ServiceLoa

Re: 0.4 RC2

Hi Paul I've successfuly reproduced your issue and are tracking our progress under PROTON-249. We don't need your debug output at this stage. Kind regards, Keith. On 24 February 2013 00:27, Paul O'Fallon wrote: > I filed this as https://issues.apache.org/jira/browse/PROTON-249 > > I have some

Problem building Proton-c's java bindings on Windows - Cannot open include file: 'stdbool.h

I’m trying to build Proton-C’s Java Bindings on Windows using Microsoft Visual Studio 2010 in order to verify the changes for PROTON-249. I’m following the instructions in the README successfully but I am failing to build target proton-jni (proton target is building okay). It is failing whilst try

Re: Need help Re: jenkins interop test failing due to PROTON-215 commits?

On 27 February 2013 22:28, Alan Conway wrote: > On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote: >> Hi, >> >> I notice that proton-jni on Jenkins is failing [1] , probably due to the >> recent PROTON-215 commits. >> >> The failing test is: >> proton_tests.interop.InteropTest.test_message

Re: Context object type in proton-j

On 1 March 2013 20:49, Saggi Mizrahi wrote: > I've been using the proton-j 0.3 and I was surprised to find > out that the context type of a connector returned from Listener.accept() > is created with the context object type of the parent listener. > I am wondering why that is that enforced. I thi

Publishing javadoc to site

Phil and I are currently working on PROTON-256 - Improve Engine API Javadoc. As part of this task, I'd like to start publishing the resulting javadoc to qpid.apache.org and link from http://qpid.apache.org/proton/documentation. My intention is to automate this process using Apache Buildbot http:/

Re: maven artifactId for the tests

I raised a Jira for this: https://issues.apache.org/jira/browse/PROTON-270 On 10 March 2013 23:05, Robbie Gemmell wrote: > Hi all, > > I just noticed the maven artifactId for the proton tests for 0.4: > > > org.apache.qpid > tests > 0.4 > > > Can we add 'proton' to that Id for consistency

Re: Difficulties building Swig-generated C++ code for proton-jni binding (due to nested typedef union)

On 1 March 2013 16:15, Cliff Jansen wrote: > I did all that and verified the c++ swig call was used and g++ on > javaJAVA_wrap.cxx. I also needed the fix in PROTON-249 to progress on > Windows. > > Let me know if you have made further progress. Otherwise, I will keep > digging. > > Cliff Hi Cl

Re: Difficulties building Swig-generated C++ code for proton-jni binding (due to nested typedef union)

in that respect. If my patch seems distasteful in its foibles, I > would look to Rafi for his views on changing codec.h. Let me know > what you think. > > I had just got this working yesterday on Linux and was trying a > Windows build before posting a review. It fails in cma

Re: Help needed [Fwd: Jenkins build is still unstable: Qpid-proton-j » tests #295]

Resolved by rev. 1458901 On 20 March 2013 13:24, Ken Giusti wrote: > > This failure is due to my updates to the SSL certificates and keys used by > the SSL unit tests. > > Specifically: > > IllegalStateException: java.lang.IllegalStateException: Unable to read PEM > object from file > /home/je

Re: Difficulties building Swig-generated C++ code for proton-jni binding (due to nested typedef union)

with the other bindings (surely they would need the same >> solution??). > > Let me think about that or perhaps another way to address your > (sensible) concern and get back to you later today or tomorrow. > > Cliff > > On Wed, Mar 20, 2013 at 11:33 AM, Keith W wrote:

Re: Difficulties building Swig-generated C++ code for proton-jni binding (due to nested typedef union)

On 21 March 2013 12:39, Keith W wrote: > Hi Cliff > > The winsock.h change resolved the remaining C++ compilation errors. > Will this be part of your patch? > > The next error I see is still from a java step within > binding/java/CMakeLists.txt - a problem with determining a

NPE from MessengerTests since rev 1460174

Hi, I'm seeing a NPE from MessengerTests since rev 1460174 whilst running the proton-j maven profile (mvn test -Pproton-j). It seems new test testDefaultRoute causes a NPE, and then the following MessengerTests fail with .java.net.BindException: Address already in use. The misleading commit mess

Re: NPE from MessengerTests since rev 1460174

_error(self._mng))) MessengerException: [-2]: unable to subscribe to address amqp://~0.0.0.0:12345: bind: Address already in use proton_tests.messenger.MessengerTest.testSendReceive100K fail Error during setu On 23 March 2013 16:30, Rafael Schloming wrote: > Should be fixed now. I a

Defining the behaviour of Proton Engine API under error conditions

Hi all Phil and I are tasked with producing a comprehensive set of system tests for Proton Engine. The aim is to produce a test suite that will execute against all Proton implementations thus guaranteeing that all exhibit identical behaviour and assuring conformance with the AMQP 1-0 specificatio

Continually failing MessengerTests WAS: NPE from MessengerTests since rev 1460174

till uses the orginal message). Kind regards, Keith On 25 March 2013 09:30, Keith W wrote: > Hi, > > The NPE has gone from the proton-j, but we now are seeing "No address > associated with hostname" and "Address already in use" errors when > running the Py

What are the use cases for pn_transport_unbind?

I'm curious to understand the use-cases for the pn_transport_unbind API method. I understand that one such use case is failover. When a client discovers that it has lost connectivity to the server, the client calls pn_transport_unbind to unbind the connection from the old transport, establish a n

Valgrind based soak tests fail against earlier versions of valgrind (3.2.1)

Hello We are seeing a the valgrind based soak tests fail on boxes with earlier versions of valgrind (3.2.1). proton_tests.soak.MessengerTests.test_star_topology_valgrind ...location should start with fun: or obj: ==1403=

Re: Valgrind based soak tests fail against earlier versions of valgrind (3.2.1)

but let me check if I can fix the suppression in some backward compatible >> way. >> >> /me valgrind noob. >> >> >> - Original Message - >> > From: "Keith W" >> > To: proton@qpid.apache.org >> > Sent: Thursday, April 4

Re: Valgrind based soak tests fail against earlier versions of valgrind (3.2.1)

u can "undefine" the >> environment variable VALGRIND that was set via config.sh. >> >> export -n VALGRIND >> >> that should keep the valgrind-based test cases from running. >> >> There's also an ENABLE_VALGRIND flag you can turn off if you are used ct