Re: wiki access

[Hiram Chirino]

Hi Nathan,

We recently moved the confluence instance.. Something must have gotten
borked.  I'll look into it.  BUT... I think we are looking into moving
the space on to ASF managed machines.. not sure how long that will
take so, I'll try to get this fix for you ASAP in the mean time.

On 1/27/07, Nathan Mittler <[EMAIL PROTECTED]> wrote:

Hey guys,
I've apparently lost my privileges to change our wiki.  Was just trying to
update the AMQCPP 1.1 release page (
http://www.activemq.org/site/activemq-cpp-11-release.html) and was denied.

Thanks,
Nate





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Doxample: Can we ship it with our code?

[Hiram Chirino]

Yes think so.

On 1/27/07, Nathan Mittler <[EMAIL PROTECTED]> wrote:

Hey Hiram,
Is the resolution on this that we can just add a new header to his file in
our distro?

On 1/19/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>
> Thanks Oren!
>
> On Jan 18, 2007, at 6:49 PM, Oren Ben-Kiki wrote:
>
> > On Thu, 2007-01-18 at 18:09 -0500, Hiram Chirino wrote:
> >> ...
> >> Yeah the differences between the two get a bit complex and IANAL
> >> too :)
> >>
> >> But I think the biggest difference between the Licenses are that
> >> Apache licensed software is a bit more liberal with how it can be
> >> used.  For example it allows commercial companies to make
> >> modifications and redistribute without giving back the changes.
> >> Which is contrary to the GPL philosophy.  In essence the Apache, BSD,
> >> and MIT licenses are more Business friendly.
> >>
> >> So I light of that, you might not actually want to Apache License
> >> it.. And that would be OK...
> >
> > I don't feel that strongly about it. It isn't exactly the crown
> > jewels :-)
> >
> >> But if you don't mind other folks using your file (even for
> >> commercial reasons), you would just need to also add this to the
> >> header for us to be able to consume it:
> >>
> >> Copyright [] [name of copyright owner]
> >>
> >> Licensed under the Apache License, Version 2.0 (the "License");
> >> you may not use this file except in compliance with the License.
> >> You may obtain a copy of the License at
> >>
> >> http://www.apache.org/licenses/LICENSE-2.0
> >>
> >> Unless required by applicable law or agreed to in writing,
> >> software
> >> distributed under the License is distributed on an "AS IS" BASIS,
> >> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >> See the License for the specific language governing
> >> permissions and
> >> limitations under the License.
> >
> > Fine, put that in there with my name (Oren Ben-Kiki) and the current
> > year (2007). And hopefully within a "short period of time" this
> > will be
> > in the Autoconf archive and the problem will go away.
> >
> > Share & Enjoy,
> >
> >   Oren Ben-Kiki
> >
>
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: change ActiveMQ 4.2 to ActiveMQ 5.0

[Hiram Chirino]

yes. trunk has already tossed  backport-util-concurrent

On 1/23/07, Christopher G. Stach II <[EMAIL PROTECTED]> wrote:

Rob Davies wrote:
> Hi Brian,
>
> this isn't exactly true - we have always incremented the major version
> number with wire protocol changes when they are not backward compatible
> - but it's erroneous to assume that there is a casual link between the
> two - its just been coincidental to date.
>
> cheers,
>
> Rob

Is 5.0 going to be a requirement?  If so, does that mean finally tossing
backport-util-concurrent?

--
Christopher G. Stach II





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: change ActiveMQ 4.2 to ActiveMQ 5.0

[Hiram Chirino]

This is a good point. The new openwire should be able to always stay
backwards compatible so the old model of revving the major number when
the wire protocol breaks might not be right anymore.

On 1/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

I am under the impression that the open wire protocol should
always be able to maintain backward compatibility.
Does this mean that we will never change the major version ;-)

On 1/23/07, Brian McCallister <[EMAIL PROTECTED]> wrote:
>
> On Jan 23, 2007, at 9:15 AM, Rob Davies wrote:
>
> > The latest development is being done on ActiveMQ 4.2 - however
> > there are a lot of improvements between 4.1 and 4.2 - namely:
> >
> > 1. Use of Java 5
> > 2. Message cursors for persistent messages
> > 3. Spooling of temporary messages id broker memory is full
> >
> > and to be delivered in the next couple of weeks:
> >
> > 1. New very fast journal message store - that we good to be the
> > default
> > 2. Improvements to message flow control - to take into account the
> > spooling and cursors
> >
> > Given the above - I'd like to propose that the 4.2 release is re-
> > versioned to 5.0 and that we deliver a number of milestone releases
> > first - before GA
>
> -1, We have, thus far, used major version numbers to mean
> incompatible wire protocol changes, not "impressive new features" and
> I would like to maintain that.
>
> -Brian
>
>


--
Cheers,
Guillaume Nodet

Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/




--
Regards,
Hiram

Blog: http://hiramchirino.com

Are we graduated yet?

[Hiram Chirino]

From some of the posts in the incubator lists, it sounds like were

have now graduated.  If this is so, what are the next steps?

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Doxample: Can we ship it with our code?

[Hiram Chirino]

Thanks Oren!

On Jan 18, 2007, at 6:49 PM, Oren Ben-Kiki wrote:


On Thu, 2007-01-18 at 18:09 -0500, Hiram Chirino wrote:

...
Yeah the differences between the two get a bit complex and IANAL  
too :)


But I think the biggest difference between the Licenses are that
Apache licensed software is a bit more liberal with how it can be
used.  For example it allows commercial companies to make
modifications and redistribute without giving back the changes.
Which is contrary to the GPL philosophy.  In essence the Apache, BSD,
and MIT licenses are more Business friendly.

So I light of that, you might not actually want to Apache License
it.. And that would be OK...


I don't feel that strongly about it. It isn't exactly the crown
jewels :-)


But if you don't mind other folks using your file (even for
commercial reasons), you would just need to also add this to the
header for us to be able to consume it:

Copyright [] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,  
software

distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
See the License for the specific language governing  
permissions and

limitations under the License.


Fine, put that in there with my name (Oren Ben-Kiki) and the current
year (2007). And hopefully within a "short period of time" this  
will be

in the Autoconf archive and the problem will go away.

Share & Enjoy,

Oren Ben-Kiki

Re: [VOTE] Release ActiveMQ-CPP 1.1

[Hiram Chirino]

Hi Nathan,

No I'm not really sure what it is but I assume it had to be something
BSDish.. I'll do a little digging and see what I can find.

On 1/15/07, Nathan Mittler <[EMAIL PROTECTED]> wrote:

Hiram,
Do you know anything about the license in this file?  Is it compatible with
the ASF?

Also, does anyone have an example of a LICENSE.txt that includes multiple
licenses ... not sure what this should look like?

Thanks,
Nate

On 1/15/07, Kevan Miller <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 14, 2007, at 11:07 AM, Nathan Mittler wrote:
>
> > Hi everyone,
> > Several bug fixes as well as a few new features have been
> > incorporated into
> > ActiveMQ-CPP - worthy of a 1.1 release, before we go for full openwire
> > support in 2.0.
> >
> > The source bundle for the release candidate can be found here:
> > http://people.apache.org/~nmittler/incubator-activemq-cpp-1.1-src.zip
> > 
> >
> > And here's the wiki page for the release:
> > http://www.activemq.org/site/activemq-cpp-11-release.html
> > 
> >
> > Please cast your votes:
> >
> > [ ] +1 Release the source as Apache ActiveMQ  CPP 1.1
> > [ ] -1 Veto the release (provide specific comments)
>
> The following file in your distribution seems to be licensed under
> the same license as Autoconf. I don't know what that license is. I
> assume it's compatible with the ASF. The license needs to be included
> in your LICENSE.txt file.
>
> ===
> ==./m4/ac_doxygen.m4
> ===
> # This file is part of Autoconf.   -*- Autoconf -*-
>
> # Copyright (C) 2004 Oren Ben-Kiki
> # This file is distributed under the same terms as the Autoconf macro
> files.
>
> ...
>
> --kevan
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Openwire Generator Changes

[Hiram Chirino]

Hi Andrew I think It's only valid to run that in the activemq-core
module.  Is that were your running it?

On 1/9/07, Andrew Lusk <[EMAIL PROTECTED]> wrote:

I'm having trouble running the generators (I'm trying to port my
old-style generation scripts to the new style).  In a fresh checkout
of 4.1.0, I run:

mvn antrun:run

in the root directory, and get:

[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing ant tasks

Embedded error: taskdef class 
org.apache.activemq.openwire.tool.JavaGeneratorTask cannot be found

Running from activemq-openwire-generator doesn't help - that runs with
no errors but doesn't appear to do anything productive either.  Can
you shed some light here?

Andrew

From: "Hiram Chirino" <[EMAIL PROTECTED]>
Subject: Openwire Generator Changes
Date: Tue, 26 Sep 2006 19:14:05 -0800

> For all you who are interested in openwire...
>
> I have just checked in some changes for the openwire generators.  They
> are now 100% java based.  This should make them easier to grok and
> maintain / refactor.
>
> I have also updated the pom.xml files for all the modules that use
> openwire generated marshalers so that the marshaller code is generated
> when you run:
> mvn antrun:run
>
> Since the generators use the java sources of the activemq-core module
> when generating the marshallers, the default location configured in
> the pom.xml may not work for you.  You may need to set the
> activemq-core-dir property to the directory location where it is
> checked out to.  For example:
> mvn antrun:run -Dactivemq-core-dir=../../../activemq/activemq-core
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: svn commit: r491346 - in /incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region: PrefetchSubscription.java cursors/TopicStorePrefetch.java

[Hiram Chirino]

On 12/31/06, Rob Davies <[EMAIL PROTECTED]> wrote:


On 31 Dec 2006, at 07:59, Hiram Chirino wrote:

> On 12/31/06, Rob Davies <[EMAIL PROTECTED]> wrote:
>> Hey Hiram,
>>
>> this change breaks  org.apache.activemq.broker.RecoveryBrokerTest,
>> oorg.apache.activemq.broker.BrokerTest, etc   for me.
>>
>
> yeah I think I have fix for that. sorry I broke it.  I'm running the
> test suite again now.  Basically I think I need to default boolean
> empty=false;  So that an initial recovery of subscription is done.
>
>> also - I'm not sure I like TopicStorePrefetch possibly returning null
>> when a hasNext() has returned true
>>
>
> Yeah me neither :)  I did not fully understand why it was returning
> null when I expected it to return a value.  I was thinking it could be
> a timing issue with the MessageStore.
>
>> What was the problem in CursorDurableTest ? I hadn't seen that one
>>
>
> CursorDurableTest had a test that was failing due to out of
> order/duplicates showing up.  This was cause sometimes some messages
> were direct dispatched and at other times they are dispatched from the
> pending list.  But since the pending list's .next() was returning the
> items that were directly dispatched and not even added to the pending
> list.  This is when the dups and out of order issues would show up.
>
> The problem is that TopicStorePrefetch.next() was returning everything
> added to the durable subscription since it's backed by the
> MessageStore.  And that's not what we want.  We only want it to return
> things that are explicitly added to it since it's the pending list.

I wonder if the real problem is then in PrefetchSubscription.add() -
because only if pending is empty (nothing in the store) should it
dispatch directly


Could be an interaction.  I think TopicStorePrefetch still needs a
little more work.  I think we need to recover the TopicStorePrefetch
when the the durable subscription is created so that way we know if it
is initially empty or not.


