[jira] Resolved: (AMQ-1140) Compression not working
[
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-1140.
Resolution: Fixed
Fix Version/s: 4.2.0
4.1.1
Added test case and fixed.
> Compression not working
>
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true.
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets
> between brokers, the message bodies are not compressed - they're just plain
> text. This appears to be a bug.
> I'll try to create a test for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1140) Compression not working
[
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38427
]
Hiram Chirino commented on AMQ-1140:
Fix in trunk rev 501506 and fixed in 4.1 branch in rev 501500
> Compression not working
>
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true.
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets
> between brokers, the message bodies are not compressed - they're just plain
> text. This appears to be a bug.
> I'll try to create a test for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1140) Compression not working
[
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-1140:
---
Affects Version/s: (was: 4.1.2)
4.1.0
> Compression not working
>
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true.
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets
> between brokers, the message bodies are not compressed - they're just plain
> text. This appears to be a bug.
> I'll try to create a test for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1123) Deadlocks can occur with even with sync sends since they share a connection.
[ https://issues.apache.org/activemq/browse/AMQ-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino reassigned AMQ-1123: -- Assignee: Hiram Chirino > Deadlocks can occur with even with sync sends since they share a connection. > > > Key: AMQ-1123 > URL: https://issues.apache.org/activemq/browse/AMQ-1123 > Project: ActiveMQ > Issue Type: Bug >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > > If a producer sends to a queue and blocks, any other producer sharing the > same connection even if he would be sending to an empty queue would also > block. This in effect can cause a deadlock if the right message processing > flow is set up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1123) Deadlocks can occur with even with sync sends since they share a connection.
Deadlocks can occur with even with sync sends since they share a connection. Key: AMQ-1123 URL: https://issues.apache.org/activemq/browse/AMQ-1123 Project: ActiveMQ Issue Type: Bug Reporter: Hiram Chirino If a producer sends to a queue and blocks, any other producer sharing the same connection even if he would be sending to an empty queue would also block. This in effect can cause a deadlock if the right message processing flow is set up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=comments#action_37602 ] Hiram Chirino commented on AMQ-1078: Fixed in trunk revision 480717 > Messages consumed with the Resource Adapter are intermittently not delivered > > > Key: AMQ-1078 > URL: https://issues.apache.org/activemq/browse/AMQ-1078 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Connector >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.2.0, 4.1.1 > > > The cause is that the ActiveMQSessionExecutor was starting and using it's > dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
Messages consumed with the Resource Adapter are intermittently not delivered Key: AMQ-1078 URL: https://issues.apache.org/activemq/browse/AMQ-1078 Project: ActiveMQ Issue Type: Bug Components: Broker, Connector Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 The cause is that the ActiveMQSessionExecutor was starting and using it's dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.
[ https://issues.apache.org/activemq/browse/AMQ-1042?page=all ] Hiram Chirino resolved AMQ-1042. Resolution: Fixed reverted in trunk rev 477356 and 4.1 branch rev 477357 Made the test case smarter so that the it would not intermittently fail. > The JMSConsumerTest interminitently failed on linux systems. > > > Key: AMQ-1042 > URL: https://issues.apache.org/activemq/browse/AMQ-1042 > Project: ActiveMQ > Issue Type: Bug > Components: CMS (C++ client) >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.2.0, 4.1.0 > > > JMSConsumerTest fails on linux sometimes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.
[ https://issues.apache.org/activemq/browse/AMQ-1042?page=all ] Hiram Chirino reopened AMQ-1042: This patch may need to get backed out. Some performance testing has shown that in high throughput scenarios, we spend 300% of our time doing the yeild() call. :( Back to the drawing board. > The JMSConsumerTest interminitently failed on linux systems. > > > Key: AMQ-1042 > URL: https://issues.apache.org/activemq/browse/AMQ-1042 > Project: ActiveMQ > Issue Type: Bug > Components: CMS (C++ client) >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.0, 4.2.0 > > > JMSConsumerTest fails on linux sometimes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-12) Modified pom.xml for VS .net 2003 compilation
[ https://issues.apache.org/activemq/browse/AMQCPP-12?page=all ] Hiram Chirino updated AMQCPP-12: Fix Version/s: 1.0 > Modified pom.xml for VS .net 2003 compilation > - > > Key: AMQCPP-12 > URL: https://issues.apache.org/activemq/browse/AMQCPP-12 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Environment: VS .net 2003 on XP. Using maven build with win32-msvc. >Reporter: Lalit Nagpal > Assigned To: Timothy Bish > Fix For: 1.0 > > Attachments: pom_vc2003.xml > > > The following tag > true > was moved from the profile release to profile debug > The following switch was added in the for both debug and > release > /GR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-10) Compiling fails under SuSe
[ https://issues.apache.org/activemq/browse/AMQCPP-10?page=all ] Hiram Chirino updated AMQCPP-10: Fix Version/s: 1.0 > Compiling fails under SuSe > -- > > Key: AMQCPP-10 > URL: https://issues.apache.org/activemq/browse/AMQCPP-10 > Project: ActiveMQ C++ Client > Issue Type: Bug > Environment: gcc (GCC) 3.3.3 (SuSE Linux) > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking build system type... x86_64-suse-linux > checking host system type... x86_64-suse-linux > checking for a sed that does not truncate output... /usr/bin/sed > checking for egrep... grep -E > checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld > checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes > checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking whether ln -s works... yes > checking how to recognise dependent libraries... pass_all > checking how to run the C preprocessor... gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking how to run the C++ preprocessor... g++ -E > checking for g77... g77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether g77 accepts -g... yes > checking the maximum length of command line arguments... 32768 > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for objdir... .libs > checking for ar... ar > checking for ranlib... ranlib > checking for strip... strip > checking if gcc static flag works... yes > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc supports -c -o file.o... yes > checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) > supports shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64 > checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU > ld... yes > checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) > supports shared libraries... yes > checking for g++ option to produce PIC... -fPIC > checking if g++ PIC flag -fPIC works... yes > checking if g++ supports -c -o file.o... yes > checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) > supports shared libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > appending configuration tag "F77" to libtool > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for g77 option to produce PIC... -fPIC > checking if g77 PIC flag -fPIC works... yes > checking if g77 supports -c -o file.o... yes > checking whether the g77 linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) > supports shared libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether
[jira] Updated: (AMQCPP-8) Code Drop for Version 0.0.2 of the activemq-cpp library
[ https://issues.apache.org/activemq/browse/AMQCPP-8?page=all ] Hiram Chirino updated AMQCPP-8: --- Fix Version/s: 1.0 > Code Drop for Version 0.0.2 of the activemq-cpp library > --- > > Key: AMQCPP-8 > URL: https://issues.apache.org/activemq/browse/AMQCPP-8 > Project: ActiveMQ C++ Client > Issue Type: Improvement >Reporter: Timothy Bish > Assigned To: Nathan Mittler > Fix For: 1.0 > > Attachments: activemq-cpp-0-0-2-071906.zip > > > This issues addresses the code drop for Revision 0.0.2 of the ActiveMQ CPP > library. Changes are listed below. > New Features: > * Destinations now support the Destination Options shown here: > http://www.activemq.org/site/destination-options.html > Additional Changes > * Extensive code cleanup, including expanded Java DOC comments and more > consistant formatting. > * Memory leak checking with Rational Purify were done and several small > leaks were fixed. > * Added additional Unit tests for new functionality, and additional tests > for existing feature correctness > * Minor bug fixes > Known Issues > * Unchanged from version 0.0.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-13) Patch to make activemq-cpp compile under sun studio 11
[ https://issues.apache.org/activemq/browse/AMQCPP-13?page=all ] Hiram Chirino updated AMQCPP-13: Fix Version/s: 1.0 > Patch to make activemq-cpp compile under sun studio 11 > -- > > Key: AMQCPP-13 > URL: https://issues.apache.org/activemq/browse/AMQCPP-13 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Environment: Sun Solaris 10 (SunOS chi-dev-chris1 5.10 > Generic_118855-15 i86pc i386 i86pc Solaris) > Studio 11 (Sun C++ 5.8 Patch 121018-04 2006/08/02) >Reporter: Chris Knight > Assigned To: Timothy Bish >Priority: Minor > Fix For: 1.0 > > Attachments: makefile-solaris-debug.cfg, makefile-solaris-debug.cfg, > makefile-solaris-release.cfg, makefile-solaris-release.cfg, > makefile.cfg.PATCH, PATCH, PATCH > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Fixes compilation of activemq-cpp for studio 11 C++ compiler. Mostly > additions of #include and added namespace qualifiers std:: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-3) Receiving a BytesMessage sent from Java using CMS listener causes exception thrown in class BufferedInputStream
[ https://issues.apache.org/activemq/browse/AMQCPP-3?page=all ]
Hiram Chirino updated AMQCPP-3:
---
Fix Version/s: 1.0
> Receiving a BytesMessage sent from Java using CMS listener causes exception
> thrown in class BufferedInputStream
>
>
> Key: AMQCPP-3
> URL: https://issues.apache.org/activemq/browse/AMQCPP-3
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Environment: Ubuntu Linux 6.06 LTS, ActiveMQ 4.0.2, CMS version 0.0.2
> with STOMP
>Reporter: Mark Silberbauer
> Fix For: 1.0
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 1) Setup a MessageListener to listen for messages on Topic X using CMS.
> 2) Send a BytesMessage from ActiveMQ java JMS interface to Topic X
> 3) An exception is thrown from BufferedInputStream::bufferData() with
> description "failed reading bytes from stream""
> int bytesRead = stream->read( buffer+tail, bufferSize-tail );
> if( bytesRead == 0 ){
> throw IOException( __FILE__, __LINE__,
> "BufferedInputStream::read() - failed reading bytes from stream");
> }
> 4) The operation of the CMS interface is broken thereafter.
> Note:
> This only occurs when sending a BytesMessage from Java to C++
> Sending a BytesMessage from C++ to Java or C++ to C++ works perfectly.
> Sending messages of Type TextMessage also works perfectly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-5) Make Session.h more polymorphic like JMS 1.1 with createProducer/createConsumer methods on Session.h
[ https://issues.apache.org/activemq/browse/AMQCPP-5?page=all ] Hiram Chirino updated AMQCPP-5: --- Fix Version/s: 1.0 > Make Session.h more polymorphic like JMS 1.1 with > createProducer/createConsumer methods on Session.h > > > Key: AMQCPP-5 > URL: https://issues.apache.org/activemq/browse/AMQCPP-5 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Components: CMS Impl >Reporter: james strachan > Assigned To: Nathan Mittler > Fix For: 1.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-7) ActiveMQ Cpp Windows Makefiles fail to link the test, and test-integration targets
[ https://issues.apache.org/activemq/browse/AMQCPP-7?page=all ] Hiram Chirino updated AMQCPP-7: --- Fix Version/s: 1.0 > ActiveMQ Cpp Windows Makefiles fail to link the test, and test-integration > targets > -- > > Key: AMQCPP-7 > URL: https://issues.apache.org/activemq/browse/AMQCPP-7 > Project: ActiveMQ C++ Client > Issue Type: Bug > Environment: Windows Mingw GNU builds >Reporter: Timothy Bish > Assigned To: Nathan Mittler >Priority: Minor > Fix For: 1.0 > > Attachments: patch-makefile-windows-debug.txt, > patch-makefile-windows-release.txt > > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > The windows makefiles for the MinGW targets fail to link the test and > test-integration targets. > When the code was submitted the makefiles were changed to build the library > with the libactivemq-cpp.a name, but the windows makefiles still try and link > the tests against libactivemq.a -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-2) Release build of ActiveMQ-CPP from trunk with Visual Studio 2005 fails due to Windows headers include order issue
[ https://issues.apache.org/activemq/browse/AMQCPP-2?page=all ]
Hiram Chirino updated AMQCPP-2:
---
Fix Version/s: 1.0
> Release build of ActiveMQ-CPP from trunk with Visual Studio 2005 fails due to
> Windows headers include order issue
> -
>
> Key: AMQCPP-2
> URL: https://issues.apache.org/activemq/browse/AMQCPP-2
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Environment: Windows
>Reporter: Albert Strasheim
> Assigned To: Timothy Bish
> Fix For: 1.0
>
>
> Doing a release build of ActiveMQ-CPP from trunk with Visual Studio 2005
> results in the following error when compiling DataInputStreamTest.cpp:
> {quote}
> 1>-- Build started: Project: vc2005-activemq-unittests, Configuration:
> Release Win32 --
> 1>Compiling...
> 1>DataInputStreamTest.cpp
> 1>f:\activemq-cpp\src\main\activemq/io/ByteArrayInputStream.h(142) : warning
> C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(112) : error
> C2011: 'fd_set' : 'struct' type redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(54) : see
> declaration of 'fd_set'
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(147) : warning
> C4005: 'FD_SET' : macro redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(88) : see
> previous definition of 'FD_SET'
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(156) : error
> C2011: 'timeval' : 'struct' type redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(97) : see
> declaration of 'timeval'
> ...
> {quote}
> This error happens when some combination of winsock.h, winsock2.h and
> windows.h is included in the wrong order. The following change fixes the
> problem and might provide some clue as to what is going on.
> {quote}
> Index: DataInputStreamTest.h
> ===
> --- DataInputStreamTest.h (revision 470321)
> +++ DataInputStreamTest.h (working copy)
> @@ -21,10 +21,10 @@
> #include
> #include
> +#include
> #include
> #include
> #include
> -#include
> #include
> #ifdef min
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-1) host_os env variable is empty in configure.ac
[ https://issues.apache.org/activemq/browse/AMQCPP-1?page=all ] Hiram Chirino updated AMQCPP-1: --- Fix Version/s: 1.0 > host_os env variable is empty in configure.ac > - > > Key: AMQCPP-1 > URL: https://issues.apache.org/activemq/browse/AMQCPP-1 > Project: ActiveMQ C++ Client > Issue Type: Bug > Environment: building on linux, solaris, and cygwin >Reporter: Nathan Mittler >Priority: Minor > Fix For: 1.0 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The host_os environment variable is undefined when executing the configure.ac > file. As a result, the switch on os_host doesn't execute properly. This > seems to be fixed (at least on linux) by adding AC_CANONICAL_HOST at the top > of the file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-11) Update to activemq-cpp source to enable documentation generation
[ https://issues.apache.org/activemq/browse/AMQCPP-11?page=all ] Hiram Chirino updated AMQCPP-11: Fix Version/s: 1.0 > Update to activemq-cpp source to enable documentation generation > > > Key: AMQCPP-11 > URL: https://issues.apache.org/activemq/browse/AMQCPP-11 > Project: ActiveMQ C++ Client > Issue Type: Improvement >Reporter: Timothy Bish > Assigned To: Nathan Mittler >Priority: Minor > Fix For: 1.0 > > Attachments: activemq-cpp-0-0-2-DOCUpdates.zip > > > This patch contains updated source files for the activemq-cpp project which > expand the code documentation and clean up documentation that caused warnings > when running the doxygen tool to document the code. A set of generated > documentation files is included in the new docs folder. > This patch adds no new functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-9) The Activemq-cpp example code no longer builds.
[ https://issues.apache.org/activemq/browse/AMQCPP-9?page=all ] Hiram Chirino updated AMQCPP-9: --- Fix Version/s: 1.0 > The Activemq-cpp example code no longer builds. > --- > > Key: AMQCPP-9 > URL: https://issues.apache.org/activemq/browse/AMQCPP-9 > Project: ActiveMQ C++ Client > Issue Type: Bug >Reporter: Timothy Bish > Assigned To: Nathan Mittler >Priority: Minor > Fix For: 1.0 > > Attachments: example-patch-081306.txt > > > Code in the Activemq-cpp example is no longer up to date with the latest > version. We need to clean this code up to match the samll changes in the CMS > interface. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-4) Compilation warning under windows for activemq-cpp
[ https://issues.apache.org/activemq/browse/AMQCPP-4?page=all ] Hiram Chirino updated AMQCPP-4: --- Fix Version/s: 1.0 > Compilation warning under windows for activemq-cpp > -- > > Key: AMQCPP-4 > URL: https://issues.apache.org/activemq/browse/AMQCPP-4 > Project: ActiveMQ C++ Client > Issue Type: Bug > Environment: windows >Reporter: Nathan Mittler > Assigned To: Nathan Mittler >Priority: Trivial > Fix For: 1.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Under Windows, the following warning gets printed out: > c:\ActiveMQ\activemq\connector\stomp\commands\AckCommand.h(102) : warning > C4390: ';' : empty controlled statement found; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-6) add createDurableSubscriber() methods to Session.h
[ https://issues.apache.org/activemq/browse/AMQCPP-6?page=all ] Hiram Chirino updated AMQCPP-6: --- Fix Version/s: 1.0 > add createDurableSubscriber() methods to Session.h > -- > > Key: AMQCPP-6 > URL: https://issues.apache.org/activemq/browse/AMQCPP-6 > Project: ActiveMQ C++ Client > Issue Type: Improvement > Components: CMS Impl >Reporter: james strachan > Assigned To: Timothy Bish > Fix For: 1.0 > > > e.g. > http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Session.html#createDurableSubscriber(javax.jms.Topic,%20java.lang.String) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1057) consumer queue is empty when running requester
[ https://issues.apache.org/activemq/browse/AMQ-1057?page=comments#action_37480 ] Hiram Chirino commented on AMQ-1057: Also applied to 4.1 branch revision: 476144 > consumer queue is empty when running requester > -- > > Key: AMQ-1057 > URL: https://issues.apache.org/activemq/browse/AMQ-1057 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.1.0 >Reporter: Marlon Santos > Assigned To: Jonas Lim >Priority: Minor > Fix For: 4.2.0 > > Attachments: ConsumerTool.patch, RequesterTool.java, > RequesterTool.patch > > Original Estimate: 1 day > Remaining Estimate: 1 day > > consumer queue is empty when running requester, producer and consumer. > The reply destination also results into an empty string. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1056) Expire messages at the Broker
[ https://issues.apache.org/activemq/browse/AMQ-1056?page=all ] Hiram Chirino resolved AMQ-1056. Resolution: Fixed Implemented in trunk revision 475848 If a message takes a while to transmit to the broker either because : * sender connection is slow * producer was blocked because queue was full * tansaction took a a while to commit then messages are now check to see if they expired before enqueueing to subscriptions. We also now check to see if a message has expired when taking it off the subscribers pending message list right before it gets dispatched to the consumer. This should help reduce load the amount of expired messages that are delivered to the consumer. > Expire messages at the Broker > - > > Key: AMQ-1056 > URL: https://issues.apache.org/activemq/browse/AMQ-1056 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1056) Expire messages at the Broker
Expire messages at the Broker - Key: AMQ-1056 URL: https://issues.apache.org/activemq/browse/AMQ-1056 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
[ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ] Hiram Chirino updated AMQ-1045: --- Description: The DefaultMessageListenerContainer has retry logic built into it. When a connection dies it tried to reconnect by getting a new connection from the ConnectionFactory. Since the PooledConenctionFactory has one Connection it, it keeps on trying to give out the Connection that died. We would like the PooledConnectionFactory to be able to "evict" the dead connection and create a new one. > PooledConnectionFactory does not work with the > org.springframework.jms.listener.DefaultMessageListenerContainer in the > failure case > --- > > Key: AMQ-1045 > URL: https://issues.apache.org/activemq/browse/AMQ-1045 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.2.0, 4.1.1 > > > The DefaultMessageListenerContainer has retry logic built into it. When a > connection dies it tried to reconnect by getting a new connection from the > ConnectionFactory. Since the PooledConenctionFactory has one Connection it, > it keeps on trying to give out the Connection that died. We would like the > PooledConnectionFactory to be able to "evict" the dead connection and create > a new one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
[ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ] Hiram Chirino resolved AMQ-1045. Resolution: Fixed Fixed in trunk rev 474799 and in 4.1 branch rev 474800 > PooledConnectionFactory does not work with the > org.springframework.jms.listener.DefaultMessageListenerContainer in the > failure case > --- > > Key: AMQ-1045 > URL: https://issues.apache.org/activemq/browse/AMQ-1045 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.1, 4.2.0 > > > The DefaultMessageListenerContainer has retry logic built into it. When a > connection dies it tried to reconnect by getting a new connection from the > ConnectionFactory. Since the PooledConenctionFactory has one Connection it, > it keeps on trying to give out the Connection that died. We would like the > PooledConnectionFactory to be able to "evict" the dead connection and create > a new one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case --- Key: AMQ-1045 URL: https://issues.apache.org/activemq/browse/AMQ-1045 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1044) Failed to register MBean error.
[ https://issues.apache.org/activemq/browse/AMQ-1044?page=all ] Hiram Chirino resolved AMQ-1044. Resolution: Fixed Fixed in trunk rev 474769 and in 4.1 branch rev 474771 > Failed to register MBean error. > --- > > Key: AMQ-1044 > URL: https://issues.apache.org/activemq/browse/AMQ-1044 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.1, 4.2.0 > > > If async error such as a inactivity IO exception is detected while a > subscription is being created, then that subscription is not fully cleaned up > when the connection is disposed. If the client is using failover and > reconnects, then it gets a "Failed to register MBean error." Since the > subscription is still registered in JMX. This is also a source of a memory > leak since subscriptions are are left registered in JMX. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1044) Failed to register MBean error.
Failed to register MBean error. --- Key: AMQ-1044 URL: https://issues.apache.org/activemq/browse/AMQ-1044 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1.1, 4.2.0 If async error such as a inactivity IO exception is detected while a subscription is being created, then that subscription is not fully cleaned up when the connection is disposed. If the client is using failover and reconnects, then it gets a "Failed to register MBean error." Since the subscription is still registered in JMX. This is also a source of a memory leak since subscriptions are are left registered in JMX. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-651) Deadlock in ActiveMQ close processing of Resource Adapter
[ https://issues.apache.org/activemq/browse/AMQ-651?page=all ] Hiram Chirino updated AMQ-651: -- Comment: was deleted > Deadlock in ActiveMQ close processing of Resource Adapter > - > > Key: AMQ-651 > URL: https://issues.apache.org/activemq/browse/AMQ-651 > Project: ActiveMQ > Issue Type: Bug > Components: Connector >Reporter: Hiram Chirino > Fix For: 4.0 > > > Need to check to see if this is still valid against 4.x > See: > http://issues.apache.org/jira/browse/GERONIMO-1493 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.
The JMSConsumerTest interminitently failed on linux systems. Key: AMQ-1042 URL: https://issues.apache.org/activemq/browse/AMQ-1042 Project: ActiveMQ Issue Type: Bug Components: CMS (C++ client) Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.2 JMSConsumerTest fails on linux sometimes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-465) deadlock when using VM transport and Jencks...
[ https://issues.apache.org/activemq/browse/AMQ-465?page=comments#action_37412 ] Hiram Chirino commented on AMQ-465: --- This was fixed in rev 386335. > deadlock when using VM transport and Jencks... > -- > > Key: AMQ-465 > URL: https://issues.apache.org/activemq/browse/AMQ-465 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 M4 >Reporter: james strachan > Assigned To: Hiram Chirino > Fix For: 4.0 RC2 > > > Background here: http://forums.logicblaze.com/posts/list/146.page > It seems to be VM protocol specific -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (AMQ-976) Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects.
[ https://issues.apache.org/activemq/browse/AMQ-976?page=all ] Work on AMQ-976 started by Hiram Chirino. > Abstract the Transport and TransportListener Interfaces so that the move > around Objects instead of Command and Response objects. > > > Key: AMQ-976 > URL: https://issues.apache.org/activemq/browse/AMQ-976 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > If the Transport and TransportListener interfaces can be abstracted even more > so that they move around Objects instead of Commands and Responses. This > would allow us to use most of the Transport components with other command > sets besides the current ActiveMQ one. > The main use case I'm thinking of is the possibility of supporting the qpid > command set directly by the broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-976) Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects.
[ https://issues.apache.org/activemq/browse/AMQ-976?page=all ] Hiram Chirino resolved AMQ-976. --- Resolution: Fixed done. > Abstract the Transport and TransportListener Interfaces so that the move > around Objects instead of Command and Response objects. > > > Key: AMQ-976 > URL: https://issues.apache.org/activemq/browse/AMQ-976 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > If the Transport and TransportListener interfaces can be abstracted even more > so that they move around Objects instead of Commands and Responses. This > would allow us to use most of the Transport components with other command > sets besides the current ActiveMQ one. > The main use case I'm thinking of is the possibility of supporting the qpid > command set directly by the broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.
[ https://issues.apache.org/activemq/browse/AMQ-1026?page=all ] Hiram Chirino resolved AMQ-1026. Resolution: Fixed > Sometimes a failover connection on reconnect produces a Client ID:x-1:1 > already connected error message. > > > Key: AMQ-1026 > URL: https://issues.apache.org/activemq/browse/AMQ-1026 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.
[ https://issues.apache.org/activemq/browse/AMQ-1026?page=comments#action_37362 ] Hiram Chirino commented on AMQ-1026: fixed in trunk rev 471837 > Sometimes a failover connection on reconnect produces a Client ID:x-1:1 > already connected error message. > > > Key: AMQ-1026 > URL: https://issues.apache.org/activemq/browse/AMQ-1026 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.
[ https://issues.apache.org/activemq/browse/AMQ-1026?page=comments#action_37354 ] Hiram Chirino commented on AMQ-1026: timing issues.. if the client reconnect back to the broker before it detects it failure, the broker does not properly clean up the previous connection resources. > Sometimes a failover connection on reconnect produces a Client ID:x-1:1 > already connected error message. > > > Key: AMQ-1026 > URL: https://issues.apache.org/activemq/browse/AMQ-1026 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.
Sometimes a failover connection on reconnect produces a Client ID:x-1:1 already connected error message. Key: AMQ-1026 URL: https://issues.apache.org/activemq/browse/AMQ-1026 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1004) Upgrade to spring 2.0 and xbean 2.7
Upgrade to spring 2.0 and xbean 2.7 --- Key: AMQ-1004 URL: https://issues.apache.org/activemq/browse/AMQ-1004 Project: ActiveMQ Issue Type: Improvement Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1004) Upgrade to spring 2.0 and xbean 2.7
[ https://issues.apache.org/activemq/browse/AMQ-1004?page=all ] Hiram Chirino resolved AMQ-1004. Resolution: Fixed fix in 467783 > Upgrade to spring 2.0 and xbean 2.7 > --- > > Key: AMQ-1004 > URL: https://issues.apache.org/activemq/browse/AMQ-1004 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer
[ https://issues.apache.org/activemq/browse/AMQ-978?page=all ] Hiram Chirino resolved AMQ-978. --- Fix Version/s: 4.1 4.0.2 Resolution: Fixed > No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java > JMS Producer/Consumer > --- > > Key: AMQ-978 > URL: https://issues.apache.org/activemq/browse/AMQ-978 > Project: ActiveMQ > Issue Type: Bug > Components: Connector > Environment: This problem seems platform independent: It happens in > Linux, Mac OSX, and Windows. > Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module > Net-Stomp-0.31 >Reporter: Sileshi Kassa > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > Attachments: Net-Stomp-0.31-bytemessage-support.patch, > Net-Stomp-0.31-bytemessage-support.sileshi-patch, Publisher.pl, Subscriber.pl > > > Facts: Perl Stomp client Producer and Consumer works fine >Java JMS client Producer and Consumer works fine > I have also used other Perl Stomp protocol implementation with no problem. > The problem happens when I mix Java and Perl clients > Scenario Test 1: > A. Perl Stomp client Consumer > B. Java JMS client Producer > Scenario Test 2: > A. Java JMS client Consumer > B. Perl Stomp client Producer > I have looked into it via Java JMX management jconsole, and it seems to me > there is a wall between > the stomp server and default server. It the stomp server only passes messages > coming from stomp lients > and default server also does the same. > If this is truly the case, and this is by design, I will be very > disappointed. There should not be any wall. > A message is message irrespective of its source and should be delivered to > any one that is listening > on the same destination. > I will attach the Perl clients testcases. > For Java client, a simple JMS client Producer and Consumer with the same > topic used as > the perl side will do the job. The topic I used on the perl side: > "/topic/Test.CrossDelivery" > and the Java side topic is "Test.CrossDelivery" > This problem is a show stopper for us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1002) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml
org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml - Key: AMQ-1002 URL: https://issues.apache.org/activemq/browse/AMQ-1002 Project: ActiveMQ Issue Type: Test Reporter: Hiram Chirino Fix For: 4.1 Upgrading to spring 2.0 broker this test. Commenting out till we can fix it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1001) Allow the openwire value cache size to be configurable.
[ https://issues.apache.org/activemq/browse/AMQ-1001?page=all ] Hiram Chirino resolved AMQ-1001. Resolution: Fixed Added in revision 467676 in trunk > Allow the openwire value cache size to be configurable. > --- > > Key: AMQ-1001 > URL: https://issues.apache.org/activemq/browse/AMQ-1001 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > This means that the cache size needs to be a negociated option between the > client and broker. We should also default the cache size to be much smaller > like 1024 since every connection was using too much memory for cached objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1001) Allow the openwire value cache size to be configurable.
Allow the openwire value cache size to be configurable. --- Key: AMQ-1001 URL: https://issues.apache.org/activemq/browse/AMQ-1001 Project: ActiveMQ Issue Type: New Feature Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 This means that the cache size needs to be a negociated option between the client and broker. We should also default the cache size to be much smaller like 1024 since every connection was using too much memory for cached objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-969) .NET Compact Framevork compatibility
[ https://issues.apache.org/activemq/browse/AMQ-969?page=all ] Hiram Chirino resolved AMQ-969. --- Resolution: Fixed Thanks for the patch and the info. Changes commited in revision: 465501. > .NET Compact Framevork compatibility > > > Key: AMQ-969 > URL: https://issues.apache.org/activemq/browse/AMQ-969 > Project: ActiveMQ > Issue Type: Improvement > Components: NMS (C# client) > Environment: .NET Compact Framework 2.0 >Reporter: Oleg Deribas > Attachments: nms-cf20-projects.zip > > > For connecting to ActiveMQ from PDA (PocketPC) NMS should be compiled for > .NET Compact Framework. > And currently there are not projects for .NET CF in vs2005 solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (AMQ-993) test
[ https://issues.apache.org/activemq/browse/AMQ-993?page=all ] Hiram Chirino closed AMQ-993. - Resolution: Won't Fix > test > > > Key: AMQ-993 > URL: https://issues.apache.org/activemq/browse/AMQ-993 > Project: ActiveMQ > Issue Type: Test >Reporter: Hiram Chirino > Attachments: test.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-993) test
[ https://issues.apache.org/activemq/browse/AMQ-993?page=all ] Hiram Chirino updated AMQ-993: -- Attachment: test.txt test attachment. > test > > > Key: AMQ-993 > URL: https://issues.apache.org/activemq/browse/AMQ-993 > Project: ActiveMQ > Issue Type: Test >Reporter: Hiram Chirino > Attachments: test.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-993) test
test Key: AMQ-993 URL: https://issues.apache.org/activemq/browse/AMQ-993 Project: ActiveMQ Issue Type: Test Reporter: Hiram Chirino Attachments: test.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-938) Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable and overriding of the SUNJMX
[ https://issues.apache.org/activemq/browse/AMQ-938?page=all ] Hiram Chirino resolved AMQ-938. --- Fix Version/s: 4.0.2 (was: 4.0.3) Resolution: Fixed in trunk: rev 452108 and 449079 in 4.0 branch rev 452107 and 449077 > Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable > and overriding of the SUNJMX > -- > > Key: AMQ-938 > URL: https://issues.apache.org/activemq/browse/AMQ-938 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > This will allow folks to be able to customized thier run enviorment without > having to modify the activemq start script -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-971) NMSTimestamp returning LocalTime instead of UTC
[ https://issues.apache.org/activemq/browse/AMQ-971?page=all ] Hiram Chirino resolved AMQ-971. --- Resolution: Fixed Fixed in 465441 > NMSTimestamp returning LocalTime instead of UTC > --- > > Key: AMQ-971 > URL: https://issues.apache.org/activemq/browse/AMQ-971 > Project: ActiveMQ > Issue Type: Improvement > Components: NMS (C# client) >Affects Versions: incubation > Environment: Windows >Reporter: Rob Lugt > Assigned To: Hiram Chirino >Priority: Minor > > The NMSTimestamp property has been changed from long to DateTime - which is a > good thing. However, the DateTime is currently being adjusted to localtime > before being returned to the client - which is probably not ideal. The > DateTime struct does not contain timezone information, therefore the > programmer has to make some assumption about what timezone the time is > expressed in. A UTC time is more in-keeping with the JMS specification - > which specifies that Timestamp is a normal Java time i.e. expressed in GMT. > This article from Microsoft also suggests using UTC as a common time where > possible: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/datetimecode.asp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-986) Homepage download page points to wrong directory for 4.x
[ https://issues.apache.org/activemq/browse/AMQ-986?page=all ] Hiram Chirino resolved AMQ-986. --- Resolution: Fixed download page update. Thanks for the tip! Simplified it down and added more detailed section about where our maven repositories are located. > Homepage download page points to wrong directory for 4.x > > > Key: AMQ-986 > URL: https://issues.apache.org/activemq/browse/AMQ-986 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 4.x >Reporter: Bernhard Wellhöfer > > The www.activemq.org web page points for the 4.1 distro under > Download/"Latest Release" to the wrong download directory. > Currently it points to > http://people.apache.org/repository/incubator-activemq/distributions, but > here the oldest distro is from Jul 2006. The ocrrect URL is > http://people.apache.org/maven-snapshot-repository/org/apache/activemq/apache-activemq/4.1-incubator-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] Hiram Chirino resolved AMQ-855. --- Resolution: Fixed Fix for 'sendPullCommand(0)' issue applied to trunk revision 464643 > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.java.patch3, > ActiveMQMessageConsumer.patch, ActiveMQMessageConsumer.patch2, > PrefetchSubscription.java.patch2, PrefetchSubscription.java.patch3, > PrefetchSubscription.patch, region.QueueSubscription.java.patch, > ZeroPrefetchConsumerTest.java.patch, ZeroPrefetchConsumerTest.java.patch3 > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-927) Default log4j.properties has stdout enabled and not the out file appender
[
https://issues.apache.org/activemq/browse/AMQ-927?page=comments#action_37186 ]
Hiram Chirino commented on AMQ-927:
---
I just started up activemq from the command line and noticed this change. I
think that the previous behaviour of logging to the console was a good idea.
That way folks see when the broker is fully started and what transports are
opened and such.
> Default log4j.properties has stdout enabled and not the out file appender
> -
>
> Key: AMQ-927
> URL: https://issues.apache.org/activemq/browse/AMQ-927
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Jason Dillon
> Assigned To: Rob Davies
>Priority: Trivial
> Fix For: 4.1
>
>
> The default log4j.properties has:
> {noformat}
> log4j.rootLogger=INFO, stdout
> {noformat}
> and then goes on to say:
> {noformat}
> # CONSOLE appender not used by default
> log4j.appender.stdout=org.apache.log4j.ConsoleAppender
> ..
> {noformat}
> And it also has this header... which is misleading:
> {noformat}
> #
> # The logging properties used during tests..
> #
> {noformat}
> Also not sure why this would be in data... nor do I ever see this being
> created, even when out is enabled...
> {noformat}
> log4j.appender.out.file=${activemq.home}/data/activemq.log
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-805) Restart network bridges if they ever get stopped
[ https://issues.apache.org/activemq/browse/AMQ-805?page=comments#action_37114 ] Hiram Chirino commented on AMQ-805: --- Hi Tom, do you have a test case? > Restart network bridges if they ever get stopped > > > Key: AMQ-805 > URL: https://issues.apache.org/activemq/browse/AMQ-805 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > > Right now it seems like we only trap remote exceptions and then restart the > bridge. I think we should restart the network bridge if the bridge fails for > any reason. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-813) can get a shutdown hang when using embedded broker with VM transport along with the activemq-web module
[ https://issues.apache.org/activemq/browse/AMQ-813?page=comments#action_37112 ] Hiram Chirino commented on AMQ-813: --- Hi Gary, Please open a new issue since ti seems like a different problem. Also, a small web app test case would help us be able to reproduce the issue. > can get a shutdown hang when using embedded broker with VM transport along > with the activemq-web module > --- > > Key: AMQ-813 > URL: https://issues.apache.org/activemq/browse/AMQ-813 > Project: ActiveMQ > Issue Type: Bug >Reporter: james strachan > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > See attached thread dump. I think we just need to use a timeout on the close > operations (such as to close consumers, sessions, producers) > Full thread dump Java HotSpot(TM) Client VM (1.5.0_04-b05 mixed mode, > sharing): > > "Shutdown" prio=1 tid=0x08385960 nid=0x5e99 in Object.wait() > [0xaed7d000..0xaed7e130] > at java.lang.Object.wait(Native Method) > - waiting on <0x88af01c8> (a > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) > at java.lang.Object.wait(Object.java:474) > at > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75) > - locked <0x88af01c8> (a > edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) > at > edu.emory.mathcs.backport.java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:318) > at > org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:41) > at > org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:72) > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1130) > at > org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:1660) > at > org.apache.activemq.ActiveMQMessageConsumer.close(ActiveMQMessageConsumer.java:516) > at > org.apache.activemq.web.WebClient.closeConsumers(WebClient.java:135) > - locked <0x893e6558> (a org.apache.activemq.web.WebClient) > at org.apache.activemq.web.WebClient.close(WebClient.java:145) > - locked <0x893e6558> (a org.apache.activemq.web.WebClient) > at org.apache.activemq.web.WebClient.valueUnbound(WebClient.java:318) > at > org.mortbay.jetty.servlet.AbstractSessionManager$Session.unbindValue(AbstractSessionManager.java:899) > at > org.mortbay.jetty.servlet.AbstractSessionManager$Session.invalidate(AbstractSessionManager.java:755) > - locked <0x893caa88> (a > org.mortbay.jetty.servlet.HashSessionManager$Session) > at > org.mortbay.jetty.servlet.AbstractSessionManager.doStop(AbstractSessionManager.java:551) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at > org.mortbay.jetty.servlet.SessionHandler.doStop(SessionHandler.java:124) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at > org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:131) > at > org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:467) > at > org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:477) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at > org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:173) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at > org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:173) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at > org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:131) > at org.mortbay.jetty.Server.doStop(Server.java:242) > at > org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:63) > at org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:450) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-958) Supprot a create=false option on the vm://localhost transport so that the connect fails if the broker is not allready running
[ https://issues.apache.org/activemq/browse/AMQ-958?page=all ] Hiram Chirino resolved AMQ-958. --- Resolution: Fixed Committed in trunk revision: 453380 > Supprot a create=false option on the vm://localhost transport so that the > connect fails if the broker is not allready running > - > > Key: AMQ-958 > URL: https://issues.apache.org/activemq/browse/AMQ-958 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-958) Supprot a create=false option on the vm://localhost transport so that the connect fails if the broker is not allready running
Supprot a create=false option on the vm://localhost transport so that the connect fails if the broker is not allready running - Key: AMQ-958 URL: https://issues.apache.org/activemq/browse/AMQ-958 Project: ActiveMQ Issue Type: New Feature Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=all ] Hiram Chirino updated AMQ-915: -- Fix Version/s: 4.0.2 (was: 4.0.3) > Failover transport does not replay all the transaction operations on failover. > -- > > Key: AMQ-915 > URL: https://issues.apache.org/activemq/browse/AMQ-915 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Adrian Co > Fix For: 4.1, 4.0.2 > > > If transactions are being used on a connection that is using failover.. these > is a small chance that the transaction will fail or the connection will fail > due to a partial tx being run when the client reconnects. > I will change the failover transport to buffer up all the tx operations that > are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-872) Don't monitor activity on vm transports
[ https://issues.apache.org/activemq/browse/AMQ-872?page=all ] Hiram Chirino updated AMQ-872: -- Fix Version/s: 4.0.2 (was: 4.0.3) > Don't monitor activity on vm transports > --- > > Key: AMQ-872 > URL: https://issues.apache.org/activemq/browse/AMQ-872 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Rob Davies > Assigned To: Rob Davies > Fix For: 4.0.2 > > > currently all transport servers montitor transport channels for activity - > closing down blocked transports. This can occassionally result in stranged > side-affects for networks - which use an inbound vm:// channel to the broker > in their communications -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-847) Memory Leaks
[ https://issues.apache.org/activemq/browse/AMQ-847?page=all ] Hiram Chirino updated AMQ-847: -- Fix Version/s: 4.0.2 (was: 4.1) (was: 4.0.3) > Memory Leaks > > > Key: AMQ-847 > URL: https://issues.apache.org/activemq/browse/AMQ-847 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.0.2 > > > 1) factoryStats in the connection factory was holding on to connections even > when they are closed. > 2) peer BrokerInfos were never removed even when the peer disconnected. > 3) messages dispatched from a Queue would retain a referece to the client > connection even after they had been acked. > 4) ScheduledThreadPoolExecutor does not always seem to release references to > canceled tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-776) ConduitBridge can malfunction when first of a set of consumers goes away
[ https://issues.apache.org/activemq/browse/AMQ-776?page=all ] Hiram Chirino reopened AMQ-776: --- This issue looks like it's still not resolved. > ConduitBridge can malfunction when first of a set of consumers goes away > > > Key: AMQ-776 > URL: https://issues.apache.org/activemq/browse/AMQ-776 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.1 >Reporter: Kevin Yaussy > Assigned To: Rob Davies >Priority: Critical > Fix For: 4.0.3 > > Attachments: ConduitBridge.patch, DemandForwardingBridgeSupport.patch > > > When the following scenario is followed, any of the subsequent consumers will > stop receiving messages. I've reproduced this using the ConsumerTool, and > ProducerTool supplied in the example area of the distribution. > +++ > Start Broker A > Start Broker B > Start Consumer 1, connecting to Broker B, consuming FOO > Start Consumer 2, connecting to Broker B, consuming FOO > Start Publisher, connecting to Broker A, publishing FOO > Ctl-C out of Consumer 1 > Consumer 2 stops receiving messages > +++ > Seems to me that ConduitBridge is supposed to track all consumers for a given > subscription, by way of DemandSubscription. It is seeding DemandSubscription > with the originating consumer, but when subsequent consumers are added, the > ConduitBridge::addToAlreadyInterestedConsumers re-adds the original > subscriber to the DemandSubscription's map - so the map only ever has the > original subscription. > I've attached a patch. Hope the change is good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-953) ActiveMQ standalone sever does not start in Windows
[ https://issues.apache.org/activemq/browse/AMQ-953?page=all ]
Hiram Chirino updated AMQ-953:
--
Fix Version/s: 4.0.3
> ActiveMQ standalone sever does not start in Windows
> ---
>
> Key: AMQ-953
> URL: https://issues.apache.org/activemq/browse/AMQ-953
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0.2
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.0.3
>
>
> When you use the activemq.bat file in the bin directory of the 4.0.2
> distribution you get one of the following errors:
> {code}
> C:\incubator-activemq-4.0.2\bin>activemq
> ACTIVEMQ_HOME: .
> Failed to execute main task. Reason: java.lang.ClassNotFoundException:
> org.apache.activemq.console.command.ShellCommand
> {code}
> and
> {code}
> ACTIVEMQ_HOME: .
> Loading message broker from: xbean:activemq.xml
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
> org.springframework.beans.factory.Bea
> nDefinitionStoreException: Error registering bean with name
> 'org.apache.activemq.xbean.XBeanBrokerService' def
> ined in class path resource [activemq.xml]: Could not resolve placeholder
> 'activemq.home'
> ERROR: java.lang.Exception:
> org.springframework.beans.factory.BeanDefinitionStoreException: Error
> registering
> bean with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in
> class path resource [activemq.xml]: C
> ould not resolve placeholder 'activemq.home'
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-953) ActiveMQ standalone sever does not start in Windows
[
https://issues.apache.org/activemq/browse/AMQ-953?page=comments#action_37069 ]
Hiram Chirino commented on AMQ-953:
---
As a simple workaround, users can either:
# Replace thier activemq.bat with this one:
https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.0/assembly/src/release/bin/activemq.bat
# Run this before you execute the existing activemq.bat:
{code}
set ACTIVEMQ_CLASSPATH=""
{code}
> ActiveMQ standalone sever does not start in Windows
> ---
>
> Key: AMQ-953
> URL: https://issues.apache.org/activemq/browse/AMQ-953
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0.2
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
>
> When you use the activemq.bat file in the bin directory of the 4.0.2
> distribution you get one of the following errors:
> {code}
> C:\incubator-activemq-4.0.2\bin>activemq
> ACTIVEMQ_HOME: .
> Failed to execute main task. Reason: java.lang.ClassNotFoundException:
> org.apache.activemq.console.command.ShellCommand
> {code}
> and
> {code}
> ACTIVEMQ_HOME: .
> Loading message broker from: xbean:activemq.xml
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
> org.springframework.beans.factory.Bea
> nDefinitionStoreException: Error registering bean with name
> 'org.apache.activemq.xbean.XBeanBrokerService' def
> ined in class path resource [activemq.xml]: Could not resolve placeholder
> 'activemq.home'
> ERROR: java.lang.Exception:
> org.springframework.beans.factory.BeanDefinitionStoreException: Error
> registering
> bean with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in
> class path resource [activemq.xml]: C
> ould not resolve placeholder 'activemq.home'
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-953) ActiveMQ standalone sever does not start in Windows
[ https://issues.apache.org/activemq/browse/AMQ-953?page=all ]
Hiram Chirino resolved AMQ-953.
---
Resolution: Fixed
Fixed in 4.0 branch Committed revision 452107
Fixed in trunk revision 452108
> ActiveMQ standalone sever does not start in Windows
> ---
>
> Key: AMQ-953
> URL: https://issues.apache.org/activemq/browse/AMQ-953
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0.2
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
>
> When you use the activemq.bat file in the bin directory of the 4.0.2
> distribution you get one of the following errors:
> {code}
> C:\incubator-activemq-4.0.2\bin>activemq
> ACTIVEMQ_HOME: .
> Failed to execute main task. Reason: java.lang.ClassNotFoundException:
> org.apache.activemq.console.command.ShellCommand
> {code}
> and
> {code}
> ACTIVEMQ_HOME: .
> Loading message broker from: xbean:activemq.xml
> ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
> org.springframework.beans.factory.Bea
> nDefinitionStoreException: Error registering bean with name
> 'org.apache.activemq.xbean.XBeanBrokerService' def
> ined in class path resource [activemq.xml]: Could not resolve placeholder
> 'activemq.home'
> ERROR: java.lang.Exception:
> org.springframework.beans.factory.BeanDefinitionStoreException: Error
> registering
> bean with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in
> class path resource [activemq.xml]: C
> ould not resolve placeholder 'activemq.home'
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-953) ActiveMQ standalone sever does not start in Windows
ActiveMQ standalone sever does not start in Windows
---
Key: AMQ-953
URL: https://issues.apache.org/activemq/browse/AMQ-953
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.0.2
Reporter: Hiram Chirino
Assigned To: Hiram Chirino
When you use the activemq.bat file in the bin directory of the 4.0.2
distribution you get one of the following errors:
{code}
C:\incubator-activemq-4.0.2\bin>activemq
ACTIVEMQ_HOME: .
Failed to execute main task. Reason: java.lang.ClassNotFoundException:
org.apache.activemq.console.command.ShellCommand
{code}
and
{code}
ACTIVEMQ_HOME: .
Loading message broker from: xbean:activemq.xml
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
org.springframework.beans.factory.Bea
nDefinitionStoreException: Error registering bean with name
'org.apache.activemq.xbean.XBeanBrokerService' def
ined in class path resource [activemq.xml]: Could not resolve placeholder
'activemq.home'
ERROR: java.lang.Exception:
org.springframework.beans.factory.BeanDefinitionStoreException: Error
registering
bean with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in class
path resource [activemq.xml]: C
ould not resolve placeholder 'activemq.home'
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-938) Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable and overriding of the SUNJMX
Support extending the activemq classpath with the ACTIVEMQ_CLASSPATH variable and overriding of the SUNJMX -- Key: AMQ-938 URL: https://issues.apache.org/activemq/browse/AMQ-938 Project: ActiveMQ Issue Type: New Feature Components: Broker Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.0.2 This will allow folks to be able to customized thier run enviorment without having to modify the activemq start script -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=comments#action_36973 ] Hiram Chirino commented on AMQ-912: --- remaining problem fixed up in 447635 > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport, Test Cases >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Fix For: 4.1 > > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt, > svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=comments#action_36972 ] Hiram Chirino commented on AMQ-912: --- but having them in the jaas modules helps us test the login modules.. so fine. lets leave it there. I can live with requiring a dependency on activemq-jaas even if amq does not use any of the login modules. :) > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport, Test Cases >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Fix For: 4.1 > > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt, > svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=comments#action_36971 ] Hiram Chirino commented on AMQ-912: --- Now that I think about it... I think callback handlers should be in the ActiveMQ space. Handlers are ment to be implemented by the application which in our case is the ActiveMQ broker. The activemq-jaas module should only hold jaas login modules so it should not have handler impls. > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport, Test Cases >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Fix For: 4.1 > > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt, > svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Hiram Chirino resolved AMQ-912. --- Fix Version/s: 4.1 Resolution: Fixed Thanks for the great patch. Just need to fix a few compile issues caused by recent chanages on trunk. commited to trunk in revision 447607 and 447608 > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport, Test Cases >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Fix For: 4.1 > > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt, > svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=comments#action_36968 ] Hiram Chirino commented on AMQ-912: --- Hi Kelly, Yep I got the same results with xbean. The error was not too friendly to figure out what was going wrong so I opened and resolved issue: http://issues.apache.org/jira/browse/XBEAN-53?page=all The reason xbean was barfing is that the patch produced a .java file that was empty. The current version of xbean could not cope with that, but I've applied a fix to it so it should not be a problem with future versions. Looking into the patch now. > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport, Test Cases >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt, > svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (XBEAN-53) "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo
[ http://issues.apache.org/jira/browse/XBEAN-53?page=all ] Hiram Chirino closed XBEAN-53. -- Resolution: Fixed Fixed in trunk revision 447551 > "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo > --- > > Key: XBEAN-53 > URL: http://issues.apache.org/jira/browse/XBEAN-53 > Project: XBean > Issue Type: Bug > Components: spring >Affects Versions: 2.6 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 2.7 > > > I noticed this happened when I was trying to apply a patch to ActiveMQ. The > patch left a .java file empty. And this is why XBean is barfing. We should > protect against such cases and instead issue a warnning message. > Full Error: > java.lang.ArrayIndexOutOfBoundsException: 0 > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadElements(QdoxMappingLoader.java:147) > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:107) > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:101) > at org.apache.xbean.maven.XBeanMojo.execute(XBeanMojo.java:153) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (XBEAN-53) "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo
[ http://issues.apache.org/jira/browse/XBEAN-53?page=comments#action_12435570 ] Hiram Chirino commented on XBEAN-53: Also noticed that xbean will only process the first java class defined in the source file. It should process all java classes since the first one may not be the xbean enabled one. > "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo > --- > > Key: XBEAN-53 > URL: http://issues.apache.org/jira/browse/XBEAN-53 > Project: XBean > Issue Type: Bug > Components: spring >Affects Versions: 2.6 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 2.7 > > > I noticed this happened when I was trying to apply a patch to ActiveMQ. The > patch left a .java file empty. And this is why XBean is barfing. We should > protect against such cases and instead issue a warnning message. > Full Error: > java.lang.ArrayIndexOutOfBoundsException: 0 > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadElements(QdoxMappingLoader.java:147) > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:107) > at > org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:101) > at org.apache.xbean.maven.XBeanMojo.execute(XBeanMojo.java:153) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (XBEAN-53) "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo
"java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo --- Key: XBEAN-53 URL: http://issues.apache.org/jira/browse/XBEAN-53 Project: XBean Issue Type: Bug Components: spring Affects Versions: 2.6 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 2.7 I noticed this happened when I was trying to apply a patch to ActiveMQ. The patch left a .java file empty. And this is why XBean is barfing. We should protect against such cases and instead issue a warnning message. Full Error: java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.xbean.spring.generator.QdoxMappingLoader.loadElements(QdoxMappingLoader.java:147) at org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:107) at org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:101) at org.apache.xbean.maven.XBeanMojo.execute(XBeanMojo.java:153) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=comments#action_36949 ] Hiram Chirino commented on AMQ-915: --- I'm not even sure that this has made it into trunk either. > Failover transport does not replay all the transaction operations on failover. > -- > > Key: AMQ-915 > URL: https://issues.apache.org/activemq/browse/AMQ-915 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > If transactions are being used on a connection that is using failover.. these > is a small chance that the transaction will fail or the connection will fail > due to a partial tx being run when the client reconnects. > I will change the failover transport to buffer up all the tx operations that > are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=all ] Hiram Chirino reopened AMQ-915: --- Assignee: Adrian Co (was: Hiram Chirino) > Failover transport does not replay all the transaction operations on failover. > -- > > Key: AMQ-915 > URL: https://issues.apache.org/activemq/browse/AMQ-915 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Adrian Co > Fix For: 4.1 > > > If transactions are being used on a connection that is using failover.. these > is a small chance that the transaction will fail or the connection will fail > due to a partial tx being run when the client reconnects. > I will change the failover transport to buffer up all the tx operations that > are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
[ https://issues.apache.org/activemq/browse/AMQ-915?page=comments#action_36948 ] Hiram Chirino commented on AMQ-915: --- Adrian what was the svn revision that the fix was comitted on and on what branch? > Failover transport does not replay all the transaction operations on failover. > -- > > Key: AMQ-915 > URL: https://issues.apache.org/activemq/browse/AMQ-915 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > If transactions are being used on a connection that is using failover.. these > is a small chance that the transaction will fail or the connection will fail > due to a partial tx being run when the client reconnects. > I will change the failover transport to buffer up all the tx operations that > are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-918) Inactivity Monitor timeout does not on disconnected client does not cause blocked dispatch to client to fail.
Inactivity Monitor timeout does not on disconnected client does not cause blocked dispatch to client to fail. - Key: AMQ-918 URL: https://issues.apache.org/activemq/browse/AMQ-918 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.0.2 The cause is that inactivity timeout cause an async thread to call TransportConnection.stop() but it in turn tries to do a "transport.oneway(new ShutdownInfo());" before a transport.stop(); Since another thread is currently stuck in the oneway() call (due to the client having disconnected but the OS has not thrown an IOException up to us yet), our ShutdownInfo message blocks too. So in essence the InactivityMonitor is not currently shutitng down the failed connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Hiram Chirino reassigned AMQ-912: - Assignee: Hiram Chirino > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Test Cases, Transport >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (AMQ-912) ActiveMQ support for SSL authentication and authorization
[ https://issues.apache.org/activemq/browse/AMQ-912?page=all ] Work on AMQ-912 started by Hiram Chirino. > ActiveMQ support for SSL authentication and authorization > - > > Key: AMQ-912 > URL: https://issues.apache.org/activemq/browse/AMQ-912 > Project: ActiveMQ > Issue Type: Improvement > Components: Test Cases, Transport >Reporter: Sepand Mavandadi > Assigned To: Hiram Chirino > Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This patch adds new Transports, Brokers, and Plugins needed for > authentication and authorization based on SSL certificates. > It also adds a few unit tests for the mentioned classes. > The new (or heavily modified) SslTransport, SslTransportServer, and > SslTransportFactory classes allow for access to the underlying socket's need > and want client auth settings. If a certificate is found, it is set as the > transportContext of the created connection. > The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule > to authenticate certificates (this class is abstract to allow for different > backends for certificate authentication, a concrete class is > TextFileCertificateLoginModule). > JaasCertificateAuthenticationBroker also sets the security context's user > name to that provided for the certificate by the login module. This allows > for authorization using the existing authorization broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] Hiram Chirino resolved AMQ-855. --- Resolution: Fixed patches applied.. Thanks Vadim! > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.java.patch3, > ActiveMQMessageConsumer.patch, ActiveMQMessageConsumer.patch2, > PrefetchSubscription.java.patch2, PrefetchSubscription.java.patch3, > PrefetchSubscription.patch, region.QueueSubscription.java.patch, > ZeroPrefetchConsumerTest.java.patch, ZeroPrefetchConsumerTest.java.patch3 > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-886) Timing bug could cause duplicate client id exception in network code.
[ https://issues.apache.org/activemq/browse/AMQ-886?page=all ] Hiram Chirino resolved AMQ-886. --- Fix Version/s: 4.0.2 (was: 4.0.3) Resolution: Fixed Applied fix to 4.0 branch rev 441189 > Timing bug could cause duplicate client id exception in network code. > - > > Key: AMQ-886 > URL: https://issues.apache.org/activemq/browse/AMQ-886 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-915) Failover transport does not replay all the transaction operations on failover.
Failover transport does not replay all the transaction operations on failover. -- Key: AMQ-915 URL: https://issues.apache.org/activemq/browse/AMQ-915 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 If transactions are being used on a connection that is using failover.. these is a small chance that the transaction will fail or the connection will fail due to a partial tx being run when the client reconnects. I will change the failover transport to buffer up all the tx operations that are run against the broker and on failure, replay those operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-907) Make the ActiveIO dependency and optional dependency.
[ https://issues.apache.org/activemq/browse/AMQ-907?page=all ] Hiram Chirino resolved AMQ-907. --- Resolution: Fixed done.. > Make the ActiveIO dependency and optional dependency. > - > > Key: AMQ-907 > URL: https://issues.apache.org/activemq/browse/AMQ-907 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > Need to move some core classes that are in activeio to activemq > so that it is not needed to run. Right now the only real > functionality that it provides that is optional is the journal > implementation. > Everything else that is use from activeio are just abstract interfaces, and I > think > those need to be moved/copied to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-888) Licence headers missing from several source files.
[ https://issues.apache.org/activemq/browse/AMQ-888?page=all ]
Hiram Chirino reassigned AMQ-888:
-
Assignee: james strachan (was: Hiram Chirino)
Just a few more unaccounted files remain in the web modules.. assining to
james to see if he can look into these.
> Licence headers missing from several source files.
> --
>
> Key: AMQ-888
> URL: https://issues.apache.org/activemq/browse/AMQ-888
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 4.0
>Reporter: Hiram Chirino
> Assigned To: james strachan
> Fix For: 4.1, 4.0.2
>
> Attachments: findunlicensed.pl
>
>
> robert burrell donkin reported:
> {quote}
> missing license headers from some of the files i checked at random
> gives me concerns. for example:
> maven-bundle-plugin/src/main/java/org/apache/activemq/maven/BundleMojo.java
> activemq-web-demo worries me: there are a lot of files without license
> headers and some which have them were not created at the ASF (which is
> ok but gives me concerns about the rest).
> i would like to see the issue of licenses in the source tidied up
> before this release ships. i haven't gone through every file but IMO
> this needs to be done.
> {quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-887) Allow temp destination message bridging to be disable across demand based bridges.
[ https://issues.apache.org/activemq/browse/AMQ-887?page=all ] Hiram Chirino resolved AMQ-887. --- Resolution: Fixed Fixed in trunk rev 433673 > Allow temp destination message bridging to be disable across demand based > bridges. > -- > > Key: AMQ-887 > URL: https://issues.apache.org/activemq/browse/AMQ-887 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=all ] Hiram Chirino resolved AMQ-855. --- Resolution: Fixed no further feedback.. assuming issue is now resolved. > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.patch, > ActiveMQMessageConsumer.patch2, PrefetchSubscription.patch, > region.QueueSubscription.java.patch, ZeroPrefetchConsumerTest.java.patch > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-911) Transient connection failure with Failover transport can cause InvalidClientIDException
[ https://issues.apache.org/activemq/browse/AMQ-911?page=comments#action_36910 ] Hiram Chirino commented on AMQ-911: --- fixed in 4.0 branch rev 440548 > Transient connection failure with Failover transport can cause > InvalidClientIDException > --- > > Key: AMQ-911 > URL: https://issues.apache.org/activemq/browse/AMQ-911 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > It shows up as errors on the broker log: > Error occured while processing sync command: > javax.jms.InvalidClientIDException: Broker: localhost - Client: > ID:hchirino-mac.local-51624-1157486953862-2:0 already connected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-913) Wireformat negociation needs to negociate to to the minimum version supported by both sides.
[ https://issues.apache.org/activemq/browse/AMQ-913?page=all ] Hiram Chirino resolved AMQ-913. --- Resolution: Fixed Fix applied in 4.0 branch rev 440543 Fix applied in trunk rev 440541 > Wireformat negociation needs to negociate to to the minimum version supported > by both sides. > > > Key: AMQ-913 > URL: https://issues.apache.org/activemq/browse/AMQ-913 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.0.2 > > > Right now it's negociating to the maximum supported by both sides. This > means that old version will try to load a newer version of the wireformat > that it does not support! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-913) Wireformat negociation needs to negociate to to the minimum version supported by both sides.
Wireformat negociation needs to negociate to to the minimum version supported by both sides. Key: AMQ-913 URL: https://issues.apache.org/activemq/browse/AMQ-913 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1, 4.0.2 Right now it's negociating to the maximum supported by both sides. This means that old version will try to load a newer version of the wireformat that it does not support! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2364) Update geronimo to use ActiveMQ 4.1.x
[ http://issues.apache.org/jira/browse/GERONIMO-2364?page=comments#action_12432632 ] Hiram Chirino commented on GERONIMO-2364: - in otherwords, the main thing that needs to get voted on is moving to 4.1 of activemq and the related changes. the small change can be treated as a bug fix and RTC does not apply.. > Update geronimo to use ActiveMQ 4.1.x > - > > Key: GERONIMO-2364 > URL: http://issues.apache.org/jira/browse/GERONIMO-2364 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: ActiveMQ >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 1.2 > > Attachments: GERONIMO-2364.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2364) Update geronimo to use ActiveMQ 4.1.x
[ http://issues.apache.org/jira/browse/GERONIMO-2364?page=comments#action_12432631 ] Hiram Chirino commented on GERONIMO-2364: - It's a small change and is simple enough to apply manually. I don't think the patch needs to be updated. It should not affect the voting on patch. > Update geronimo to use ActiveMQ 4.1.x > - > > Key: GERONIMO-2364 > URL: http://issues.apache.org/jira/browse/GERONIMO-2364 > Project: Geronimo > Issue Type: RTC > Security Level: public(Regular issues) > Components: ActiveMQ >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 1.2 > > Attachments: GERONIMO-2364.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=comments#action_36893 ] Hiram Chirino commented on AMQ-855: --- we need to also build some test cases for this. Any takers? > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.patch, > ActiveMQMessageConsumer.patch2, PrefetchSubscription.patch > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-855) Add support for prefetchSize = 0
[ https://issues.apache.org/activemq/browse/AMQ-855?page=comments#action_36892 ] Hiram Chirino commented on AMQ-855: --- 'm going to start looking into it today. I may not use the DataResponse to return the message right away. I think I would still prefer to use the normal message dispatching flow and logic. What I'm thinking is that on timeout, or when receiveNoWait() is called, and no message has arrived to be dispatched, we dispatch a message to the consumer letting it know that no message was available. Then it can unblock. The nice thing about this is that you don't get timing issues between the client and server where the client times out but the broker actually dispatched the message. > Add support for prefetchSize = 0 > > > Key: AMQ-855 > URL: https://issues.apache.org/activemq/browse/AMQ-855 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker >Affects Versions: 4.0, 4.0.1, 4.0.2 > Environment: any >Reporter: Vadim Pesochinskiy > Assigned To: Hiram Chirino >Priority: Critical > Fix For: 4.1 > > Attachments: ActiveMQMessageConsumer.patch, > ActiveMQMessageConsumer.patch2, PrefetchSubscription.patch > > > This feature would enable to support following test case: > 2 servers are processing 3 submitted jobs with following processing times 10 > min, 1 min, 1 min. This sequence should finish in 10 minutes as one service > will pick up the 10 minutes job, meanwhile the other one should manage the > two 1 minute jobs. Since I cannot set prefetchSize=0, one of the 1 minute > jobs is sitting in prefetch buffer and the jobs are processed in 11 minutes > instead of 10. > This is simplification of the real scenario where I have about 30 consumers > submitting jobs to 20 consumers through AMQ 4.0.1. I have following problems: > Messages are sitting in prefetch buffer are not available to processors, > which results in a lot of idle time. > Order of processing is random. For some reason Job # 20 is processed after > Job # 1500. Since senders are synchronously blocked this can result in > time-outs. > Some requests are real-time, i.e. there is a user waiting, so the system > cannot wait, so AMQ-850 does not fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-907) Make the ActiveIO dependency and optional dependency.
[ https://issues.apache.org/activemq/browse/AMQ-907?page=comments#action_36890 ] Hiram Chirino commented on AMQ-907: --- Moved the activeio transport to a seperate module and placed it in the sandbox. The tcp/ssl/stomp and vm transports do the equivalent and perform better and are much better tested. We might want to consider trashing this transport if no one finds a need for it. > Make the ActiveIO dependency and optional dependency. > - > > Key: AMQ-907 > URL: https://issues.apache.org/activemq/browse/AMQ-907 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > Need to move some core classes that are in activeio to activemq > so that it is not needed to run. Right now the only real > functionality that it provides that is optional is the journal > implementation. > Everything else that is use from activeio are just abstract interfaces, and I > think > those need to be moved/copied to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-907) Make the ActiveIO dependency and optional dependency.
[ https://issues.apache.org/activemq/browse/AMQ-907?page=comments#action_36891 ] Hiram Chirino commented on AMQ-907: --- activeio transport moved in trunk revision 439204. > Make the ActiveIO dependency and optional dependency. > - > > Key: AMQ-907 > URL: https://issues.apache.org/activemq/browse/AMQ-907 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > Need to move some core classes that are in activeio to activemq > so that it is not needed to run. Right now the only real > functionality that it provides that is optional is the journal > implementation. > Everything else that is use from activeio are just abstract interfaces, and I > think > those need to be moved/copied to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-907) Make the ActiveIO dependency and optional dependency.
[ https://issues.apache.org/activemq/browse/AMQ-907?page=comments#action_36889 ] Hiram Chirino commented on AMQ-907: --- Applied changes in trunk rev 439108 and 439111.. > Make the ActiveIO dependency and optional dependency. > - > > Key: AMQ-907 > URL: https://issues.apache.org/activemq/browse/AMQ-907 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1 > > > Need to move some core classes that are in activeio to activemq > so that it is not needed to run. Right now the only real > functionality that it provides that is optional is the journal > implementation. > Everything else that is use from activeio are just abstract interfaces, and I > think > those need to be moved/copied to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-907) Make the ActiveIO dependency and optional dependency.
Make the ActiveIO dependency and optional dependency. --- Key: AMQ-907 URL: https://issues.apache.org/activemq/browse/AMQ-907 Project: ActiveMQ Issue Type: Improvement Components: Broker Reporter: Hiram Chirino Assigned To: Hiram Chirino Fix For: 4.1 Need to move some core classes that are in activeio to activemq so that it is not needed to run. Right now the only real functionality that it provides that is optional is the journal implementation. Everything else that is use from activeio are just abstract interfaces, and I think those need to be moved/copied to ActiveMQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2364) Update geronimo to use ActiveMQ 4.1.x
[
http://issues.apache.org/jira/browse/GERONIMO-2364?page=comments#action_12431332
]
Hiram Chirino commented on GERONIMO-2364:
-
The broker seems to be working good with this patch. But it seems that on
shutdown it throws an error:
{code}
15:18:42,042 INFO [TransportConnector] Connector tcp://0.0.0.0:61616 Stopped
Server shutdown completed
15:18:46,727 WARN [GeronimoConnectionEventListener] connectionErrorOccurred
called with null
SQL Exception: 08003 :
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback(Unknown
Source)
at
org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback(ManagedXAConnection.java:124)
at
org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.rollback(AbstractManagedConnection.java:196)
at
org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.java:135)
at
org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultDatabaseLocker.java:80)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersistenceAdapter.java:202)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(JournalPersistenceAdapter.java:248)
at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:433)
at
org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
at
org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
15:18:46,731 ERROR [JournalPersistenceAdapter] Could not stop service: [EMAIL
PROTECTED] Reason: org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy
is no longer valid
org.apache.geronimo.kernel.proxy.DeadProxyException: Proxy is no longer valid
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:87)
at
org.apache.geronimo.connector.outbound.connectiontracking.ConnectionTracker$$EnhancerByCGLIB$$b426a8b3.handleReleased()
at
org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.returnConnection(ConnectionTrackingInterceptor.java:81)
at
org.apache.geronimo.connector.outbound.GeronimoConnectionEventListener.connectionErrorOccurred(GeronimoConnectionEventListener.java:81)
at
org.tranql.connector.AbstractManagedConnection.unfilteredConnectionError(AbstractManagedConnection.java:119)
at
org.tranql.connector.jdbc.ManagedXAConnection.access$000(ManagedXAConnection.java:44)
at
org.tranql.connector.jdbc.ManagedXAConnection$1.connectionErrorOccurred(ManagedXAConnection.java:65)
at org.apache.derby.jdbc.EmbedPooledConnection.notifyError(Unknown
Source)
at org.apache.derby.jdbc.EmbedPooledConnection.notifyException(Unknown
Source)
at
org.apache.derby.iapi.jdbc.BrokeredConnection.notifyException(Unknown Source)
at org.apache.derby.iapi.jdbc.BrokeredConnection.rollback(Unknown
Source)
at
org.tranql.connector.jdbc.ManagedXAConnection.localTransactionRollback(ManagedXAConnection.java:124)
at
org.tranql.connector.AbstractManagedConnection$LocalTransactionImpl.rollback(AbstractManagedConnection.java:196)
at
org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.java:135)
at
org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultDatabaseLocker.java:80)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersistenceAdapter.java:202)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(JournalPersistenceAdapter.java:248)
at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:433)
at
org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
at
org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
java.lang.NoClassDefFoundError: org/apache/activemq/broker/BrokerService$2$1
at
org.apache.activemq.broker.BrokerService$2.stop(BrokerService.java:1065)
at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:436)
at
org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:1235)
at
org.apache.activemq.broker.BrokerService$3.run(BrokerService.java:1212)
{code}
Not sure if we have to fix this befo
