[jira] [Resolved] (QPID-3353) Windows-specific file is missing from 0.12 beta cpp source kit
[ https://issues.apache.org/jira/browse/QPID-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-3353. --- Resolution: Fixed Assignee: Chuck Rolke > Windows-specific file is missing from 0.12 beta cpp source kit > -- > > Key: QPID-3353 > URL: https://issues.apache.org/jira/browse/QPID-3353 > Project: Qpid > Issue Type: Bug > Components: Packaging >Affects Versions: 0.11 > Environment: Windows >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.12 > > > Changes made in QPID-2905 > http://svn.apache.org/viewvc?rev=1104662&view=rev > add a file that is not packaged in the source kit. > Checkin 1143995 > http://svn.apache.org/viewvc?view=revision&revision=1143995 > adds the file by name to Makefile.am so that it is packaged in the cpp source > kit. -- This message is automatically generated by JIRA. 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
Re: qpid-config slow
> Ken, > > QMFv2 solves this issue, can't we port the tools to QMFv2? > We're already part way there - the tools use the pure python qmf implementation, which supports v2 map data. There may be issues with using the tools against older v1-only brokers - I'd have to think about that. But I'd really want to pinpoint the source of the perf issue first - my theory could be wrong. > Carl. > > > On 07/21/2011 01:47 PM, Ken Giusti wrote: > > Alan's correct - I *believe* (not looking at the code in the > > debugger ATM) that qpid-config is most likely downloading the broker > > schema data on connection, and perhaps parsing that - all under > > python. > > > > So I don't think bringing up the connection is the problem - it's > > more like pulling in all the QMF-related data once we're connected, > > but before we can issue commands. > > > > No doubt that whole approach could use a little performance > > tuning > > > > -K > > > > - Original Message - > >> On 07/20/2011 10:43 AM, Pavel Moravec wrote: > >>> Hi all, > >>> I realised on every qpid version& system I used a poor performance > >>> of qpid-config tool. It usually takes 2 to 3 seconds to execute a > >>> command, e.g.: > >>> > >>> # time qpid-config add queue test > >>> > >>> real 0m2.243s > >>> user 0m0.161s > >>> sys 0m0.027s > >>> # time qpid-config del queue test > >>> > >>> real 0m2.303s > >>> user 0m0.208s > >>> sys 0m0.037s > >>> # > >>> > >>> I wrote a simple C++ program to emulate some parts of qpid-config > >>> tool by connecting to the broker and sending proper QMF > >>> message(s). > >>> The program executes equivalent stuff almost instantly. > >>> > >>> Why is qpid-config so slow? Is there some timeout waiting for > >>> (potentially negative) response? Does it make sense / would not it > >>> be usefull to speed it up? > >>> > >> It's an issue with QMF. Setting up the initial QMF connection is > >> very > >> slow. I'm > >> not sure why. It most definitely would be good to speed it up, it > >> annoys me no end. > >> > >> If you have a large number of operations to do, you can write your > >> own > >> client in > >> python that sets up the QMF connection once, then uses it to do all > >> the work. > >> That's not particularly easy right now, qpid-config is not set up > >> to > >> be reused > >> like that. It would be nice to have a little python API that > >> mirrors > >> the command > >> line arguments to qpid-config. It would be even nicer to fix the > >> real > >> problem by > >> getting the QMF init time down to something reasonable. > >> > >> - > >> Apache Qpid - AMQP Messaging Implementation > >> Project: http://qpid.apache.org > >> Use/Interact: mailto:users-subscr...@qpid.apache.org > > - > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:users-subscr...@qpid.apache.org > > > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: qpid-config slow
Ken, QMFv2 solves this issue, can't we port the tools to QMFv2? Carl. On 07/21/2011 01:47 PM, Ken Giusti wrote: > Alan's correct - I *believe* (not looking at the code in the debugger ATM) > that qpid-config is most likely downloading the broker schema data on > connection, and perhaps parsing that - all under python. > > So I don't think bringing up the connection is the problem - it's more like > pulling in all the QMF-related data once we're connected, but before we can > issue commands. > > No doubt that whole approach could use a little performance tuning > > -K > > - Original Message - >> On 07/20/2011 10:43 AM, Pavel Moravec wrote: >>> Hi all, >>> I realised on every qpid version& system I used a poor performance >>> of qpid-config tool. It usually takes 2 to 3 seconds to execute a >>> command, e.g.: >>> >>> # time qpid-config add queue test >>> >>> real 0m2.243s >>> user 0m0.161s >>> sys 0m0.027s >>> # time qpid-config del queue test >>> >>> real 0m2.303s >>> user 0m0.208s >>> sys 0m0.037s >>> # >>> >>> I wrote a simple C++ program to emulate some parts of qpid-config >>> tool by connecting to the broker and sending proper QMF message(s). >>> The program executes equivalent stuff almost instantly. >>> >>> Why is qpid-config so slow? Is there some timeout waiting for >>> (potentially negative) response? Does it make sense / would not it >>> be usefull to speed it up? >>> >> It's an issue with QMF. Setting up the initial QMF connection is very >> slow. I'm >> not sure why. It most definitely would be good to speed it up, it >> annoys me no end. >> >> If you have a large number of operations to do, you can write your own >> client in >> python that sets up the QMF connection once, then uses it to do all >> the work. >> That's not particularly easy right now, qpid-config is not set up to >> be reused >> like that. It would be nice to have a little python API that mirrors >> the command >> line arguments to qpid-config. It would be even nicer to fix the real >> problem by >> getting the QMF init time down to something reasonable. >> >> - >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:users-subscr...@qpid.apache.org > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscr...@qpid.apache.org > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
0.12 release update - RC2 is ready
Hi, folks. I'm encouraged by the RC1 feedback that we've seen so far. Big thanks is due to our responsive testers: Chuck, Cliff, Gordon, Keith, Robbie, and Steve. RC2 contains just two changes versus RC1: - A fix for a threading problem in windows, QPID-3256 (Cliff and Steve) - Corrected README text and ivy.xml version (Robbie and Gordon) Unless a new blocker issue is discovered, I anticipate that RC3, due next week, will be the final RC and therefore the bits we ship as Qpid 0.12. Thanks, Justin --- Release page: https://cwiki.apache.org/qpid/012-release.html - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-1834) Misconfiguration of config path for Debian libsasl2-2 (SASL support)
[ https://issues.apache.org/jira/browse/QPID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069136#comment-13069136 ] Sam Hendley commented on QPID-1834: --- I just tried this on ubunutu and it doesn't seem to have any affect. I see the log message in the qpidd logs: info SASL: config path set to /etc/sasl2/qpidd.conf But when I try connecting it is still looking at /etc/sasldb2. I verified this by adding different users to /etc/sasldb2 and /var/lib/qpidd/qpidd.sasldb and attempting to log in with both, the ones listed in /etc/sasldb2 worked. I built qpidd using the PPA package on launchpad. This is not a blocker for me, I can just use default sasldb2 location, but the sasl-config option doesn't appear to do the job fully. > Misconfiguration of config path for Debian libsasl2-2 (SASL support) > > > Key: QPID-1834 > URL: https://issues.apache.org/jira/browse/QPID-1834 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: M4 > Environment: Debian "squeeze" >Reporter: Garrett Smith > > The libsasl2-2 package is configured with the option: > --with-configdir=/etc/sasl:/usr/lib/sasl2 > Background on this decision can be found here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211156 > cpp/etc/Makefile.in specifies SASL_CONF as /etc/sasl2, which isn't on the > config path that the Debian package is compiled with. The result is that the > qpid sasl configuration is never used. This is a pain to debug as the missed > configuration is silently ignored. > I'm not sure what the ideal solution is here, but I think this ought to be > addressed given we're talking about Debian. > A config option for qpidd would probably be appropriate, or, in keeping with > the hard coding strategy, create a link from /etc/sasl to /etc/sasl2. Just a > couple ideas though. -- This message is automatically generated by JIRA. 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] [Resolved] (QPID-3338) qpidxarm CMake target is missing in 0-12
[ https://issues.apache.org/jira/browse/QPID-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved QPID-3338. Resolution: Fixed > qpidxarm CMake target is missing in 0-12 > > > Key: QPID-3338 > URL: https://issues.apache.org/jira/browse/QPID-3338 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.12 > Environment: Windows with Microsoft compilers (as opposed to mingw) >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Blocker > Fix For: 0.12 > > Attachments: jira-3338.patch > > > cpp/src/CMakeLists.txt was altered for mingw builds in QPID-2905 (r1104662). > The qpidxarm target builds the XA distributed transaction resource manager > for use with the Microsoft distributed trasanction coordinator. It was > targeted for Windows builds only, using the CMake variable "WIN32". > This variable was changed to "_MSC_VER" for QPID-2905, presumably to indicate > that the build target should only apply to builds using the Microsoft > compiler, and not mingw. Unfortunately "_MSC_VER" is not a recognized CMAKE > variable and the qpidxarm target is never generated. > The CMake documentation indicates the the variable "MSVC" should be used to > indicate The Microsoft compiler compared to mingw. -- This message is automatically generated by JIRA. 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] [Resolved] (QPID-3256) Application which uses Qpid (in my case Excel) hangs on shutdown
[
https://issues.apache.org/jira/browse/QPID-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved QPID-3256.
Resolution: Fixed
Fix Version/s: (was: 0.13)
0.12
Applied to 0.12 branch r1149268
> Application which uses Qpid (in my case Excel) hangs on shutdown
>
>
> Key: QPID-3256
> URL: https://issues.apache.org/jira/browse/QPID-3256
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: 0.8, 0.10
> Environment: OS: Windows.
> Qpid is assembled as DLL.
>Reporter: Eugene
>Assignee: Cliff Jansen
> Fix For: 0.12
>
> Attachments: qpid-3256-3.patch, qpid-3256.patch
>
>
> Hi All
> I encountered with strange behavior on shutdown when using qpid 0-8 and 0-10.
> When I use qpid in standalone console-application everything is ok. But when
> I use qpid in DLL which is loaded into Excel (as RTD module), Excel hangs on
> shutdown.
> I found out that in standalone application on shutdown I have next stack:
> qpidclientd.dll!qpid::client::`anonymous
> namespace'::IOThread::~IOThread() Line 138C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x6008, unsigned long
> dwReason=0, void * lpreserved=0x0001) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77b9a516()
> ntdll.dll!77b9a3b8()
> kernel32.dll!77657363()
> msvcr90d.dll!__crtExitProcess(int status=0) Line 732 C
> msvcr90d.dll!doexit(int code=0, int quick=0, int retcaller=0) Line 644
> + 0x9 bytes C
> msvcr90d.dll!exit(int code=0) Line 412 + 0xd bytes C
> Test.exe!__tmainCRTStartup() Line 599 C
> Test.exe!mainCRTStartup() Line 403 C
> kernel32.dll!77653677()
> ntdll.dll!77b79f02()
> ntdll.dll!77b79ed5()
> And in this state all threads of application have been already terminated.
> The only thread is:
> 1 > 21720 Main Thread Main Thread
> qpid::client::`anonymous namespace'::IOThread::~IOThreadNormal 0
> so code from file ConnectionImpl.cpp works well:
> ~IOThread() {
> std::vector threads;
> {
> ScopedLock l(threadLock);
> if (poller_)
> poller_->shutdown();
> t.swap(threads);
> }
> for (std::vector::iterator i = threads.begin(); i !=
> threads.end(); ++i) {
> i->join();
> }
> }
> BUT in Excel I get stack:
> qpidclientd.dll!qpid::client::`anonymous namespace'::IOThread::~IOThread()
> Line 130 C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x0770, unsigned long
> dwReason=0, void * lpreserved=0x) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77ba1525()
> ntdll.dll!77b81231()
> KernelBase.dll!77281da7()
> ole32.dll!75bb9562()
> ole32.dll!75bb9593()
> ole32.dll!75bb95a7()
> ole32.dll!75bb98bf()
> ole32.dll!75bb9805()
> ole32.dll!75bb9a8c()
> EXCEL.EXE!2f3811e9()
> EXCEL.EXE!2f6933e8()
> EXCEL.EXE!2f32a5af()
> EXCEL.EXE!2f34894a()
> EXCEL.EXE!2f670001()
> MSO.DLL!65bc6ed5()
> MSO.DLL!65c26a34()
> MSO.DLL!65c30305()
> MSO.DLL!65bc910c()
> MSO.DLL!65c4f420()
> MSO.DLL!65bbf161()
> comctl32.dll!7233463d()
> user32.dll!762971be()
> user32.dll!76297d31()
> user32.dll!76297dfa()
> EXCEL.EXE!2f324572()
> EXCEL.EXE!2f324534()
> EXCEL.EXE!2f324441(
[jira] [Commented] (QPID-3256) Application which uses Qpid (in my case Excel) hangs on shutdown
[
https://issues.apache.org/jira/browse/QPID-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069054#comment-13069054
]
Cliff Jansen commented on QPID-3256:
Steve, thanks for looking into the nightly scoreboard build.
Justin, I'm fine with this patch included now. I will apply it asap and send
you mail.
> Application which uses Qpid (in my case Excel) hangs on shutdown
>
>
> Key: QPID-3256
> URL: https://issues.apache.org/jira/browse/QPID-3256
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: 0.8, 0.10
> Environment: OS: Windows.
> Qpid is assembled as DLL.
>Reporter: Eugene
>Assignee: Cliff Jansen
> Fix For: 0.13
>
> Attachments: qpid-3256-3.patch, qpid-3256.patch
>
>
> Hi All
> I encountered with strange behavior on shutdown when using qpid 0-8 and 0-10.
> When I use qpid in standalone console-application everything is ok. But when
> I use qpid in DLL which is loaded into Excel (as RTD module), Excel hangs on
> shutdown.
> I found out that in standalone application on shutdown I have next stack:
> qpidclientd.dll!qpid::client::`anonymous
> namespace'::IOThread::~IOThread() Line 138C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x6008, unsigned long
> dwReason=0, void * lpreserved=0x0001) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77b9a516()
> ntdll.dll!77b9a3b8()
> kernel32.dll!77657363()
> msvcr90d.dll!__crtExitProcess(int status=0) Line 732 C
> msvcr90d.dll!doexit(int code=0, int quick=0, int retcaller=0) Line 644
> + 0x9 bytes C
> msvcr90d.dll!exit(int code=0) Line 412 + 0xd bytes C
> Test.exe!__tmainCRTStartup() Line 599 C
> Test.exe!mainCRTStartup() Line 403 C
> kernel32.dll!77653677()
> ntdll.dll!77b79f02()
> ntdll.dll!77b79ed5()
> And in this state all threads of application have been already terminated.
> The only thread is:
> 1 > 21720 Main Thread Main Thread
> qpid::client::`anonymous namespace'::IOThread::~IOThreadNormal 0
> so code from file ConnectionImpl.cpp works well:
> ~IOThread() {
> std::vector threads;
> {
> ScopedLock l(threadLock);
> if (poller_)
> poller_->shutdown();
> t.swap(threads);
> }
> for (std::vector::iterator i = threads.begin(); i !=
> threads.end(); ++i) {
> i->join();
> }
> }
> BUT in Excel I get stack:
> qpidclientd.dll!qpid::client::`anonymous namespace'::IOThread::~IOThread()
> Line 130 C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x0770, unsigned long
> dwReason=0, void * lpreserved=0x) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77ba1525()
> ntdll.dll!77b81231()
> KernelBase.dll!77281da7()
> ole32.dll!75bb9562()
> ole32.dll!75bb9593()
> ole32.dll!75bb95a7()
> ole32.dll!75bb98bf()
> ole32.dll!75bb9805()
> ole32.dll!75bb9a8c()
> EXCEL.EXE!2f3811e9()
> EXCEL.EXE!2f6933e8()
> EXCEL.EXE!2f32a5af()
> EXCEL.EXE!2f34894a()
> EXCEL.EXE!2f670001()
> MSO.DLL!65bc6ed5()
> MSO.DLL!65c26a34()
> MSO.DLL!65c30305()
> MSO.DLL!65bc910c()
> MSO.DLL!65c4f420()
> MSO.DLL!65bbf161()
> comctl32.dll!7233463d()
> user32.dll!762971be()
> user32.dll!76297d31()
> user32.dll!76297dfa()
>
Re: federation_topic_test
IMHO: Instead of bringing it up to date, it probably would make more sense to add the test case to the rest of the tests in federation.py - if it isn't there already - then delete it. -K - Original Message - > $subject exists in the cpp/src/tests directory and is (used to be) a > test for federation. However it seems not to be used anymore and > indeed > won't even work currently without some (fairly trivial) work to make > it > fit into the current build environment. > > Should it be deleted? Or does someone plan to resurrect it? I have to > say that it has actually been useful to me as a simple example of > setting up and using federation, but that isn't really a good enough > reason to keep it IMO. > > Andrew > > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3256) Application which uses Qpid (in my case Excel) hangs on shutdown
[
https://issues.apache.org/jira/browse/QPID-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069008#comment-13069008
]
Justin Ross commented on QPID-3256:
---
Cliff, I'd like to produce RC2 today, and if we want to go ahead with this
patch, I'd like to get it in RC2 (RC3 would be too late). How does that strike
you?
> Application which uses Qpid (in my case Excel) hangs on shutdown
>
>
> Key: QPID-3256
> URL: https://issues.apache.org/jira/browse/QPID-3256
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: 0.8, 0.10
> Environment: OS: Windows.
> Qpid is assembled as DLL.
>Reporter: Eugene
>Assignee: Cliff Jansen
> Fix For: 0.13
>
> Attachments: qpid-3256-3.patch, qpid-3256.patch
>
>
> Hi All
> I encountered with strange behavior on shutdown when using qpid 0-8 and 0-10.
> When I use qpid in standalone console-application everything is ok. But when
> I use qpid in DLL which is loaded into Excel (as RTD module), Excel hangs on
> shutdown.
> I found out that in standalone application on shutdown I have next stack:
> qpidclientd.dll!qpid::client::`anonymous
> namespace'::IOThread::~IOThread() Line 138C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x6008, unsigned long
> dwReason=0, void * lpreserved=0x0001) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77b9a516()
> ntdll.dll!77b9a3b8()
> kernel32.dll!77657363()
> msvcr90d.dll!__crtExitProcess(int status=0) Line 732 C
> msvcr90d.dll!doexit(int code=0, int quick=0, int retcaller=0) Line 644
> + 0x9 bytes C
> msvcr90d.dll!exit(int code=0) Line 412 + 0xd bytes C
> Test.exe!__tmainCRTStartup() Line 599 C
> Test.exe!mainCRTStartup() Line 403 C
> kernel32.dll!77653677()
> ntdll.dll!77b79f02()
> ntdll.dll!77b79ed5()
> And in this state all threads of application have been already terminated.
> The only thread is:
> 1 > 21720 Main Thread Main Thread
> qpid::client::`anonymous namespace'::IOThread::~IOThreadNormal 0
> so code from file ConnectionImpl.cpp works well:
> ~IOThread() {
> std::vector threads;
> {
> ScopedLock l(threadLock);
> if (poller_)
> poller_->shutdown();
> t.swap(threads);
> }
> for (std::vector::iterator i = threads.begin(); i !=
> threads.end(); ++i) {
> i->join();
> }
> }
> BUT in Excel I get stack:
> qpidclientd.dll!qpid::client::`anonymous namespace'::IOThread::~IOThread()
> Line 130 C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x0770, unsigned long
> dwReason=0, void * lpreserved=0x) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77ba1525()
> ntdll.dll!77b81231()
> KernelBase.dll!77281da7()
> ole32.dll!75bb9562()
> ole32.dll!75bb9593()
> ole32.dll!75bb95a7()
> ole32.dll!75bb98bf()
> ole32.dll!75bb9805()
> ole32.dll!75bb9a8c()
> EXCEL.EXE!2f3811e9()
> EXCEL.EXE!2f6933e8()
> EXCEL.EXE!2f32a5af()
> EXCEL.EXE!2f34894a()
> EXCEL.EXE!2f670001()
> MSO.DLL!65bc6ed5()
> MSO.DLL!65c26a34()
> MSO.DLL!65c30305()
> MSO.DLL!65bc910c()
> MSO.DLL!65c4f420()
> MSO.DLL!65bbf161()
> comctl32.dll!7233463d()
> user32.dll!762971be()
> user32.dll!76297d31()
> user32.dll!76297dfa(
federation_topic_test
$subject exists in the cpp/src/tests directory and is (used to be) a test for federation. However it seems not to be used anymore and indeed won't even work currently without some (fairly trivial) work to make it fit into the current build environment. Should it be deleted? Or does someone plan to resurrect it? I have to say that it has actually been useful to me as a simple example of setting up and using federation, but that isn't really a good enough reason to keep it IMO. Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.12 release update - RC1 is out
Excellent, thanks. On Thu, 21 Jul 2011, Robbie Gemmell wrote: I have tested the java client and broker bundles extract and work ok using the Hello example as a smoke test, and also that the Linux x86_64 management console connects ok to the broker. As Gordon previously pointed out, there was a typo in the README indicating how to run the Hello example and so I have updated that, along with the version number in the ivy.xml file. Given that they are single character non-code changes I just went ahead and put them on the release branch too, hopefully thats ok with you? :) Robbie On 14 July 2011 20:11, Justin Ross wrote: Greetings, everyone. Today I produced RC1 from revision 1146605: http://people.apache.org/~jross/qpid-0.12-rc1/ Thanks to everyone who has tested and prodded. RC2 is due this time next week, and the final RC is planned for the end of this month. See all the details at the release page. Justin --- 0.12 release page: https://cwiki.apache.org/confluence/display/qpid/0.12+Release - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3365) Improvements to build system to support client-plugins modules
[ https://issues.apache.org/jira/browse/QPID-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3365. -- Resolution: Fixed Changes look good to me, patch applied. > Improvements to build system to support client-plugins modules > -- > > Key: QPID-3365 > URL: https://issues.apache.org/jira/browse/QPID-3365 > Project: Qpid > Issue Type: Improvement > Components: Ant Build System, Java Client >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.13 > > Attachments: > 0001-QPID-3365-Extend-build-system-to-build-optional-clie.patch > > > The Ant Build system already builds broker side plugins beneath the > broker-plugins. This improvement is to introduce an analogous client-plugins > directory to allow for the building optional client side components. An > example of such components would be optional transport or security mechanisms. > This change does not introduce OSGi onto the client. -- This message is automatically generated by JIRA. 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] [Resolved] (QPID-3367) FileUtils improvements
[ https://issues.apache.org/jira/browse/QPID-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3367. -- Resolution: Fixed Changes look good to me, patch applied. > FileUtils improvements > -- > > Key: QPID-3367 > URL: https://issues.apache.org/jira/browse/QPID-3367 > Project: Qpid > Issue Type: Improvement > Components: Java Common >Reporter: Keith Wall >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.13 > > Attachments: > 0001-QPID-3367-FileUtils-improvements.-openFileOrDefaultR.patch > > > Improvements to the FileUtils.openFileOrDefaultResource to additionally > search the classpath for the filename to open before falling back to the > default. This is helpful to plugin JARs as it allows the JAR file to ship > resources/properties files with the plugin JAR. -- This message is automatically generated by JIRA. 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] [Issue Comment Edited] (QPID-3365) Improvements to build system to support client-plugins modules
[ https://issues.apache.org/jira/browse/QPID-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068946#comment-13068946 ] Keith Wall edited comment on QPID-3365 at 7/21/11 12:12 PM: Hi Robbie Can you review please? This patch extends the build system to support an optional 'client-plugins'. If the directory is present, any modules found within will be built in the normal way. This patch brings a dependency on Ant 1.7.1 (use erroronmissingdir on DirSet), but as Ant 1.7.1 has been out for more than three years, I doubt this will cause anyone a serious problem. was (Author: k-wall): Hi Robbie Can you review please? This patch extends the build system to support an optional 'client-plugins'. If the directory is present, an modules found within will be compiled in the normal way. This patch brings a dependency on Ant 1.7.1 (use erroronmissingdir on DirSet), but as Ant 1.7.1 has been out for more than three years, I doubt this will cause anyone a serious problem. > Improvements to build system to support client-plugins modules > -- > > Key: QPID-3365 > URL: https://issues.apache.org/jira/browse/QPID-3365 > Project: Qpid > Issue Type: Improvement > Components: Ant Build System, Java Client >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > Attachments: > 0001-QPID-3365-Extend-build-system-to-build-optional-clie.patch > > > The Ant Build system already builds broker side plugins beneath the > broker-plugins. This improvement is to introduce an analogous client-plugins > directory to allow for the building optional client side components. An > example of such components would be optional transport or security mechanisms. > This change does not introduce OSGi onto the client. -- This message is automatically generated by JIRA. 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] [Assigned] (QPID-3365) Improvements to build system to support client-plugins modules
[ https://issues.apache.org/jira/browse/QPID-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3365: Assignee: Robbie Gemmell (was: Keith Wall) > Improvements to build system to support client-plugins modules > -- > > Key: QPID-3365 > URL: https://issues.apache.org/jira/browse/QPID-3365 > Project: Qpid > Issue Type: Improvement > Components: Ant Build System, Java Client >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.13 > > Attachments: > 0001-QPID-3365-Extend-build-system-to-build-optional-clie.patch > > > The Ant Build system already builds broker side plugins beneath the > broker-plugins. This improvement is to introduce an analogous client-plugins > directory to allow for the building optional client side components. An > example of such components would be optional transport or security mechanisms. > This change does not introduce OSGi onto the client. -- This message is automatically generated by JIRA. 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] [Updated] (QPID-3365) Improvements to build system to support client-plugins modules
[ https://issues.apache.org/jira/browse/QPID-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3365: - Attachment: 0001-QPID-3365-Extend-build-system-to-build-optional-clie.patch Hi Robbie Can you review please? This patch extends the build system to support an optional 'client-plugins'. If the directory is present, an modules found within will be compiled in the normal way. This patch brings a dependency on Ant 1.7.1 (use erroronmissingdir on DirSet), but as Ant 1.7.1 has been out for more than three years, I doubt this will cause anyone a serious problem. > Improvements to build system to support client-plugins modules > -- > > Key: QPID-3365 > URL: https://issues.apache.org/jira/browse/QPID-3365 > Project: Qpid > Issue Type: Improvement > Components: Ant Build System, Java Client >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > Attachments: > 0001-QPID-3365-Extend-build-system-to-build-optional-clie.patch > > > The Ant Build system already builds broker side plugins beneath the > broker-plugins. This improvement is to introduce an analogous client-plugins > directory to allow for the building optional client side components. An > example of such components would be optional transport or security mechanisms. > This change does not introduce OSGi onto the client. -- This message is automatically generated by JIRA. 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] [Resolved] (QPID-3255) JMX Console to be changed to remove use of deprecated UserManagement methods
[ https://issues.apache.org/jira/browse/QPID-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-3255. -- Resolution: Fixed Hi Robbie, No comments from the review. > JMX Console to be changed to remove use of deprecated UserManagement methods > > > Key: QPID-3255 > URL: https://issues.apache.org/jira/browse/QPID-3255 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Affects Versions: 0.11, 0.12 >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > > QPID-2759 deprecated some JMX UserManagement operations whilst removing > support for the old jmxremote.access file. > This task is to change the Java Management Console to cease using those > deprecated methods and remove the on-screen widgets pertaining to access > management. -- This message is automatically generated by JIRA. 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-3256) Application which uses Qpid (in my case Excel) hangs on shutdown
[
https://issues.apache.org/jira/browse/QPID-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068915#comment-13068915
]
Steve Huston commented on QPID-3256:
The nightly scoreboard build on Windows was hanging up because of an svn
conflict. That's resolved and now things appear to be good wrt this change.
> Application which uses Qpid (in my case Excel) hangs on shutdown
>
>
> Key: QPID-3256
> URL: https://issues.apache.org/jira/browse/QPID-3256
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: 0.8, 0.10
> Environment: OS: Windows.
> Qpid is assembled as DLL.
>Reporter: Eugene
>Assignee: Cliff Jansen
> Fix For: 0.13
>
> Attachments: qpid-3256-3.patch, qpid-3256.patch
>
>
> Hi All
> I encountered with strange behavior on shutdown when using qpid 0-8 and 0-10.
> When I use qpid in standalone console-application everything is ok. But when
> I use qpid in DLL which is loaded into Excel (as RTD module), Excel hangs on
> shutdown.
> I found out that in standalone application on shutdown I have next stack:
> qpidclientd.dll!qpid::client::`anonymous
> namespace'::IOThread::~IOThread() Line 138C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x6008, unsigned long
> dwReason=0, void * lpreserved=0x0001) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x6008,
> unsigned long dwReason=0, void * lpreserved=0x0001) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77b9a516()
> ntdll.dll!77b9a3b8()
> kernel32.dll!77657363()
> msvcr90d.dll!__crtExitProcess(int status=0) Line 732 C
> msvcr90d.dll!doexit(int code=0, int quick=0, int retcaller=0) Line 644
> + 0x9 bytes C
> msvcr90d.dll!exit(int code=0) Line 412 + 0xd bytes C
> Test.exe!__tmainCRTStartup() Line 599 C
> Test.exe!mainCRTStartup() Line 403 C
> kernel32.dll!77653677()
> ntdll.dll!77b79f02()
> ntdll.dll!77b79ed5()
> And in this state all threads of application have been already terminated.
> The only thread is:
> 1 > 21720 Main Thread Main Thread
> qpid::client::`anonymous namespace'::IOThread::~IOThreadNormal 0
> so code from file ConnectionImpl.cpp works well:
> ~IOThread() {
> std::vector threads;
> {
> ScopedLock l(threadLock);
> if (poller_)
> poller_->shutdown();
> t.swap(threads);
> }
> for (std::vector::iterator i = threads.begin(); i !=
> threads.end(); ++i) {
> i->join();
> }
> }
> BUT in Excel I get stack:
> qpidclientd.dll!qpid::client::`anonymous namespace'::IOThread::~IOThread()
> Line 130 C++
> qpidclientd.dll!`qpid::client::`anonymous
> namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
> C++
> qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x0770, unsigned long
> dwReason=0, void * lpreserved=0x) Line 449 C
> qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 560 + 0x11
> bytesC
> qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x0770,
> unsigned long dwReason=0, void * lpreserved=0x) Line 510 + 0x11
> bytes C
> ntdll.dll!77b79960()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> ntdll.dll]
> ntdll.dll!77ba1525()
> ntdll.dll!77b81231()
> KernelBase.dll!77281da7()
> ole32.dll!75bb9562()
> ole32.dll!75bb9593()
> ole32.dll!75bb95a7()
> ole32.dll!75bb98bf()
> ole32.dll!75bb9805()
> ole32.dll!75bb9a8c()
> EXCEL.EXE!2f3811e9()
> EXCEL.EXE!2f6933e8()
> EXCEL.EXE!2f32a5af()
> EXCEL.EXE!2f34894a()
> EXCEL.EXE!2f670001()
> MSO.DLL!65bc6ed5()
> MSO.DLL!65c26a34()
> MSO.DLL!65c30305()
> MSO.DLL!65bc910c()
> MSO.DLL!65c4f420()
> MSO.DLL!65bbf161()
> comctl32.dll!7233463d()
> user32.dll!762971be()
> user32.dll!76297d31()
> user32.dll!76297dfa()
>
[jira] [Assigned] (QPID-3255) JMX Console to be changed to remove use of deprecated UserManagement methods
[ https://issues.apache.org/jira/browse/QPID-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3255: Assignee: Keith Wall (was: Robbie Gemmell) Hi Keith, could you review these changes please? I have removed the display of the unsupported operations from the console, and moved the old methods out to a legacy interface used only by the console when connected to older brokers. > JMX Console to be changed to remove use of deprecated UserManagement methods > > > Key: QPID-3255 > URL: https://issues.apache.org/jira/browse/QPID-3255 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Affects Versions: 0.11, 0.12 >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > > QPID-2759 deprecated some JMX UserManagement operations whilst removing > support for the old jmxremote.access file. > This task is to change the Java Management Console to cease using those > deprecated methods and remove the on-screen widgets pertaining to access > management. -- This message is automatically generated by JIRA. 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] [Updated] (QPID-3255) JMX Console to be changed to remove use of deprecated UserManagement methods
[ https://issues.apache.org/jira/browse/QPID-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3255: - Status: Ready To Review (was: In Progress) > JMX Console to be changed to remove use of deprecated UserManagement methods > > > Key: QPID-3255 > URL: https://issues.apache.org/jira/browse/QPID-3255 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Affects Versions: 0.11, 0.12 >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.13 > > > QPID-2759 deprecated some JMX UserManagement operations whilst removing > support for the old jmxremote.access file. > This task is to change the Java Management Console to cease using those > deprecated methods and remove the on-screen widgets pertaining to access > management. -- This message is automatically generated by JIRA. 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
Re: 0.12 release update - RC1 is out
I have tested the java client and broker bundles extract and work ok using the Hello example as a smoke test, and also that the Linux x86_64 management console connects ok to the broker. As Gordon previously pointed out, there was a typo in the README indicating how to run the Hello example and so I have updated that, along with the version number in the ivy.xml file. Given that they are single character non-code changes I just went ahead and put them on the release branch too, hopefully thats ok with you? :) Robbie On 14 July 2011 20:11, Justin Ross wrote: > Greetings, everyone. Today I produced RC1 from revision 1146605: > > http://people.apache.org/~jross/qpid-0.12-rc1/ > > Thanks to everyone who has tested and prodded. RC2 is due this time next > week, and the final RC is planned for the end of this month. See all the > details at the release page. > > Justin > > --- > 0.12 release page: > https://cwiki.apache.org/confluence/display/qpid/0.12+Release > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3367) FileUtils improvements
[ https://issues.apache.org/jira/browse/QPID-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3367: Assignee: Robbie Gemmell (was: Keith Wall) > FileUtils improvements > -- > > Key: QPID-3367 > URL: https://issues.apache.org/jira/browse/QPID-3367 > Project: Qpid > Issue Type: Improvement > Components: Java Common >Reporter: Keith Wall >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.13 > > Attachments: > 0001-QPID-3367-FileUtils-improvements.-openFileOrDefaultR.patch > > > Improvements to the FileUtils.openFileOrDefaultResource to additionally > search the classpath for the filename to open before falling back to the > default. This is helpful to plugin JARs as it allows the JAR file to ship > resources/properties files with the plugin JAR. -- This message is automatically generated by JIRA. 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] [Updated] (QPID-3367) FileUtils improvements
[ https://issues.apache.org/jira/browse/QPID-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3367: - Attachment: 0001-QPID-3367-FileUtils-improvements.-openFileOrDefaultR.patch Hi Robbie, Please could you review this patch? cheers Keith. > FileUtils improvements > -- > > Key: QPID-3367 > URL: https://issues.apache.org/jira/browse/QPID-3367 > Project: Qpid > Issue Type: Improvement > Components: Java Common >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Fix For: 0.13 > > Attachments: > 0001-QPID-3367-FileUtils-improvements.-openFileOrDefaultR.patch > > > Improvements to the FileUtils.openFileOrDefaultResource to additionally > search the classpath for the filename to open before falling back to the > default. This is helpful to plugin JARs as it allows the JAR file to ship > resources/properties files with the plugin JAR. -- This message is automatically generated by JIRA. 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