>
>
>> cheers,
>>
>> Rob
>>
>> On 30 Dec 2006, at 23:49, [EMAIL PROTECTED] wrote:
>>
>> > Author: chirino
>> > Date: Sat Dec 30 15:49:03 2006
>> > New Revision: 491346
>> >
>> > URL: http://svn.apache.org/viewvc?view=rev&rev=491346
>> > Log:
>> > Fix for CursorDurableTest.
>> > The TopicStorePrefetch was iterating items that were in the
>> > subscription but not added to the pending list.
>> >
>> > Modified:
>> > incubator/activemq/trunk/activemq-core/src/main/java/org/
>> apache/
>> > activemq/broker/region/PrefetchSubscription.java
>> > incubator/activemq/trunk/activemq-core/src/main/java/org/
>> apache/
>> > activemq/broker/region/cursors/TopicStorePrefetch.java
>> >
>> > Modified: incubator/activemq/trunk/activemq-core/src/main/java/org/
>> > apache/activemq/broker/region/PrefetchSubscription.java
>> > URL: http://svn.apache.org/viewvc/incubator/activemq/trunk/
>> activemq-
>> > core/src/main/java/org/apache/activemq/broker/region/
>> > PrefetchSubscription.java?view=diff&rev=491346&r1=491345&r2=491346
>> >
>> =
>> =
>> > 
>> > --- incubator/activemq/trunk/activemq-core/src/main/java/org/
>> apache/
>> > activemq/broker/region/PrefetchSubscription.java (original)
>> > +++ incubator/activemq/trunk/activemq-core/src/main/java/org/
>> apache/
>> > activemq/broker/region/PrefetchSubscription.java Sat Dec 30
>> > 15:49:03 2006
>> > @@ -406,7 +406,9 @@
>> >  pending.reset();
>> >  while(pending.hasNext()&&!isFull()
>> > &&count> >  MessageReference
>> node=pending.next();
>> > -
>> > +if ( node == null )
>> > + break;
>> > +
>> >  if(canDispatch(node)){
>> >  pending.remove();
>> >  // Message may have been
>> > sitting in the pending list a while
>> >
>> > Modified: incubator/activemq/trunk/activemq-core/src/main/java/org/
>> > apache/activemq/broker/region/cursors/TopicStorePrefetch.java
>> > URL: http://svn.apache.org/viewvc/incubator/activemq/trunk/
>> activemq-
>> > core/src/main/java/org/apache/activemq/broke

Re: svn commit: r491346 - in /incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region: PrefetchSubscription.java cursors/TopicStorePrefetch.java

[Hiram Chirino]

On 12/31/06, Rob Davies <[EMAIL PROTECTED]> wrote:

Hey Hiram,

this change breaks  org.apache.activemq.broker.RecoveryBrokerTest,
oorg.apache.activemq.broker.BrokerTest, etc   for me.



yeah I think I have fix for that. sorry I broke it.  I'm running the
test suite again now.  Basically I think I need to default boolean
empty=false;  So that an initial recovery of subscription is done.


also - I'm not sure I like TopicStorePrefetch possibly returning null
when a hasNext() has returned true



Yeah me neither :)  I did not fully understand why it was returning
null when I expected it to return a value.  I was thinking it could be
a timing issue with the MessageStore.


What was the problem in CursorDurableTest ? I hadn't seen that one



CursorDurableTest had a test that was failing due to out of
order/duplicates showing up.  This was cause sometimes some messages
were direct dispatched and at other times they are dispatched from the
pending list.  But since the pending list's .next() was returning the
items that were directly dispatched and not even added to the pending
list.  This is when the dups and out of order issues would show up.

The problem is that TopicStorePrefetch.next() was returning everything
added to the durable subscription since it's backed by the
MessageStore.  And that's not what we want.  We only want it to return
things that are explicitly added to it since it's the pending list.



cheers,

Rob

On 30 Dec 2006, at 23:49, [EMAIL PROTECTED] wrote:

> Author: chirino
> Date: Sat Dec 30 15:49:03 2006
> New Revision: 491346
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=491346
> Log:
> Fix for CursorDurableTest.
> The TopicStorePrefetch was iterating items that were in the
> subscription but not added to the pending list.
>
> Modified:
> incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/PrefetchSubscription.java
> incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/cursors/TopicStorePrefetch.java
>
> Modified: incubator/activemq/trunk/activemq-core/src/main/java/org/
> apache/activemq/broker/region/PrefetchSubscription.java
> URL: http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-
> core/src/main/java/org/apache/activemq/broker/region/
> PrefetchSubscription.java?view=diff&rev=491346&r1=491345&r2=491346
> ==
> 
> --- incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/PrefetchSubscription.java (original)
> +++ incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/PrefetchSubscription.java Sat Dec 30
> 15:49:03 2006
> @@ -406,7 +406,9 @@
>  pending.reset();
>  while(pending.hasNext()&&!isFull()
> &&count  MessageReference node=pending.next();
> -
> +if ( node == null )
> + break;
> +
>  if(canDispatch(node)){
>  pending.remove();
>  // Message may have been
> sitting in the pending list a while
>
> Modified: incubator/activemq/trunk/activemq-core/src/main/java/org/
> apache/activemq/broker/region/cursors/TopicStorePrefetch.java
> URL: http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-
> core/src/main/java/org/apache/activemq/broker/region/cursors/
> TopicStorePrefetch.java?view=diff&rev=491346&r1=491345&r2=491346
> ==
> 
> --- incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/cursors/TopicStorePrefetch.java (original)
> +++ incubator/activemq/trunk/activemq-core/src/main/java/org/apache/
> activemq/broker/region/cursors/TopicStorePrefetch.java Sat Dec 30
> 15:49:03 2006
> @@ -20,7 +20,7 @@
>
>  import java.io.IOException;
>  import java.util.LinkedList;
> -import javax.jms.JMSException;
> +
>  import org.apache.activemq.broker.region.Destination;
>  import org.apache.activemq.broker.region.MessageReference;
>  import org.apache.activemq.broker.region.Topic;
> @@ -48,6 +48,10 @@
>  private String subscriberName;
>  private Destination regionDestination;
>
> +boolean empty=true;
> + private MessageId firstMessageId;
> + private MessageId lastMessageId;
> +
>  /**
>   * @param topic
>   * @param clientId
> @@ -73,7 +77,7 @@
>   * @return true if there are no pending messages
>   */
>  public boolean isEmpty(){
> -return batchList.isEmpty();
> +return empty;
>  }
>
>  public synchronized int size(){
> @@ -86,27 +90,55 @@
>  }
>
>  public synchronized void addMessageLast(MessageReference node)
> throws Exception{
> -if(node!=null){
> + if(node!=null){
> +

Re: svn commit: r490789 - /incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java

[Hiram Chirino]

Hi Rob,

The connection actually has some concurrency to it.  This is when an
async error is detected on the connection.  Those syncs where there to
ensure that proper cleanup was performed.  I.e. if the connection is
adding a consumer and and publisher detects that the consumer failed
it will clean up the consumer's connection and it might not do it
properly if the consumer subscription was still being setup.

so in short that's why the syncs were in place.  If we could get the
async errors to get serviced from the transport's thread then we could
eliminate the syncs.


On 12/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: rajdavies
Date: Thu Dec 28 12:44:59 2006
New Revision: 490789

URL: http://svn.apache.org/viewvc?view=rev&rev=490789
Log:
drop synchronization from connectionState and connection context -
not required when using ConcurrentHashMap and limited concurrency for
publishers or transactions for the same client connection

Modified:

incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java

Modified: 
incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java
URL: 
http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java?view=diff&rev=490789&r1=490788&r2=490789
==
--- 
incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java
 (original)
+++ 
incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/TransportConnection.java
 Thu Dec 28 12:44:59 2006
@@ -352,7 +352,7 @@
 return null;
 }

-synchronized public Response processBeginTransaction(TransactionInfo info) 
throws Exception {
+public Response processBeginTransaction(TransactionInfo info) throws 
Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -367,14 +367,14 @@
 return null;
 }

-synchronized public Response processEndTransaction(TransactionInfo info) 
throws Exception {
+public Response processEndTransaction(TransactionInfo info) throws 
Exception {
 // No need to do anything.  This packet is just sent by the client
 // make sure he is synced with the server as commit command could
 // come from a different connection.
 return null;
 }

-synchronized public Response processPrepareTransaction(TransactionInfo 
info) throws Exception {
+public Response processPrepareTransaction(TransactionInfo info) throws 
Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -398,7 +398,7 @@
 }
 }

-synchronized public Response 
processCommitTransactionOnePhase(TransactionInfo info) throws Exception {
+public Response processCommitTransactionOnePhase(TransactionInfo info) 
throws Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -412,7 +412,7 @@

 }

-synchronized public Response 
processCommitTransactionTwoPhase(TransactionInfo info) throws Exception {
+public Response processCommitTransactionTwoPhase(TransactionInfo info) 
throws Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -424,7 +424,7 @@
 return null;
 }

-synchronized public Response processRollbackTransaction(TransactionInfo 
info) throws Exception {
+public Response processRollbackTransaction(TransactionInfo info) throws 
Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -436,7 +436,7 @@
 return null;
 }

-synchronized public Response processForgetTransaction(TransactionInfo 
info) throws Exception {
+public Response processForgetTransaction(TransactionInfo info) throws 
Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -446,7 +446,7 @@
 return null;
 }

-synchronized public Response processRecoverTransactions(TransactionInfo 
info) throws Exception {
+public Response processRecoverTransactions(TransactionInfo info) throws 
Exception {
 ConnectionState cs = (ConnectionState) 
localConnectionStates.get(info.getConnectionId());
 ConnectionContext context=null;
 if( cs!=null ) {
@@ -501,7 +501,7 @

Re: openwire protocol

[Hiram Chirino]

Hi Motl,

I've started documenting more OpenWire protocol details here:

http://goopen.org/confluence/display/ACTIVEMQ/OpenWire

I'll try to add more as I get time but please ping me if something
needs clarification.

On 12/28/06, Motl <[EMAIL PROTECTED]> wrote:


Thank you for fast response.
Really, I'm not looking for code generators, but more for some simple (might
be incomplete) description of openwire network protocol.
If I had one, I'd like to write an ethereal sniffer plugin for the protocol
in future, that could ease significantly development process.


Hiram Chirino wrote:
>
> Hi Motl,
>
> We have not yet put together a formal specification for it.  But I
> guess it should be done, we are looking for a volunteer :)
>
> What we have are code generators that will generate the openwire
> marshallers for a few different languages.  I did lots of working in
> putting those generators together and would be happy to help you
> document if you want, but I'm a bit busy to do it by myself.
>
>
> On 12/28/06, Motl <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> Is there any specification for openwire protocol? (I mean network
>> protocol,
>> i.e. header fields, body, byte order etc).
>> Where can I get it?
>>
>> Thanks in advance.
>> --
>> View this message in context:
>> http://www.nabble.com/openwire-protocol-tf2890803.html#a8076068
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>

--
View this message in context: 
http://www.nabble.com/openwire-protocol-tf2890803.html#a8076644
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: openwire protocol

[Hiram Chirino]

Hi Motl,

We have not yet put together a formal specification for it.  But I
guess it should be done, we are looking for a volunteer :)

What we have are code generators that will generate the openwire
marshallers for a few different languages.  I did lots of working in
putting those generators together and would be happy to help you
document if you want, but I'm a bit busy to do it by myself.


On 12/28/06, Motl <[EMAIL PROTECTED]> wrote:


Hi,

Is there any specification for openwire protocol? (I mean network protocol,
i.e. header fields, body, byte order etc).
Where can I get it?

Thanks in advance.
--
View this message in context: 
http://www.nabble.com/openwire-protocol-tf2890803.html#a8076068
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Board report

[Hiram Chirino]

Just noticed that we are running late submitting our board report.

I'm going to post the following as our board report:
http://wiki.apache.org/incubator/December2006?action=edit

Please add anything you think is important.

=== ActiveMQ ===

Apache ActiveMQ is a messaging broker and client.

The ActiveMQ team has put out several release since it last reported:

 - ActiveMQ 4.0.2 - was a small bug fix release.
 - ActiveMQ 4.1.0 - was a major feature enhancement release.
 - ActiveMQ CPP 1.0 - was the first release of the C++ client for ActiveMQ

We are now focusing on the next 4.1.1 bug fix release but also making
major enhancements to trunk for better scalability and that will
either be released as ActiveMQ 4.2 or 5.0.

The project has discussed graduating and feels that ActiveMQ is ready
and would prefer to become a TLP.




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: java.io.InterruptedIOException

[Hiram Chirino]

I would recommend that you use ActiveMQ 4.1

On 12/15/06, mar1394 <[EMAIL PROTECTED]> wrote:


I have just upgraded from ActiveMQ-3.2.2 to ActiveMQ-4.0 RC2.

On all my pplatforms I am getting this exeption over and over when I try to
publish:

javax.jms.JMSException: java.io.InterruptedIOException
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:57)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1118)
at
org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1524)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:462)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:384)
at
org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:151)

My code is quite vanilla JMS and works with at leat 4 JMS providers.  What
is the deal here?

--
View this message in context: 
http://www.nabble.com/java.io.InterruptedIOException-tf2830293.html#a7901746
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Performance Issue

[Hiram Chirino]

Best bet is to run it with a profiler to figure out where the hot spot
is for linux.

On 12/18/06, garima015 <[EMAIL PROTECTED]> wrote:


I am facing a really bad performance of ActiveMq on linux box.
When running on windows 1000 transactions are taking 2 seconds and when
running on Linux same are taking 40 sec.
Please if anybody can tell me solution to performance issue.

Here is the code i am using to send and receive the message.

Thanks in advance

public class Requestor{
private Session session;
private Destination replyQueue;
private MessageProducer requestProducer;
private MessageConsumer replyConsumer;
Logger logger = null;

/**
 * Constructor
 */
protected Requestor() {
super();
logger = LoggerWrapper.getLogger(this.getClass().getName());
}

/**
 * This method will return the object of Requestor
 * @param connection, Connection
 * @param requestQueueName , String
 * @return  Requestor object
 * @throws JMSException
 * @throws NamingException
 */
public static Requestor newRequestor(Connection connection, String
requestQueueName)throws JMSException, NamingException {
Requestor requestor = new Requestor();
requestor.initialize(connection, requestQueueName);
return requestor;
}

/**
 * This method will initialize the Producer and Consumer on request
and reply queue
 * @param connection, Connection
 * @param requestQueueName , String
 * @throws NamingException
 * @throws JMSException
 */
protected void initialize(Connection connection, String
requestQueueName)throws NamingException, JMSException {
session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);
Destination requestQueue =
session.createQueue(requestQueueName);

replyQueue = session.createTemporaryQueue();
requestProducer = session.createProducer(requestQueue);

requestProducer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
replyConsumer = session.createConsumer(replyQueue);
replyConsumer.receive(10);
}

/**
 * This method is used to send the message to queue
 * @param message
 * @throws JMSException
 */
public String send(String message) throws JMSException {
TextMessage requestMessage = (TextMessage)
session.createTextMessage();
requestMessage.setText(message);
requestMessage.setJMSReplyTo(replyQueue);
requestProducer.send(requestMessage);
return receiveSync();
}

