[jira] [Closed] (PROTON-330) Centos 6.4 build failure: Could NOT find Java
[ https://issues.apache.org/jira/browse/PROTON-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-330. -- Resolution: Fixed https://github.com/apache/qpid-proton/blob/master/INSTALL.md The install instructions now reference the openjdk-devel package. > Centos 6.4 build failure: Could NOT find Java > - > > Key: PROTON-330 > URL: https://issues.apache.org/jira/browse/PROTON-330 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.4 > Environment: Centos 6.4 x86_64 >Reporter: Evgeny Minkevich >Priority: Minor > > [tcs@centos build]$ echo $M2_HOME > /home/tcs/apache-maven-3.0.5 > [tcs@centos build]$ echo $JAVA_HOME > /usr/lib/jvm/jre-1.6.0-openjdk.x86_64 > [tcs@centos build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. > PN_VERSION: 0.4 > -- Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE > Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) > -- Cannot find both Java and Maven: testing disabled for Proton-J and JNI > Bindings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-363) recv.exe fails on Windows XP because getnameinfo returns WSANO_DATA / error 11004
[ https://issues.apache.org/jira/browse/PROTON-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-363: --- Labels: windows (was: ) > recv.exe fails on Windows XP because getnameinfo returns WSANO_DATA / error > 11004 > - > > Key: PROTON-363 > URL: https://issues.apache.org/jira/browse/PROTON-363 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.5 > Environment: Windows XP, Visual Studio 2010 >Reporter: Jakub Scholz > Labels: windows > > I build the proton-c library on Windows XP using Visual Studio 10. > Afterwards, when trying to run the recv.exe and send.exe examples, the > recv.exe always fails with: > > recv.exe amqp://~0.0.0.0:5672 > getnameinfo: The requested name is valid and was found in the database, but > it does not have the correct associated data being resolved for. > It doesn't fail immediately after start but only when I attempt to connect > with send.exe. As a result, the Proton seems to be pretty much not working on > my machine. > --- > The error seems to originate from the function pn_listener_accept in driver.c > and it translates to WSANO_DATA error / error 11004. I did some digging > around and playing with the getnameinfo function and it seems to me, that the > problem is that the getnameinfo function is unable to recognize the service > name based on the port number. And - according to MSDN > (http://msdn.microsoft.com/en-us/library/windows/desktop/ms738532(v=vs.85).aspx) > - that on Windows Server 2003 and earlier results in error (on Windows Vista > and later this works fine). > If I add a flag NI_NUMERICSERV to the getnameinfo call: > code = getnameinfo((struct sockaddr *) , addrlen, host, 1024, serv, 64, > NI_NUMERICSERV) > it will not return an error but return success and use the port number as a > service name. And with this change the recv.exe starts working fine. > However, adding this flag will on Windows Vista and higher and in Linux > probably result in the service name being always returned as a port number > and not as a name. So I'm not sure it is desired to add this flag on all > platforms. > Regards > Jakub -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-21) Extract the logical AMQP frame handling to an AbstractConnectionHandler
[ https://issues.apache.org/jira/browse/PROTON-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-21: -- Labels: api patch (was: api) > Extract the logical AMQP frame handling to an AbstractConnectionHandler > --- > > Key: PROTON-21 > URL: https://issues.apache.org/jira/browse/PROTON-21 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c, proton-j >Reporter: Hiram Chirino >Assignee: Rob Godfrey > Labels: api, patch > Attachments: PROTON-21-v3.patch > > > Right now all the logic that handles logical AMQP frame events is inside of > the TransportImpl class. That interface only allows you to pump bytes in and > out of the connection. If we extract all the handling logic to an > AbstractConnectionHandler you should be able to use that directly and pump > logical AMQP frames and avoid the frame encoding/decoding phase that the > TransportImpl also does. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-73) Server should force renegotiate when client authentication setting is changed on an active connection.
[ https://issues.apache.org/jira/browse/PROTON-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-73: -- Labels: security ssl (was: ssl) > Server should force renegotiate when client authentication setting is changed > on an active connection. > -- > > Key: PROTON-73 > URL: https://issues.apache.org/jira/browse/PROTON-73 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Labels: security, ssl > > If the server application changes the peer authentication setting from > 'anonymous' to 'verify-peer' while an SSL session is active, then the server > should force the client to re-negotiate (SSL handshake) to verify the > remote's identity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-291) fix the SSL layer of the transport to only pop from the amqp layer when bytes are known to have actually been written to the socket
[ https://issues.apache.org/jira/browse/PROTON-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-291: --- Labels: ssl (was: ) > fix the SSL layer of the transport to only pop from the amqp layer when bytes > are known to have actually been written to the socket > --- > > Key: PROTON-291 > URL: https://issues.apache.org/jira/browse/PROTON-291 > Project: Qpid Proton > Issue Type: Bug >Reporter: Rafael H. Schloming >Assignee: Ken Giusti > Labels: ssl > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-303) Need an easy to use Map handling API
[ https://issues.apache.org/jira/browse/PROTON-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-303: --- Labels: codec (was: ) > Need an easy to use Map handling API > > > Key: PROTON-303 > URL: https://issues.apache.org/jira/browse/PROTON-303 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Affects Versions: 0.4 >Reporter: Ken Giusti >Priority: Minor > Labels: codec > > Using the exiting data and codec apis for manipulating maps are a pain. As a > convenience, a set of higher level map utilities should be provided by proton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-158) detach with invalid handle causes segfault
[ https://issues.apache.org/jira/browse/PROTON-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-158: --- Labels: crash (was: ) > detach with invalid handle causes segfault > -- > > Key: PROTON-158 > URL: https://issues.apache.org/jira/browse/PROTON-158 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.2 >Reporter: Gordon Sim >Assignee: Ken Giusti >Priority: Minor > Labels: crash > > I.e. a detach where the handle was not previously used in an attach -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-357) Add PHP PECL package
[ https://issues.apache.org/jira/browse/PROTON-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-357: --- Labels: packaging (was: ) > Add PHP PECL package > > > Key: PROTON-357 > URL: https://issues.apache.org/jira/browse/PROTON-357 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Affects Versions: 0.4 > Environment: Linux, Macos X >Reporter: Serge Smertin > Labels: packaging > > In order to get Proton adoption in PHP ecosystem and not to build library > from sources, PECL package should be introduced. Probably with Packagist as > well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-254) Swig generated c code for java bindings fails to compile on Windows Visual Studio 2010
[ https://issues.apache.org/jira/browse/PROTON-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-254: --- Labels: patch windows (was: windows) > Swig generated c code for java bindings fails to compile on Windows Visual > Studio 2010 > -- > > Key: PROTON-254 > URL: https://issues.apache.org/jira/browse/PROTON-254 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.4 > Environment: Windows 7 > Visual Studio 2010 >Reporter: Keith Wall >Assignee: Cliff Jansen > Labels: patch, windows > Attachments: > 0001-PROTON-254-Resolve-Nested-union-not-currently-suppor.patch, > make-proton-jni-cxx-errors.txt, pn254-cj-0.patch > > > Swig generated C code for the Java bindings fails to compile on Visual Studio > 2010 with error message: > C1083: Cannot open include file: 'stdbool.h': No such file or directory > After discussion on list [1], we tried changing bindings/java/CMakeLists.txt > to use CPLUSPLUS ON directive to CMake in the case where BUILD_WITH_CXX has > been enabled earlier in the build. > if (BUILD_WITH_CXX) >SET_SOURCE_FILES_PROPERTIES(java.i PROPERTIES CPLUSPLUS ON) > endif (BUILD_WITH_CXX) > Switching to CPP in this way exposed a number of errors when compiling the > CPP code resulting from the java.i (casting issues, pointer arithmetic etc - > see attached make-proton-jni-cxx-errors.txt). However, even after resolving > the CPP compilation issues, we then encounter a problem with Swig's handling > of nested unions when when CPP. The seeming inability of SWIG (when used > with CPP) to represent the union means that SWIG does not produce > pn_atom_t_u.java. JNIMessage.java, which references pn_atom_t_u, > consequently fails to compile. > The warning from swig is: > /home/keith/src/proton/proton-c/include/proton/codec.h:91: Warning 312: > Nested union not currently supported (ignored). > > [1] > http://mail-archives.apache.org/mod_mbox/qpid-proton/201302.mbox/%3ccamyv19mgbdvd2wextvpwywtysskadokb7wtj+u-3jkncwdx...@mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (PROTON-326) proton-c ServerTest.testIdleTimeout sometimes fails, causing test suite to hang forever
[
https://issues.apache.org/jira/browse/PROTON-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed PROTON-326.
--
Resolution: Unresolved
Closing this on the idea that it's probably out of date. Please reopen if I am
wrong.
> proton-c ServerTest.testIdleTimeout sometimes fails, causing test suite to
> hang forever
> ---
>
> Key: PROTON-326
> URL: https://issues.apache.org/jira/browse/PROTON-326
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: 0.4
> Environment: Linux
>Reporter: Philip Harvey
>
> I ran the python test suite against proton-c today and noticed that
> ServerTest.testIdleTimeout failed with the following output:
> {noformat}
> proton_tests.engine.ServerTest.testIdleTimeout
> ..ERROR amqp:resource-limit-exceeded
> local-idle-timeout expired
> fail
> Error during test: Traceback (most recent call last):
> File "./tests/python/proton-test", line 340, in run
> phase()
> File "/.../workspace/proton/tests/python/proton_tests/engine.py", line
> 1412, in testIdleTimeout
> assert self.conn.state == (Endpoint.LOCAL_ACTIVE |
> Endpoint.REMOTE_ACTIVE), "Connection terminated"
> AssertionError: Connection terminated
> {noformat}
> This test usually succeeds so I guess it contains a race condition.
> Something that is arguably more problematic is that this failure causes the
> test suite to hang. The suite proceeds to run the other tests, but does not
> terminate when it reaches the end. On Linux, I actually had to kill the
> process rather than ctrl-c-ing it.
> I cannot reproduce the test failure, but I do find that if I make it fail
> (for example, by modifying the assert on line 1412 to always fail) then the
> suite hangs every time.
> It's obviously undesirable for a failing test to cause the entire suite to
> hang.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (PROTON-327) proton-c: soak.MessengerTests.test_relay_C_SSL sometimes fails
[ https://issues.apache.org/jira/browse/PROTON-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-327. -- Resolution: Unresolved An old test failure that is probably out of date. Please reopen if it makes sense to. > proton-c: soak.MessengerTests.test_relay_C_SSL sometimes fails > -- > > Key: PROTON-327 > URL: https://issues.apache.org/jira/browse/PROTON-327 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.4 > Environment: Linux >Reporter: Philip Harvey > > Today I observed the following test failure on my CI server. This is the > first time I've seen the test fail. It passed when I re-ran it. > Here is the test output: > proton_tests.soak.MessengerTests.test_relay_C_SSL (from pythontests) > Failing for the past 1 build (Since Failed#122 ) > Took 1 min 0 sec. > add description > Error Message > Command '['msgr-send', '-a', > 'amqps://0.0.0.0:58694/X0Y,amqps://0.0.0.0:58694/X1Y,amqps://0.0.0.0:58694/X2Y,amqps://0.0.0.0:58694/X3Y,amqps://0.0.0.0:58694/X4Y', > '-c', '85', '-R', '-t', '60']' failed > Stacktrace > Error during test: Traceback (most recent call last): > File "./tests/python/proton-test", line 340, in run > phase() > File "/.../proton/tests/python/proton_tests/soak.py", line 310, in > test_relay_C_SSL > self._do_relay_test(MessengerReceiverC(), MessengerReceiverC(), > MessengerSenderC(), "amqps") > File "/.../proton/tests/python/proton_tests/soak.py", line 220, in > _do_relay_test > self._do_test(iterations) > File "/.../proton/tests/python/proton_tests/soak.py", line 96, in _do_test > assert S.status() == 0, "Command '%s' failed" % str(S.cmdline()) > AssertionError: Command '['msgr-send', '-a', > 'amqps://0.0.0.0:58694/X0Y,amqps://0.0.0.0:58694/X1Y,amqps://0.0.0.0:58694/X2Y,amqps://0.0.0.0:58694/X3Y,amqps://0.0.0.0:58694/X4Y', > '-c', '85', '-R', '-t', '60']' failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-241) proton-c: mark old transport interfaces 'deprecated'
[
https://issues.apache.org/jira/browse/PROTON-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-241:
---
Labels: visibility (was: )
> proton-c: mark old transport interfaces 'deprecated'
>
>
> Key: PROTON-241
> URL: https://issues.apache.org/jira/browse/PROTON-241
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Ken Giusti
>Priority: Trivial
> Labels: visibility
>
> Once PROTON-225 is implemented, we should eventually remove the old
> interfaces after marking them deprecated.
> Example:
> #ifdef __GNUC__
> #define DEPRECATED(func) func __attribute__ ((deprecated))
> #elif defined(_MSC_VER)
> #define DEPRECATED(func) __declspec(deprecated) func
> #else
> #pragma message("WARNING: You need to implement DEPRECATED for this compiler")
> #define DEPRECATED(func) func
> #endif
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (PROTON-186) Message encode should always return the number of bytes needed to fully encode the message
[ https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-186: --- Labels: patch (was: ) > Message encode should always return the number of bytes needed to fully > encode the message > -- > > Key: PROTON-186 > URL: https://issues.apache.org/jira/browse/PROTON-186 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c, proton-j >Reporter: Hiram Chirino > Labels: patch > Attachments: PROTON-186v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-151) Have the python interface use dynamic proxies to the engine impl objects so to ensure that only public interface methods are being used by the python tests.
[ https://issues.apache.org/jira/browse/PROTON-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-151: --- Labels: patch (was: ) > Have the python interface use dynamic proxies to the engine impl objects so > to ensure that only public interface methods are being used by the python > tests. > > > Key: PROTON-151 > URL: https://issues.apache.org/jira/browse/PROTON-151 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino > Labels: patch > Attachments: PROTON-151.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-162) SSL implementation does not support certification revocation
[ https://issues.apache.org/jira/browse/PROTON-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-162: --- Labels: security ssl (was: ) > SSL implementation does not support certification revocation > > > Key: PROTON-162 > URL: https://issues.apache.org/jira/browse/PROTON-162 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.3 >Reporter: Ken Giusti > Labels: security, ssl > > OpenSSL supports a means for configuring lists of revoked certificates. The > SSL layer used by proton-c does not provide a means to configure this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-237) Porting Issue -- basename() not found in Visual Studio 2010
[
https://issues.apache.org/jira/browse/PROTON-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-237:
---
Labels: build windows (was: build)
> Porting Issue -- basename() not found in Visual Studio 2010
> ---
>
> Key: PROTON-237
> URL: https://issues.apache.org/jira/browse/PROTON-237
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Environment: Windows Visual Studio 2010
>Reporter: Mary hinton
> Labels: build, windows
>
> The basename() function in proton.c is not found in Visual Studio 2010. It is
> in Visual Studio 2012 when the header is included.
> It is only used in a printf statement and is not needed for porting to Visual
> Studio 2010:
> printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a ] [-m
> ]\n", basename(argv[0]));
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
