Mac OS X
Hello, There is anyone working on qpid client lib (C++) for Mac OS X? Thank you. -- Bruno Matos bruno.ma...@paradigmaxis.pt - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2518) Qpid C++ broker can easily be blocked by client trying to connect over SSL port
Qpid C++ broker can easily be blocked by client trying to connect over SSL port --- Key: QPID-2518 URL: https://issues.apache.org/jira/browse/QPID-2518 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Red Hat Enterprise MRG 1.2 Reporter: Armin Noll We are running a C++ broker as deamon with the following configuration: log-enable=info+ log-to-file=/var/lib/qpidd/op_prod09/data/0097/qpidd.log log-to-syslog=no auth=yes acl-file=qpidd.acl realm=QPID0097 data-dir=/var/lib/qpidd/op_prod09/data/0097 pid-dir=/var/lib/qpidd/op_prod09/data/0097 port=20097 wait=30 num-jfiles=4 jfile-size-pgs=1 wcache-page-size=128 tpl-num-jfiles=4 tpl-jfile-size-pgs=1 tpl-wcache-page-size=128 ssl-cert-db=/var/lib/qpidd/op_prod09/data/0097 ssl-port=10097 ssl-cert-name=RGC001 ssl-cert-password-file=/var/lib/qpidd/op_prod09/data/0097/amq_cert_db.pwd ssl-require-client-authentication=yes cluster-name=QPID0097 cluster-url=amqp:tcp:172.16.45.198:20097 cluster-username=x cluster-password=x We tried to connect an application to the SSL port which does not talk the correct protocol. We simply used telnet: $ telnet 172.16.45.198 10097 The result was (we waited at least 30 min, then killed the process running telnet): The broker doesn't react anymore, no more new client connections can be established, the broker even cannot be stopped with qpidd -p 20097 -q. This way anybody in the world could easily block our service provided over a Qpid broker. Is there a way to get around this? This issue has also been reported as Red Hat service request no. 2014266. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2097) InVM JMX Console appears to have problems starting up/shutting down.
[ https://issues.apache.org/jira/browse/QPID-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2097: - Status: Ready To Review (was: In Progress) InVM JMX Console appears to have problems starting up/shutting down. Key: QPID-2097 URL: https://issues.apache.org/jira/browse/QPID-2097 Project: Qpid Issue Type: Bug Components: Java Broker, Java Management : JMX Interface Reporter: Martin Ritchie Assignee: Robbie Gemmell Summary: Running queue.ModelTest InVM results in alternating Pass/Fails. The even tests will always fail to get a JMX Connection however, the by the time the next test starts it will have cleared up the issue and the new JMX interface will be ok. So while QPID-2094 has enabled the ability to use the JMX interface from an InVM test case it appears that there are problems with the registration/unregistration of the JMX Server components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[Java] Broker Roadmap/0-10 Java Client Query
All, Java Broker - 0.8 Release - I'm currently figuring out the remaining work required on the Java side to complete the broker 0-10 implementation, test it and support multiple versions of the protocol from client to broker and back. In roadmap terms, I'm targeting our next release (0.8) for 0-10 complete on the Java broker side and 0-10 interop with the C++ client, at least. You'll see the Java devs who work near me raising JIRAs for these items and starting on them imminently. Obviously please shout or pitch in where you can/would like to. There might be time for docs too once we've got the code figured out. Java 0-10 Client I'm currently knee (chin) deep in todos, massively on the client side. I'll be perusing the JIRAs open shortly. Can the devs on this list please chip in with the key items outstanding on the Java Client side for 0-10 i.e. - are there features on the 0-8/0-9 codepaths that have not been completed on the 0-10 client path ? - Anything partially there but needing more work ? Bring our your skeletons now ! Be kind and save me from hundreds of todos (470 on trunk argh) and JIRA browsing. Also, please don't add empty todos or worse 'fix' todos with no comment saying what needs fixed. Sometimes it is obvious, other times really not so much . Don't even get me started on comments ;-) Bfn, Marnie
Re: Mac OS X
On 2010/04/20, at 15:33, Andrew Stitcher wrote: On Tue, 2010-04-20 at 09:53 +0100, Bruno Matos wrote: Hello, There is anyone working on qpid client lib (C++) for Mac OS X? There has been some interest expressed in this, and some patches have been submitted. However, the OSX runtime has no support for the gcc thread specific variables extension that we use on that compiler, fixing this isn't trivial, and the patches that have been submitted aren't good enough yet (see https://issues.apache.org/jira/browse/QPID-2206). If you have the skills and interest we would welcome you to help, we don't have anyone in the current core team who is using Mac OS X as far as I know. Note that you should already be able to use the other clients (Python, ruby, Java) on Mac OS. Andrew Thank you Andrew! I'll see what I can do. At this time we are using a Qt client, and would be better to use a C+ + lib than trying to make a jms proxy or something like that. Regards. -- Bruno Matos bruno.ma...@paradigmaxis.pt - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2520) Broken POM generation on Windows
[
https://issues.apache.org/jira/browse/QPID-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2520:
-
Description:
The genpom script doesn't work on Windows. Calling ant pom gives the
following stacktrace :
{code}
pom:
[java] Traceback (most recent call last):
[java] File C:\dev\apache\qpid\java/genpom, line 95, in module
[java] pom = search(expanded_path, %s.pom % base)
[java] File C:\dev\apache\qpid\java/genpom, line 83, in search
[java] return mllib.xml_parse(f)
[java] File C:\dev\apache\qpid\python\mllib\__init__.py, line 79, in
xml_parse
[java] p.parse(source)
[java] File
C:\dev\apache\qpid\java\lib\jython-2.5.0.jar\Lib\xml\sax\drivers2\drv_javasax.py,
line 141, in parse
[java] at java.io.FileInputStream.open(Native Method)
[java] at java.io.FileInputStream.init(FileInputStream.java:106)
[java] at java.io.FileInputStream.init(FileInputStream.java:66)
[java] at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
[java] at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:653)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:772)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
[java] at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
[java] at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
[java] at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java]
[java] java.io.FileNotFoundException: java.io.FileNotFoundException:
C:\dev\apache\qpid\java\common\dev\apache\qpid\java\lib\poms\slf4j-api-1.4.0.pom
(Le chemin d'accès spécifié est introuvable)
{code}
It works fine on Linux
was:
The genpom script doesn't work on Windows. Calling ant pom gives the
following stacktrace :
{code}
pom:
[java] Traceback (most recent call last):
[java] File C:\dev\apache\qpid-trunk\java/genpom, line 95, in module
[java] pom = search(expanded_path, %s.pom % base)
[java] File C:\dev\apache\qpid-trunk\java/genpom, line 83, in search
[java] return mllib.xml_parse(f)
[java] File C:\dev\apache\qpid-trunk\python\mllib\__init__.py, line
79, in xml_parse
[java] p.parse(source)
[java] File
C:\dev\apache\qpid-trunk\java\lib\jython-2.5.0.jar\Lib\xml\sax\drivers2\drv_javasax.py,
line 141, in parse
[java] at java.io.FileInputStream.open(Native Method)
[java] at java.io.FileInputStream.init(FileInputStream.java:106)
[java] at java.io.FileInputStream.init(FileInputStream.java:66)
[java] at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
[java] at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:653)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:772)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
[java] at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
[java] at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
[java] at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java]
[java] java.io.FileNotFoundException:
Re: [Java] Broker Roadmap/0-10 Java Client Query
On 04/20/2010 05:03 PM, Marnie McCormack wrote: In roadmap terms, I'm targeting our next release (0.8) for 0-10 complete on the Java broker side and 0-10 interop with the C++ client, at least. I think it would be worth planning to release 0.8 sooner rather than later. Its been over 3 months since the freeze for 0.6 and there have been many fixes (and indeed some features) on trunk since then. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [Java] Broker Roadmap/0-10 Java Client Query
On 04/20/2010 05:03 PM, Marnie McCormack wrote: Can the devs on this list please chip in with the key items outstanding on the Java Client side for 0-10 i.e. - are there features on the 0-8/0-9 codepaths that have not been completed on the 0-10 client path ? Server-side selectors is the obvious item. That is not yet supported by the c++ broker so the 0-10 client implements it (or attempts to!) client side. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2520) Broken POM generation on Windows
[
https://issues.apache.org/jira/browse/QPID-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated QPID-2520:
-
Attachment: genpom.patch
This is caused by a wrong path separator in the genpom script that restricts it
to POSIX platforms. The fix is trivial.
Broken POM generation on Windows
Key: QPID-2520
URL: https://issues.apache.org/jira/browse/QPID-2520
Project: Qpid
Issue Type: Bug
Components: Build Tools, python tools
Affects Versions: 0.6
Reporter: Emmanuel Bourg
Fix For: 0.7
Attachments: genpom.patch
The genpom script doesn't work on Windows. Calling ant pom gives the
following stacktrace :
{code}
pom:
[java] Traceback (most recent call last):
[java] File C:\dev\apache\qpid\java/genpom, line 95, in module
[java] pom = search(expanded_path, %s.pom % base)
[java] File C:\dev\apache\qpid\java/genpom, line 83, in search
[java] return mllib.xml_parse(f)
[java] File C:\dev\apache\qpid\python\mllib\__init__.py, line 79, in
xml_parse
[java] p.parse(source)
[java] File
C:\dev\apache\qpid\java\lib\jython-2.5.0.jar\Lib\xml\sax\drivers2\drv_javasax.py,
line 141, in parse
[java] at java.io.FileInputStream.open(Native Method)
[java] at java.io.FileInputStream.init(FileInputStream.java:106)
[java] at java.io.FileInputStream.init(FileInputStream.java:66)
[java] at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
[java] at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:653)
[java] at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:772)
[java] at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
[java] at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
[java] at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
[java] at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java]
[java] java.io.FileNotFoundException: java.io.FileNotFoundException:
C:\dev\apache\qpid\java\common\dev\apache\qpid\java\lib\poms\slf4j-api-1.4.0.pom
(Le chemin d'accès spécifié est introuvable)
{code}
It works fine on Linux
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2498) Upgrade Mina to 1.1.7
[ https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2498: - Attachment: mina-poms.patch Additional patch to update the POMs Upgrade Mina to 1.1.7 - Key: QPID-2498 URL: https://issues.apache.org/jira/browse/QPID-2498 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: mina-poms.patch, mina.patch, mina2.patch Upgrading Mina to 1.1.7 would allow the removal of backport-util-concurrent.jar from the dependencies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Issue Comment Edited: (QPID-2519) Allow Windows Broker to run as a Service
[ https://issues.apache.org/jira/browse/QPID-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12858943#action_12858943 ] Kerry Bonin edited comment on QPID-2519 at 4/20/10 1:38 PM: This patch implements most of my worklist for the feature. - No changes to cross-platform qpidd.cpp - Preserve single executable. - Preserve service encapsulation in separate class (WinService) - Encapsulate basic SCM features via command line - install, start, stop, uninstall - Allow basic SCM options at install - account, dependent service list - Runs on XP through Win7, Server 2003 2008 (passed a few weeks system test) Features I still want and plan to add, but can't get to right now, hope to get back to soon... - Rename service - Set service description text - Change default account name - Change startup error level - Clean up event log use for error reporting - add use message files for proper formatting. Please let me know if anyone has any issues or concerns with these changes, and I'll do my best to fix them ASAP. We've already built this into a major product release, its worked well in test so far... Kerry Bonin Systems Architect United Technologies Fire Security, formerly GE Security was (Author: kbonin): This patch implements most of my worklist for the feature. - No changes to cross-platform qpidd.cpp - Preserve single executable. - Preserve service encapsulation in separate class (WinService) - Encapsulate basic SCM features via command line - install, start, stop, uninstall - Allow basic SCM options at install - account, dependent service list - Runs on XP through Win7, Server 2003 2008 (passed a few weeks system test) Features I still want and plan to add, but can't get to right now, hope to get back to soon... - Rename service - Set service description text - Change default account name - Change startup error level - Clean up event log use for error reporting - add use message files for proper formatting. Please let me know if anyone has any issues or concerns with these changes, and I'll do my best to fix them ASAP. We've already built this into a major product release (GE Security / United Technologies Fire Security), its worked well in test so far... Kerry Bonin Systems Architect United Technologies Fire Security, formerly GE Security Allow Windows Broker to run as a Service Key: QPID-2519 URL: https://issues.apache.org/jira/browse/QPID-2519 Project: Qpid Issue Type: New Feature Components: C++ Broker Reporter: Kerry Bonin Attachments: broker_as_service_r921371.patch The Windows version of the C++ Broker should have the ability to run as a Windows Service, to correspond with the ability of the *nix version to run as a daemon, as this is a common requirement for critical software infrastructure elements of enterprise class software on the Windows platform. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Issue Comment Edited: (QPID-2519) Allow Windows Broker to run as a Service
[ https://issues.apache.org/jira/browse/QPID-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12858943#action_12858943 ] Kerry Bonin edited comment on QPID-2519 at 4/20/10 1:38 PM: This patch implements most of my worklist for the feature. - No changes to cross-platform qpidd.cpp - Preserve single executable. - Preserve service encapsulation in separate class (WinService) - Encapsulate basic SCM features via command line - install, start, stop, uninstall - Allow basic SCM options at install - account, dependent service list - Runs on XP through Win7, Server 2003 2008 (passed a few weeks system test) Features I still want and plan to add, but can't get to right now, hope to get back to soon... - Rename service - Set service description text - Change default account name - Change startup error level - Clean up event log use for error reporting - add use message files for proper formatting. Please let me know if anyone has any issues or concerns with these changes, and I'll do my best to fix them ASAP. We've already built this into a major product release, its worked well in test so far... Kerry Bonin was (Author: kbonin): This patch implements most of my worklist for the feature. - No changes to cross-platform qpidd.cpp - Preserve single executable. - Preserve service encapsulation in separate class (WinService) - Encapsulate basic SCM features via command line - install, start, stop, uninstall - Allow basic SCM options at install - account, dependent service list - Runs on XP through Win7, Server 2003 2008 (passed a few weeks system test) Features I still want and plan to add, but can't get to right now, hope to get back to soon... - Rename service - Set service description text - Change default account name - Change startup error level - Clean up event log use for error reporting - add use message files for proper formatting. Please let me know if anyone has any issues or concerns with these changes, and I'll do my best to fix them ASAP. We've already built this into a major product release, its worked well in test so far... Kerry Bonin Systems Architect United Technologies Fire Security, formerly GE Security Allow Windows Broker to run as a Service Key: QPID-2519 URL: https://issues.apache.org/jira/browse/QPID-2519 Project: Qpid Issue Type: New Feature Components: C++ Broker Reporter: Kerry Bonin Attachments: broker_as_service_r921371.patch The Windows version of the C++ Broker should have the ability to run as a Windows Service, to correspond with the ability of the *nix version to run as a daemon, as this is a common requirement for critical software infrastructure elements of enterprise class software on the Windows platform. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1916) Maven releases for the client and management jars
[ https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859012#action_12859012 ] Emmanuel Bourg commented on QPID-1916: -- The patch is probably a bit outdated now. It would be better to reuse the poms generated by the pom task. Maven releases for the client and management jars - Key: QPID-1916 URL: https://issues.apache.org/jira/browse/QPID-1916 Project: Qpid Issue Type: New Feature Components: Ant Build System, Build Tools, Java Client, Java Common, Java Tools, Maven build system, Qpid Managment Framework Reporter: Bryan Kearney Attachments: mavenize3.patch The attached patch files adds the maven ant tasks to the build system. It allows, on a per-module basis, to support creating a pom file and exporting the jars to a maven repository. This is not a very DRY solution, as it requires copying the dependency information from the build.deps file. I have only added the pom files for the client bits, since i believe these are the most likely to be required by folks using QMF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
How do we run python tools after recent changes?
I used to be able to get qpid-route, ect. to run by updating my PYTHONPATH, but now I get ImportError: No module named qmf.console even with that set correctly. Any updated methods? Thanks...
[jira] Commented: (QPID-2518) Qpid C++ broker can easily be blocked by client trying to connect over SSL port
[ https://issues.apache.org/jira/browse/QPID-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859035#action_12859035 ] Gordon Sim commented on QPID-2518: -- I believe this is addressed by http://svn.apache.org/viewvc?view=revisionrevision=790291. Qpid C++ broker can easily be blocked by client trying to connect over SSL port --- Key: QPID-2518 URL: https://issues.apache.org/jira/browse/QPID-2518 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Red Hat Enterprise MRG 1.2 Reporter: Armin Noll We are running a C++ broker as deamon with the following configuration: log-enable=info+ log-to-file=/var/lib/qpidd/op_prod09/data/0097/qpidd.log log-to-syslog=no auth=yes acl-file=qpidd.acl realm=QPID0097 data-dir=/var/lib/qpidd/op_prod09/data/0097 pid-dir=/var/lib/qpidd/op_prod09/data/0097 port=20097 wait=30 num-jfiles=4 jfile-size-pgs=1 wcache-page-size=128 tpl-num-jfiles=4 tpl-jfile-size-pgs=1 tpl-wcache-page-size=128 ssl-cert-db=/var/lib/qpidd/op_prod09/data/0097 ssl-port=10097 ssl-cert-name=RGC001 ssl-cert-password-file=/var/lib/qpidd/op_prod09/data/0097/amq_cert_db.pwd ssl-require-client-authentication=yes cluster-name=QPID0097 cluster-url=amqp:tcp:172.16.45.198:20097 cluster-username=x cluster-password=x We tried to connect an application to the SSL port which does not talk the correct protocol. We simply used telnet: $ telnet 172.16.45.198 10097 The result was (we waited at least 30 min, then killed the process running telnet): The broker doesn't react anymore, no more new client connections can be established, the broker even cannot be stopped with qpidd -p 20097 -q. This way anybody in the world could easily block our service provided over a Qpid broker. Is there a way to get around this? This issue has also been reported as Red Hat service request no. 2014266. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2523) When reloading a large acl file while acl lookup is in progress, the broker core dumps
When reloading a large acl file while acl lookup is in progress, the broker
core dumps
--
Key: QPID-2523
URL: https://issues.apache.org/jira/browse/QPID-2523
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.5, M4, 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
Description of problem:
When reloading a large acl file , the broker core dumps.
This surfaced while running the attached reproducer.
How reproducible:
Always - reproducer attached.
Steps to Reproduce:
1. Start the broker with the acl module and and --acl-file /tmp/policy.acl
2. The initial acl file should contain only acl allow all all
3. run the message_sender.py (This program will keep on publishing to
amq.direct)
4. run acl_reloader.py with --mode allow | deny a few times
Actual results:
The broker core dumps.
Expected results:
The broker should continue to work after reloading the acl file properly.
Additional info:
Following is the backtrace from the code dump.
1.
(gdb) bt
2.
#0 0x00cbe422 in __kernel_vsyscall ()
3.
#1 0x00183781 in raise () from /lib/libc.so.6
4.
#2 0x0018504a in abort () from /lib/libc.so.6
5.
#3 0x001c1619 in __libc_message () from /lib/libc.so.6
6.
#4 0x001c7a71 in malloc_printerr () from /lib/libc.so.6
7.
#5 0x001ca363 in munmap_chunk () from /lib/libc.so.6
8.
#6 0x040a1681 in operator delete(void*) () from /usr/lib/libstdc++.so.6
9.
#7 0x0035243e in qpid::acl::AclData::clear (this=0x8221328) at
qpid/acl/AclData.cpp:40
10.
#8 0x003524ad in qpid::acl::AclData::~AclData (this=0x8221328,
__in_chrg=value optimized out) at qpid/acl/AclData.cpp:259
11.
#9 0x003515a8 in checked_deleteqpid::acl::AclData (x=value optimized
out) at /usr/include/boost/checked_delete.hpp:34
12.
#10 boost::detail::sp_counted_impl_pqpid::acl::AclData::dispose
(x=value optimized out) at /usr/include/boost/detail/sp_counted_impl.hpp:78
13.
#11 0x0034e50b in boost::detail::sp_counted_base::release (this=value
optimized out) at /usr/include/boost/detail/sp_counted_base_gcc_x86.hpp:145
14.
#12 ~shared_count (this=value optimized out) at
/usr/include/boost/detail/shared_count.hpp:216
15.
#13 ~shared_ptr (this=value optimized out) at
/usr/include/boost/shared_ptr.hpp:165
16.
#14 qpid::acl::Acl::authorise (this=value optimized out) at
qpid/acl/Acl.cpp:86
17.
#15 0x00add720 in qpid::broker::SemanticState::route (this=0x82218a0,
msg={p_ = 0xb5644868}, strate...@0xb61fe178)
18.
at qpid/broker/SemanticState.cpp:447
19.
#16 0x00ade215 in qpid::broker::SemanticState::handle (this=0x82218a0,
msg={p_ = 0xb5644868}) at qpid/broker/SemanticState.cpp:415
20.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Unresolved issues but marked 0.6
Rajith Attapattu a écrit : Could we please take a moment to resolve any JIRA's with ready to review status that actually made it into the 0.6 release? If a fix actually made it into a release, then it's not correct to just bump the version to the next release. Therefore at the end of the week, what ever that is renaming will be pushed into no version as suggested by Martin. Please shout if anybody disagrees. Closing the 0.6 release in JIRA would be much welcome. However instead of unscheduling the issues by removing the Fix Version field I would advise prioritizing the issues and dispatching them over the next 3 releases in JIRA (to be created). Also you would probably like to create a Later release ordered after all the others for the low priority stuff. The benefit of this organization is to have a clear view of the roadmap by looking at the JIRA dashboard: https://issues.apache.org/jira/browse/QPID?report=com.atlassian.jira.plugin.system.project:roadmap-panel If the issues are not scheduled they aren't displayed there and tend to be forgotten. Regards, Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: commons-lang.patch Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: (was: commons-lang.patch) Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: commons-lang.patch Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: commons-lang.patch Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: (was: commons-lang.patch) Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: (was: commons-lang.patch) Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2522) Remove the dependency on Commons Lang for the Java client
[ https://issues.apache.org/jira/browse/QPID-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2522: - Attachment: commons-lang.patch Remove the dependency on Commons Lang for the Java client - Key: QPID-2522 URL: https://issues.apache.org/jira/browse/QPID-2522 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Fix For: 0.7 Attachments: commons-lang.patch Commons Lang is required by the Java client but is used only once to perform a trivial string substitution. This dependency could easily be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Unresolved issues but marked 0.6
-Original Message- From: Emmanuel Bourg [mailto:ebo...@apache.org] Sent: 20 April 2010 22:30 To: dev@qpid.apache.org Subject: Re: Unresolved issues but marked 0.6 snip Closing the 0.6 release in JIRA would be much welcome. /snip Done, 0.6 no longer shows on the roadmap view. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