/**
 * This method is used to receive the message from the queue
 * @return String
 * @throws JMSException
 */
private String receiveSync() throws JMSException {
TextMessage replyMessage = null;
Message msg =  replyConsumer.receive();

if (msg instanceof TextMessage){
replyMessage = (TextMessage) msg;
}
logger.debug("receive Sync:"+ new Date().getTime());
return replyMessage.getText();
}
}

public class Replier implements MessageListener {

private Session session;
Logger logger = null;
Engine engineRef = null;
Transformer transformerRef = null;
MessageConsumer requestConsumer = null;
Destination replyDestination = null;
private static Map destinationMap = new HashMap();
/**
 * Constructor
 *
 */
protected Replier(){
super();
logger = LoggerWrapper.getLogger(this.getClass().getName());
}

/**
 * This will return the instance of replier
 * @param connection, Connection
 * @param requestQueueName
 * @return
 * @throws Exception
 */
public static Replier newReplier(Connection connection,String
requestQueueName ,Engine engine,Transformer transformer)throws Exception {
Replier replier = new Replier();
replier.initialize(connection,
requestQueueName,engine,transformer);
return replier;
}

/**
 * This method will initilize the consumer on request queue
 * @param connection
 * @param requestQueueName
 * @throws Exception
 */
protected void initialize(Connection connection, String
requestQueueName, Engine engine,Transformer transformer)throws Exception {
session = connection.createSession(false,
Session.AUTO_ACKNOWLEDGE);

// Create the destination (Topic or Queue)
//Destination requestQueue =
session.createQueue(requestQueueName+"?consumer.retroactive=true");
   

Re: error when start broker

[Hiram Chirino]

How do you do a pessimistic lock on database record in sybase ASE 12.5??

On 12/19/06, rain.xk <[EMAIL PROTECTED]> wrote:


Hi,
My database is sybaseASE12.5,and I use the activemq4.1.0.
The following is the series of messages when I start broker:

- ActiveMQ 4.1.0-incubator JMS Message Broker (xuke) is starting
- For help or more information please see:
http://incubator.apache.org/activemq/
- Database driver recognized: [jconnect__tm__for_jdbc__tm_]
- Attempting to acquire the exclusive lock to become the Master broker
- Failed to acquire lock: com.sybase.jdbc3.jdbc.SybSQLException: FOR UPDATE
can not be used in a SELECT which is not part of the declaration of a cursor
or which is not a stored procedure.
com.sybase.jdbc3.jdbc.SybSQLException:  FOR UPDATE can not be used in a
SELECT which is not part of the declaration of a cursor or which is not a
stored procedure.
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeLoop(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.execute(Unknown Source)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.execute(Unknown Source)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117)
at
org.apache.activemq.store.jdbc.DefaultDatabaseLocker.start(DefaultDatabaseLocker.java:59)

How can I handle this?
--
View this message in context: 
http://www.nabble.com/error-when-start-broker-tf2844348.html#a7942260
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered

[Hiram Chirino (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1078?page=comments#action_37604 ] 

Hiram Chirino commented on AMQ-1078:


fix in 4.1 branch rev 480862

> 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

Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)

[Hiram Chirino]

Howdy ActiveMQ Mentors...

This is just a gentle reminder that this vote is still open and
looking for at least 1 more incubator PMC binding vote to make it
official.  Please take a moment and review the release.

Thanks!

On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Hey folks,

I was able to finally get around to doing a binary release candidate
from the 4.1 branch.

it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-410-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.1.0
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1


--
Regards,
Hiram

Blog: http://hiramchirino.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: src-jar at rc2 download location is "null"

[Hiram Chirino]

That maven module actually has no java sources that is why non are
included the sources.jar.  Perhaps we should delete it from the
directory structure.

Most of the other modules do have java sources.

On 11/20/06, Endre Stølsvik <[EMAIL PROTECTED]> wrote:

Hi!

The sources.jar available at
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/

.. is only 5.4 KB big, containing only the META-INF dir and some files
within, nothing else.

It would also be very nice if this file was included in the binary tarball.

Regards,
Endre




--
Regards,
Hiram

Blog: http://hiramchirino.com

Now that 4.0.2 is release should we start the Graduation ball rolling?

[Hiram Chirino]

I think this project is like the 40 year old virgin still living at
home with his parents.  lol!  Don't you think it's about time we get
the ball rolling on graduating our of the incubator?

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Switching to ActiveMQ 4.2 to Java 5???

[Hiram Chirino]

On 11/15/06, Endre Stølsvik <[EMAIL PROTECTED]> wrote:

Hiram Chirino wrote:
> Hi folks,
>
> How do you guys feel about switching the minimum run time requirement
> for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> has a much better set of concurrent implementation.
>
> We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
> Also I have a feeling that once we switch to Java 5, someone will
> figure out how to use retrotranslator to make our Java 5 binaries also
> run on Java 1.4.  But I doubt anybody will make any efforts to look
> into that until we actually jump to Java 5.
>

Rather big move for a minor version - why not call it ActiveMQ 5 instead
(It'll even align!).



lol.. good point.  But I'd hate to have big increases without big
functionality changes especially if the clients are still compatible
with the 4.x stuff.


Then keep ActiveMQ 4.x on 1.4.

Regards,
Endre.




--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Created: (AMQ-1052) Connection is not released by broker when client is killed when client is sending to a queue that is full

[Hiram Chirino (JIRA)]

Connection is not released by broker when client is killed when client is 
sending to a queue that is full
-

 Key: AMQ-1052
 URL: https://issues.apache.org/activemq/browse/AMQ-1052
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1.1, 4.1.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

ActiveMQ CPP Change log.

[Hiram Chirino]

Nathan,

Nice work on putting together the activemq-cpp release page!
http://activemq.com/site/activemq-cpp-10-release.html

How hard was it to build that change log?  Would it make it simpler if
the ActiveMQ cpp stuff it's own Jira space???

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Switching to ActiveMQ 4.2 to Java 5???

[Hiram Chirino]

On 11/15/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

Sounds good.
Do you plan to refactor some code to use generics, or other
Java 5 features ?


At a minimum we should switch to the Java 1.5 concurrent package.
Switch generics has an upside that it will make our code more type
safe but a downside that merging patches from 4.2.x <-> 4.1.x will be
more difficult.

How about annotations?? any places where you think those would make more sense?



On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> How do you guys feel about switching the minimum run time requirement
> for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> has a much better set of concurrent implementation.
>
> We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
>  Also I have a feeling that once we switch to Java 5, someone will
> figure out how to use retrotranslator to make our Java 5 binaries also
> run on Java 1.4.  But I doubt anybody will make any efforts to look
> into that until we actually jump to Java 5.
>
> So what do you say?  Shall we switch ??
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>


--
Cheers,
Guillaume Nodet




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Switching to ActiveMQ 4.2 to Java 5???

[Hiram Chirino]

On 11/15/06, James Strachan <[EMAIL PROTECTED]> wrote:

+1.

We should switch to Java 5 for compilation and for the default release
(since the concurrent stuff is  faster & more bug free on Java 5) but
maybe provide a retrotranslator version of the jars for those who
can't move JVM.

i.e. build on Java 5 only - but allow deployments on 1.4



I agree.. but I don't want to condition the switch to 1.5 on getting
the retrotranslator stuff working first.  If we get the
retrotranslator stuff working.. well that should just be the gravy.


On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> How do you guys feel about switching the minimum run time requirement
> for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> has a much better set of concurrent implementation.
>
> We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
>  Also I have a feeling that once we switch to Java 5, someone will
> figure out how to use retrotranslator to make our Java 5 binaries also
> run on Java 1.4.  But I doubt anybody will make any efforts to look
> into that until we actually jump to Java 5.
>
> So what do you say?  Shall we switch ??
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>


--

James
---
http://radio.weblogs.com/0112098/




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Switching to ActiveMQ 4.2 to Java 5???

[Hiram Chirino]

Well..

I think we should get used to it.  We should always keep at least 1
stable branch.


On 11/15/06, Bruce Snyder <[EMAIL PROTECTED]> wrote:

On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> How do you guys feel about switching the minimum run time requirement
> for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> has a much better set of concurrent implementation.
>
> We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
>  Also I have a feeling that once we switch to Java 5, someone will
> figure out how to use retrotranslator to make our Java 5 binaries also
> run on Java 1.4.  But I doubt anybody will make any efforts to look
> into that until we actually jump to Java 5.
>
> So what do you say?  Shall we switch ??

Maybe this message should be CC'd to the activemq-user list to see how
users feel about such a change. Keeping a 4.1.x branch alive might
wind up being a lot of work WRT backporting fixes to the trunk.

Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL 
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/




--
Regards,
Hiram

Blog: http://hiramchirino.com

Switching to ActiveMQ 4.2 to Java 5???

[Hiram Chirino]

Hi folks,

How do you guys feel about switching the minimum run time requirement
for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
has a much better set of concurrent implementation.

We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
Also I have a feeling that once we switch to Java 5, someone will
figure out how to use retrotranslator to make our Java 5 binaries also
run on Java 1.4.  But I doubt anybody will make any efforts to look
into that until we actually jump to Java 5.

So what do you say?  Shall we switch ??

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: ActiveMQ POM

[Hiram Chirino]

I'm actually ok with that.  overwriting old artifacts.  That part the
kinda sucks is that maven won't download updates to those artifacts.

On 11/14/06, Fritz Oconer <[EMAIL PROTECTED]> wrote:

Hi,

I think the downside here is that it will loose reference to previous
builds. Since "development" will not change to timestamp, then "deploy" will
just overwrite the existing artifacts.

Regards,
Fritz

- Original Message -
From: "Hiram Chirino" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, November 15, 2006 12:52 AM
Subject: Re: ActiveMQ POM


> Thanks Fritz!
>
> I knew there had to be a reason that I was just not aware of.  What do
> you think would be the downsides of not using the special "SNAPSHOT"
> handling that maven provides?  What if we tagged our SNAPSHOT builds
> with something like like "DEVELOPMENT" instead of "SNAPSHOT".
>
> I'm guessing that problem would go away, but what other ones would we get?
>
> On 11/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>> This is also my experience.
>> If we just use the real version 4.2-SNAPSHOT
>> for example, it should also work and maven
>> should be able to change (*nearly*) all these
>> occurrences when using the release plugin.
>>
>> I say nearly, because in ServiceMix, there are
>> some edge cases where this fail (when including
>> the version in files other than pom.xml like artifacts
>> resources for example).
>>
>> On 11/14/06, Fritz Oconer <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > I added ${activemq-version} instead of ${project.version} basically as
>> > a
>> > workaround for build failures due to differences in timestamp. If we
>> > use
>> > ${project.version} then it will require all activemq type artifacts
>> > (specified as  in the parent pom.xml) to have the same
>> > timestamp
>> > as the parent. This becomes an issue when nightly-build deploy fails
>> > after
>> > some of the modules have been deployed causing some activemq modules to
>> > have
>> > different timestamp as the parent. We can change this back to using
>> > project.version but we need to make sure that nightly-build always
>> > deploys
>> > successfully or I wonder if there is another workaround for this?
>> >
>> > https://issues.apache.org/activemq/browse/AMQ-956
>> >
>> > Regards,
>> > Fritz
>> >
>> > - Original Message -
>> > From: "Hiram Chirino" <[EMAIL PROTECTED]>
>> > To: 
>> > Sent: Tuesday, November 14, 2006 8:48 PM
>> > Subject: ActiveMQ POM
>> >
>> >
>> > > Howdy,
>> > >
>> > > I was wondering if anybody knows why we are using
>> > > "${activemq-version}" instead of "${project.version}" in our ActiveMQ
>> > > poms??  When doing a release build, it's easy to forget that you need
>> > > to updated the version in to places.  Can't we just use the
>> > > "${project.version}" variable??
>> > >
>> > > --
>> > > Regards,
>> > > Hiram
>> > >
>> > > Blog: http://hiramchirino.com
>> >
>> >
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Updated: (AMQ-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1047?page=all ]

Hiram Chirino updated AMQ-1047:
---

Assignee: Adrian Co  (was: Hiram Chirino)

> ActiveMQ admin scripts should hide JMX from the user as much as possible.
> -
>
> Key: AMQ-1047
> URL: https://issues.apache.org/activemq/browse/AMQ-1047
> Project: ActiveMQ
>  Issue Type: Improvement
>        Reporter: Hiram Chirino
> Assigned To: Adrian Co
> Fix For: 4.2.0
>
>
> The fact that JMX is being used to access the management functions of the 
> Broker should be hidden from the user of the admin scripts as much as 
> possible.
> For example, users should not be displayed objects names of a list of 
> subscriptions.  They should be shown the subscription ids of the 
> subscriptions.  The same goes for connections and so forth.

-- 
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-1046) Consolidate the ActiveMQ admin scripts to a single command line script

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1046?page=all ]

Hiram Chirino reassigned AMQ-1046:
--

Assignee: Adrian Co  (was: Fritz Oconer)

> Consolidate the ActiveMQ admin scripts to a single command line script
> --
>
> Key: AMQ-1046
> URL: https://issues.apache.org/activemq/browse/AMQ-1046
> Project: ActiveMQ
>  Issue Type: Improvement
>        Reporter: Hiram Chirino
> Assigned To: Adrian Co
> Fix For: 4.2.0
>
>
> Right now we have serveral command line scripts in the ActiveMQ bin directory 
> of the binary distribution.  They are used for admin purposes.  They are less 
> than ideal because some of them have very generic names and might clash with 
> existing commands if the activemq bin directory is added to the PATH of a 
> unix system.
> I think it would be more idea if we consolidated all the command so that are 
> executed using just 1 script.  Something like:
> $ activemq-admin list
> $ activemq-admin stat
> $ activemq-admin browse
> etc. etc. etc.  This way only 2 executable scripts are added to the path:
>  (1) activemq - the binary that starts up ActiveMQ
>  (2) activemq-admin - the binary used to manage the ActiveMQ instance.

-- 
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-1047) ActiveMQ admin scripts should hide JMX from the user as much as possible.

[Hiram Chirino (JIRA)]

ActiveMQ admin scripts should hide JMX from the user as much as possible.
-

