[jira] [Commented] (QPID-3900) Windows build fails to compile store ms-clfs
[ https://issues.apache.org/jira/browse/QPID-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250286#comment-13250286 ] Steve Huston commented on QPID-3900: And, indeed, we do need to backport it to 0.16 - good thinking, Mr.Chug :-) Windows build fails to compile store ms-clfs Key: QPID-3900 URL: https://issues.apache.org/jira/browse/QPID-3900 Project: Qpid Issue Type: Bug Reporter: Chuck Rolke Assignee: Chuck Rolke Fix For: 0.17 missing a '#include vector' in Transaction.h -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3759) Heartbeat timeout in Windows does not lead to timely reconnect
[ https://issues.apache.org/jira/browse/QPID-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247776#comment-13247776 ] Steve Huston commented on QPID-3759: With the closesocket instead of CancelIoEx, the nightly quick qpid-perftest crashes trying to close the socket after its impl has been freed. Test case: - Start broker - qpid-perftest --summary --count 100 Heartbeat timeout in Windows does not lead to timely reconnect -- Key: QPID-3759 URL: https://issues.apache.org/jira/browse/QPID-3759 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.14 Environment: Windows C++ messaging Reporter: Chuck Rolke Assignee: Cliff Jansen Fix For: 0.17 Attachments: main.cpp Reported by Wolf Wolfswinkel on Qpid users http://qpid.2158936.n2.nabble.com/Heartbeats-in-C-broker-on-Windows-td7118702.html 22-Dec-2011 The simplest test case is in attached main.cpp. Establish a good network connection to the broker and then start the program. It creates a connection, sends two messages, and then pauses for 15 seconds. During the pause disconnect the network connection to the broker for at least two heartbeat timeouts (12 seconds). After the heartbeat timeout the timer task fires and a debug trace shows: Traffic timeout, TCPConnector::abort, TCPConnector::eof, TCPConnector::close But the connection is not actually closed until something happens on the network to wake up the thread waiting in Poller::run(). The timer event appears unable to interrupt the IO thread waiting for the completion port. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3908) qpid-0.14 is incompatible with boost_1_49_0
[ https://issues.apache.org/jira/browse/QPID-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13235927#comment-13235927 ] Steve Huston commented on QPID-3908: Since Qpid 0.16 is nearing release, I recommend you obtain the latest source and retry the build. Or, make local changes to work around the issue. qpid-0.14 is incompatible with boost_1_49_0 --- Key: QPID-3908 URL: https://issues.apache.org/jira/browse/QPID-3908 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.14 Environment: Red Hat Enterprise Linux Server release 5.4 Reporter: sprasad Priority: Minor Fix For: Future Hi, We are upgrading our system to qpid-0.14 and boost_1_49_0. The following error is reported during qpid upgradation, and it looks like the boost/pool/detail/singleton.hpp is not with recent boost_1_49_0. Looking into the similar reported issue QPID-3638, it seems the issue was fixed for boost version 1.48. We probably need the similar fix for boost_1_49_0 pid/log/Logger.cpp:26:43: error: boost/pool/detail/singleton.hpp: No such file or directory qpid/log/Logger.cpp: In static member function 'static qpid::log::Logger qpid::log::Logger::instance()': qpid/log/Logger.cpp:48: error: 'boost::details::pool' has not been declared qpid/log/Logger.cpp:48: error: expected primary-expression before '' token qpid/log/Logger.cpp:48: error: '::instance' has not been declared Please have a look on this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3870) C++ tests based on python don't always have correct PYTHONPATH on Windows
[ https://issues.apache.org/jira/browse/QPID-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13217412#comment-13217412 ] Steve Huston commented on QPID-3870: Oops, sorry, Chuck. I just added test_env.ps1.in at r1294284. The cmake configure builds test_env.ps1 from that. C++ tests based on python don't always have correct PYTHONPATH on Windows - Key: QPID-3870 URL: https://issues.apache.org/jira/browse/QPID-3870 Project: Qpid Issue Type: Bug Components: Python Test Suite Affects Versions: 0.15 Environment: Windows Reporter: Steve Huston Assignee: Steve Huston Fix For: 0.15 When new python support modules are added for tests, sometimes they are in new directories and the Windows scripts don't always pick this up. The scripts set PYTHONPATH in an ad-hoc way and don't use a central place for this setup as the Linux build does (test_env.sh) although the structure is there to generate test_env.ps1 as well. The scripts that require python support should get their setup from test_env.ps1 instead of hand-coding the info. Recently, this affected the python_tests, acl_tests, store_tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3571) A generic Posix poller implementation
[ https://issues.apache.org/jira/browse/QPID-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178083#comment-13178083 ] Steve Huston commented on QPID-3571: What's happening with this effort? It's been a while since the last comment/review - is this ready to check in, Cliff? A generic Posix poller implementation - Key: QPID-3571 URL: https://issues.apache.org/jira/browse/QPID-3571 Project: Qpid Issue Type: Improvement Components: C++ Broker, C++ Client Affects Versions: Future Environment: Platforms that support the posix definition of the poll() call. Reporter: Cliff Jansen Assignee: Cliff Jansen Attachments: QPID-3571-1.patch An implementation of qpid::sys::Poller that is portable to any OS that supports poll() (as defined in the posix specification for sockets and pipes) is useful for future porting work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3571) A generic Posix poller implementation
[ https://issues.apache.org/jira/browse/QPID-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144487#comment-13144487 ] Steve Huston commented on QPID-3571: Looks good in general. There are a number of mentions of epoll which could be changed to reflect the demux mechanism in use. Also, some comments to explain better what's going on would be good. Would also be worth a post on review board - may attract better feedback. A generic Posix poller implementation - Key: QPID-3571 URL: https://issues.apache.org/jira/browse/QPID-3571 Project: Qpid Issue Type: Improvement Components: C++ Broker, C++ Client Affects Versions: Future Environment: Platforms that support the posix definition of the poll() call. Reporter: Cliff Jansen Assignee: Cliff Jansen Attachments: QPID-3571-1.patch An implementation of qpid::sys::Poller that is portable to any OS that supports poll() (as defined in the posix specification for sockets and pipes) is useful for future porting work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
