[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 ] Rafael H. Schloming updated PROTON-241: --- Fix Version/s: (was: 0.5) 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-348) Tests and examples need some platform helper functions
[ https://issues.apache.org/jira/browse/PROTON-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-348: --- Fix Version/s: (was: 0.5) Tests and examples need some platform helper functions -- Key: PROTON-348 URL: https://issues.apache.org/jira/browse/PROTON-348 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.5 Environment: All Reporter: Cliff Jansen Assignee: Cliff Jansen New functionality in examples and tests require platform neutral basic functionality such as getopt (again) and time. The existing code doesn't build on Windows. Presumably additional such functionality will be needed in the future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-288) Make it possible to start the server later during the test
[ https://issues.apache.org/jira/browse/PROTON-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-288: --- Fix Version/s: (was: 0.5) Make it possible to start the server later during the test -- Key: PROTON-288 URL: https://issues.apache.org/jira/browse/PROTON-288 Project: Qpid Proton Issue Type: Bug Reporter: Bozo Dragojevic Attachments: 0001-Make-it-possible-to-start-the-server-later-during-th.patch, 0001-PROTON-288-Make-it-possible-to-start-the-server-late.patch I'm seeing weird behavior of messenger if the server is not around. The attached patch adds such capability to the messenger test class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-62) Proton(-j) does not support attaching to the transaction coordinator
[ https://issues.apache.org/jira/browse/PROTON-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-62: -- Fix Version/s: (was: 0.5) Proton(-j) does not support attaching to the transaction coordinator Key: PROTON-62 URL: https://issues.apache.org/jira/browse/PROTON-62 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Reporter: Hiram Chirino Assignee: Rafael H. Schloming Priority: Blocker Labels: api Got at: Caused by: java.lang.ClassCastException: org.apache.qpid.proton.type.transaction.Coordinator cannot be cast to org.apache.qpid.proton.type.messaging.Target at org.apache.qpid.proton.engine.impl.TransportImpl.handleAttach(TransportImpl.java:977) at org.apache.qpid.proton.engine.impl.TransportImpl.handleAttach(TransportImpl.java:59) at org.apache.qpid.proton.type.transport.Attach.invoke(Attach.java:389) at org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:1090) at org.apache.qpid.proton.engine.impl.FrameParser.input(FrameParser.java:409) at org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:156) at org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:120) ... 5 more and I think the frame being processed was the following (hex): 00 00 00 6a 02 00 00 01 00 53 12 c0 5d 0a a1 11 74 78 6e 43 6f 6e 74 72 6f 6c 6c 65 72 4c 69 6e 6b 43 42 50 00 50 00 00 53 28 c0 01 00 00 53 30 c0 35 01 e0 32 02 a3 17 61 6d 71 70 3a 6c 6f 63 61 6c 2d 74 72 61 6e 73 61 63 74 69 6f 6e 73 17 61 6d 71 70 3a 6d 75 6c 74 69 2d 74 78 6e 73 2d 70 65 72 2d 73 73 6e 40 40 43 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-234) Add lots of logging to better understand inner working of proton
[ https://issues.apache.org/jira/browse/PROTON-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-234: --- Fix Version/s: (was: 0.5) Add lots of logging to better understand inner working of proton Key: PROTON-234 URL: https://issues.apache.org/jira/browse/PROTON-234 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Bozo Dragojevic Add lots of logging to proton to ease understnding of it's inner workings Introduce object naming facility as some layers are coupled really loosely for now the logging route will just dump everything out to stderr, as it was before This is currently one giant commit off 0.3: https://github.com/ttlj/qpid-proton/commits/upstream-logging It doesn't merge quite cleanly to trunk. If this is interesting thing to have I'd be willing to merge or rebase whichever is preferred. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-278) Messenger - allow the application to control the use of the message reply-to field.
[ https://issues.apache.org/jira/browse/PROTON-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-278: --- Fix Version/s: (was: 0.5) Messenger - allow the application to control the use of the message reply-to field. --- Key: PROTON-278 URL: https://issues.apache.org/jira/browse/PROTON-278 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.4 Reporter: Ken Giusti Priority: Blocker Currently, messenger always sets the reply-to field in a sent message. This should be changed to allow the application to set the reply-to field only when a reply is desired. Messenger should be changed to not unconditionally set this field. In order to set this field in the case of a client that has not established a subscription, the client needs to be able to query messenger for the proper value of the reply-to address. A new api would need to be created for this. Proposal: int pn_messenger_set_reply( pn_messenger_t *msgr, pn_message_t *msg ) Set the proper reply-to address in msg. msg would need to have its to address configured in order for this method to succeed. At least, I think the value for the reply-to may depend on the 'to' address... I may be wrong about that Opinions? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-375) Engine does not indicate when a link has completed draining.
[ https://issues.apache.org/jira/browse/PROTON-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-375: --- Fix Version/s: (was: 0.5) Engine does not indicate when a link has completed draining. Key: PROTON-375 URL: https://issues.apache.org/jira/browse/PROTON-375 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Affects Versions: 0.4 Reporter: Ken Giusti Assignee: Ken Giusti The engine API provides the pn_link_drain() method, which allows the application to force the peer to drain its credit. The engine API does not provide a way for the application to know when the remote has completed draining. At least there needs to be a way to find out when the remote credit value has been exhausted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-265) Change Message#decode to signal inability to decode entire buffer via exception rather than return value
[ https://issues.apache.org/jira/browse/PROTON-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-265: --- Fix Version/s: (was: 0.5) Change Message#decode to signal inability to decode entire buffer via exception rather than return value Key: PROTON-265 URL: https://issues.apache.org/jira/browse/PROTON-265 Project: Qpid Proton Issue Type: Improvement Components: proton-j Reporter: Keith Wall Assignee: Keith Wall Change Message#decode signature to throw an exception in the case where the decoder fails to decode all the bytes in the input buffer, rather than returning the number of bytes actually decoded. This will make the Java implementation more closely follow the Proton-C. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-344) Need Ruby version of msgr-send/msgr-recv tools
[ https://issues.apache.org/jira/browse/PROTON-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-344: --- Fix Version/s: (was: 0.5) Need Ruby version of msgr-send/msgr-recv tools -- Key: PROTON-344 URL: https://issues.apache.org/jira/browse/PROTON-344 Project: Qpid Proton Issue Type: Task Components: proton-c Affects Versions: 0.4 Reporter: Ken Giusti Assignee: Ken Giusti A ruby variant of msgr-send/recv traffic generators should be added to the soak tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-342: --- Fix Version/s: (was: 0.5) installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-238) Initial CTest support
[ https://issues.apache.org/jira/browse/PROTON-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-238: --- Fix Version/s: (was: 0.5) Initial CTest support - Key: PROTON-238 URL: https://issues.apache.org/jira/browse/PROTON-238 Project: Qpid Proton Issue Type: New Feature Components: proton-c Affects Versions: 0.3 Environment: Mainly proton-c and interop testing. Reporter: Cliff Jansen Assignee: Cliff Jansen This is a proposal for starting to use CMake's built in CTest capabilities in order to allow a unified test mechanism on multiple platforms. For the supplied review patch, it assumes that instead of using trunk/config.sh and calling proton-test directly, you do: cd path/to/trunk mkdir build cd build cmake .. make ctest Assuming the make succeeds, this will test two targets for now (proton-c and proton-jni), but the newer proposed tests (i.e. performance) can be added as well. Once the desired work flow is captured, this can be tweaked to run in a platform neutral way. CMake even has the capability to run CTest from inside the Visual Studio IDE. Concepts and strategies are stolen from the qpid/cpp tree. By default, you just get a brief summary of the tests. Also try ctest -V [ to see the full output ] ctest -N [ to list the available tests ] ctest -R proton-c [ just run the one test in this case, or a regexp if supplied ] ctest -E regexp [ run all tests except ones that match regexp ] Fancier tests can use cmake scripts to do things in a platform neutral manner (move files around), run the test from a different directory, etc. Python scripts and Java programs are already platform neutral, so there is no need to make changes for those. Tests can be conditionally configured (in the example proton-jni will not be configured if maven or java aren't found). Note that if you wish to just build and test proton-c, there is no requirement to build from within the specific directory .../trunk/build. This restriction currently exists for testing proton-jni using maven, but perhaps that can be relaxed in future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Rafael H. Schloming updated PROTON-158: --- Fix Version/s: (was: 0.5) 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 I.e. a detach where the handle was not previously used in an attach -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Rafael H. Schloming updated PROTON-303: --- Fix Version/s: (was: 0.5) 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-226) Porting Issue -- Heap Corruption using Visual Studio when running client/server proton in debug mode.
[ https://issues.apache.org/jira/browse/PROTON-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-226: --- Fix Version/s: (was: 0.4) Porting Issue -- Heap Corruption using Visual Studio when running client/server proton in debug mode. - Key: PROTON-226 URL: https://issues.apache.org/jira/browse/PROTON-226 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Windows using Visual Studio 2010 Reporter: Mary hinton Labels: build Code changes for windows port were added (MinGW and Visual Studio) to the proton codebase recently. Using the new codebase and some additional changes, I ran the proton executable using the Visual Studio toolset as both a server and client. When the client exits, a Windows popup displays: Windows has triggered a breakpoint in proton.exe. This may be due to a corruption of the heap, which indicates a bug in proton.exe or any of the DLLs it has loaded. Still tracking this problem down. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-239) Porting Issue -- gethostname() is part of winsock library
[
https://issues.apache.org/jira/browse/PROTON-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-239:
---
Fix Version/s: (was: 0.4)
Porting Issue -- gethostname() is part of winsock library
-
Key: PROTON-239
URL: https://issues.apache.org/jira/browse/PROTON-239
Project: Qpid Proton
Issue Type: Improvement
Components: proton-c
Environment: Windows using Visual Studio 2010
Reporter: Mary hinton
Assignee: Cliff Jansen
Labels: build
In Visual Studio, gethostname() is found within the winsock library. To use
it in proton.c, we have to include the winsock header and make sure the
WSAStartup() (used to initialize the windows socket library) has already been
called by pn_driver().
I was wondering if we could isolate the winsock header so that it is only
included in driver.c.
We could set up a new function in driver.c called pn_gethostname() whose only
function is to call gethostname().
int pn_gethostname(char *name, int namelen)
{
return gethostname(name, namelen);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-209) Update README file(s) to more specific about required versions of tools
[ https://issues.apache.org/jira/browse/PROTON-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-209: --- Fix Version/s: (was: 0.4) Update README file(s) to more specific about required versions of tools --- Key: PROTON-209 URL: https://issues.apache.org/jira/browse/PROTON-209 Project: Qpid Proton Issue Type: Task Affects Versions: 0.3 Reporter: Philip Harvey Priority: Minor We should be more explicit about which version of the following tools are required by Proton, either in the top level README or in READMEs in the relevant sub-folders: - Python (see PROTON-199). - Swig - cmake? (the required version is specified in the CMakeLists.txt files but maybe it would be polite to mention in the README too). - Maven? (or maybe we can omit this for same reasons as cmake version) - possibly others, e.g. openssl, gcc, epydoc, Perl, Ruby etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Rafael H. Schloming updated PROTON-237: --- Fix Version/s: (was: 0.4) 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 The basename() function in proton.c is not found in Visual Studio 2010. It is in Visual Studio 2012 when the filesystem 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 address] [-m sasl-mech]\n, basename(argv[0])); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-142) Messenger has no unsubscribe
[ https://issues.apache.org/jira/browse/PROTON-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-142: --- Fix Version/s: (was: 0.5) Messenger has no unsubscribe Key: PROTON-142 URL: https://issues.apache.org/jira/browse/PROTON-142 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Reporter: William Henry Doesn't Messenger need a: void pn_messenger_unsubscribe(pn_subscription_t*) It would see to be important. Is there a reason this does not exist? (besides that it only recently got pn_subscription_t exposed) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-401) Ordering issue prevents credit drain from working properly
[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-401: --- Fix Version/s: (was: 0.5) Ordering issue prevents credit drain from working properly -- Key: PROTON-401 URL: https://issues.apache.org/jira/browse/PROTON-401 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Ken Giusti Assignee: Ken Giusti Attachments: drain-error.patch, drain-hack.patch If the sending link calls pn_link_drained() to indicate that it has send all pending data, and afterwards it receives a Flow frame with drain=true from the peer, then the drain never completes. The ordering is the problem: if the flow frame w/drain=true is received _BEFORE_ the sender calls pn_link_drained(), then it works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-128) Access the link's queued size in bytes to aid callers in implementing flow control
[ https://issues.apache.org/jira/browse/PROTON-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-128: --- Fix Version/s: (was: 0.5) Access the link's queued size in bytes to aid callers in implementing flow control -- Key: PROTON-128 URL: https://issues.apache.org/jira/browse/PROTON-128 Project: Qpid Proton Issue Type: New Feature Components: proton-c, proton-j Reporter: Hiram Chirino Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Rafael H. Schloming updated PROTON-186: --- Fix Version/s: (was: 0.5) 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 Attachments: PROTON-186v2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-262) Fully implement (error) condtion API in Proton-J
[ https://issues.apache.org/jira/browse/PROTON-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-262: --- Fix Version/s: (was: 0.5) Fully implement (error) condtion API in Proton-J Key: PROTON-262 URL: https://issues.apache.org/jira/browse/PROTON-262 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rob Godfrey Assignee: Rob Godfrey -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Rafael H. Schloming updated PROTON-357: --- Fix Version/s: (was: 0.5) 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-310) [Proton-J] pipelined session opening and closing causes NPE on receipt of Begin
[
https://issues.apache.org/jira/browse/PROTON-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-310:
---
Fix Version/s: (was: 0.5)
[Proton-J] pipelined session opening and closing causes NPE on receipt of
Begin
---
Key: PROTON-310
URL: https://issues.apache.org/jira/browse/PROTON-310
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Affects Versions: 0.4
Reporter: Robbie Gemmell
Assignee: Philip Harvey
Pipelined session opening and closing causes NPE on receipt of Begin:
{noformat}
Exception in thread main java.lang.NullPointerException
at
org.apache.qpid.proton.engine.impl.TransportImpl.handleBegin(TransportImpl.java:1033)
at
org.apache.qpid.proton.engine.impl.TransportImpl.handleBegin(TransportImpl.java:1)
at org.apache.qpid.proton.amqp.transport.Begin.invoke(Begin.java:144)
at
org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:1221)
at
org.apache.qpid.proton.engine.impl.FrameParser.input(FrameParser.java:407)
at
org.apache.qpid.proton.engine.impl.SaslImpl$1.input(SaslImpl.java:486)
at
org.apache.qpid.proton.engine.impl.TransportImpl.input(TransportImpl.java:170)
at
org.apache.qpid.proton.driver.impl.ConnectorImpl.processInput(ConnectorImpl.java:112)
at
org.apache.qpid.proton.driver.impl.ConnectorImpl.read(ConnectorImpl.java:99)
at
org.apache.qpid.proton.driver.impl.ConnectorImpl.process(ConnectorImpl.java:82)
...
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-296) need a new message status
[ https://issues.apache.org/jira/browse/PROTON-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-296: --- Fix Version/s: (was: 0.5) need a new message status - Key: PROTON-296 URL: https://issues.apache.org/jira/browse/PROTON-296 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: michael goulish Currently, if a receiver settles messages rather than accepting or rejecting, the status that the sender sees is PENDING. That would seem to suggest that it might change in the future, so the sender might keep checking back to see if the status changes. But the status isn't going to change. The only other available status for this situation is UNKNOWN, which has the same problem. Seems like we could use a separate status integer, like SETTLED, that means the other side doesn't care, and that's final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-289) outgoing tracker and outgoing queue disagree in case the server is not around
[ https://issues.apache.org/jira/browse/PROTON-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-289: --- Fix Version/s: (was: 0.5) outgoing tracker and outgoing queue disagree in case the server is not around - Key: PROTON-289 URL: https://issues.apache.org/jira/browse/PROTON-289 Project: Qpid Proton Issue Type: Bug Reporter: Bozo Dragojevic Attachments: 0002-Add-test-for-sending-to-a-server-that-is-not-started.patch send a message to localhost:12345 when there is no server tracker will say it's PENDING outgoing count will be 0 Which of them is wrong? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-313) [Proton-J] no consistent way to determine remote settlement
[
https://issues.apache.org/jira/browse/PROTON-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-313:
---
Fix Version/s: (was: 0.5)
[Proton-J] no consistent way to determine remote settlement
---
Key: PROTON-313
URL: https://issues.apache.org/jira/browse/PROTON-313
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Affects Versions: 0.4
Reporter: Robbie Gemmell
Assignee: Philip Harvey
In order to determine remote settlement it is currently necessary to perform
a cast :
{noformat}
// TODO - remove this hack when Proton-J and -C APIs are
properly aligned
// The C API defines isSettled as being true if the delivery
has been settled locally OR remotely
return _delivery.isSettled() || ((_delivery instanceof
DeliveryImpl ((DeliveryImpl)_delivery).remotelySettled()));
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-323) Regression: Messenger sends null in disposition state after accept
[ https://issues.apache.org/jira/browse/PROTON-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-323: --- Fix Version/s: (was: 0.5) Regression: Messenger sends null in disposition state after accept Key: PROTON-323 URL: https://issues.apache.org/jira/browse/PROTON-323 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Ted Ross Priority: Blocker Using the following Python code snippet: from proton import * mng = Messenger() mng.start() mng.subscribe(amqp://0.0.0.0/Queue_1) mng.timeout=100 mng.recv() msg = Message() t = mng.get(msg) mng.accept(t) mng.stop() The following trace is seen after the call to stop: [0xf7f6a0:1] - DISPOSITION @21 [true, 0, 0, true, null] On Proton 0.4, this problem does not exist. The trace is: [0x1087bb0:1] - DISPOSITION @21 [true, 0, 0, true, @36 []] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-200) [Proton-c] Credit distribution by messenger is not balanced across all links
[ https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-200: --- Fix Version/s: (was: 0.5) [Proton-c] Credit distribution by messenger is not balanced across all links Key: PROTON-200 URL: https://issues.apache.org/jira/browse/PROTON-200 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.3 Reporter: Ken Giusti Assignee: Ken Giusti Attachments: proton-200.patch, upstream-credit.patch The method used to distribute credit to receiving links may lead to starvation when the number of receiving links is the available credit. The distribution algorithm always starts with the same link - see messenger.c::pn_messenger_flow() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-250) Add -fvisibility option when building shared libraries
[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-250: --- Fix Version/s: (was: 0.5) Add -fvisibility option when building shared libraries --- Key: PROTON-250 URL: https://issues.apache.org/jira/browse/PROTON-250 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: GNU Compiler Reporter: Irina Boverman Assignee: Darryl L. Pierce Priority: Minor Attachments: proton.patch Add an option to hide symbols in shared libraries except when they are declared public. Extends efforts already in place for Windows builds. Excludes an effort to determine what symbols should be considered public interfaces. The gcc 4 -fvisibility option is said to: ...very substantially improve linking and load times of shared object libraries, produce more optimized code, provide near-perfect API export and prevent symbol clashes. It is strongly recommended that you use this in any shared objects you distribute. See here: http://gcc.gnu.org/wiki/Visibility Attached patch (patch.txt) will build libqpid-proton.so shared library using this flag. It reduces number of symbols from 700+ to 500+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-131) Add a engine test which validates transferring a large number of message between a receiver and sender
[ https://issues.apache.org/jira/browse/PROTON-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-131: --- Fix Version/s: (was: 0.5) Add a engine test which validates transferring a large number of message between a receiver and sender -- Key: PROTON-131 URL: https://issues.apache.org/jira/browse/PROTON-131 Project: Qpid Proton Issue Type: Test Reporter: Hiram Chirino Assignee: Ken Giusti Test should transfer at least 100,000 messages with a new 4k body per message in both pre-settled and non-pre-settled modes. A test like that might have caught issues PROTON-129 and PROTON-130 earlier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-395) Messenger - tracker-settled method is needed
[ https://issues.apache.org/jira/browse/PROTON-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-395: --- Fix Version/s: (was: 0.6) Messenger - tracker-settled method is needed Key: PROTON-395 URL: https://issues.apache.org/jira/browse/PROTON-395 Project: Qpid Proton Issue Type: New Feature Components: proton-c Affects Versions: 0.4 Reporter: Ted Ross Messenger has a way to query trackers to get the status of a message delivery. However, there is no way to query the settlement of a delivery. This is needed for the three-ack (exactly-once) exchange pattern. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-390) Suppress or Fix the warnings openssl.c produce
[ https://issues.apache.org/jira/browse/PROTON-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-390: --- Fix Version/s: (was: 0.6) Suppress or Fix the warnings openssl.c produce -- Key: PROTON-390 URL: https://issues.apache.org/jira/browse/PROTON-390 Project: Qpid Proton Issue Type: Bug Components: proton-c Environment: OS X Reporter: Hiram Chirino openssl.c produces lots of warnings. /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘_log_ssl_error’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:165: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:167: warning: ‘ERR_error_string_n’ is deprecated (declared at /usr/include/openssl/err.h:280) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:169: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘ssl_failed’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:189: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:191: warning: ‘ERR_error_string_n’ is deprecated (declared at /usr/include/openssl/err.h:280) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘verify_callback’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:257: warning: ‘X509_STORE_CTX_get_error_depth’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:453) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:261: warning: ‘X509_STORE_CTX_get_current_cert’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:454) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:262: warning: ‘X509_STORE_CTX_get_ex_data’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:450) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:262: warning: ‘SSL_get_ex_data_X509_STORE_CTX_idx’ is deprecated (declared at /usr/include/openssl/ssl.h:1601) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:268: warning: ‘SSL_get_ex_data’ is deprecated (declared at /usr/include/openssl/ssl.h:1587) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:285: warning: ‘X509_get_ext_d2i’ is deprecated (declared at /usr/include/openssl/x509.h:1151) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:287: warning: ‘sk_num’ is deprecated (declared at /usr/include/openssl/stack.h:81) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:290: warning: ‘sk_value’ is deprecated (declared at /usr/include/openssl/stack.h:82) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:295: warning: ‘ASN1_STRING_to_UTF8’ is deprecated (declared at /usr/include/openssl/asn1.h:981) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:299: warning: ‘CRYPTO_free’ is deprecated (declared at /usr/include/openssl/crypto.h:480) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:308: warning: ‘X509_get_subject_name’ is deprecated (declared at /usr/include/openssl/x509.h:1013) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:310: warning: ‘X509_NAME_get_index_by_NID’ is deprecated (declared at /usr/include/openssl/x509.h:1105) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:311: warning: ‘X509_NAME_get_entry’ is deprecated (declared at /usr/include/openssl/x509.h:1108) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:312: warning: ‘X509_NAME_ENTRY_get_data’ is deprecated (declared at /usr/include/openssl/x509.h:1130) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:315: warning: ‘ASN1_STRING_to_UTF8’ is deprecated (declared at /usr/include/openssl/asn1.h:981) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:319: warning: ‘CRYPTO_free’ is deprecated (declared at /usr/include/openssl/crypto.h:480) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:329: warning: ‘X509_STORE_CTX_set_error’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:452) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘get_dh2048’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:371: warning: ‘DH_new’ is deprecated (declared at /usr/include/openssl/dh.h:184) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:372: warning: ‘BN_bin2bn’ is deprecated (declared at /usr/include/openssl/bn.h:422) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:373: warning: ‘BN_bin2bn’ is
[jira] [Updated] (PROTON-410) Remove driver dependencies in Messenger to allow the application to manage I/O
[ https://issues.apache.org/jira/browse/PROTON-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-410: --- Fix Version/s: (was: 0.6) Remove driver dependencies in Messenger to allow the application to manage I/O -- Key: PROTON-410 URL: https://issues.apache.org/jira/browse/PROTON-410 Project: Qpid Proton Issue Type: New Feature Components: proton-c Affects Versions: 0.5 Reporter: Ken Giusti Assignee: Ken Giusti Messenger currently makes calls to the driver in order to perform network operations (ie. open a listening socket, create an outgoing connection, accept an incoming connection, etc). It also invokes the driver to do I/O. This feature would allow the application to control all aspects of the I/O, while using the Messenger library as a pure data processing engine. With this feature, it would be easier to integrate Messenger into pre-existing applications that already perform network I/O. It should also be easier to integrate Messenger into language environments that provide native I/O implementations (eg. use python sockets underneath Messenger). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-359) [Proton-j] Create a simple entry point for creating all Proton entities
[ https://issues.apache.org/jira/browse/PROTON-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-359: --- Fix Version/s: 0.5 [Proton-j] Create a simple entry point for creating all Proton entities --- Key: PROTON-359 URL: https://issues.apache.org/jira/browse/PROTON-359 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.5 Rather than requiring users to create a ProtonFactoryLoader, get a factory and then create an object, instead just do Proton.connection(), Proton.message(), etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-343) Add a pluggable Proton logging layer
[ https://issues.apache.org/jira/browse/PROTON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-343: --- Fix Version/s: 0.6 Add a pluggable Proton logging layer Key: PROTON-343 URL: https://issues.apache.org/jira/browse/PROTON-343 Project: Qpid Proton Issue Type: Improvement Components: proton-c, proton-j Reporter: Philip Harvey Assignee: Philip Harvey Fix For: 0.6 Attachments: 0001-PROTON-343-sketched-out-the-Java-parts-of-the-propos.patch Applications that use Proton sometimes want Proton to produce logging. Goals * Proton should provide a default logging implementation. * It should be easy for Proton client code to provide custom logging implementation, e.g. one that uses the same third party logging framework as their application code. * Proton should not have a compile-time dependency on a third party logging framework * Proton's log output is considered to be part of its public interface. Therefore, in the spirit of Proton's cross-language consistency goals, this output should be consistent between proton-c and proton-j. * The goals that general-purpose logging frameworks try to meet - performance, ease of use etc - also apply. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-359) [Proton-j] Create a simple entry point for creating all Proton entities
[ https://issues.apache.org/jira/browse/PROTON-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-359. Resolution: Fixed [Proton-j] Create a simple entry point for creating all Proton entities --- Key: PROTON-359 URL: https://issues.apache.org/jira/browse/PROTON-359 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.5 Rather than requiring users to create a ProtonFactoryLoader, get a factory and then create an object, instead just do Proton.connection(), Proton.message(), etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-221) optionally set warning flags only if gcc version supports them
[ https://issues.apache.org/jira/browse/PROTON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-221: --- Fix Version/s: (was: 0.4) optionally set warning flags only if gcc version supports them -- Key: PROTON-221 URL: https://issues.apache.org/jira/browse/PROTON-221 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Building with gcc Reporter: Cliff Jansen Assignee: Cliff Jansen Older versions of gcc do not support the C++ compatibility flags. Instead of failing the build, they should print a warning that won't scare proton users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-206) Use const char* variables for string literals
[ https://issues.apache.org/jira/browse/PROTON-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-206: --- Fix Version/s: (was: 0.4) Use const char* variables for string literals - Key: PROTON-206 URL: https://issues.apache.org/jira/browse/PROTON-206 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.3 Environment: all Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Minor proton sometimes uses declarations of the form char *host = 0.0.0.0; These should be hunted down and replaced with a const declaration. Where these variables are passed as arguments to other functions, those should be additionally changed to const where appropriate. This occurs in examples/messenger/c/send.c examples/messenger/c/recv.c src/messenger.c src/util.c src/proton.c -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (PROTON-189) SSL certs used in unit tests fail on some platforms when certs are generated on Fedora 17
[ https://issues.apache.org/jira/browse/PROTON-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming closed PROTON-189. -- Resolution: Fixed I'm closing this as there doesn't seem to be any specific action associated with this. Please reopen and clarify if this is still a problem. SSL certs used in unit tests fail on some platforms when certs are generated on Fedora 17 - Key: PROTON-189 URL: https://issues.apache.org/jira/browse/PROTON-189 Project: Qpid Proton Issue Type: Bug Environment: Generate keys on fedora 17, use them on Java platform. Reporter: Ken Giusti Priority: Minor Attachments: certpatch.txt When creating new keys on fedora 17 while using the method described in proton_tests/ssl_db/README.txt, parsing the keys will fail on some Java platforms with the error: ENCRYPTED PRIVATE KEY: java.security.InvalidKeyException: Illegal key size -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-417) Remove/optionalize bouncycastle dependency
Rafael H. Schloming created PROTON-417: -- Summary: Remove/optionalize bouncycastle dependency Key: PROTON-417 URL: https://issues.apache.org/jira/browse/PROTON-417 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rafael H. Schloming Fix For: 0.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