 Key: AMQ-1047
 URL: https://issues.apache.org/activemq/browse/AMQ-1047
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.2.0


The fact that JMX is being used to access the management functions of the 
Broker should be hidden from the user of the admin scripts as much as possible.
For example, users should not be displayed objects names of a list of 
subscriptions.  They should be shown the subscription ids of the subscriptions. 
 The same goes for connections and so forth.

-- 
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-1046) Consolidate the ActiveMQ admin scripts to a single command line script

[Hiram Chirino (JIRA)]

Consolidate the ActiveMQ admin scripts to a single command line script
--

 Key: AMQ-1046
 URL: https://issues.apache.org/activemq/browse/AMQ-1046
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Hiram Chirino
 Assigned To: Fritz Oconer
 Fix For: 4.2.0


Right now we have serveral command line scripts in the ActiveMQ bin directory 
of the binary distribution.  They are used for admin purposes.  They are less 
than ideal because some of them have very generic names and might clash with 
existing commands if the activemq bin directory is added to the PATH of a unix 
system.

I think it would be more idea if we consolidated all the command so that are 
executed using just 1 script.  Something like:
$ activemq-admin list
$ activemq-admin stat
$ activemq-admin browse

etc. etc. etc.  This way only 2 executable scripts are added to the path:
 (1) activemq - the binary that starts up ActiveMQ
 (2) activemq-admin - the binary used to manage the ActiveMQ instance.


-- 
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-746) JournalPersistenceAdapterGBean needs to resolve the persistence adapter directory via serverInfo.resolveServer

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-746?page=all ]

Hiram Chirino resolved AMQ-746.
---

Resolution: Won't Fix

Geronimo no longer uses this GBean.

> JournalPersistenceAdapterGBean needs to resolve the persistence adapter 
> directory via serverInfo.resolveServer
> --
>
> Key: AMQ-746
> URL: https://issues.apache.org/activemq/browse/AMQ-746
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Geronimo Integration
>Affects Versions: 3.2.4
>Reporter: Gianny DAMOUR
> Fix For: 3.2.5
>
> Attachments: GERONIMO-1638-AMQ.patch
>
>
> The current implementation resolves the persistence adapter directory via 
> serverInfo.resolve. This causes a problem with the multi-server feature: the 
> journal is located at var/activemq/journal instead of  name>/var/activemq/journal

-- 
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-319) ActiveMQ hangs when initial connection to broker fails using reliable transport

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-319?page=all ]

Hiram Chirino resolved AMQ-319.
---

Fix Version/s: 4.0.3
   (was: 3.2.5)
   Resolution: Fixed
 Assignee: Hiram Chirino

Since you can set a max reconnect attempt in 4.0.. this problem is not an issue 
there anymore.

>  ActiveMQ hangs when initial connection to broker fails using reliable 
> transport
> 
>
> Key: AMQ-319
> URL: https://issues.apache.org/activemq/browse/AMQ-319
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: JMS client
>Affects Versions: 3.0
>Reporter: Ramzi Saba
> Assigned To: Hiram Chirino
> Fix For: 4.0.3
>
>
> Make these changes in the JMS client to avoid blocking on startup in case all 
> brokers are down:
> 1- Start the reliable tcp channel in its own thread (seems there was an 
> attempt to do so anyway)
> 2- Synchronous and asynchronous client calls (via session, consumer, etc.) to 
> the reliable tcp channel should simply verify if a reliable channel has been 
> already established, else throw a JMSException, alternatively allow the 
> client to configure a timeout (currently it's hardcoded for synchronous calls 
> only I believe).
> 3- Other than starting the reliable channel, the client should not be 
> responsible of reestablishing a lost or unavailable channel. I would delegate 
> reliability to the reliable channel itself.
> 4- Look into adding a listener to allow for a silent client startup and 
> reconnect behind the scene once the broker is 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] Updated: (AMQ-734) Network connections do not reconnect when using static: with failover=true

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-734?page=all ]

Hiram Chirino updated AMQ-734:
--

Fix Version/s: 4.1.1
   (was: 4.0.1)

I've got a feeling that this was related to the timing issues addressed in 
issue:
https://issues.apache.org/activemq/browse/AMQ-1044
which is now fixed.

Could one you guys retest against a source build from the 4.1 branch and let me 
know if it resolves this issue?

> Network connections do not reconnect when using static: with failover=true
> --
>
> Key: AMQ-734
> URL: https://issues.apache.org/activemq/browse/AMQ-734
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 4.0
> Environment: winxp java1.5.6
>    Reporter: tao
> Assigned To: Hiram Chirino
>Priority: Critical
> Fix For: 4.2.0, 4.1.1
>
>
> If I pull out RJ45 port from net card ,waiting a time ,then put  RJ45 port 
> net card .Network is resume.Other computer always throw errors and net 
> channel can't work.

-- 
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-1036) web-console broken (queue browsing).

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1036?page=all ]

Hiram Chirino updated AMQ-1036:
---

Fix Version/s: 4.1.1
   4.2.0
   (was: 4.1.0)

> web-console broken (queue browsing).
> 
>
> Key: AMQ-1036
> URL: https://issues.apache.org/activemq/browse/AMQ-1036
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: incubation
>Reporter: Dave Syer
> Assigned To: Adrian Co
> Fix For: 4.2.0, 4.1.1
>
>
> I managed to build and launch the web-console from svn, but the queue 
> browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size} 
> that do not exist.  When I hacked queue.jsp to remove references to those 
> properties I got another error on trying to purge a queue:
> RequestURI=/activemq-web-console/purgeDestination.action
> Caused by:
> java.lang.IllegalArgumentException: Target bean must not be null
>   at org.springframework.util.Assert.notNull(Assert.java:113)
>   at 
> org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
>   at 
> org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
>   at 
> org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
>   at 
> org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
>   at 
> org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
>   at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
>   at 
> org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
>   at 
> org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
>   at 
> org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
> ...

-- 
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-910) backoffMultiplier should be a double value

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-910?page=all ]

Hiram Chirino updated AMQ-910:
--

Fix Version/s: 4.2.0
   (was: 4.0.1)

> backoffMultiplier should be a double value
> --
>
> Key: AMQ-910
> URL: https://issues.apache.org/activemq/browse/AMQ-910
> Project: ActiveMQ
>  Issue Type: Improvement
>Reporter: Daniel Aioanei
> Fix For: 4.2.0
>
>
> Having org.apache.activemq.ra.ActiveMQActivationSpec.backOffMultiplier as a 
> short value is too limiting. I think a double value would be more 
> appropriate. For instance, I'd like to set it to about 1.1 but that's not 
> possible at the time being.

-- 
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-1016) 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1016?page=all ]

Hiram Chirino resolved AMQ-1016.


Fix Version/s: 4.1.1
   4.2.0
   Resolution: Fixed
 Assignee: Hiram Chirino

Fix applied in trunk rev 474872 and in 4.1 branch rev 474876

> 4.1 RC1: META-INF/spring.schemas refers to building user 
> "file:/Users/chirino/"
> ---
>
> Key: AMQ-1016
> URL: https://issues.apache.org/activemq/browse/AMQ-1016
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1.0
> Environment: n/a
>Reporter: Endre Stølsvik
> Assigned To: Hiram Chirino
>Priority: Minor
> Fix For: 4.1.1, 4.2.0
>
>
> Referring to the 4.1 RC1 posted by Hiram Chirino  Oct 06, here:
>   http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974
> The META-INF file spring.schemas have the single line.
> "http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd"
> Notice "file:/" and "Users/chirino". Referring to 
> org.springframework.beans.factory.xml.PluggableSchemaResolver's javadoc: 
> "schema-location should also be a schema file in the classpath", and that 
> no-one can tell what structure I will have on my fs, this must be wrong. In 
> addition, I most probably won't have a user name "chirino".
> PS: In addition, the doc at
>   
> http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html
> refers as such:
> xmlns:amq="http://activemq.org/config/1.0";
>  .. and ..
> xsi:schemaLocation="http://activemq.org/config/1.0 
> http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd";
> Wouldn't it be nice if this was put at a better place than such a 
> snapshot-build URI? It could be put where it will reside when 4.1 actually is 
> out, w/o anyone being to angry about changes during the finalization period, 
> I personally believe.

-- 
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

Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)

[Hiram Chirino]

Thanks for the tip Guillaume!  Fix applied!

On 11/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

I think the problem comes from the fact that the xsds are not generated
in their default locations (target/xbean).
Changing the configuration to:
  target/xbean/activemq.xsd
should work.

On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Hi Endre,
>
> Thanks for the feedback but I don't agree that this issue should hold
> up the release.  I'm sure we can fix this in a subsequent bug fix
> release.
>
> BTW, if you submit a patch with the fix for this it would make getting
> the fix into the next release much easier :)
>
> Regards,
> Hiram
>
> On 11/14/06, Endre Stølsvik <[EMAIL PROTECTED]> wrote:
> > Hiram Chirino wrote:
> > > Hey folks,
> > >
> > > I was able to finally get around to doing a binary release candidate
> > > from the 4.1 branch.
> > >
> > > it's available here:
> > >
> > > 
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/
> > >
> > >
> > > Maven 1 and Maven 2 repos for this release can be found at:
> > > http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2
> > >
> > > Here's the wiki page for the release notes:
> > > http://incubator.apache.org/activemq/activemq-410-release.html
> > >
> > > Please vote to approve this release binary
> > >
> > > [ ] +1 Release the binary as Apache ActiveMQ  4.1.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > This vote is being cross posted to the general incubator mailing list
> > > also to expedite the voting process.
> >
> > Here's my useless -1:
> >
> > [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat
> > spring.schemas
> >
> > 
http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd
> >
> > Two things:
> >a) where is the xsd supposed to lay? (The _proper_ URL? Not this one
> > mentioned on this page:
> > http://incubator.apache.org/activemq/spring-support.html
> >
> > "http://activemq.org/config/1.0
> > 
http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd";
> >
> >b) The idea behind "spring.schemas" is, AFAIK, that the spring-magic
> > should kick in, and instead of going online to fetch the xsd, it will
> > find it in the classpath. Given that the "file:/Users/chirino/blahblah"
> > most definately isn't present on my machine, this will, AFAIK, result in
> > every startup of ActiveMQ with spring-xbeans integration online access
> > (which probably explains why all elements of the namespace-loading goes
> > lightning, except from the activeMQ one, which stalls for some seconds).
> >
> > In comparison, here's the spring.schemas for spring-2.0.jar actually
> > bundled with this ActiveMQ 4.1.0 RC2:
> >
> > [EMAIL 
PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$
> > cat spring.schemas
> >
> > 
http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd
> > 
http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd
> >
> > Note two things: the http-URL mentioned actually return the file, but in
> > addition, the resource specified is a classpath-resource, which exists:
> >
> > [EMAIL 
PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$
> > ls -la spring-*
> > -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd
> > -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd
> > -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd
> > -rw-r--r-- 1 endre endre  1999 2006-09-09 23:53 spring-tool-2.0.xsd
> > -rw-r--r-- 1 endre endre  5132 2006-09-09 23:53 spring-util-2.0.xsd
> >
> >
> > This is bug AMQ-1016:
> >https://issues.apache.org/activemq/browse/AMQ-1016
> >
> >
> > I think this should be fixed before 4.1.0 is released.
> >
> >
> > Kind regards,
> > Endre.
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>


--
Cheers,
Guillaume Nodet




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: ActiveMQ POM

[Hiram Chirino]

On 11/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

I think the main problem is that users will never
download newest versions.  IMHO, this would be a bad
idea.


yeah.



On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Thanks Fritz!
>
> I knew there had to be a reason that I was just not aware of.  What do
> you think would be the downsides of not using the special "SNAPSHOT"
> handling that maven provides?  What if we tagged our SNAPSHOT builds
> with something like like "DEVELOPMENT" instead of "SNAPSHOT".
>
> I'm guessing that problem would go away, but what other ones would we get?
>
> On 11/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > This is also my experience.
> > If we just use the real version 4.2-SNAPSHOT
> > for example, it should also work and maven
> > should be able to change (*nearly*) all these
> > occurrences when using the release plugin.
> >
> > I say nearly, because in ServiceMix, there are
> > some edge cases where this fail (when including
> > the version in files other than pom.xml like artifacts
> > resources for example).
> >
> > On 11/14/06, Fritz Oconer <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I added ${activemq-version} instead of ${project.version} basically as a
> > > workaround for build failures due to differences in timestamp. If we use
> > > ${project.version} then it will require all activemq type artifacts
> > > (specified as  in the parent pom.xml) to have the same 
timestamp
> > > as the parent. This becomes an issue when nightly-build deploy fails after
> > > some of the modules have been deployed causing some activemq modules to 
have
> > > different timestamp as the parent. We can change this back to using
> > > project.version but we need to make sure that nightly-build always deploys
> > > successfully or I wonder if there is another workaround for this?
> > >
> > > https://issues.apache.org/activemq/browse/AMQ-956
> > >
> > > Regards,
> > > Fritz
> > >
> > > - Original Message -
> > > From: "Hiram Chirino" <[EMAIL PROTECTED]>
> > > To: 
> > > Sent: Tuesday, November 14, 2006 8:48 PM
> > > Subject: ActiveMQ POM
> > >
> > >
> > > > Howdy,
> > > >
> > > > I was wondering if anybody knows why we are using
> > > > "${activemq-version}" instead of "${project.version}" in our ActiveMQ
> > > > poms??  When doing a release build, it's easy to forget that you need
> > > > to updated the version in to places.  Can't we just use the
> > > > "${project.version}" variable??
> > > >
> > > > --
> > > > Regards,
> > > > Hiram
> > > >
> > > > Blog: http://hiramchirino.com
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>


--
Cheers,
Guillaume Nodet




--
Regards,
Hiram

Blog: http://hiramchirino.com

[VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)

[Hiram Chirino]

Hey folks,

I was able to finally get around to doing a binary release candidate
from the 4.1 branch.

it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-410-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.1.0
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1


--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Updated: (AMQ-327) Orphanded/lost queue messages in various failover tests in two broker configuration

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-327?page=all ]

Hiram Chirino updated AMQ-327:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Orphanded/lost queue messages in various failover tests in two broker 
> configuration
> ---
>
> Key: AMQ-327
> URL: https://issues.apache.org/activemq/browse/AMQ-327
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0
> Environment: w2k & RH 9.0 jdk1.4.2
>Reporter: Dennis Cook
> Assigned To: John Heitmann
> Fix For: 4.2.0
>
> Attachments: AMQ-327.tar.gz
>
>
> Seems like the messages being passed to a broker where no client is connected 
> when the failed broker is re-established.  This message is "lost" until a 
> client is connected to this 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] Updated: (AMQ-375) advisory and MBean notification if a slow consumer is killed (with access to the userName in in the message)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-375?page=all ]

