[jira] [Commented] (QPID-6266) qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
[ https://issues.apache.org/jira/browse/QPID-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390310#comment-14390310 ] Enrico Popall commented on QPID-6266: - Hi guys Thanks for the extremly helpful hints you provide here. I was able to compile Qpid including Proton with VS 2013. Nevertheless, the examples won't work as they run into an error when connecting to the qpid broker: Sasl error: no common mechanism. My compiled version does not include SASL. I get the same error with Chucks precompiled dlls so I guess it is left out there as well. Is there a way to include cyrus sasl in the windows build? qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll Key: QPID-6266 URL: https://issues.apache.org/jira/browse/QPID-6266 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.30 Environment: Windows XP (x86) Windows 7 ( x64). Visual Studios 2008, 2010 Reporter: Fred Cheng Assignee: Chuck Rolke Original Estimate: 120h Remaining Estimate: 120h The build instructions in the file INSTALL-WINDOWS in qpid-cpp-0.30 does not work. For example, the file said to install 1. CMake 2.4 2. cmake -i -G Visual Studio 9 2008 The problem is the CMake 2.4 does not support Visual Studio 9 2008 A second example is that the command -i for cmake has been depreciated in current version of cmake. The file README-winsdk.txt also appears to be outdated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6446) [Java Broker] Existing virtual host/node derby database is shutdown on attempt to create a virtual host/node with duplicate name
[ https://issues.apache.org/jira/browse/QPID-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6446: - Summary: [Java Broker] Existing virtual host/node derby database is shutdown on attempt to create a virtual host/node with duplicate name (was: [Java Broker] On creation of duplicate virtual host node the existion virtual host node configuration store is deleted as part of removal of duplicate node) [Java Broker] Existing virtual host/node derby database is shutdown on attempt to create a virtual host/node with duplicate name Key: QPID-6446 URL: https://issues.apache.org/jira/browse/QPID-6446 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.30 Reporter: Alex Rudyy Assignee: Alex Rudyy Attachments: VirtualHostNodeTest.java On creation operation for virtual host node having the same name as an existing virtual host node, the existing virtual host node store is deleted as part of cleanup of duplicate virtual host node. The stack trace below is generate on creating of duplicate DERBY VHN: {noformat} java.sql.SQLException: Database '/tmp/qpid.work_dir-1426160975964/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose/config/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose' not found. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleDBNotFound(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.init(Unknown Source) at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:571) at java.sql.DriverManager.getConnection(DriverManager.java:233) at org.apache.qpid.server.store.derby.DerbyUtils.shutdownDatabase(DerbyUtils.java:108) at org.apache.qpid.server.store.derby.DerbyConfigurationStore.closeConfigurationStore(DerbyConfigurationStore.java:107) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.closeConfigurationStore(AbstractVirtualHostNode.java:287) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.onClose(AbstractVirtualHostNode.java:242) at org.apache.qpid.server.model.AbstractConfiguredObject.close(AbstractConfiguredObject.java:506) at org.apache.qpid.server.store.derby.VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose(VirtualHostNodeTest.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at junit.framework.TestCase.runTest(TestCase.java:176) at junit.framework.TestCase.runBare(TestCase.java:141) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:148) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[jira] [Updated] (QPID-6446) [Java Broker] Existing virtual host/node derby database is shutdown on attempt to create a virtual host/node with duplicate name
[ https://issues.apache.org/jira/browse/QPID-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6446: - Description: On creation operation for virtual host node having the same name as an existing virtual host node, the existing virtual host node store is shutdown as part of on create validation. The stack trace below is generated on close of existing DERBY VHN after its shutdown due to validation checks: {noformat} java.sql.SQLException: Database '/tmp/qpid.work_dir-1426160975964/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose/config/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose' not found. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleDBNotFound(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.init(Unknown Source) at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:571) at java.sql.DriverManager.getConnection(DriverManager.java:233) at org.apache.qpid.server.store.derby.DerbyUtils.shutdownDatabase(DerbyUtils.java:108) at org.apache.qpid.server.store.derby.DerbyConfigurationStore.closeConfigurationStore(DerbyConfigurationStore.java:107) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.closeConfigurationStore(AbstractVirtualHostNode.java:287) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.onClose(AbstractVirtualHostNode.java:242) at org.apache.qpid.server.model.AbstractConfiguredObject.close(AbstractConfiguredObject.java:506) at org.apache.qpid.server.store.derby.VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose(VirtualHostNodeTest.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at junit.framework.TestCase.runTest(TestCase.java:176) at junit.framework.TestCase.runBare(TestCase.java:141) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:148) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) Caused by: ERROR XJ004: Database '/tmp/qpid.work_dir-1426160975964/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose/config/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose' not found. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source) ... 42 more 2015-03-12 11:49:42,188 DEBUG [main] [TaskExecutorImpl] Stopping task executor 2015-03-12 11:49:42,190 DEBUG [main] [TaskExecutorImpl] Task executor is stopped 2015-03-12 11:49:42,196 INFO [main] [QpidTestCase] == tearDown VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose == 2015-03-12
[jira] [Commented] (QPID-6446) [Java Broker] On creation of duplicate virtual host node the existion virtual host node configuration store is deleted as part of removal of duplicate node
[ https://issues.apache.org/jira/browse/QPID-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390489#comment-14390489 ] ASF subversion and git services commented on QPID-6446: --- Commit 1670629 from oru...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1670629 ] QPID-6446: Verify that store path is a writable folder on creation of derby virtual host and node [Java Broker] On creation of duplicate virtual host node the existion virtual host node configuration store is deleted as part of removal of duplicate node --- Key: QPID-6446 URL: https://issues.apache.org/jira/browse/QPID-6446 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.30 Reporter: Alex Rudyy Assignee: Alex Rudyy Attachments: VirtualHostNodeTest.java On creation operation for virtual host node having the same name as an existing virtual host node, the existing virtual host node store is deleted as part of cleanup of duplicate virtual host node. The stack trace below is generate on creating of duplicate DERBY VHN: {noformat} java.sql.SQLException: Database '/tmp/qpid.work_dir-1426160975964/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose/config/VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose' not found. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleDBNotFound(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.init(Unknown Source) at org.apache.derby.jdbc.InternalDriver.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:571) at java.sql.DriverManager.getConnection(DriverManager.java:233) at org.apache.qpid.server.store.derby.DerbyUtils.shutdownDatabase(DerbyUtils.java:108) at org.apache.qpid.server.store.derby.DerbyConfigurationStore.closeConfigurationStore(DerbyConfigurationStore.java:107) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.closeConfigurationStore(AbstractVirtualHostNode.java:287) at org.apache.qpid.server.virtualhostnode.AbstractVirtualHostNode.onClose(AbstractVirtualHostNode.java:242) at org.apache.qpid.server.model.AbstractConfiguredObject.close(AbstractConfiguredObject.java:506) at org.apache.qpid.server.store.derby.VirtualHostNodeTest.testCreateDuplicateVirtualHostNodeAndClose(VirtualHostNodeTest.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at junit.framework.TestCase.runTest(TestCase.java:176) at junit.framework.TestCase.runBare(TestCase.java:141) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:148) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at
[jira] [Created] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
Alan Conway created DISPATCH-130: Summary: qdrouterd with --daemon and --user options does not dump core. Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390579#comment-14390579 ] Alan Conway commented on DISPATCH-130: -- There is a historical problem with core dumps and setuid executables, e.g. from https://access.redhat.com/solutions/4896 : 6) With this setup, a core file from the application should result. If this does not generate a core, make sure that the application has the correct uid and that it does not use setuid to change uid when running. On Red Hat Enterprise Linux 3, use the following command to enable the dumping of setuid applications: # echo 1 /proc/sys/kernel/core_setuid_ok This kernel setting no longer exists on RHEL6/Fedora 21 but it looks likely the the problem is in the way we are setting the UID in qdroutered with --user. Given the presence of systemd as well, it might be best to get rid of the daemonizing logic in qdrouterd and use the daemon() function for sysv init or let systemd do daemonizing when systemd is in use. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6266) qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
[ https://issues.apache.org/jira/browse/QPID-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390589#comment-14390589 ] Chuck Rolke commented on QPID-6266: --- Gordon suggests that the windows client uses PLAIN by default, but does not supply a username. Try adding {NOFORMAT} --connection-options '{sasl_mechanisms:ANONYMOUS}' or --connection-options '{username:foo}' {NOFORMAT} to your connection creation qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll Key: QPID-6266 URL: https://issues.apache.org/jira/browse/QPID-6266 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.30 Environment: Windows XP (x86) Windows 7 ( x64). Visual Studios 2008, 2010 Reporter: Fred Cheng Assignee: Chuck Rolke Original Estimate: 120h Remaining Estimate: 120h The build instructions in the file INSTALL-WINDOWS in qpid-cpp-0.30 does not work. For example, the file said to install 1. CMake 2.4 2. cmake -i -G Visual Studio 9 2008 The problem is the CMake 2.4 does not support Visual Studio 9 2008 A second example is that the command -i for cmake has been depreciated in current version of cmake. The file README-winsdk.txt also appears to be outdated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned DISPATCH-130: --- Assignee: Ken Giusti (was: Alan Conway) qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Ken Giusti Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6266) qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll
[ https://issues.apache.org/jira/browse/QPID-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390773#comment-14390773 ] Enrico Popall commented on QPID-6266: - Call yourself a life saver :) Thanks a lot! For everyone else having trouble connecting to the broker, this is how it looks like in the example {code:title=csharp.example.helloworld.cs|borderStyle=solid} connection = new Connection(broker); connection.SetOption(sasl_mechanisms, PLAIN); connection.SetOption(username, guest); connection.SetOption(password, guest); connection.Open(); Session session = connection.CreateSession(); {code} qpid-cpp-0.30 Build Fail - Org.Apache.Qpid.Messaging.dll Key: QPID-6266 URL: https://issues.apache.org/jira/browse/QPID-6266 Project: Qpid Issue Type: Bug Components: Dot Net Client Affects Versions: 0.30 Environment: Windows XP (x86) Windows 7 ( x64). Visual Studios 2008, 2010 Reporter: Fred Cheng Assignee: Chuck Rolke Original Estimate: 120h Remaining Estimate: 120h The build instructions in the file INSTALL-WINDOWS in qpid-cpp-0.30 does not work. For example, the file said to install 1. CMake 2.4 2. cmake -i -G Visual Studio 9 2008 The problem is the CMake 2.4 does not support Visual Studio 9 2008 A second example is that the command -i for cmake has been depreciated in current version of cmake. The file README-winsdk.txt also appears to be outdated. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391039#comment-14391039 ] Ken Giusti commented on DISPATCH-130: - +1 to the deprecation of the setuid stuff. That's the root cause of this problem. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390988#comment-14390988 ] Ken Giusti edited comment on DISPATCH-130 at 4/1/15 5:05 PM: - I've been able to get dumping of setuid processes (qdrouterd -d --user qpidd specifically) on my RHEL 6 and RHEL 7 boxes. I added the following to /etc/sysctl.conf: fs.suid_dumpable = 2 and to /etc/security/limits.conf: * soft core unlimited (that's an asterisk as the first character above - for some reason that forces a bullet format!) then cat /tmp/core.%e.%p /proc/sys/kernel/core_pattern I was able to use kill -6 to cause qdrouterd to dump core into the /tmp directory. was (Author: kgiusti): I've been able to get dumping of setuid processes (qdrouterd -d --user qpidd specifically) on my RHEL 6 and RHEL 7 boxes. I added the following to /etc/sysctl.conf: fs.suid_dumpable = 2 and to /etc/security/limits.conf: * soft core unlimited then cat /tmp/core.%e.%p /proc/sys/kernel/core_pattern I was able to use kill -6 to cause qdrouterd to dump core into the /tmp directory. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Ken Giusti Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391039#comment-14391039 ] Ken Giusti edited comment on DISPATCH-130 at 4/1/15 5:32 PM: - +1 to the deprecation of the setuid stuff. That's the root cause of this problem. And it's orthogonal to the daemonization stuff anyways. was (Author: kgiusti): +1 to the deprecation of the setuid stuff. That's the root cause of this problem. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391052#comment-14391052 ] Alan Conway commented on DISPATCH-130: -- The quick (but clean) fix is to change the init script to run qdrouterd with the sysv daemon() function and to *not* use --daemonize or --user. If that works out OK we can consider whether we want to strip them out entirely or whether they still have some value. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390994#comment-14390994 ] Alan Conway commented on DISPATCH-130: -- Good to know but unfriendly. I think the problem is that qdrouter is started as root and then changes its own uid. Since it _started_ as root it _could_ have sensitive info in it's core dump so it gets the top-secret treatment from the kernel. On the other hand qpidd (for example) is started *as a non-root user* by the runuser function in the init script. So it doesn't have this problem. I think that's what we should do with qdrouterd. (In fact we might just want to strip out all the daemonizing code and let the init script do it with the daemon() function, since all that stuff becomes irrelevant under systemd anyway. I'm less sure about that though...) qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390988#comment-14390988 ] Ken Giusti edited comment on DISPATCH-130 at 4/1/15 5:03 PM: - I've been able to get dumping of setuid processes (qdrouterd -d --user qpidd specifically) on my RHEL 6 and RHEL 7 boxes. I added the following to /etc/sysctl.conf: fs.suid_dumpable = 2 and to /etc/security/limits.conf: * soft core unlimited then cat /tmp/core.%e.%p /proc/sys/kernel/core_pattern I was able to use kill -6 to cause qdrouterd to dump core into the /tmp directory. was (Author: kgiusti): I've been able to get dumping of setuid processes (qdrouterd -d --user qpidd specifically) on my RHEL 6 and RHEL 7 boxes. I added the following to /etc/sysctl.conf: fs.suid_dumpable = 2 and to /etc/security/limits.conf: * soft core unlimited then cat /tmp/core.%e.%p /proc/sys/kernel/core_pattern I was able to use kill -6 to cause qdrouterd to dump core into the /tmp directory. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Ken Giusti Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390988#comment-14390988 ] Ken Giusti commented on DISPATCH-130: - I've been able to get dumping of setuid processes (qdrouterd -d --user qpidd specifically) on my RHEL 6 and RHEL 7 boxes. I added the following to /etc/sysctl.conf: fs.suid_dumpable = 2 and to /etc/security/limits.conf: * soft core unlimited then cat /tmp/core.%e.%p /proc/sys/kernel/core_pattern I was able to use kill -6 to cause qdrouterd to dump core into the /tmp directory. qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Ken Giusti Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue
[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14391257#comment-14391257 ] Scott Nicol commented on QPID-5870: --- Can you mark this as affect java client version 0.28 and fixed in 0.30. Closing a topic consumer should delete its exclusive auto-delete queue -- Key: QPID-5870 URL: https://issues.apache.org/jira/browse/QPID-5870 Project: Qpid Issue Type: Bug Reporter: Rajith Attapattu Attachments: QPID-5870.part2.patch, QPID-5870.patch When a topic consumer is closed, the subscription queue needs to be closed as well. Currently this queue is only deleted when the session is closed (due to being marked auto-deleted). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-130) qdrouterd with --daemon and --user options does not dump core.
[ https://issues.apache.org/jira/browse/DISPATCH-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned DISPATCH-130: --- Assignee: Alan Conway (was: Ken Giusti) qdrouterd with --daemon and --user options does not dump core. -- Key: DISPATCH-130 URL: https://issues.apache.org/jira/browse/DISPATCH-130 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.3 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.4 If qdroutered is started with --daemon and --user options, and then is killed with SIGABRT or crashes, it does not produce a core file. Note both --daemon and --user are reqiured to produce the problem, either alone does not. Tested on RHEL6 and Fedora 21 as follows: Send core files in /tmp, since --daemon will set current directory to / {noformat} # echo /tmp/core.%e.%p /proc/sys/kernel/core_pattern {noformat} Verify we do get a core file with just --daemon {noformat} # qdrouterd --daemon # pkill -e -6 qdrouterd qdrouterd killed (pid 11482) # ls /tmp/core* /tmp/core.qdrouterd.11482 {noformat} Now add --user {noformat} # rm /tmp/core* # qdrouterd --daemon --user aconway # pkill -e -6 qdrouterd qdrouterd killed (pid 11432) # ls /tmp/core* ls: cannot access /tmp/core*: No such file or directory {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue
[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-5870: -- Affects Version/s: 0.28 Closing a topic consumer should delete its exclusive auto-delete queue -- Key: QPID-5870 URL: https://issues.apache.org/jira/browse/QPID-5870 Project: Qpid Issue Type: Bug Affects Versions: 0.28 Reporter: Rajith Attapattu Attachments: QPID-5870.part2.patch, QPID-5870.patch When a topic consumer is closed, the subscription queue needs to be closed as well. Currently this queue is only deleted when the session is closed (due to being marked auto-deleted). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5870) Closing a topic consumer should delete its exclusive auto-delete queue
[ https://issues.apache.org/jira/browse/QPID-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-5870. --- Resolution: Fixed Fix Version/s: 0.30 As reported by [~ScottNicol] above this defect seems to have been addressed by a commit from [~rajith] prior to the 0.30 release (the commit appears to be consistent with the attached patches). Marking as resolved as I assume no-one will be going back and adding tests that verify that this change fixed whatever the original defect was. Closing a topic consumer should delete its exclusive auto-delete queue -- Key: QPID-5870 URL: https://issues.apache.org/jira/browse/QPID-5870 Project: Qpid Issue Type: Bug Affects Versions: 0.28 Reporter: Rajith Attapattu Fix For: 0.30 Attachments: QPID-5870.part2.patch, QPID-5870.patch When a topic consumer is closed, the subscription queue needs to be closed as well. Currently this queue is only deleted when the session is closed (due to being marked auto-deleted). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org