Hiram Chirino updated AMQ-375:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> advisory and MBean notification if a slow consumer is killed (with access to 
> the  userName in in the message)
> -
>
> Key: AMQ-375
> URL: https://issues.apache.org/activemq/browse/AMQ-375
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: james strachan
> 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-132) Remotting logging of clients under flow control

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-132?page=all ]

Hiram Chirino updated AMQ-132:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Remotting logging of clients under flow control
> ---
>
> Key: AMQ-132
> URL: https://issues.apache.org/activemq/browse/AMQ-132
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Barry Kaplan
> Fix For: 4.2.0
>
>
> When performance testing a system (or troubleshooting slowdowns in 
> production) it would be very helpful to know when any client has come under 
> flow control. This information would be logged (via jmx events?) including 
> the identification of the broker(s) that cannot keep up, and the 
> corresponding client(s) that have been throttled.

-- 
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-371) auto protocol switch from openwire to stomp on JMS client in case some 4.0 JMS client cannot work with some late version (like 8.3) of ActiveMQ server - we can always move ba

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-371?page=all ]

Hiram Chirino updated AMQ-371:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> auto protocol switch from openwire to stomp on JMS client in case some 4.0 
> JMS client cannot work with some late version (like 8.3) of ActiveMQ server - 
> we can always move back to stomp
> -
>
> Key: AMQ-371
> URL: https://issues.apache.org/activemq/browse/AMQ-371
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: JMS client
>Reporter: james strachan
> 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-367) Axis/JMS/ActiveMQ demo

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-367?page=all ]

Hiram Chirino updated AMQ-367:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Axis/JMS/ActiveMQ demo
> --
>
> Key: AMQ-367
> URL: https://issues.apache.org/activemq/browse/AMQ-367
> Project: ActiveMQ
>  Issue Type: New Feature
>Affects Versions: 3.1
>Reporter: Chris Berry
> Fix For: 4.2.0
>
> Attachments: axis-jms-demo.zip
>
>
> I have created a self-contained demo of using Axis/JMS/ActiveMQ
> James suggested that I pass it along for possible inclusion in the examples
> All of the code is in the enclosed ZIP
> Cheers,
> -- Chris 

-- 
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-361) duplicate delivery, already consumed messages are reconsumed after server restart

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-361?page=all ]

Hiram Chirino updated AMQ-361:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> duplicate delivery, already consumed messages are reconsumed after server 
> restart
> -
>
> Key: AMQ-361
> URL: https://issues.apache.org/activemq/browse/AMQ-361
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, Message Store, JCA Container
>Affects Versions: 4.0
> Environment: windows xp, jdk 1.5, embedded activemq 3.1 broker, jboss 
> 4.02, persistent messages with  derby db.
>Reporter: Gokturk Ozer
> Fix For: 4.2.0
>
> Attachments: 1.log
>
>
> I am running an embedded activemq broker inside jboss server, I send 1000 
> messages with ~10K size each to a queue, these messages are consumed by MDBs. 
> After all the messages are consumed, I check the queue via hermes, it also 
> shows no message in the queue. Everything works perfect up to this point. I 
> observe the problem after I stop the jboss server. I connect to derby 
> database via networkserver, I still see some messages in activemq_msgs table. 
> I shutdown derby networkserver and start jboss again, I see from the log that 
> some of the messages which were consumed previously, are being consumed 
> again. If I start the server without deploying the MDB and check the queue 
> via hermes, I see some but not all the messages which were consumed 
> previously still in the queue, before restart hermes was showing no messages. 

-- 
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-340) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-340?page=all ]

Hiram Chirino updated AMQ-340:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> allow topics in particular but also queues to have a 'namespace URI' like 
> WS-Notification
> -
>
> Key: AMQ-340
> URL: https://issues.apache.org/activemq/browse/AMQ-340
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
> Assigned To: james strachan
> Fix For: 4.2.0
>
>
> This would allow a real clean mapping from WS-N topics and ActiveMQ at the 
> protocol level. We could use the namespace as a level of indirection to map 
> to a broker, a cluster of brokers or even a particular area of a network etc. 
> The namespace could be a broker's name too.

-- 
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-404) winxp sp2 and mysql4.1.15 throw error

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-404?page=all ]

Hiram Chirino updated AMQ-404:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> winxp sp2 and mysql4.1.15  throw error
> --
>
> Key: AMQ-404
> URL: https://issues.apache.org/activemq/browse/AMQ-404
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Message Store
>Affects Versions: 3.2
>Reporter: tao
> Fix For: 4.2.0
>
>
> 2005-11-04 11:24:17,909 [Cleanup Timmer ] ERROR JDBCPersistenceAdapter
>  - Error in cleanup due to: com.mysql.jdbc.CommunicationsException: 
> Communications link failure due to underlying exception: 
> ** BEGIN NESTED EXCEPTION ** 
> java.net.SocketException
> MESSAGE: java.net.BindException: Address already in use: connect
> STACKTRACE:
> java.net.SocketException: java.net.BindException: Address already in use: 
> connect
>   at 
> com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284)
>   at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541)
>   at com.mysql.jdbc.Connection.(Connection.java:1474)
>   at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
>   at 
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
>   at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
>   at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
>   at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
>   at 
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
>   at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown 
> Source)
>   at java.lang.Thread.run(Thread.java:534)
> ** END NESTED EXCEPTION **
> Last packet sent to the server was 0 ms ago.
> com.mysql.jdbc.CommunicationsException: Communications link failure due to 
> underlying exception: 
> ** BEGIN NESTED EXCEPTION ** 
> java.net.SocketException
> MESSAGE: java.net.BindException: Address already in use: connect
> STACKTRACE:
> java.net.SocketException: java.net.BindException: Address already in use: 
> connect
>   at 
> com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284)
>   at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541)
>   at com.mysql.jdbc.Connection.(Connection.java:1474)
>   at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
>   at 
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
>   at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
>   at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
>   at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
>   at 
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:544)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter.getConnection(JDBCPersistenceAdapter.java:418)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter.cleanup(JDBCPersistenceAdapter.java:267)
>   at 
> org.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:257)
>   at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown 
> Source)
>   at java.lang.Thread.run(Thread.java:534)
> ** END NESTED EXCEPTION **
> Last packet sent to the server was 0 ms ago.
>   at com.mysql.jdbc.Connection.createNewIO(Connection.java:2607)
>   at com.mysql.jdbc.Connection.(Connection.java:1474)
>   at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
>   at 
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
>   at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
>   at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
>   at 
> o

[jira] Updated: (AMQ-376) security plugin which can use, say, LDAP to authenticate the user, then use a custom database table to associate roles to users and destinations to roles

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-376?page=all ]

Hiram Chirino updated AMQ-376:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> security plugin which can use, say, LDAP to authenticate the user, then use a 
> custom database table to associate roles to users and destinations to roles
> -
>
> Key: AMQ-376
> URL: https://issues.apache.org/activemq/browse/AMQ-376
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
> Fix For: 4.2.0
>
>
> BTW have added org.activemq.security.SecurityAdminMBean as a simple MBean API 
> to the admin of these things.
> Note we wanna cache the security state; then have a notification (via JMS 
> Topic) to flush/reload the data when folks change it - so performance is 
> great and the security configuration is highly dynamic

-- 
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-431) only send a message once for multiple consumers on the same connection (for topics)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-431?page=all ]

Hiram Chirino updated AMQ-431:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> only send a message once for multiple consumers on the same connection (for 
> topics)
> ---
>
> Key: AMQ-431
> URL: https://issues.apache.org/activemq/browse/AMQ-431
> Project: ActiveMQ
>  Issue Type: Improvement
>Reporter: james strachan
> Fix For: 4.2.0
>
>
> in 3.x we sent a message once with a list of all the MessageConsumers on it 
> so that we could avoid sending multiple messages over a socket when several 
> consumers are on the same connection. We should add back that optimisation

-- 
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-382) Security plugin using database tables for user, role, destination mapping; along with an MBean to administer them and a JMS subscription & notification of when they change so

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-382?page=all ]

Hiram Chirino updated AMQ-382:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Security plugin using database tables for user, role, destination mapping; 
> along with an MBean to administer them and a JMS subscription & notification 
> of when they change so we can reload the cache
> --
>
> Key: AMQ-382
> URL: https://issues.apache.org/activemq/browse/AMQ-382
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
> Fix For: 4.2.0
>
>
> So the idea is its cached in RAM for speed; then it gets reloaded from the 
> database if folks change 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] Updated: (AMQ-378) add pluggable Policy which is fired in a background Timer to detect slow consumers for non-durable topics and kill them (maybe with a pre-warning of being slow a little befor

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-378?page=all ]

Hiram Chirino updated AMQ-378:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> add pluggable Policy which is fired in a background Timer to detect slow 
> consumers for non-durable topics and kill them (maybe with a pre-warning of 
> being slow a little before being killed)
> -
>
> Key: AMQ-378
> URL: https://issues.apache.org/activemq/browse/AMQ-378
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
> 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-453) Clustering subscriptions

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-453?page=all ]

Hiram Chirino updated AMQ-453:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Clustering subscriptions
> 
>
> Key: AMQ-453
> URL: https://issues.apache.org/activemq/browse/AMQ-453
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
> Fix For: 4.2.0
>
>
> To be able to use ServiceMix WS-Notification in a cluster, we need to be able 
> to:
>   * attach some data to the subscription
>   * provide a way to retrieve subscription informations from the 
> NotificationBroker (using consumer advisory ?)
>   * cluster subscriptions (sticky durable subscriber ?)
> See irc log from 21/12/2005 from 21:14
> http://servlet.uwyn.com/drone/log/hausbot/servicemix/20051221

-- 
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-468) Queue load balancing - optionally give highest priority to the local connection, then local broker then networks

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-468?page=all ]

Hiram Chirino updated AMQ-468:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Queue load balancing - optionally give highest priority to the local 
> connection, then local broker then networks
> 
>
> Key: AMQ-468
> URL: https://issues.apache.org/activemq/browse/AMQ-468
> Project: ActiveMQ
>  Issue Type: Improvement
>Reporter: Rob Davies
> Fix For: 4.2.0
>
>
> For Queues, as an option assign the highest priority for dispatching to the 
> local connection, then the local broker, then the cluster etc.
> Right now we favour consumers on the local broker above consumers on remote 
> brokers. However we should prioritise consumers on the same session, 
> connection or VM transport above consumers in other processes etc

-- 
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-488) Broker side message redelivery due to client death should be tracked so that the message can be sent to the DLQ.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-488?page=all ]

Hiram Chirino updated AMQ-488:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Broker side message redelivery due to client death should be tracked so that 
> the message can be sent to the DLQ.
> 
>
> Key: AMQ-488
> URL: https://issues.apache.org/activemq/browse/AMQ-488
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: 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-512) enhance the command line tools to allow messages on queues to be browsed, queues to be purged, messages deleted, dead letter queues to be redispatched to orginal queues etc

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-512?page=all ]

Hiram Chirino updated AMQ-512:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> enhance the command line tools to allow messages on queues to be browsed, 
> queues to be purged, messages deleted, dead letter queues to be redispatched 
> to orginal queues etc
> 
>
> Key: AMQ-512
> URL: https://issues.apache.org/activemq/browse/AMQ-512
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
> Assigned To: Adrian Co
> Fix For: 4.2.0
>
>
> You should be able to reuse the MBeans for the operations of these commands

-- 
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-528) 4.0 M4 NullPointerException while shutting down

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-528?page=all ]

Hiram Chirino updated AMQ-528:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> 4.0 M4 NullPointerException while shutting down
> ---
>
> Key: AMQ-528
> URL: https://issues.apache.org/activemq/browse/AMQ-528
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
> Environment: RedHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL 
> 5.0.18 for Linux
>Reporter: Leon Hu
>Priority: Critical
> Fix For: 4.2.0, 4.0.3
>
>
> Setup: 
> 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast 
> discovery. activemq.xml: 
>   
>   
>   
>  dataSource="#mysql-ds"/> 
>   
>   
>   
>   discoveryUri="multicast://default"/> 
>   
>   
>   
>   
>   
>   
>   
>   
>   destroy-method="close"> 
> 
> value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/> 
>   
>   
>   
>   
> Similar for B2 and B3. 
> Two queues: Q1 and Q2. 
> Two producers, one for each queue, both producers connected to B1. 
> One Q1 cosumer connected to B1, another Q1 consumer on B2. 
> One Q2 consumer connected to B2, another Q2 consumer connected to B3. 
> Steps: 
> Start the brokers and start sending messages to the queue. 
> After a while, stop the brokers (Sequence does not matter) 
> See the errors in catalina.out of the Tomcat that has a broker with both 
> producers and consumers connected 
> The problems:
> 1. 
> Exception in thread "ActiveMQ Scheduler" java.lang.NullPointerException
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137)
>  Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ 
> Scheduler" Exception in thread "ActiveMQ Scheduler"  at 
> edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667)
>  at java.lang.Thread.run(Thread.java:595)
>  java.lang.NullPointerException
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils$SunPerfProvider.nanoTime(Utils.java:219)
>  Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ 
> Scheduler" Exception in thread "ActiveMQ Scheduler"  at 
> edu.emory.mathcs.backport.java.util.concurrent.helpers.Utils.nanoTime(Utils.java:99)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor.now(ScheduledThreadPoolExecutor.java:88)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.getDelay(ScheduledThreadPoolExecutor.java:137)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.take(DelayQueue.java:154)
>  at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>  Exception in thread "ActiveMQ Scheduler" Exception in thread "ActiveMQ 
> Scheduler"   at 
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:667)
>  at java.lang.Thread.run(Thread.java:595)
> 2. The same exception is logged to the log file (in my case catalina.out) for 
> hundreds of times, resulting a log file exceeding 150 MB in 2 minutes. 

-- 
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-732) Infinite recovery loop.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-732?page=all ]

Hiram Chirino updated AMQ-732:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Infinite recovery loop.
> ---
>
> Key: AMQ-732
> URL: https://issues.apache.org/activemq/browse/AMQ-732
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0
> Environment: Linux RHEL 3
>Reporter: Maxim Fateev
> Assigned To: Hiram Chirino
> Fix For: 4.2.0, 4.0.3
>
> Attachments: activemq-data-1-journal.tar.gz, 
> activemq-data-2-journal.tar.gz
>
>
> The simplest way to reproduce the problem:
> 1. Remove storage directory. 
> 2. Start broker using the following code:
>  public static void main(String[] args)  throws Exception {
>BrokerService broker = new BrokerService();
>broker.setPersistent(true);
>DefaultPersistenceAdapterFactory pFactory = new 
> DefaultPersistenceAdapterFactory();
>pFactory.setJournalLogFiles(1);
>pFactory.setJournalLogFileSize(2048);
>broker.setPersistenceFactory(pFactory);
>broker.setUseJmx(false);
>broker.addConnector("tcp://localhost:61616");
>broker.start();
>Thread.sleep(1l);
>}
> 3. Shutdown the broker.
> 4. Start broker.
> It enters infinite loop
> [  main] BrokerService  INFO  
> ActiveMQ null JMS Message Broker (localhost) is starting
> [  main] BrokerService  INFO  For 
> help or more information please see: http://incubator.apache.org/activemq/
> [  main] JDBCPersistenceAdapter INFO  
> Database driver recognized: [apache_derby_embedded_jdbc_driver]
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER 
> VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT, 
> MSG BLOB, PRIMARY KEY ( ID ) )
> [  main] DefaultJDBCAdapter DEBUG Could 
> not create JDBC tables; The message table already existed. Failure was: 
> CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250), 
> MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION BIGINT, MSG BLOB, 
> PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in 
> Schema 'APP'. SQLState: X0Y32 Vendor code: 2
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS 
> (MSGID_PROD,MSGID_SEQ)
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER)
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION)
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, 
> CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR 
> VARCHAR(250), LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, 
> SUB_NAME))
> [  main] DefaultJDBCAdapter DEBUG Could 
> not create JDBC tables; The message table already existed. Failure was: 
> CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, CLIENT_ID 
> VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250), 
> LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME)) 
> Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState: 
> X0Y32 Vendor code: 2
> [  main] JDBCPersistenceAdapter DEBUG 
> Cleaning up old messages.
> [  main] DefaultJDBCAdapter DEBUG 
> Executing SQL: DELETE FROM ACTIVEMQ_MSGS WHERE ( EXPIRATION<>0 AND 
> EXPIRATION ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
> [  main] DefaultJDBCAdapter DEBUG Deleted 
> 0 old message(s).
> [  main] JDBCPersistenceAdapter DEBUG Cleanup 
> done.
> [  main] JournalPersistenceAdapter  INFO  Journal 
> Recovery Started from: Active Journal: using 1 x 0.001953125 Megs at: 
> /workplace/fateev/install/activemq-4.0-SNAPSHOT/activemq-core/activemq-data/journal
> [  main] Journal

[jira] Updated: (AMQ-631) verify that HttpsTransportBrokerTest won't hang on other environment

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-631?page=all ]

Hiram Chirino updated AMQ-631:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> verify that HttpsTransportBrokerTest won't hang on other environment
> 
>
> Key: AMQ-631
> URL: https://issues.apache.org/activemq/browse/AMQ-631
> Project: ActiveMQ
>  Issue Type: Task
>  Components: Test Cases
>Affects Versions: 4.0 RC2
>Reporter: Adrian Co
> Assigned To: Adrian Co
> 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-594) SimpleNetworkTest hangs

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-594?page=all ]

Hiram Chirino updated AMQ-594:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> SimpleNetworkTest hangs
> ---
>
> Key: AMQ-594
> URL: https://issues.apache.org/activemq/browse/AMQ-594
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Affects Versions: 4.0 RC2
>Reporter: Darwin Flores
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
>
> The SimpleNetworkTest appears to be hanging in Linux platform

-- 
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-690) Allow the timer to be configured (and disabled) for the async clear down of durable topic messages

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-690?page=all ]

Hiram Chirino updated AMQ-690:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Allow the timer to be configured (and disabled) for the async clear down of 
> durable topic messages
> --
>
> Key: AMQ-690
> URL: https://issues.apache.org/activemq/browse/AMQ-690
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Affects Versions: 4.0 RC2
> Environment: all
>Reporter: Kyle Himmerick
>Priority: Minor
> Fix For: 4.2.0
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Allow the timer to be configured (and disabled) for the async clear down of 
> durable topic messages.
> So Retroactive Consumers can receive all messages ever sent on a durable topic

-- 
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-693) STOMP C client ready for Sun Workshop 6 and above on Solaris

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-693?page=all ]

Hiram Chirino updated AMQ-693:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> STOMP C client ready for Sun Workshop 6 and above on Solaris
> 
>
> Key: AMQ-693
> URL: https://issues.apache.org/activemq/browse/AMQ-693
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: JMS client
>Affects Versions: 4.0 RC2
> Environment: Sun Workshop 6 and above on Solaris 8 and above
>Reporter: vik dhawan
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: stompc.tar
>
>
> Here i  modified STOMP C client so it can run on Solaris platform. I 
> saparated producer and concumer for distributed tracking purposes. 
> Thanks!

-- 
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-567) Time in queue statistics handy

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-567?page=all ]

Hiram Chirino updated AMQ-567:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Time in queue statistics handy
> --
>
> Key: AMQ-567
> URL: https://issues.apache.org/activemq/browse/AMQ-567
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Affects Versions: 4.0 M4
> Environment: any
>Reporter: Scott Ellsworth
> Fix For: 4.2.0
>
>
> It would be very keen if the JMX console exposed queue statistics, such as 
> average length of time in queue for current messages, longest/shortest time 
> in queue for current messages, average time in queue for serviced messages 
> (as opposed to those waiting), longestlshortest time for same, and a list of 
> messages in the queue with when they were posted, and how long they have been 
> waiting.

-- 
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-767) avoid use of XHTML in activemq-web-console so things work great in IE 6

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-767?page=all ]

Hiram Chirino updated AMQ-767:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> avoid use of XHTML in activemq-web-console so things work great in IE 6
> ---
>
> Key: AMQ-767
> URL: https://issues.apache.org/activemq/browse/AMQ-767
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: james strachan
> 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-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-751?page=all ]

Hiram Chirino updated AMQ-751:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Extend ExceptionListener mechanism by creating a custom AMQ exception which 
> would provide more detail about the exception
> -
>
> Key: AMQ-751
> URL: https://issues.apache.org/activemq/browse/AMQ-751
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: JMS client, Broker
>Reporter: Massive Boisson
>Priority: Minor
> Fix For: 4.2.0
>
>
> To quote James:
> "I wonder if we could add a neater non-JMS extension to ActiveMQ to make it 
> easier to be notified asynchronously of which Message objects could not be 
> sent? I guess we could just use the ExceptionListener and use a custom type 
> of Exception which contained the Message object?"
> I think this would greatly increase the usefulness of async sends.

-- 
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-644) create Java Service Wrapper for ActiveMQ

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-644?page=all ]

Hiram Chirino updated AMQ-644:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> create Java Service Wrapper for ActiveMQ
> 
>
> Key: AMQ-644
> URL: https://issues.apache.org/activemq/browse/AMQ-644
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: james strachan
> Assigned To: Joseph Dennis Gapuz
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: wrapper.conf
>
>
> http://wrapper.tanukisoftware.org/doc/english/introduction.html

-- 
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-546) Network brokers have long reconnect times and they receive duplicate messages

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-546?page=all ]

Hiram Chirino updated AMQ-546:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Network brokers have long reconnect times and they receive duplicate messages
> -
>
> Key: AMQ-546
> URL: https://issues.apache.org/activemq/browse/AMQ-546
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 3.2, 4.0 M4
>    Reporter: Hiram Chirino
> Fix For: 4.2.0
>
>
> Initially reported at:
> http://forums.activemq.org/posts/list/202.page
> Notice that the forum has a JUnit test case that demonstrates the problem.

-- 
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-616) SpringTest hangs

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-616?page=all ]

Hiram Chirino updated AMQ-616:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> SpringTest hangs
> 
>
> Key: AMQ-616
> URL: https://issues.apache.org/activemq/browse/AMQ-616
> Project: ActiveMQ
>  Issue Type: Test
>  Components: Test Cases
>Affects Versions: 4.0 RC2
>Reporter: Darwin Flores
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
>
>  The SpringTest appears to be hanging in Linux platform

-- 
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-730) 4.x Javadoc

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-730?page=all ]

Hiram Chirino updated AMQ-730:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> 4.x Javadoc
> ---
>
> Key: AMQ-730
> URL: https://issues.apache.org/activemq/browse/AMQ-730
> Project: ActiveMQ
>  Issue Type: Wish
>  Components: Documentation
>Affects Versions: 4.0
>Reporter: jason evans
> Fix For: 4.2.0
>
>
> While ActiveMQ proves to be a high quality open-source JMS implementation the 
> incomplete Javadoc decreases developer understanding, development and test 
> time, and overall confidence of the adoption of each implementation. Although 
> I have submitted this as a wish I would like to see an effort to beef up the 
> documentation. I believe the community will benefit tremendously!

-- 
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-720) Use the Apache Commons CLI to parse the command line

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-720?page=all ]

Hiram Chirino updated AMQ-720:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Use the Apache Commons CLI to parse the command line
> 
>
> Key: AMQ-720
> URL: https://issues.apache.org/activemq/browse/AMQ-720
> Project: ActiveMQ
>  Issue Type: Improvement
>Affects Versions: 4.1.0
>Reporter: Adrian Co
> Assigned To: Adrian Co
> Fix For: 4.2.0
>
>
> Change the current way of parsing command line to use the apache commons cli 
> for a more standard format.

-- 
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-652) Potential infinite loop in ActiveMQ shutdown processing when in Geronimo

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-652?page=all ]

Hiram Chirino updated AMQ-652:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Potential infinite loop in ActiveMQ shutdown processing when in Geronimo
> 
>
> Key: AMQ-652
> URL: https://issues.apache.org/activemq/browse/AMQ-652
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 4.0
> Environment: Geronimo
>    Reporter: Hiram Chirino
> Fix For: 4.2.0
>
>
> Need to check to see if this is still valid against 4.x
> see:
> http://issues.apache.org/jira/browse/GERONIMO-1494

-- 
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-648) Changing the default JMX URL

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-648?page=all ]

Hiram Chirino updated AMQ-648:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Changing the default JMX URL
> 
>
> Key: AMQ-648
> URL: https://issues.apache.org/activemq/browse/AMQ-648
> Project: ActiveMQ
>  Issue Type: Wish
>  Components: Documentation
>Affects Versions: 4.0 M4
>Reporter: Bruce Mitchener
>Priority: Minor
> Fix For: 4.2.0
>
>
> Most of the command line utilities accept a jmxurl parameter, but there 
> doesn't seem to be an easy way to set up ActiveMQ to use a JMX URL other than 
> the default.  I'd wanted to do so for my development environment so that I 
> could run a JMX console on my desktop and connect to the server running on 
> another machine.  At ab0oo's suggestion, I'll use an SSH port forward (ssh 
> remotehost -L1099:localhost:1099) for now, but it'd be nice to see this 
> covered in some form in the JMX notes.

-- 
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-734) Network connections do not reconnect when using static: with failover=true

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-734?page=all ]

Hiram Chirino updated AMQ-734:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Network connections do not reconnect when using static: with failover=true
> --
>
> Key: AMQ-734
> URL: https://issues.apache.org/activemq/browse/AMQ-734
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 4.0
> Environment: winxp java1.5.6
>Reporter: tao
> Assigned To: Hiram Chirino
>Priority: Critical
> Fix For: 4.0.1, 4.2.0
>
>
> If I pull out RJ45 port from net card ,waiting a time ,then put  RJ45 port 
> net card .Network is resume.Other computer always throw errors and net 
> channel can't work.

-- 
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-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-796?page=all ]

Hiram Chirino updated AMQ-796:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Client may shtudown when failover connection is reconnecting.  We need to 
> maintain at least 1 non-daemon thread alive.
> --
>
> Key: AMQ-796
> URL: https://issues.apache.org/activemq/browse/AMQ-796
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Fix For: 4.2.0, 4.0.3
>
>
> Dejan Reported on the User lists:
> Hi,
> after some experiments I found that this problem only exists if there are no
> other threads in the application. It seems like connection thread dies
> before it manages to reconnect. By starting another thread in the
> application, it succeeds to recover from master failure and reconnect to the
> slave broker. So I have a workaround for now, but it would be nice to make
> this work even for simple (single-threaded) clients.
> Regards,
> Dejan

-- 
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-815) generate a warning by default if a client connects via openwire using a different release version of the broker

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-815?page=all ]

Hiram Chirino updated AMQ-815:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> generate a warning by default if a client connects via openwire using a 
> different release version of the broker
> ---
>
> Key: AMQ-815
> URL: https://issues.apache.org/activemq/browse/AMQ-815
> Project: ActiveMQ
>  Issue Type: Improvement
>Reporter: james strachan
> Assigned To: Hiram Chirino
> Fix For: 4.2.0
>
>
> While we can be quite liberal in supporting backwards compatible clients, the 
> default should be to warn folks if they connect via different versions - as 
> thats often an indication of classpath issues.
> Maybe have 3 options - lenient (try to work with anything), warning (just log 
> warning on connection), strict (disconnect non-similar version clients)

-- 
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-795) security plugin to deal with temporary queue and topics better

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-795?page=all ]

Hiram Chirino updated AMQ-795:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> security plugin to deal with temporary queue and topics better
> --
>
> Key: AMQ-795
> URL: https://issues.apache.org/activemq/browse/AMQ-795
> Project: ActiveMQ
>  Issue Type: Improvement
>Reporter: james strachan
> Assigned To: Jonas Lim
> Fix For: 4.2.0
>
>
> Allow a role to be specified for read/write/admin of temporary queue and 
> temporary topics

-- 
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-804) Use of Temporary Destinations over broker networks can cause the network bridges to die.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-804?page=all ]

Hiram Chirino updated AMQ-804:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Use of Temporary Destinations over broker networks can cause the network 
> bridges to die.
> 
>
> Key: AMQ-804
> URL: https://issues.apache.org/activemq/browse/AMQ-804
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>    Reporter: Hiram Chirino
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
>
> And when the bridge dies, it is not re-established.

-- 
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-821) Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-821?page=all ]

Hiram Chirino updated AMQ-821:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Openwire code (from HEAD) doesn't compile on .Net 1.1 - uses sizeof(int)
> 
>
> Key: AMQ-821
> URL: https://issues.apache.org/activemq/browse/AMQ-821
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
> Environment: Net 1.1
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: ActiveMQTextMessage.cs.diff, nant.build.diff
>
>
> sizeof(int) is unsafe code on Net-1.1.
> I've attached patches to put the code in unsafe { ... } block, plus fix to 
> nant.build.  Same code also (still) compiles on 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-876) Kaha DB cannot locate queue data files

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-876?page=all ]

Hiram Chirino updated AMQ-876:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Kaha DB cannot locate queue data files
> --
>
> Key: AMQ-876
> URL: https://issues.apache.org/activemq/browse/AMQ-876
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Message Store
>Affects Versions: 4.1.0
> Environment: WinXP
>Reporter: Vadim Pesochinskiy
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
> Attachments: test.zip
>
>
> Keep getting exception below.  Note that you are looking for queue-data-1, 
> but actual file name is data-queue-data-1
> $ pwd
>   /cygdrive/d/amq/activemq-kaha/kaha.db
> $ ls
> data-kaha-1  data-queue-data-1  index-kaha  index-queue-data  
> index-transactions
> javax.jms.JMSException: java.io.IOException: Could not locate data file 
> queue-data-1
> at 
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46)
> at 
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1154)
> at 
> org.apache.activemq.TransactionContext.commit(TransactionContext.java:260)
> at 
> org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:464)
> at 
> com.barra.cp.common.io.MultiQueueReceiver.onMessage(MultiQueueReceiver.java:163)
> at 
> com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.runMultiQueue(SingleMessageMultiQueueReceiver.java:176)
> at 
> com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.doRun(SingleMessageMultiQueueReceiver.java:143)
> at 
> com.barra.cp.common.io.SingleMessageMultiQueueReceiver$OneMessageAtATime.run(SingleMessageMultiQueueReceiver.java:124)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.activemq.kaha.RuntimeStoreException: 
> java.io.IOException: Could not locate data file queue-data-1
> at 
> org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:340)
> at 
> org.apache.activemq.kaha.impl.MapContainerImpl.remove(MapContainerImpl.java:265)
> at 
> org.apache.activemq.store.kahadaptor.KahaMessageStore.removeMessage(KahaMessageStore.java:68)
> at 
> org.apache.activemq.store.kahadaptor.KahaTransaction.commit(KahaTransaction.java:92)
> at 
> org.apache.activemq.store.kahadaptor.KahaTransactionStore.commit(KahaTransactionStore.java:95)
> at 
> org.apache.activemq.transaction.LocalTransaction.commit(LocalTransaction.java:68)
> at 
> org.apache.activemq.broker.TransactionBroker.commitTransaction(TransactionBroker.java:154)
> at 
> org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92)
> at 
> org.apache.activemq.broker.BrokerFilter.commitTransaction(BrokerFilter.java:92)
> at 
> org.apache.activemq.broker.MutableBrokerFilter.commitTransaction(MutableBrokerFilter.java:102)
> at 
> org.apache.activemq.broker.AbstractConnection.processCommitTransactionOnePhase(AbstractConnection.java:330)
> at 
> org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:99)
> at 
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:228)
> at 
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:63)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92)
> at 
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:123)
> at 
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:123)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:88)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:127)
> ... 1 more
> Caused by: java.io.IOException: Could not locate data file queue-data-1
> at 
> org.apache.activemq.kaha.impl.DataManager.getDataFile(DataManager.java:117)
> at 
> org.apache.activemq.kaha.impl.StoreDataReader.readItem(StoreDataReader.java:62)
> at 
> org.apache.activemq.kaha.impl.DataManager.readItem(DataManager.java:121)
> at 
> org.apache.activemq.kaha.impl.MapContainerImpl.getValue(MapContainerImpl.java:337)
> ... 20 more

-- 
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-861) Kaha DB files are not removed

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-861?page=all ]

Hiram Chirino updated AMQ-861:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Kaha DB files are not removed
> -
>
> Key: AMQ-861
> URL: https://issues.apache.org/activemq/browse/AMQ-861
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0.1
> Environment: Win XP, Java 5
>Reporter: Vadim Pesochinskiy
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
>
> I have request-response point to point test case, which I ran for 12 hours. 
> Each message is exactly 5KBytes. This is what I see in the Kaha directory:
>  779 Aug  1 17:03 roots-data1
>  32M Aug  2 15:28 queue-data4
>  32M Aug  2 18:02 queue-data5
>  32M Aug  2 19:03 queue-data6
>  32M Aug  2 20:04 queue-data7
>  32M Aug  2 21:05 queue-data8
>  32M Aug  2 22:07 queue-data9
>  32M Aug  2 23:08 queue-data10
>  32M Aug  3 00:09 queue-data11
>  32M Aug  3 01:10 queue-data12
>  32M Aug  3 02:12 queue-data13
>  32M Aug  3 03:13 queue-data14
>  32M Aug  3 04:19 queue-data15
>  32M Aug  3 05:20 queue-data16
>  32M Aug  3 06:21 queue-data17
>  32M Aug  3 07:22 queue-data18
>  32M Aug  3 08:23 queue-data19
>  19M Aug  3 09:25 queue-data20
> 8.6K Aug  3 09:52 kaha.idx

-- 
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-908) Authorization plugin should have configurable principal classes

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-908?page=all ]

Hiram Chirino updated AMQ-908:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Authorization plugin should have configurable principal classes
> ---
>
> Key: AMQ-908
> URL: https://issues.apache.org/activemq/browse/AMQ-908
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 4.0.1
>Reporter: Aaron Mulder
> Fix For: 4.2.0, 4.0.3
>
>
> Currently, if you configure the authorization plugin, it assumes that all 
> principals listed should be of type 
> {{org.apache.activemq.jaas.GroupPrincipal}}.  This is OK if you're using 
> ActiveMQ LoginModules, but since there's a fairly small supply of those, it 
> would be great if you could use arbitrary login modules and tell the 
> authorization plugin which principal classes to use.  For example, 
> {{groupClass="weblogic.security.principal.WLSGroupImpl}} or something like 
> that.  A good first step would be to let you change the group class.  A good 
> second step would be to let you specify user and group classes and then 
> somehow indicate which names are which (e.g. 
> {{admin="administrators,user:aaron,user:bob"}} or whatever).  Someday maybe 
> it will be nice to support any arbitrary combination of principal classes but 
> that seems far away.
> When instantiating the principal classes, I imagine we should use a 
> constructor with a single String argument if available, or else a default 
> constructor plus a "setName" method, or else I guess bail.

-- 
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-943) Pluggable Stomp Message Mapping

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-943?page=all ]

Hiram Chirino updated AMQ-943:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Pluggable Stomp Message Mapping
> ---
>
> Key: AMQ-943
> URL: https://issues.apache.org/activemq/browse/AMQ-943
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Transport
>Affects Versions: 4.1.0
>Reporter: Dejan Bosanac
> Assigned To: Brian McCallister
> Fix For: 4.2.0
>
> Attachments: protocol-mapping.patch
>
>
> I have finally found time to finish this. Here's the draft version of the 
> Pluggable Stomp Message Mapping implementation.
> Few notes:
> - New interface has been defined: ProtocolMapping (I wanted to use the same 
> name as the message header that we check)
> - There are two implementations of this interface: DefaultProtocolMapping and 
> ByteProtocolMapping
> - I used FactoryFinder to create appropriate mapper. The finder use the 
> following path to find keys: 
> META-INF/services/org/apache/activemq/transport/mapping/ (we can change this 
> if you want)
> - The appropriate mapper is used according to the "protocol-mapping" header 
> in the CONNECT message. For example protocol-mapping:byte for 
> ByteProtocolMapping handler.
> - Currently I have implemented only the mapper for BytesMessage since I 
> wasn't sure whether you want to integrate JSON mapper for MapMessages or 
> distribute it in a separate library.
> - I have changed the test case that tests subscription for byte messages
> - This solution is not compatible with current mapping for byte messages. If 
> you want backward compatibility, I can hard-code it in a ProtocolConverter 
> class (as it was) since it could not be implemented through this mechanism.
> TODO:
> - test it more (create more unit test cases and test it more in a real 
> environment)
> - create a proper documentation so others can create their handlers.
> - create a proper JavaDoc documentation for key interfaces and classes
> - create JSON mapper (integrated or external)
> - fix STOMP client(s)
> Give it a try and let me know your impressions
> Dejan Bosanac 

-- 
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-979) Allow NetworkConnections to bi-directional

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-979?page=all ]

Hiram Chirino updated AMQ-979:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Allow NetworkConnections to bi-directional
> --
>
> Key: AMQ-979
> URL: https://issues.apache.org/activemq/browse/AMQ-979
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Rob Davies
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
>
> Network connections are generally one way - with messages only flowing out 
> from the broker that made the network connection.
> In order to support WAN hub/spoke - where the central broker is behind a 
> firewall, and can only receive inbound connections, it is necessary to enable 
> optional b-idirectional network connections.
> This issue was raised on the activemq-dev list: 
> http://www.nabble.com/Having-some-trouble-making-a-simple-network...-tf2449661.html

-- 
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-967) setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but doc says otherwise

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-967?page=all ]

Hiram Chirino updated AMQ-967:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> setting maximumRedeliveries to -1 is equivalent to maximumRedeliveries=0, but 
> doc says otherwise
> 
>
> Key: AMQ-967
> URL: https://issues.apache.org/activemq/browse/AMQ-967
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Affects Versions: 4.1.0, 4.0.2
>Reporter: Renaud Bruyeron
> Fix For: 4.2.0, 4.0.3
>
> Attachments: patch.txt
>
>
> The documentation 
> (http://incubator.apache.org/activemq/resource-adapter-properties.html) 
> suggests that setting maximumRedeliveries to -1 means "no maximum", i.e. 
> infinite retries.
> However, my tests (and the code) show that -1 is equivalent to 0 (i.e. no 
> redelivery).
> The patch attempts to fix this.

-- 
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-962) Messages are read from queue but not removed

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-962?page=all ]

Hiram Chirino updated AMQ-962:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Messages are read from queue but not removed
> 
>
> Key: AMQ-962
> URL: https://issues.apache.org/activemq/browse/AMQ-962
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client, Broker
>Affects Versions: 4.0.1
> Environment: Java Virtual Machine: Java HotSpot(TM) Server VM version 
> 1.5.0_06-b05JIT 
> compiler:  HotSpot Server Compiler
> Operating System:  Windows XP 5.1
> Architecture: x86
> Number of processors:  1
> Total physical memory:   1,048,048 kbytes
> Free physical memory:     107,240 kbytes
> Committed virtual memory:     374,048 kbytes
> Total swap space:   2,518,944 kbytes
> Free swap space:     721,416 kbytes
>Reporter: Randy
>Priority: Critical
> Fix For: 4.2.0
>
>
> Using Spring, configured a VM message broker (non-persistant) and a message 
> consumer that reads messages from queue.
> Messages are read from queue, but despite calling message.acknowledge(); 
> messages remain on the queue (and consume memory).
> I turned off optimiseAcknowledge.
> May be related to bug# AMQ-716.
> 
>   
> 
>   
> 
>
>  class="org.apache.activemq.pool.PooledConnectionFactory">
>   
> 
>   
> vm://localhost
>   
>   
> false
>
> 
>   
> 
>  class="org.springframework.jms.core.JmsTemplate">
>   
>   
>   
> 

-- 
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-998) add support for stomp+ssl

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-998?page=all ]

Hiram Chirino updated AMQ-998:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> add support for stomp+ssl
> -
>
> Key: AMQ-998
> URL: https://issues.apache.org/activemq/browse/AMQ-998
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Transport
>Reporter: james strachan
> 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-984) make the "slave" status of a broker available through JMX (in jdbc-master-slave mode)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-984?page=all ]

Hiram Chirino updated AMQ-984:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> make the "slave" status of a broker available through JMX (in 
> jdbc-master-slave mode)
> -
>
> Key: AMQ-984
> URL: https://issues.apache.org/activemq/browse/AMQ-984
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 4.1.0
>Reporter: Renaud Bruyeron
>Priority: Minor
> Fix For: 4.2.0
>
>
> Right now, it is not possible to know that a broker is in "Attempting to 
> acquire the exclusive lock to become the Master broker" mode via JMX, even 
> though this would be a natural place to find out.
> Do you think it would be possible to expose the DatabaseLocker or the 
> JDBCPersistenceAdapter over JMX so that a simple boolean isMaster() can be 
> queried?

-- 
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-1014) Invalid Schema URL for example config file

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1014?page=all ]

Hiram Chirino updated AMQ-1014:
---

Fix Version/s: 4.2
   (was: 4.1.0)

> Invalid Schema URL for example config file
> --
>
> Key: AMQ-1014
> URL: https://issues.apache.org/activemq/browse/AMQ-1014
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Test Cases
>Affects Versions: 4.1.0
>Reporter: Bernhard Wellhöfer
> Fix For: 4.2.0
>
> Attachments: XMLSpy1.png, XMLSpy2.png
>
>
> The config file 
> https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/spring-embedded-xbean.xml
>  should ise http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd as schema 
> URL for Spring 2.0. Moreover and more worse the used schema URL 
> (http://activemq.org/config/1.0 
> http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd)
>  for ActiveMQ points to a schema file which is not valid. 

-- 
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-999) Message dispatcher issues (use dedicated dispatching thread for each session)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-999?page=all ]

Hiram Chirino updated AMQ-999:
--

Fix Version/s: 4.2
   (was: 4.1.0)

> Message dispatcher issues (use dedicated dispatching thread for each session)
> -
>
> Key: AMQ-999
> URL: https://issues.apache.org/activemq/browse/AMQ-999
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: NMS (C# client)
>Affects Versions: 4.0.2
> Environment: Windows
>Reporter: Rob Lugt
> Assigned To: james strachan
> Fix For: 4.2.0
>
> Attachments: amq999-patch.txt, AtomicBoolean.cs, DispatchingThread.cs
>
>
> There are a number of issues with the dispatching of inbound messages.
> - A slow consumer will potentially use and block all ThreadPool threads
> - Use of a ThreadPool thread to dispatch a single message is inefficient due 
> to context switching
> - No mechanism to suspend asynchronous delivery to a session (i.e. 
> Connection.Stop() is currently a no-op)
> - Retroactive consumer is currently broken because retoractive messages are 
> delivered before the listener delegate is assigned.
> - [minor] Application cannot predict which thread messages will be dispatched 
> on
> All of these problems can simply be resolved by creating a dedicated 
> dispatcher thread for a session

-- 
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-1010) Simplify SimpleAuthenticationPlugin Configuration

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1010?page=all ]

Hiram Chirino updated AMQ-1010:
---

Fix Version/s: 4.2
   (was: 4.1.0)

> Simplify SimpleAuthenticationPlugin Configuration
> -
>
> Key: AMQ-1010
> URL: https://issues.apache.org/activemq/browse/AMQ-1010
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 4.1.0
>Reporter: Dejan Bosanac
> Fix For: 4.2.0
>
> Attachments: simple-auth.patch
>
>
> In order to be useful, SimpleAuthenticationPlugin has to be easy to configure 
> and well documented. I added some additional logic in order to make it play 
> well with XBean. The patch also contains an additional class 
> (AuthenticationUser) and the appropriate test suite.
> The example configuration is as follows (taken from simple-auth-broker.xml):
>   
>   
>password="manager"  group="users,admins"/>
>password="password"  group="users"/>
>password="password"  group="guests"/>
>   
>   
> I will make a proper documentation for the "Security" page if this 
> functionality ever gets committed in the repository.

-- 
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-1002) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1002?page=all ]

Hiram Chirino updated AMQ-1002:
---

Fix Version/s: 4.2
   (was: 4.1.0)

> 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.2.0
>
>
> 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] Updated: (AMQ-1013) Web console does not escape message details (/activemq-web-console/message.jsp)

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1013?page=all ]

Hiram Chirino updated AMQ-1013:
---

Fix Version/s: 4.2
   (was: 4.1.0)

> Web console does not escape message details 
> (/activemq-web-console/message.jsp)
> ---
>
> Key: AMQ-1013
> URL: https://issues.apache.org/activemq/browse/AMQ-1013
> Project: ActiveMQ
>  Issue Type: Improvement
> Environment: OS X 10.4.8 / Java 1.5 / ActiveMQ 4.1-SNAPSHOT
>Reporter: Stefan Arentz
> Fix For: 4.2.0
>
>
> The web console does not html-escape the message contents on the /message.jsp 
> page which makes it difficult to see a xml test message.

-- 
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

Re: Lets vote: activemq-cpp-1.0 release

[Hiram Chirino]

+1

On 11/9/06, Nathan Mittler <[EMAIL PROTECTED]> wrote:

Agreed - this is long overdue!  I've just tried it out on linux and all is
well.

+1

On 11/9/06, Timothy Bish <[EMAIL PROTECTED]> wrote:
>
>
> I think it's about time we start this ball rolling, so let's take a vote
> on
> whether to call the source archive located here:
> http://people.apache.org/~tabish the official 1.0 release of activemq-cpp
>
> What do you think, is it time to put this one to bed?
>
> -
> Timothy A. Bish
>
>
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Activemq 4.0.2 - stops sending message after some time

[Hiram Chirino]

Sandeep, the memory profile is indeed that needed bits.  Could you
upload it to a publicly accessible website and post a link?

On 11/8/06, Sandeep Chayapathi <[EMAIL PROTECTED]> wrote:

Here is the profile data from YourKit profiler (cpu and telemetry). I
cannot attach the memory profile, as the zip file is quite large (70M).
In case you need that file, mail me back. Later I will mail a simplified
test case. Thanks.

- Sandeep





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release Apache ActiveMQ 4.0.2 (RC 6)

[Hiram Chirino]

Unless I'm lossing email... I think we still need a few more votes
from incubator pmc members to make this release official.  Anybody
around that can help check this release??

On 10/29/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Some last minute NOTICE issues were still present in the 5th release
candidate of the
4.0.2 build.  We have also received confirmation from Apache legal
discuss that it's ok to include work covered by the "Creative Commons
Attribution" license.  I have cut and RC 6 of the 4.0.2 build with the
fixes and it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6/maven1/incubator-activemq/distributions/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-402-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.0.2
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1

--
Regards,
Hiram

Blog: http://hiramchirino.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Creating a 4.1 Branch

[Hiram Chirino]

Well folks,

I think it's about time we get serious about doing a 4.1 release.  In
that effort I'm going to create a 4.1 branch in SVN unless anybody has
an objection.  Please let me know!

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Activemq 4.0.2 - stops sending message after some time

[Hiram Chirino]

Hi Sandeep,

Could you post a memory snapshot of the broker from a tool like
jprofiler or yourkit?  That would help folks help you identify what is
holding the memory.

Also if you can simplify your use case down to 1 simple unit test it
would help folks be able to reproduce your problem.

On 11/7/06, Sandeep Chayapathi <[EMAIL PROTECTED]> wrote:

Update:

 I was using Stomp protocol for both the Publishers and Consumers. A
check with jconsole showed me that there were around 20,000 threads. To
test it further, I modified my stomp library (written in perl), to close
connection and re-connect, every 100 messages. Activemq, consistently
stopped responding, and the memory used was around 400MB (with another
500 MB of physical memory free) and the number of threads were 20,000.
On selecting the MBean tab in jconsole, I got java.net.connection exception.

 For the next test, I used the ProducerTool (bundled with the activemq
binaries). The only change was that the ProducerTool would run in a
while(true){} loop. The idea was to see if/when activemq would break.
Again, there were 8 Producers and 3 Consuemers (of which, one of them
was the bundled ConsumerTool and the remaining used Stomp). Around
400,000th message (roughly the same number on all 8 processes), the
jconsole showed non-heap memory used as around 400MB and the number of
threads at 200, when activemq stopped responding. I had enabled DEBUG
messages, but no error message were reported in the log. I was able to
use jconsole to look into the enqueue and dequeue count.

This scenario can be duplicated using the bundled ProducerTool and
ConsumerTool. I guess the average message/second was 150 per Producer
process. Also a live environment can easily have 8 or more producers
(although not with such a high message/second rate), also this set of
tests show me that the Stomp implementation is not as stable as desired.

Does anyone here use activemq on a production server, if so under what
load and what is the availability of the activemq service ? How can I
setup a stable activemq server in a high availability manner. Thanks

- Sandeep

Sandeep Chayapathi wrote:
> Hi all,
>
>  Recently I noticed that the activemq would stop sending message to
> the consumers after some time. Here is a unscientific test to
> duplicate this issue:
> The test involved creating around 7 durable subscriptions and
> ctrl+c'ing them. Once the durable subscriptions were registered,
> around 8 publisher processes were started, each process wrote a
> 'fortune cookie' , in an infiniteloop, to the activemq server. In
> parallel,  3 subscriber processes were started. The 3 subscribers were
> randomly stopped and started, cyclically. At about 15000 messages (on
> each of the 8 write processes), activemq stopped sending the message
> to to the subscribers and the publisher processes hung on "syswrite"
> to activemq.  Then another publisher process was started, activemq
> actually accepted messages, but none of the subscribers received it.
>
> The next test involved, using mysql as the data store (instead of the
> default journalled db). The same steps were followed and at about
> 18000 messages (on each of the 8 processes), activemq stopped sending
> messages to the subscribers.
>
> Im using activemq 4.0.2. Any suggestions/help is appreciated. Thanks
>
> - Sandeep
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Resolved: (AMQ-1031) Message delivered out of order to a MessageListener when session is transced and a rollback occurs.

[Hiram Chirino (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1031?page=all ]

Hiram Chirino resolved AMQ-1031.


Resolution: Fixed

Fixed in trunk revision 472345

> Message delivered out of order to a MessageListener when session is transced 
> and a rollback occurs.
> ---
>
> Key: AMQ-1031
> URL: https://issues.apache.org/activemq/browse/AMQ-1031
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> This is actually spotted by a message in the broker log saying that 
> "Acknowledgment out of sync (Normally occurs when failover connection 
> reconnects)" or in some previous version of ActiveMQ, an async exception 
> being delivered to the client with a similar error message.

-- 
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