Re: [VOTE] a few more geronimo-spec alpha-1 artifacts

[Hiram Chirino]

+1

> Hello guys,
>
> As announced few weeks ago let's try to release more alpha of our EE 7
> spec jars. I added javamail as well since it got some nice fixes
> (thanks Hendrik mainly) which are important to release since I saw too
> much people replacing our implementation by javax one for small
> blocking bugs fixed since weeks on SNAPSHOTs. Also note this release
> train was mainly motivated by AMQ which is waiting JMS 2 API to
> release their version 6 (thanks to John D Ament for the patch on the
> API BTW).
>
> Here is the list of artifacts included in this vote:
>
> - geronimo-javamail_1.4 + geronimo-javamail_1.4_mail +
> geronimo-javamail_1.4_provider
> - geronimo-ejb_3.2_spec
> - geronimo-javamail_1.4_spec
> - geronimo-jaxrs_2.0_spec
> - geronimo-jms_2.0_spec
> - geronimo-jta_1.2_spec
>
>
> Here is the staging repo
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-1012
>
> I bet you will find the source/javadoc/etc yourself.
>
> My key can be found at
> https://svn.apache.org/repos/asf/geronimo/KEYS
>
> please VOTE
> [+1] all fine, ship it
> [+0] don't care
> [-1] stop, because ${reason}
>
> here is my +1
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

Re: [VOTE] XBean 3.15 release

[Hiram Chirino]

+1

On Wed, Nov 6, 2013 at 11:55 PM, David Blevins  wrote:
> Ok, release rolled!
>
> Binaries:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-086/
>
> Tag:
>
> http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.15/
>
>
> 72 hours for voting! :)
>
>
> -David
>



-- 
Hiram Chirino

Engineering | Red Hat, Inc.

hchir...@redhat.com | fusesource.com | redhat.com

skype: hiramchirino | twitter: @hiramchirino

blog: Hiram Chirino's Bit Mojo

XBean JIRA Roadmap

[Hiram Chirino]

Hi,

I was about to cleanup/close up the 3.9 XBean release in JIRA and I
noticed there are lots of unressolved issues assigned to 3.8 and 3.9,
Should I just moved those to 3.10?

Regards,
Hiram

FuseSource
Web: http://fusesource.com/

[RESULT][VOTE] Release XBean 3.9

[Hiram Chirino]

Results of the XBean 3.9 release vote:
Vote passes with 4 binding +1 votes.
Thanks to all who voted.  I'll start pushing out the release shortly.

Regards,
Hiram

FuseSource
Web: http://fusesource.com/

Re: [VOTE] Release XBean 3.9

[Hiram Chirino]

72 Hours have passed.  Closing the vote, I post the results in a new thread.

Regards,
Hiram

FuseSource
Web: http://fusesource.com/



On Mon, Dec 19, 2011 at 9:30 AM, James Strachan  wrote:
> +1
>
> On 16 December 2011 14:31, Hiram Chirino  wrote:
>> Please vote for the geronimo xbean 3.9 release,.
>>
>> The components up for vote are:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip
>>
>> Staging repo is here:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/
>>
>> tag is here:
>> https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/
>>
>> Vote open 72 hours
>>
>> [ ] +1 release this
>> [ ] 0 don't care
>> [ ] -1 don't release this (please explain)
>>
>> Here's my +1
>>
>> Regards,
>> Hiram
>>
>> FuseSource
>> Web: http://fusesource.com/
>
>
>
> --
> James
> ---
> FuseSource
> Email: ja...@fusesource.com
> Web: http://fusesource.com
> Twitter: jstrachan, fusenews
> Blog: http://macstrac.blogspot.com/
>
> Open Source Integration and Messaging

Re: [VOTE] Release XBean 3.9

[Hiram Chirino]

Not yet,

I'm mainly cutting this as we want to roll out a new ActiveMQ release
and want to include xbean-191.

Regards,
Hiram

FuseSource
Web: http://fusesource.com/



On Fri, Dec 16, 2011 at 6:23 PM, David Jencks  wrote:
> Have you verified that current xbean-blueprint (including my inclusion of 
> necessary aries blueprint compendium.cm classes) works with the aries 
> blueprint compatibility bundles (small bundles) with activemq?  I'm not yet 
> at a point to verify this in geronimo, although I hope to be able to shortly.
>
> thanks
> david jencks
>
> On Dec 16, 2011, at 6:31 AM, Hiram Chirino wrote:
>
>> Please vote for the geronimo xbean 3.9 release,.
>>
>> The components up for vote are:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip
>>
>> Staging repo is here:
>> https://repository.apache.org/content/repositories/orgapachegeronimo-349/
>>
>> tag is here:
>> https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/
>>
>> Vote open 72 hours
>>
>> [ ] +1 release this
>> [ ] 0 don't care
>> [ ] -1 don't release this (please explain)
>>
>> Here's my +1
>>
>> Regards,
>> Hiram
>>
>> FuseSource
>> Web: http://fusesource.com/
>

[VOTE] Release XBean 3.9

[Hiram Chirino]

Please vote for the geronimo xbean 3.9 release,.

The components up for vote are:
https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.tar.gz
https://repository.apache.org/content/repositories/orgapachegeronimo-349/org/apache/xbean/xbean/3.9/xbean-3.9-source-release.zip

Staging repo is here:
https://repository.apache.org/content/repositories/orgapachegeronimo-349/

tag is here:
https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.9/

Vote open 72 hours

[ ] +1 release this
[ ] 0 don't care
[ ] -1 don't release this (please explain)

Here's my +1

Regards,
Hiram

FuseSource
Web: http://fusesource.com/

Re: Releasing XBean 3.9

[Hiram Chirino]

Ok,

I'm really going to start cutting a release candidate for XBean 3.9.
I've got my fingers crossed that the release plugin is working
smoothly!

Regards,
Hiram

FuseSource
Web: http://fusesource.com/



On Thu, Oct 27, 2011 at 12:57 PM, Kevan Miller  wrote:
>
> On Oct 27, 2011, at 9:30 AM, Hiram Chirino wrote:
>
>> I've just added in a little feature which we really need in the next
>> version of ActiveMQ.  Details at:
>> https://issues.apache.org/jira/browse/XBEAN-191
>>
>> Are there any problems with doing a quick XBean 3.9 release soon?
>
> No problems from my perspective.
>
> --kevan
>

Releasing XBean 3.9

[Hiram Chirino]

I've just added in a little feature which we really need in the next
version of ActiveMQ.  Details at:
https://issues.apache.org/jira/browse/XBEAN-191

Are there any problems with doing a quick XBean 3.9 release soon?

Regards,
Hiram

FuseSource
Web: http://fusesource.com/

Re: GShell ANSI colors support on Window.

[Hiram Chirino]

Not yet.

On Dec 12, 2007 4:37 PM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> Did you hear back from Marc about this?
>
> --jason
>
>
>
> On Dec 11, 2007, at 9:19 PM, Hiram Chirino wrote:
>
> > It was a bit of bummer when I noticed that GShell has no colorized
> > output on Windows.  :(
> > But I noticed that the Perl guys were able to do it.  See the
> > "Win32::Console::ANSI' project [1].
> >
> > So I updated the jline dll that is used on Windows with the c code
> > that the Perl project is using and BAM!, we have color.  I sent a note
> > out to the jline project about this.  Hopefully they incorporate this
> > feature into future releases.
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> > Open Source SOA
> > http://open.iona.com
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

GShell ANSI colors support on Window.

[Hiram Chirino]

It was a bit of bummer when I noticed that GShell has no colorized
output on Windows.  :(
But I noticed that the Perl guys were able to do it.  See the
"Win32::Console::ANSI' project [1].

So I updated the jline dll that is used on Windows with the c code
that the Perl project is using and BAM!, we have color.  I sent a note
out to the jline project about this.  Hopefully they incorporate this
feature into future releases.

-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Re: [VOTE] Release XBean 3.2

[Hiram Chirino]

+1

On 10/1/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> Please vote on releasing xbean 3.2.
> Binaries / maven repo is available at:
>http://people.apache.org/~gnodet/xbean-3.2/
> Svn source tag is available at:
>http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.2/
>
> It includes David Jencks last minute fix too.
>
> --
> Cheers,
> Guillaume Nodet
> 
> Blog: http://gnodet.blogspot.com/
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release XBean 3.1

[Hiram Chirino]

+1

On 8/1/07, David Blevins <[EMAIL PROTECTED]> wrote:
> I have tagged an XBean 3.1 version at
>   http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.1/
>
> Binaries:
>   http://people.apache.org/~dblevins/stage/org/apache/xbean/
>
> Please review the tag/binaries and vote for this release.  Once the
> vote passes,
> I will upload the release to the repository.
>
> [ ] +1 Release XBean 3.1
> [ ] +/- 0
> [ ] -1 Do not release
>
> Here's my +1
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Slim spring?

[Hiram Chirino]

+1

On 7/19/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:

How does everyone feel about changing from the uber-spring jar (2M)
to the spring module jars?  Here is a sizing chart:

spring-beans-2.0.5.jar379K
spring-context-2.0.5.jar  156K
   
   531K

spring-web-2.0.5.jar  148K  # optional for web context
spring-jmx-2.0.5.jar   85K  # optional xbean-server


With full spring at 2M this is a pretty big savings.  This will also
help to keep the modules free of using other stuff from spring.

On the other hand, maven and uber jars don't always get along.  If
anther project imports xbean-spring, they will either need to use the
spring module jars, or exclude them transitively from the xbean-
spring.  Alternatively, we could mark them as provided, and then the
importing project will need to explicitly import spring in which ever
form they like.

I'd prefer we go with the spring-module approach, but mark all the
spring jars as provided.  This make it easier for users to upgrade to
newer spring releases (no exclude/reinclude).

-dain

BTW, I did test this actually works :)




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: 1.2 status

[Hiram Chirino]

Both the AMQ issues now have fixes applied to the 4.1 branch.

On 2/22/07, Rick McGuire <[EMAIL PROTECTED]> wrote:

Dain Sundstrom wrote:
> This release is finally wrapping up.  We are basically waiting on
> final releases from the projects we depend on.  Specifically, we need
> releases from:
>
>   Yoko 1.0 - Contains many fixes to CORBA interoperability
>   ActiveMQ 4.1.1 - We need a release which contains AMQ-1165 and AMQ-1088
>   OpenEJB 2.3 - Once Yoko is released, OpenEJB 2.3 can be release
There are a couple of fixes to both the javamail 1.3.1 specs and
providers we really should try to get into 1.2.  Multiple customers have
hit this problem in 1.1.1.   This will require releasing new versions of
both deliverables.  The fixes are already in the code, we just need to
go through the mechanics of releasing it.

Rick


>
> As always, this could take a painful amount of time to get the
> binaries, but I'm hopeful.
>
> -dain
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Switching to 3.0-SNAPSHOT and dropping spring 1.x release

[Hiram Chirino]

Sounds good to me.  +1

On 2/21/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

What about switching to 3.0-SNAPSHOT
and dropping support for spring < 2.0 release ?
The code of xbean-spring is split into
at least 4 modules, just to keep with the different
milestones and the older 1.x release ...

--
Cheers,
Guillaume Nodet

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release ServiceMix 3.1 (2nd try)

[Hiram Chirino]

Sorry for the delay.

+1

On 2/5/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

The vote is extended for another period of 3 days.
And here's my +1

On 2/1/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> I have fixed and uploaded the samples, the jbi plugin (which i had to
> build manually)
> and uploaded everything to the incubating repository
>
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/
>
> Distributions are available at:
> 
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.1-incubating/
> 
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix-web/3.1-incubating/
>
> Please download, review and vote ...
> This vote will be closed on sunday, midnight GMT
>
> --
> Cheers,
> Guillaume Nodet
> 
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>


--
Cheers,
Guillaume Nodet

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Confluence move

[Hiram Chirino]

I've put the following redirects in on the old confluence site:

   RewriteRule   ^/confluence/display/ACTIVEMQ$
http://cwiki.apache.org/confluence/display/ACTIVEMQ
   RewriteRule   ^/confluence/display/ACTIVEMQ/(.*)$
http://cwiki.apache.org/confluence/display/ACTIVEMQ/$1
   RewriteRule   ^/confluence/display/SM$
http://cwiki.apache.org/confluence/display/SM
   RewriteRule   ^/confluence/display/SM/(.*)$
http://cwiki.apache.org/confluence/display/SM/$1

This should help move the traffic over to the new pages, but the link
at the bottom of the
http://incubator.apache.org/activemq/ page are in the form of:
http://goopen.org/confluence/pages/editpage.action?pageId=269
so that stuff is still not getting redirected.

Any idea if we can get the cwiki to generate the static content sites?

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

The conluence wiki has been moved to
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Home

The space is not yet replicated to http://activemq.org or
http://activemq.apache.org (there's nothing atm) and there are still
some problems (the snippet plugin does not seem to work).

Please report any problems.

--
Cheers,
Guillaume Nodet

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Confluence move

[Hiram Chirino]

awesome!

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

The conluence wiki has been moved to
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Home

The space is not yet replicated to http://activemq.org or
http://activemq.apache.org (there's nothing atm) and there are still
some problems (the snippet plugin does not seem to work).

Please report any problems.

--
Cheers,
Guillaume Nodet

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Resolved: (AMQ-1140) Compression not working

[Hiram Chirino (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiram Chirino resolved AMQ-1140.


   Resolution: Fixed
Fix Version/s: 4.2.0
   4.1.1

Added test case and fixed.

> Compression not working 
> 
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the 
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the 
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true. 
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets 
> between brokers, the message bodies are not compressed - they're just plain 
> text. This appears to be a bug. 
> I'll try to create a test for this. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQ-1140) Compression not working

[Hiram Chirino (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38427
 ] 

Hiram Chirino commented on AMQ-1140:


Fix in trunk rev 501506 and fixed in 4.1 branch in rev 501500

> Compression not working 
> 
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the 
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the 
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true. 
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets 
> between brokers, the message bodies are not compressed - they're just plain 
> text. This appears to be a bug. 
> I'll try to create a test for this. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-1140) Compression not working

[Hiram Chirino (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQ-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiram Chirino updated AMQ-1140:
---

Affects Version/s: (was: 4.1.2)
   4.1.0

> Compression not working 
> 
>
> Key: AMQ-1140
> URL: https://issues.apache.org/activemq/browse/AMQ-1140
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1.0
>Reporter: Bruce Snyder
> Assigned To: Bruce Snyder
> Fix For: 4.1.1, 4.2.0
>
>
> When setting compression from the message producer side using the 
> {{ActiveMQConnectionFactory.setUseCompression(true)}} method, a call to the 
> {{ActiveMQConnectionFactory.isUseCompression()}} method then returns true. 
> However, when using [Ethereal|http://www.ethereal.com/] to sniff the packets 
> between brokers, the message bodies are not compressed - they're just plain 
> text. This appears to be a bug. 
> I'll try to create a test for this. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

[Hiram Chirino]

On Jan 18, 2007, at 5:50 PM, Oren Ben-Kiki wrote:


I have just pinged the people in the Autoconf project and they are
interested in adding this to their archive. This may take a while
though.


Thanks!



BTW, AFAIK the main difference between the Apache license and the  
GPL is
that Apache may be distributed in binary-only form; since my files  
have

no binary form I don't see how they are incompatible. But IANAL.



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


To solve your problem in the meanwhile, I hereby formally grant you  
the

permission to change the license line to "... the same terms as the
Apache server" in your distribution. I trust that would settle the
issue?


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.



Oren.

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

Hi Oren,

Thanks for the reply. Apache Projects can't distribute any source
code that is GPL or LGPL licensed.  But we can distribute Apache or
BSD or MIT style licensed source code.  We would not be be
distributing Autoconf, but expect our developers to have it installed
prior to building our source code.  We could make the same assumption
for your ac_doxygen.m4 too but making someone download and install
that file seperately is a bit annoying for new developers checking
out the project.  We were hoping to distribute your ac_doxygen.m4
with our source code to make it easier for them to have Doxygen  
support.


So is there any chance you could at least dual license that file so
that could include it?

Regards,
Hiram

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

[Hiram Chirino]

Hi Oren,

Thanks for the reply. Apache Projects can't distribute any source  
code that is GPL or LGPL licensed.  But we can distribute Apache or  
BSD or MIT style licensed source code.  We would not be be  
distributing Autoconf, but expect our developers to have it installed  
prior to building our source code.  We could make the same assumption  
for your ac_doxygen.m4 too but making someone download and install  
that file seperately is a bit annoying for new developers checking  
out the project.  We were hoping to distribute your ac_doxygen.m4  
with our source code to make it easier for them to have Doxygen support.


So is there any chance you could at least dual license that file so  
that could include it?


Regards,
Hiram

On Jan 18, 2007, at 3:53 PM, Oren Ben-Kiki wrote:


AFAIK Autoconf itself is released under the GPL. I believe this is
compatible with the Apache license... and at any rate you must include
Autoconf for my code to work, so once you do that, you don't have to
worry about my code.

Let me know if this is a problem, if it is I'm certain we can work
something out. I'll also e-mail [EMAIL PROTECTED] so maybe this will be
added to the official macros list...

Good luck,

Oren Ben-Kiki

On Mon, 2007-01-15 at 21:41 -0500, Hiram Chirino wrote:

Hi Oren,

Thanks for putting together your excellent http://ben-kiki.org/ 
oren/doxample/ !!


I work on a  Messaging product called ActiveMQ.  For more info see:
http://incubator.apache.org/activemq/

We want to make use of your ac_doxygen.m4 file to get doxygen to work
with our build but we are not sure what license it available to us
under.  It just says:

# Copyright (C) 2004 Oren Ben-Kiki
# This file is distributed under the same terms as the Autoconf  
macro files.


But we are not to sure what those terms are.  Ideally for us it would
be terms that are compatible with the Apache Software License, which
basically means stuff Apache, BSD, MIT, or other similar licenses.

Please advise as we are want to do a release soon and if we cannot
include your m4 script in our source distribution we need to  
remove it

from our repository.

Re: [VOTE] Release ActiveMQ-CPP 1.1

[Hiram Chirino]

Yep..  still need incubator votes until we actually make it to TLP.

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

And here's my +1 ... bringing the totals to:

+1: 6
+0: 0
-1 : 0

Since the vote has been out for 3 days, I think it's safe to say that the
release passes.

Given that AMQ is on the verge of becoming a TLP, is the next step still to
bring a vote on the general incubator list?


On 1/17/07, Kevan Miller <[EMAIL PROTECTED] > wrote:
>
>
> On Jan 17, 2007, at 9:36 AM, Mittler, Nathan wrote:
>
> > Hi Kevan,
> > With the current changes, can I call you a +1?
> >
> > Thanks,
> > Nate
> >
> >> -Original Message-
> >> From: Nathan Mittler [mailto: [EMAIL PROTECTED]
> >> Sent: Wednesday, January 17, 2007 6:42 AM
> >> To: activemq-dev@geronimo.apache.org
> >> Subject: Re: [VOTE] Release ActiveMQ-CPP 1.1
> >>
> >>
> >> I've removed the doxygen files from the project and have cut
> >> a new source
> >> bundle:
> >>
> >> 
http://people.apache.org/~nmittler/incubator-activemq-cpp-1.1-src.zip
> >>
>
> Thanks for the reminder Nathan.
>
> +1 Release the source as Apache ActiveMQ  CPP 1.1
>
> --kevan
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release ActiveMQ-CPP 1.1

[Hiram Chirino]

This is the case then we need to delete the m4 macro from the svn repo
and the distro.  And ask folks to install it manually as part of the
build procedure... or we could just remove all the doxygen bits out of
the autoconf stuff so that it's not a dependency.

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

It appears that the Autoconf macros are under the GPL (as expected)
http://sourceforge.net/projects/ac-archive/.  What is the typical way we
deal with this at the ASF?

On 1/16/07, Nathan Mittler <[EMAIL PROTECTED]> wrote:
>
> Great - thanks!
>
> On 1/15/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> >
> > 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<http://people.apache.org/%7Enmittler/incubator-activemq-cpp-1.1-src.zip>
> > > > > < http://people.apache.org/%7Etabish/activemq-cpp-1.0.zip>
> > > > >
> > > > > And here's the wiki page for the release:
> > > > > http://www.activemq.org/site/activemq-cpp-11-release.html
> > > > > <http://www.activemq.org/site/activemq-cpp-10-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
> >
>
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Error while Sending Map message

[Hiram Chirino]

yes.

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


Can i also send exception object ?? as Object Message


Hiram Chirino wrote:
>
> But if that is not an option you could always send the hash map using
> an ObjectMessage.
>
> On 1/12/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>> Try using 4.1.0 I think it supports sending hashmaps of primitive data.
>>
>> On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:
>> >
>> > we are using 4.0.2
>> > any solution?? i want to send hashmap
>> >
>> > Hiram Chirino wrote:
>> > >
>> > > Are you using ActiveMQ 4.1.0 ???
>> > >
>> > > On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:
>> > >>
>> > >> Hi,
>> > >>
>> > >> I have an urgent requirement in which i have to send Map as a
>> message to
>> > >> Queue
>> > >> I am trying this code:
>> > >> if(message instanceof Map){
>> > >>   MapMessage requestMessage = (MapMessage)
>> > >> session.createMapMessage();
>> > >>   requestMessage.setObjectProperty("MAP", message);
>> > >>  requestMessage.setJMSReplyTo(replyQueue);
>> > >>   requestProducer.send(requestMessage);
>> > >> }
>> > >>
>> > >> javax.jms.MessageFormatException: Only objectified primitive objects
>> and
>> > >> String types are allowed
>> > >>
>> > >> can some body please tell me the resolution.Its really very imp .
>> > >>
>> > >> thanks in advance
>> > >>
>> > >> but when running it is throwing this error
>> > >> --
>> > >> View this message in context:
>> > >>
>> http://www.nabble.com/Error-while-Sending-Map-message-tf2967725.html#a8304233
>> > >> 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/Error-while-Sending-Map-message-tf2967725.html#a8305206
>> > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>> >
>> >
>>
>>
>> --
>> Regards,
>> Hiram
>>
>> Blog: http://hiramchirino.com
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>

--
View this message in context: 
http://www.nabble.com/Error-while-Sending-Map-message-tf2967725.html#a8380165
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Doxample: Can we ship it with our code?

[Hiram Chirino]

Hi Oren,

Thanks for putting together your excellent http://ben-kiki.org/oren/doxample/ !!

I work on a  Messaging product called ActiveMQ.  For more info see:
http://incubator.apache.org/activemq/

We want to make use of your ac_doxygen.m4 file to get doxygen to work
with our build but we are not sure what license it available to us
under.  It just says:

# Copyright (C) 2004 Oren Ben-Kiki
# This file is distributed under the same terms as the Autoconf macro files.

But we are not to sure what those terms are.  Ideally for us it would
be terms that are compatible with the Apache Software License, which
basically means stuff Apache, BSD, MIT, or other similar licenses.

Please advise as we are want to do a release soon and if we cannot
include your m4 script in our source distribution we need to remove it
from our repository.

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Error while Sending Map message

[Hiram Chirino]

But if that is not an option you could always send the hash map using
an ObjectMessage.

On 1/12/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Try using 4.1.0 I think it supports sending hashmaps of primitive data.

On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:
>
> we are using 4.0.2
> any solution?? i want to send hashmap
>
> Hiram Chirino wrote:
> >
> > Are you using ActiveMQ 4.1.0 ???
> >
> > On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:
> >>
> >> Hi,
> >>
> >> I have an urgent requirement in which i have to send Map as a message to
> >> Queue
> >> I am trying this code:
> >> if(message instanceof Map){
> >>   MapMessage requestMessage = (MapMessage)
> >> session.createMapMessage();
> >>   requestMessage.setObjectProperty("MAP", message);
> >>  requestMessage.setJMSReplyTo(replyQueue);
> >>   requestProducer.send(requestMessage);
> >> }
> >>
> >> javax.jms.MessageFormatException: Only objectified primitive objects and
> >> String types are allowed
> >>
> >> can some body please tell me the resolution.Its really very imp .
> >>
> >> thanks in advance
> >>
> >> but when running it is throwing this error
> >> --
> >> View this message in context:
> >> 
http://www.nabble.com/Error-while-Sending-Map-message-tf2967725.html#a8304233
> >> 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/Error-while-Sending-Map-message-tf2967725.html#a8305206
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>


--
Regards,
Hiram

Blog: http://hiramchirino.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Error while Sending Map message

[Hiram Chirino]

Try using 4.1.0 I think it supports sending hashmaps of primitive data.

On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:


we are using 4.0.2
any solution?? i want to send hashmap

Hiram Chirino wrote:
>
> Are you using ActiveMQ 4.1.0 ???
>
> On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I have an urgent requirement in which i have to send Map as a message to
>> Queue
>> I am trying this code:
>> if(message instanceof Map){
>>   MapMessage requestMessage = (MapMessage)
>> session.createMapMessage();
>>   requestMessage.setObjectProperty("MAP", message);
>>  requestMessage.setJMSReplyTo(replyQueue);
>>   requestProducer.send(requestMessage);
>> }
>>
>> javax.jms.MessageFormatException: Only objectified primitive objects and
>> String types are allowed
>>
>> can some body please tell me the resolution.Its really very imp .
>>
>> thanks in advance
>>
>> but when running it is throwing this error
>> --
>> View this message in context:
>> http://www.nabble.com/Error-while-Sending-Map-message-tf2967725.html#a8304233
>> 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/Error-while-Sending-Map-message-tf2967725.html#a8305206
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Error while Sending Map message

[Hiram Chirino]

Are you using ActiveMQ 4.1.0 ???

On 1/12/07, garima015 <[EMAIL PROTECTED]> wrote:


Hi,

I have an urgent requirement in which i have to send Map as a message to
Queue
I am trying this code:
if(message instanceof Map){
  MapMessage requestMessage = (MapMessage) session.createMapMessage();
  requestMessage.setObjectProperty("MAP", message);
 requestMessage.setJMSReplyTo(replyQueue);
  requestProducer.send(requestMessage);
}

javax.jms.MessageFormatException: Only objectified primitive objects and
String types are allowed

can some body please tell me the resolution.Its really very imp .

thanks in advance

but when running it is throwing this error
--
View this message in context: 
http://www.nabble.com/Error-while-Sending-Map-message-tf2967725.html#a8304233
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Assigned: (AMQ-1123) Deadlocks can occur with even with sync sends since they share a connection.

[Hiram Chirino (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQ-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hiram Chirino reassigned AMQ-1123:
--

Assignee: Hiram Chirino

> Deadlocks can occur with even with sync sends since they share a connection.
> 
>
> Key: AMQ-1123
> URL: https://issues.apache.org/activemq/browse/AMQ-1123
> Project: ActiveMQ
>  Issue Type: Bug
>        Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
>
> If a producer sends to a queue and blocks, any other producer sharing the 
> same connection even if he would be sending to an empty queue would also 
> block.  This in effect can cause a deadlock if the right message processing 
> flow is set up.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1123) Deadlocks can occur with even with sync sends since they share a connection.

[Hiram Chirino (JIRA)]

Deadlocks can occur with even with sync sends since they share a connection.


 Key: AMQ-1123
 URL: https://issues.apache.org/activemq/browse/AMQ-1123
 Project: ActiveMQ
  Issue Type: Bug
Reporter: Hiram Chirino


If a producer sends to a queue and blocks, any other producer sharing the same 
connection even if he would be sending to an empty queue would also block.  
This in effect can cause a deadlock if the right message processing flow is set 
up.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: NMS byte order for doubles

[Hiram Chirino]

Could you attach your patch to that issue and make sue your click the
"Grant license to ASF for inclusion in ASF works (as per the Apache
Software License )" option.

Thanks.

On 1/11/07, rousseau <[EMAIL PROTECTED]> wrote:


Sure. It's the same as AMQ-866. Comment added on that case.

thx
Steve



Hiram Chirino wrote:
>
> Hi Steve,
>
> I would be happy to apply your patch but could you open a JIRA issue at:
> http://issues.apache.org/activemq/browse/AMQ
>
> And attach your patch to that so that we have it properly documented
> that you want to contribute your patch to the ASF.
>
> Thanks!
> Hiram
>
> On 1/10/07, rousseau <[EMAIL PROTECTED]> wrote:
>>
>> I've found a byte-order problem sending a double from Java ActiveMQ to a
>> NMS/CSharp receiver:
>>
>> (NMS) ActiveMQ.OpenWire.OpenWireBinaryReader has no definition for
>> ReadDouble(), and by default calls the MS .NET BinaryReader.ReadDouble()
>> which reads the bytes in the wrong order. Here is the fix:
>>
>> add a new method to OpenWireBinaryReader.cs:
>>
>> public override double ReadDouble()
>> {
>> return EndianSupport.SwitchEndian(base.ReadBytes(8));
>> }
>>
>> add a new method to EndianSupport.cs:
>>
>> public static double SwitchEndian(byte[] bytes)
>> {
>> //Reverse byte array
>> byte[] reverse = new byte[8];
>> reverse[0] = bytes[7];
>> reverse[1] = bytes[6];
>> reverse[2] = bytes[5];
>> reverse[3] = bytes[4];
>> reverse[4] = bytes[3];
>> reverse[5] = bytes[2];
>> reverse[6] = bytes[1];
>> reverse[7] = bytes[0];
>> BinaryReader br = new BinaryReader(new
>> MemoryStream(reverse));
>> return br.ReadDouble();
>> }
>>
>> If anyone knows a cleaner way of doing this, please let me know.
>>
>> thx
>> /Steve
>> --
>> View this message in context:
>> http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8253895
>> 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/NMS-byte-order-for-doubles-tf2951266.html#a8273932
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: NMS byte order for doubles

[Hiram Chirino]

Hi Steve,

I would be happy to apply your patch but could you open a JIRA issue at:
http://issues.apache.org/activemq/browse/AMQ

And attach your patch to that so that we have it properly documented
that you want to contribute your patch to the ASF.

Thanks!
Hiram

On 1/10/07, rousseau <[EMAIL PROTECTED]> wrote:


I've found a byte-order problem sending a double from Java ActiveMQ to a
NMS/CSharp receiver:

(NMS) ActiveMQ.OpenWire.OpenWireBinaryReader has no definition for
ReadDouble(), and by default calls the MS .NET BinaryReader.ReadDouble()
which reads the bytes in the wrong order. Here is the fix:

add a new method to OpenWireBinaryReader.cs:

public override double ReadDouble()
{
return EndianSupport.SwitchEndian(base.ReadBytes(8));
}

add a new method to EndianSupport.cs:

public static double SwitchEndian(byte[] bytes)
{
//Reverse byte array
byte[] reverse = new byte[8];
reverse[0] = bytes[7];
reverse[1] = bytes[6];
reverse[2] = bytes[5];
reverse[3] = bytes[4];
reverse[4] = bytes[3];
reverse[5] = bytes[2];
reverse[6] = bytes[1];
reverse[7] = bytes[0];
BinaryReader br = new BinaryReader(new MemoryStream(reverse));
return br.ReadDouble();
}

If anyone knows a cleaner way of doing this, please let me know.

thx
/Steve
--
View this message in context: 
http://www.nabble.com/NMS-byte-order-for-doubles-tf2951266.html#a8253895
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: error when start broker

[Hiram Chirino]

every DB is slightly different we just need to figure out how to do it
with sybase.

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


I have not used a pessimistic lock on database record in sybase ASE 12.5. :(
Is this the sybase's defect?


Hiram Chirino wrote:
>
> 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
>
>

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





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release XBean 2.8

[Hiram Chirino]

+1

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

I'm starting a vote to release XBean 2.8.
There has not been much changes since 2.7, but a few
bugs fixed, and the addition of the xbean-finder module.
Anyway, the bugs are important enough to deserver a new
release (the generated schemas can not be validated).

[ ] +1 Start xbean 2.8 release process
[ ] +/- 0
[ ] -1 Don't release xbean 2.8 now

Here's my +1.

--
Cheers,
Guillaume Nodet




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

Hiram Chirino commented on AMQ-1078:


Fixed in trunk revision 480717

> Messages consumed with the Resource Adapter are intermittently not delivered
> 
>
> Key: AMQ-1078
> URL: https://issues.apache.org/activemq/browse/AMQ-1078
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, Connector
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
> Fix For: 4.2.0, 4.1.1
>
>
> The cause is that the ActiveMQSessionExecutor was starting and using it's 
> dispatch thread instead of the Thread managed by the resource adapter.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Hiram Chirino (JIRA)]

Messages consumed with the Resource Adapter are intermittently not delivered


 Key: AMQ-1078
 URL: https://issues.apache.org/activemq/browse/AMQ-1078
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker, Connector
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1.1, 4.2.0


The cause is that the ActiveMQSessionExecutor was starting and using it's 
dispatch thread instead of the Thread managed by the resource adapter.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: communicating with Topic subscribers from custom interceptor class

[Hiram Chirino]

On 11/27/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:

Hello,

On 11/27/06, James Strachan <[EMAIL PROTECTED]> wrote:
> On 11/27/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:
>
> >I'm writing a custom interceptor that extends BrokerFilter in order
> > to process messages that are published to particular Topics.  My
> > question is, how can my interceptor make a direct connection with the
> > JMS client that published the message?
>
> What kind of thing are you trying to do?
>

   The custom interceptor creates a marketplace, and clients send
digital financial instruments.  The interceptor must keep track of the
originator of the messages that include these assets, because the
client must be able to retrieve its asset from the interceptor when it
chooses.  Also, the interceptor must be able to initiate messages to a
client when a trade has been executed, to inform them of the execution
of a trade and to deliver the result.

   What I would really like to do is have some way of, from the
interceptor, initiate communication with a subscriber that has
previously sent a message that is published to a Topic that is
processed by the interceptor.

>
> > Does the subscriber have to
> > manually set an identifier in order to be accessible, or are the
> > identifiers automatically generated?
>
> Subscribers are visible in JMX or the BrokerService via their unique
> generated consumerId's.
>

   Should I just expect the clients to subscribe to a per-client queue
so that there is a per-client control channel, so that the market
server (i.e., the interceptor class) can communicate with the client?



That would work but if your interceptor keep track of the client
subscriptions, then it could send a message that is specifically
targeted for that subscription.  The AdvisoryBroker implementation
makes use of it.  See the use of the setTargetConsumerId() method in
the AdvisoryBroker class.



>
> >Additionally, is there a way to access the list of subscribers to a
> > particular topic and send messages to individual subscribers from a
> > custom interceptor class?
>
> Not easily. What are you trying to do - maybe there's an easier way.
>

   Thanks again!

   Patrick

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


--
   J. Patrick Bedell
   [EMAIL PROTECTED]
   http://infoeng.sourceforge.net
   http://rothbardix.blogspot.com




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: obtaining a DataSource bean from a BrokerFilter-based plugin?

[Hiram Chirino]

so something like:

 

and make sure your TestICTPInterceptor has a setDataSource(DataSource
ds) method.

On 11/20/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:

Hi,
   I'm trying to utilize (in the attached activemq configuration file)
the derby-ds DataSource that is commented out in the default
configuration, which has the bean element

  


 

   I'm also writing an interceptor that extends BrokerFilter, so that
I can have an ActiveMQ-specific plugin.  My question is, how would I
obtain the "derby-ds" DataSource in my BrokerFilter-based plugin?  (I
have the suspicion that this is an extremely simple question, but I
don't know the answer and I'm not familiar enough with Spring to find
it. :)
   Thanks!

--
   J. Patrick Bedell
   [EMAIL PROTECTED]
   http://infoeng.sourceforge.net
   http://rothbardix.blogspot.com






--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Resolved: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1042.


Resolution: Fixed

reverted in trunk rev 477356 and 4.1 branch rev 477357

Made the test case smarter so that the it would not intermittently fail.

> The JMSConsumerTest interminitently failed on linux systems.
> 
>
> Key: AMQ-1042
> URL: https://issues.apache.org/activemq/browse/AMQ-1042
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: CMS (C++ client)
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.2.0, 4.1.0
>
>
> JMSConsumerTest fails on linux sometimes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Reopened: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.

[Hiram Chirino (JIRA)]

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

Hiram Chirino reopened AMQ-1042:


 
This patch may need to get backed out.  Some performance testing has shown that 
in high throughput scenarios, we spend 300% of our time doing the yeild() call. 
:(  Back to the drawing board. 

> The JMSConsumerTest interminitently failed on linux systems.
> 
>
> Key: AMQ-1042
> URL: https://issues.apache.org/activemq/browse/AMQ-1042
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: CMS (C++ client)
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.0, 4.2.0
>
>
> JMSConsumerTest fails on linux sometimes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Activemq-cpp issues moved

[Hiram Chirino]

BTW..

I just added version to the space and assigned all the resolved issue
to version 1.0..   If the "fix for version" field is properly assigned
on every issue then they will properly show up on the change long and
road map views of jira.


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

Just to give everyone a heads up...

Last night I moved over all of the issues related to the activemq-cpp
client into the new ActiveMQ C++ JIRA Project.  I've also updated the
changelog on the website to apply the filter against the new project

http://www.activemq.org/site/activemq-cpp-10-release.html





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Updated: (AMQCPP-12) Modified pom.xml for VS .net 2003 compilation

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-12:


Fix Version/s: 1.0

> Modified pom.xml for VS .net 2003 compilation
> -
>
> Key: AMQCPP-12
> URL: https://issues.apache.org/activemq/browse/AMQCPP-12
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
> Environment: VS .net 2003 on XP. Using maven build with win32-msvc.
>Reporter: Lalit Nagpal
> Assigned To: Timothy Bish
> Fix For: 1.0
>
> Attachments: pom_vc2003.xml
>
>
> The following tag 
> true
> was moved from the profile release to profile debug
> The following switch was added in the  for both debug and 
> release
> /GR 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-10) Compiling fails under SuSe

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-10:


Fix Version/s: 1.0

> Compiling fails under SuSe
> --
>
> Key: AMQCPP-10
> URL: https://issues.apache.org/activemq/browse/AMQCPP-10
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: gcc (GCC) 3.3.3 (SuSE Linux)
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking build system type... x86_64-suse-linux
> checking host system type... x86_64-suse-linux
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld
> checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
> checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag  works... yes
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) 
> supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64
> checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU 
> ld... yes
> checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) 
> supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) 
> supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works..

[jira] Updated: (AMQCPP-8) Code Drop for Version 0.0.2 of the activemq-cpp library

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-8:
---

Fix Version/s: 1.0

> Code Drop for Version 0.0.2 of the activemq-cpp library
> ---
>
> Key: AMQCPP-8
> URL: https://issues.apache.org/activemq/browse/AMQCPP-8
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>Reporter: Timothy Bish
> Assigned To: Nathan Mittler
> Fix For: 1.0
>
> Attachments: activemq-cpp-0-0-2-071906.zip
>
>
> This issues addresses the code drop for Revision 0.0.2 of the ActiveMQ CPP 
> library.  Changes are listed below.  
> New Features:
> * Destinations now support the Destination Options shown here:  
> http://www.activemq.org/site/destination-options.html
> Additional Changes
> * Extensive code cleanup, including expanded Java DOC comments and more 
> consistant formatting.
> * Memory leak checking with Rational Purify were done and several small 
> leaks were fixed.
> * Added additional Unit tests for new functionality, and additional tests 
> for existing feature correctness
> * Minor bug fixes
> Known Issues
> * Unchanged from version 0.0.1 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-13) Patch to make activemq-cpp compile under sun studio 11

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-13:


Fix Version/s: 1.0

> Patch to make activemq-cpp compile under sun studio 11
> --
>
> Key: AMQCPP-13
> URL: https://issues.apache.org/activemq/browse/AMQCPP-13
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
> Environment: Sun Solaris 10 (SunOS chi-dev-chris1 5.10 
> Generic_118855-15 i86pc i386 i86pc Solaris)
> Studio 11 (Sun C++ 5.8 Patch 121018-04 2006/08/02)
>Reporter: Chris Knight
> Assigned To: Timothy Bish
>Priority: Minor
> Fix For: 1.0
>
> Attachments: makefile-solaris-debug.cfg, makefile-solaris-debug.cfg, 
> makefile-solaris-release.cfg, makefile-solaris-release.cfg, 
> makefile.cfg.PATCH, PATCH, PATCH
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Fixes compilation of activemq-cpp for studio 11 C++ compiler. Mostly 
> additions of #include  and added namespace qualifiers std::

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-3) Receiving a BytesMessage sent from Java using CMS listener causes exception thrown in class BufferedInputStream

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-3:
---

Fix Version/s: 1.0

> Receiving a  BytesMessage sent from Java using CMS listener causes exception 
> thrown in class BufferedInputStream
> 
>
> Key: AMQCPP-3
> URL: https://issues.apache.org/activemq/browse/AMQCPP-3
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: Ubuntu Linux 6.06 LTS, ActiveMQ 4.0.2, CMS version 0.0.2 
> with STOMP
>Reporter: Mark Silberbauer
> Fix For: 1.0
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> 1) Setup a MessageListener to listen for messages on Topic X using CMS.
> 2) Send a BytesMessage from ActiveMQ java JMS interface to Topic X
> 3) An exception is thrown from BufferedInputStream::bufferData() with 
> description "failed reading bytes from stream""
> int bytesRead = stream->read( buffer+tail, bufferSize-tail );
> if( bytesRead == 0 ){
> throw IOException( __FILE__, __LINE__, 
> "BufferedInputStream::read() - failed reading bytes from stream");
> }
> 4) The operation of the CMS interface is broken thereafter.
> Note:
> This only occurs when sending a BytesMessage from Java to C++
> Sending a BytesMessage from C++ to Java or  C++ to C++ works perfectly.
> Sending messages of Type TextMessage also works perfectly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-5) Make Session.h more polymorphic like JMS 1.1 with createProducer/createConsumer methods on Session.h

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-5:
---

Fix Version/s: 1.0

> Make Session.h more polymorphic like JMS 1.1 with 
> createProducer/createConsumer methods on Session.h
> 
>
> Key: AMQCPP-5
> URL: https://issues.apache.org/activemq/browse/AMQCPP-5
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>  Components: CMS Impl
>Reporter: james strachan
> Assigned To: Nathan Mittler
> Fix For: 1.0
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-7) ActiveMQ Cpp Windows Makefiles fail to link the test, and test-integration targets

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-7:
---

Fix Version/s: 1.0

> ActiveMQ Cpp Windows Makefiles fail to link the test, and test-integration 
> targets
> --
>
> Key: AMQCPP-7
> URL: https://issues.apache.org/activemq/browse/AMQCPP-7
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: Windows Mingw GNU builds
>Reporter: Timothy Bish
> Assigned To: Nathan Mittler
>Priority: Minor
> Fix For: 1.0
>
> Attachments: patch-makefile-windows-debug.txt, 
> patch-makefile-windows-release.txt
>
>   Original Estimate: 1 minute
>  Remaining Estimate: 1 minute
>
> The windows makefiles for the MinGW targets fail to link the test and 
> test-integration targets.
> When the code was submitted the makefiles were changed to build the library 
> with the libactivemq-cpp.a name, but the windows makefiles still try and link 
> the tests against libactivemq.a

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-2) Release build of ActiveMQ-CPP from trunk with Visual Studio 2005 fails due to Windows headers include order issue

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-2:
---

Fix Version/s: 1.0

> Release build of ActiveMQ-CPP from trunk with Visual Studio 2005 fails due to 
> Windows headers include order issue
> -
>
> Key: AMQCPP-2
> URL: https://issues.apache.org/activemq/browse/AMQCPP-2
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: Windows
>Reporter: Albert Strasheim
> Assigned To: Timothy Bish
> Fix For: 1.0
>
>
> Doing a release build of ActiveMQ-CPP from trunk with Visual Studio 2005 
> results in the following error when compiling DataInputStreamTest.cpp:
> {quote}
> 1>-- Build started: Project: vc2005-activemq-unittests, Configuration: 
> Release Win32 --
> 1>Compiling...
> 1>DataInputStreamTest.cpp
> 1>f:\activemq-cpp\src\main\activemq/io/ByteArrayInputStream.h(142) : warning 
> C4244: 'return' : conversion from '__w64 int' to 'int', possible loss of data
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(112) : error 
> C2011: 'fd_set' : 'struct' type redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(54) : see 
> declaration of 'fd_set'
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(147) : warning 
> C4005: 'FD_SET' : macro redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(88) : see 
> previous definition of 'FD_SET'
> 1>C:\Program Files\Microsoft Platform SDK\Include\Winsock2.h(156) : error 
> C2011: 'timeval' : 'struct' type redefinition
> 1>C:\Program Files\Microsoft Platform SDK\Include\winsock.h(97) : see 
> declaration of 'timeval'
> ...
> {quote}
> This error happens when some combination of winsock.h, winsock2.h and 
> windows.h is included in the wrong order. The following change fixes the 
> problem and might provide some clue as to what is going on.
> {quote}
> Index: DataInputStreamTest.h
> ===
> --- DataInputStreamTest.h   (revision 470321)
> +++ DataInputStreamTest.h   (working copy)
> @@ -21,10 +21,10 @@
>  #include 
>  #include 
> +#include 
>  #include 
>  #include 
>  #include 
> -#include 
>  #include 
>  #ifdef min
> {quote}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-1) host_os env variable is empty in configure.ac

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-1:
---

Fix Version/s: 1.0

> host_os env variable is empty in configure.ac
> -
>
> Key: AMQCPP-1
> URL: https://issues.apache.org/activemq/browse/AMQCPP-1
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: building on linux, solaris, and cygwin
>Reporter: Nathan Mittler
>Priority: Minor
> Fix For: 1.0
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> The host_os environment variable is undefined when executing the configure.ac 
> file.  As a result, the switch on os_host doesn't execute properly.  This 
> seems to be fixed (at least on linux) by adding AC_CANONICAL_HOST at the top 
> of the file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-11) Update to activemq-cpp source to enable documentation generation

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-11:


Fix Version/s: 1.0

> Update to activemq-cpp source to enable documentation generation
> 
>
> Key: AMQCPP-11
> URL: https://issues.apache.org/activemq/browse/AMQCPP-11
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>Reporter: Timothy Bish
> Assigned To: Nathan Mittler
>Priority: Minor
> Fix For: 1.0
>
> Attachments: activemq-cpp-0-0-2-DOCUpdates.zip
>
>
> This patch contains updated source files for the activemq-cpp project which 
> expand the code documentation and clean up documentation that caused warnings 
> when running the doxygen tool to document the code.  A set of generated 
> documentation files is included in the new docs folder.  
> This patch adds no new functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-9) The Activemq-cpp example code no longer builds.

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-9:
---

Fix Version/s: 1.0

> The Activemq-cpp example code no longer builds.
> ---
>
> Key: AMQCPP-9
> URL: https://issues.apache.org/activemq/browse/AMQCPP-9
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>Reporter: Timothy Bish
> Assigned To: Nathan Mittler
>Priority: Minor
> Fix For: 1.0
>
> Attachments: example-patch-081306.txt
>
>
> Code in the Activemq-cpp example is no longer up to date with the latest 
> version.  We need to clean this code up to match the samll changes in the CMS 
> interface.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-4) Compilation warning under windows for activemq-cpp

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-4:
---

Fix Version/s: 1.0

> Compilation warning under windows for activemq-cpp
> --
>
> Key: AMQCPP-4
> URL: https://issues.apache.org/activemq/browse/AMQCPP-4
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
> Environment: windows
>Reporter: Nathan Mittler
> Assigned To: Nathan Mittler
>Priority: Trivial
> Fix For: 1.0
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Under Windows, the following warning gets printed out:
> c:\ActiveMQ\activemq\connector\stomp\commands\AckCommand.h(102) : warning
> C4390: ';' : empty controlled statement found;

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQCPP-6) add createDurableSubscriber() methods to Session.h

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQCPP-6:
---

Fix Version/s: 1.0

> add createDurableSubscriber() methods to Session.h
> --
>
> Key: AMQCPP-6
> URL: https://issues.apache.org/activemq/browse/AMQCPP-6
> Project: ActiveMQ C++ Client
>  Issue Type: Improvement
>  Components: CMS Impl
>Reporter: james strachan
> Assigned To: Timothy Bish
> Fix For: 1.0
>
>
> e.g.
> http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Session.html#createDurableSubscriber(javax.jms.Topic,%20java.lang.String)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Activemq-cpp issues moved

[Hiram Chirino]

Well done!

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

Just to give everyone a heads up...

Last night I moved over all of the issues related to the activemq-cpp
client into the new ActiveMQ C++ JIRA Project.  I've also updated the
changelog on the website to apply the filter against the new project

http://www.activemq.org/site/activemq-cpp-10-release.html





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Commented: (AMQ-1057) consumer queue is empty when running requester

[Hiram Chirino (JIRA)]

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

Hiram Chirino commented on AMQ-1057:


Also applied to 4.1 branch revision: 476144

> consumer queue is empty when running requester
> --
>
> Key: AMQ-1057
> URL: https://issues.apache.org/activemq/browse/AMQ-1057
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1.0
>Reporter: Marlon Santos
> Assigned To: Jonas Lim
>Priority: Minor
> Fix For: 4.2.0
>
> Attachments: ConsumerTool.patch, RequesterTool.java, 
> RequesterTool.patch
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> consumer queue is empty when running requester, producer and consumer. 
> The reply destination also results into an empty string.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Hiram Chirino]

Well it looks like we have pretty good consensus on moving to java 5
I'll start updating the build shortly.

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Resolved: (AMQ-1056) Expire messages at the Broker

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1056.


Resolution: Fixed

Implemented in trunk revision 475848

If a message takes a while to transmit to the broker either because :
 * sender connection is slow
 * producer was blocked because queue was full
 * tansaction took a a while to commit

then messages are now check to see if they expired before enqueueing to 
subscriptions.

We also now check to see if a message has expired when taking it off the 
subscribers pending message list right before it gets dispatched to the 
consumer.

This should help reduce load the amount of expired messages that are delivered 
to the consumer.

> Expire messages at the Broker
> -
>
> Key: AMQ-1056
> URL: https://issues.apache.org/activemq/browse/AMQ-1056
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
> Fix For: 4.2.0
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1056) Expire messages at the Broker

[Hiram Chirino (JIRA)]

Expire messages at the Broker
-

 Key: AMQ-1056
 URL: https://issues.apache.org/activemq/browse/AMQ-1056
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Broker
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.2.0




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: support for FileMessage?

[Hiram Chirino]

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

On 11/16/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> Ok.
>
> Why does the producer need to decide if the stream is sent out of band or 
not??



I see what you mean now.


Otherwise how would ActiveMQ know whether or not to send a URL or the
contents of the file? e.g. ActiveMQ can't really guess if

 new URL("file://foo/bar")

needs to be sent out of band or in-band? Only the producer can know if
the thing its passing to ActiveMQ is a valid in-band or out-of-band
thing.

It is completely obvious for InputStream that its not out-of-band
though - am more thinking for URL/File where it may or may not be out
of band

--

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: support for FileMessage?

[Hiram Chirino]

Ok.

Why does the producer need to decide if the stream is sent out of band or not??

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

On 11/16/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> I like it..  But I wonder if we can do something to handle streams out
> of band in general.  Here's a use case I'm thinking about...
>
> A big file is being posted to a servlet and the servlet wants to pass
> that input stream it's receiving to a JMS consumer somewhere in the
> back end.  So there is no actual file or URL to identify that stream
> but I want to 'pass' the stream to a consumer using JMS routing/load
> balancing.  And ideally the contents of the stream would be sent out
> band with respect to the JMS network.

Yeah. Am thinking something like

public class ActiveMQSession  {

// send a local file or stream over JMS
public FileMessage createLocalFileMessage(InputStream inputStream) {...}
public FileMessage createLocalFileMessage(File file) {..,}
public FileMessage createLocalFileMessage(URL url) {..,}


// send a remote URL over JMS
public FileMessage createRemoteFileMessage(URL url) {...}
}

i.e. from a consumers perpective they don't really need to care if its
in-band or out-of-band transfer of the content, its a decision for the
producer to decide

--

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: support for FileMessage?

[Hiram Chirino]

I like it..  But I wonder if we can do something to handle streams out
of band in general.  Here's a use case I'm thinking about...

A big file is being posted to a servlet and the servlet wants to pass
that input stream it's receiving to a JMS consumer somewhere in the
back end.  So there is no actual file or URL to identify that stream
but I want to 'pass' the stream to a consumer using JMS routing/load
balancing.  And ideally the contents of the stream would be sent out
band with respect to the JMS network.

It seems to me that if we can handle a case like that, transmitting
URL or File based resources is just a simple case of the above.

Regards,
Hiram

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

Saw an interesting blog post today...

http://weblogs.java.net/blog/guruwons/archive/2006/11/sending_large_f.html

As I mentioned on the comments, I'd like to extend this a little to
support both out-of-band transfer (e.g. its basically a message with a
URL in it to that the user can download the file from some remote
destination) or the file is actually sent over the JMS network, so it
can act as a facade to the existing JMS Streams feature...

http://incubator.apache.org/activemq/jms-streams.html

So am thinking from a client API perspective they do one of the following...

// send a message out of band...
FileMessage message = session.createRemoteFileMessage(new
URL("http:///foo.com/bar.jpg";));

// send a local file over the JMS network
FileMessage message = session.createLocalFileMessage(new
File("~/myfiles/bar.jpg"));

then for consumers...

if (message instanceof FileMessage) {
  FileMessage fileMessage = (FileMessage) message;
  InputStream in = fileMessage.getInputStream();
  // lets read the file...

  // or lets force the file to be manifested as a local file so we can
work directly on the file instead

  URL url = fileMessage.getURL();
  // we can now open the file as many times as we like...
}

Thoughts?

--

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




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: ActiveMQ CPP Change log.

[Hiram Chirino]

Ok.  I've created a new JIRA space for ActiveMQ CPP..

see:
https://issues.apache.org/activemq/browse/AMQCPP

I've made you a jira admin for the space so you should be able to add
components / versions for the space.  You should also be able to move
all the issues from the AMQ space to this new space.  If you need
help, let me know!

Once you get it all setup, it might be handy to update the
http://incubator.apache.org/activemq/support.html page so that folks
know which space to open an issue under for the c++ stuff.


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

Thanks!

I just ran a filter in JIRA for any closed or resolved issues in the
ActiveMQ space under CMS ... After looking the ActiveMQ release pages I
was able to figure it out :)

I think moving forward, it might be easier to have AMQ-CPP in it's own
space - that way the filter criteria gets a lot simpler - We would just
have to select every resolved issue that was targeted for that
particular release of AMQ-CPP.

Nate

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
Chirino
Sent: Wednesday, November 15, 2006 12:41 PM
To: activemq-dev@geronimo.apache.org
Subject: ActiveMQ CPP Change log.


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




--
Regards,
Hiram

Blog: http://hiramchirino.com

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

[Hiram Chirino]

Why don't we get the ball rolling on graduation and IF they choose to
make us a TLP, then we start looking into that??

On 11/15/06, Brian McCallister <[EMAIL PROTECTED]> wrote:

On Nov 15, 2006, at 12:14 PM, Hiram Chirino wrote:

> Want to take the lead on that? :) please!

Sure. Any nominations for proposed PMC Chair?

-Brian

>
> On 11/15/06, Brian McCallister <[EMAIL PROTECTED]> wrote:
>> Yes!
>>
>> We should present a fully formed resolution, based on the OFBiz
>> thread.
>>
>> -Brian
>>
>> On Nov 15, 2006, at 10:52 AM, Hiram Chirino wrote:
>>
>> > 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
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com





--
Regards,
Hiram

Blog: http://hiramchirino.com

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

[Hiram Chirino]

Want to take the lead on that? :) please!

On 11/15/06, Brian McCallister <[EMAIL PROTECTED]> wrote:

Yes!

We should present a fully formed resolution, based on the OFBiz thread.

-Brian

On Nov 15, 2006, at 10:52 AM, Hiram Chirino wrote:

> 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





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release ServiceMix 3.0.1

[Hiram Chirino]

[X] +1 Release ServiceMix 3.0.1

I ran the rat tool on the source and binary disto and I've attached it
to this email.  Lots of pom files don't have the asl header but I've
got a feeling that you may have used the maven release plugin and that
strips out comments from the poms.

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

The previous vote has been put on hold due to a problem
in the maven repository with an invalid pom.  This problem
has been solved, so I'd like to push out the release built
some weeks ago now.

Binaries have been uploaded on the incubating repository:
http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/

[ ] +1 Release ServiceMix 3.0.1
[ ] +/- 0
[ ] -1 Do not release ServiceMix 3.0.1

Here's my +1

--
Cheers,
Guillaume Nodet




--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: [VOTE] Release ServiceMix 3.0.1

[Hiram Chirino]

Here ya go!

http://www.nabble.com/file/4171/rat.log rat.log 
http://www.nabble.com/file/4172/rat-binary.log rat-binary.log 



gnodet wrote:
> 
> Could you please attach the output to the nabble forums ?
> It seems it has been removed :(
> 
> On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>>  [X] +1 Release ServiceMix 3.0.1
>>
>> I ran the rat tool on the source and binary disto and I've attached it
>> to this email.  Lots of pom files don't have the asl header but I've
>> got a feeling that you may have used the maven release plugin and that
>> strips out comments from the poms.
>>
>> On 11/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>> > The previous vote has been put on hold due to a problem
>> > in the maven repository with an invalid pom.  This problem
>> > has been solved, so I'd like to push out the release built
>> > some weeks ago now.
>> >
>> > Binaries have been uploaded on the incubating repository:
>> >
>> http://people.apache.org/repo/m2-incubating-repository/org/apache/servicemix/apache-servicemix/3.0.1-incubating/
>> >
>> > [ ] +1 Release ServiceMix 3.0.1
>> > [ ] +/- 0
>> > [ ] -1 Do not release ServiceMix 3.0.1
>> >
>> > Here's my +1
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>>
>>
>> --
>> Regards,
>> Hiram
>>
>> Blog: http://hiramchirino.com
>>
>>
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> 
> 
-- 
View this message in context: 
http://www.nabble.com/-VOTE--Release-ServiceMix-3.0.1-tf2629945s12049.html#a7340935
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

[jira] Updated: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQ-1045:
---

Description: The DefaultMessageListenerContainer has retry logic built into 
it. When a connection dies it tried to reconnect by getting a new connection 
from the ConnectionFactory. Since the PooledConenctionFactory has one 
Connection it, it keeps on trying to give out the Connection that died. We 
would like the PooledConnectionFactory to be able to "evict" the dead 
connection and create a new one.

> PooledConnectionFactory does not work with the 
> org.springframework.jms.listener.DefaultMessageListenerContainer in the 
> failure case
> ---
>
> Key: AMQ-1045
> URL: https://issues.apache.org/activemq/browse/AMQ-1045
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
>Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.2.0, 4.1.1
>
>
> The DefaultMessageListenerContainer has retry logic built into it. When a 
> connection dies it tried to reconnect by getting a new connection from the 
> ConnectionFactory. Since the PooledConenctionFactory has one Connection it, 
> it keeps on trying to give out the Connection that died. We would like the 
> PooledConnectionFactory to be able to "evict" the dead connection and create 
> a new one.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Hiram Chirino]

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

[jira] Resolved: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1045.


Resolution: Fixed

Fixed in trunk rev 474799 and in 4.1 branch rev 474800

> PooledConnectionFactory does not work with the 
> org.springframework.jms.listener.DefaultMessageListenerContainer in the 
> failure case
> ---
>
> Key: AMQ-1045
> URL: https://issues.apache.org/activemq/browse/AMQ-1045
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.1, 4.2.0
>
>
> The DefaultMessageListenerContainer has retry logic built into it. When a 
> connection dies it tried to reconnect by getting a new connection from the 
> ConnectionFactory. Since the PooledConenctionFactory has one Connection it, 
> it keeps on trying to give out the Connection that died. We would like the 
> PooledConnectionFactory to be able to "evict" the dead connection and create 
> a new one.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case

[Hiram Chirino (JIRA)]

PooledConnectionFactory does not work with the 
org.springframework.jms.listener.DefaultMessageListenerContainer in the failure 
case
---

 Key: AMQ-1045
 URL: https://issues.apache.org/activemq/browse/AMQ-1045
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1.1, 4.2.0




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

ActiveMQ POM

[Hiram Chirino]

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

Re: ActiveMQ POM

[Hiram Chirino]

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

Re: amazon client supported platforms

[Hiram Chirino]

Not supported out of box.  If you want to take a stab at doing a port,
please be my guest!  Patches would be welcomed!

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


Hi,

which platforms amazon activemq client is proposed to be built on?
I built it on RHEL4 Linux without any problems, then I tried to build it
under Cygwin.

Here are the last lines of build failure:

 g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE
_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"amq_openwirecpp\"
-DVERSION=\"
0.1.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_
H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -
DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -I. -I.
-I.
./ -I/cygdrive/c/boost_1_33_1/ -MT TCPTransport.lo -MD -MP -MF
.deps/TCPTranspor
t.Tpo -c TCPTransport.cpp  -DPIC -o .libs/TCPTransport.o
TCPTransport.cpp: In member function `virtual void
ActiveMQ::TCPTransport::conne
ct()':
TCPTransport.cpp:50: error: aggregate `addrinfo hints' has incomplete type
and c
annot be defined
TCPTransport.cpp:52: error: invalid application of `sizeof' to incomplete
type `
addrinfo'
TCPTransport.cpp:56: error: `getaddrinfo' undeclared (first use this
function)
TCPTransport.cpp:56: error: (Each undeclared identifier is reported only
once fo
r each function it appears in.)
TCPTransport.cpp:58: error: `gai_strerror' undeclared (first use this
function)
TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo'
TCPTransport.cpp:50: error: forward declaration of `struct addrinfo'
TCPTransport.cpp:60: error: invalid use of undefined type `struct addrinfo'
TCPTransport.cpp:50: error: forward declaration of `struct addrinfo'
TCPTransport.cpp:61: error: `freeaddrinfo' undeclared (first use this
function)
make[1]: *** [TCPTransport.lo] Error 1
make[1]: Leaving directory `/home/motl/devel/amazon/amq_transport'
make: *** [all-recursive] Error 1
...

Is Cygwin platform supported ? How can I cope with it?

Thank you.




--
View this message in context: 
http://www.nabble.com/amazon-client-supported-platforms-tf2628734.html#a7335457
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Resolved: (AMQ-1044) Failed to register MBean error.

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1044.


Resolution: Fixed

Fixed in trunk rev 474769 and in 4.1 branch rev 474771

> Failed to register MBean error.
> ---
>
> Key: AMQ-1044
> URL: https://issues.apache.org/activemq/browse/AMQ-1044
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1.1, 4.2.0
>
>
> If async error such as a inactivity IO exception is detected while a 
> subscription is being created, then that subscription is not fully cleaned up 
> when the connection is disposed.  If the client is using failover and 
> reconnects, then it gets a "Failed to register MBean error."  Since the 
> subscription is still registered in JMX.  This is also a source of a memory 
> leak since subscriptions are are left registered in JMX.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1044) Failed to register MBean error.

[Hiram Chirino (JIRA)]

Failed to register MBean error.
---

 Key: AMQ-1044
 URL: https://issues.apache.org/activemq/browse/AMQ-1044
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1.1, 4.2.0


If async error such as a inactivity IO exception is detected while a 
subscription is being created, then that subscription is not fully cleaned up 
when the connection is disposed.  If the client is using failover and 
reconnects, then it gets a "Failed to register MBean error."  Since the 
subscription is still registered in JMX.  This is also a source of a memory 
leak since subscriptions are are left registered in JMX.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Lets vote: activemq-cpp-1.0 release

[Hiram Chirino]

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

Hey Hiram,
So how does the PMC vote on releases?  Do we need to have a RC available for
download - or will they just sort of take the ppmc's word for it and vote it
in?


Yes, they vote on the RC artifacts that we just voted on.  They will
also review the distribution for any possible legal issues.  Here's a
simple template you can use for your vote email to the incubator
lists:

http://www.nabble.com/-VOTE--Release-Apache-ActiveMQ-4.0.2-%28RC-6%29-tf2537153.html

Things like the "[VOTE]" subject header and the '[ ] +1 Release the
binary  [ ] -1 Veto the release... " in the email make it easy for
folks identify it as a vote thread and easier for them to submit their
vote.



Also, is there anything else we need to do in advance?  Updates to the
website, etc?


Well some sort of release notes for on the website would be nice. For
example, I would recommend you add a page similar to:
http://activemq.com/site/activemq-410-release.html
and link to it from http://activemq.com/site/download.html

If you've never used our wiki, it's a simple, just hit the edit link
at the bottom of every page.



I'm such a n00b! :)

Thanks,
Nate

On 11/13/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>
> Hi Nathan,
>
> Actually.. you can't yet.  Once the ppmc has approved a release, the
> release must be approved by at least 3 incubator PMC members.
>
> You should tally the vote and then start a new vote thread on the
> general @ incubator mailing list.
>
> On 11/13/06, Mittler, Nathan <[EMAIL PROTECTED]> wrote:
> > Great!  That'll do it - thanks, guys!
> >
> > We'll update the website with the release.
> >
> > Nate
> >
> > -Original Message-
> > From: Jonas Lim [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, November 12, 2006 8:36 PM
> > To: activemq-dev@geronimo.apache.org
> > Subject: Re: Lets vote: activemq-cpp-1.0 release
> >
> >
> >
> > +1
> >
> > Regards,
> > Jonas
> > Timothy Bish 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
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Updated: (AMQ-651) Deadlock in ActiveMQ close processing of Resource Adapter

[Hiram Chirino (JIRA)]

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

Hiram Chirino updated AMQ-651:
--

Comment: was deleted

> Deadlock in ActiveMQ close processing of Resource Adapter
> -
>
> Key: AMQ-651
> URL: https://issues.apache.org/activemq/browse/AMQ-651
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>    Reporter: Hiram Chirino
> Fix For: 4.0
>
>
> Need to check to see if this is still valid against 4.x
> See:
> http://issues.apache.org/jira/browse/GERONIMO-1493

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Lets vote: activemq-cpp-1.0 release

[Hiram Chirino]

Hi Nathan,

Actually.. you can't yet.  Once the ppmc has approved a release, the
release must be approved by at least 3 incubator PMC members.

You should tally the vote and then start a new vote thread on the
general @ incubator mailing list.

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

Great!  That'll do it - thanks, guys!

We'll update the website with the release.

Nate

-Original Message-
From: Jonas Lim [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 12, 2006 8:36 PM
To: activemq-dev@geronimo.apache.org
Subject: Re: Lets vote: activemq-cpp-1.0 release



+1

Regards,
Jonas
Timothy Bish 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

[jira] Created: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.

[Hiram Chirino (JIRA)]

The JMSConsumerTest interminitently failed on linux systems.


 Key: AMQ-1042
 URL: https://issues.apache.org/activemq/browse/AMQ-1042
 Project: ActiveMQ
  Issue Type: Bug
  Components: CMS (C++ client)
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1, 4.2


JMSConsumerTest fails on linux sometimes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-465) deadlock when using VM transport and Jencks...

[Hiram Chirino (JIRA)]

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

Hiram Chirino commented on AMQ-465:
---

This was fixed in rev 386335.

> deadlock when using VM transport and Jencks...
> --
>
> Key: AMQ-465
> URL: https://issues.apache.org/activemq/browse/AMQ-465
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.0 M4
>Reporter: james strachan
> Assigned To: Hiram Chirino
> Fix For: 4.0 RC2
>
>
> Background here: http://forums.logicblaze.com/posts/list/146.page
> It seems to be VM protocol specific

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Work started: (AMQ-976) Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects.

[Hiram Chirino (JIRA)]

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

Work on AMQ-976 started by Hiram Chirino.

> Abstract the Transport and TransportListener Interfaces so that the move 
> around Objects instead of Command and Response objects.
> 
>
> Key: AMQ-976
> URL: https://issues.apache.org/activemq/browse/AMQ-976
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> If the Transport and TransportListener interfaces can be abstracted even more 
> so that they move around Objects instead of Commands and Responses.  This 
> would allow us to use most of the Transport components with other command 
> sets besides the current ActiveMQ one.
> The main use case I'm thinking of is the possibility of supporting the qpid 
> command set directly by the broker.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-976) Abstract the Transport and TransportListener Interfaces so that the move around Objects instead of Command and Response objects.

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-976.
---

Resolution: Fixed

done.

> Abstract the Transport and TransportListener Interfaces so that the move 
> around Objects instead of Command and Response objects.
> 
>
> Key: AMQ-976
> URL: https://issues.apache.org/activemq/browse/AMQ-976
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> If the Transport and TransportListener interfaces can be abstracted even more 
> so that they move around Objects instead of Commands and Responses.  This 
> would allow us to use most of the Transport components with other command 
> sets besides the current ActiveMQ one.
> The main use case I'm thinking of is the possibility of supporting the qpid 
> command set directly by the broker.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1026.


Resolution: Fixed

> Sometimes a failover connection on reconnect produces a Client ID:x-1:1 
> already connected error message.
> 
>
> Key: AMQ-1026
> URL: https://issues.apache.org/activemq/browse/AMQ-1026
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.

[Hiram Chirino (JIRA)]

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

Hiram Chirino commented on AMQ-1026:


fixed in trunk rev 471837

> Sometimes a failover connection on reconnect produces a Client ID:x-1:1 
> already connected error message.
> 
>
> Key: AMQ-1026
> URL: https://issues.apache.org/activemq/browse/AMQ-1026
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: activemq-cpp-1.0 release candidate

[Hiram Chirino]

Hi Tim,

It looks like a good start!

It compiled great under OS X and the unit tests passed fine.  The
integration tests bombed out though:

$ src/test-integration/activemq-test-integration
integration::durable::DurableTester::test.Starting activemqcms durable
test (sending 1000 messages per type and sleeping 5 milli-seconds) ...

caught unknown exception - tid: 50423296
   FILE: ./../main/activemq/concurrent/Lock.h, LINE: 111 - tid: 50423296
Bus error

Also... I noticed that we have some files with mixed line endings..
.specifically configure.ac.  We might want to make sure the svn eol
style is set to native on all the text files.

We should add a apache copyright header to
./autogen.sh
**/Makefile.am

The xcode project is also not setup correctly.. I'll work on getting
this right and commit the fix shortly.


On 11/6/06, Timothy Bish <[EMAIL PROTECTED]> wrote:

Hey all



I've put together a source archive containing the release candidate for
activemq-cpp 1.0 and placed it in my account here:
http://people.apache.org/~tabish/



I've cut a 1.0 tag for this as well in SVN located at:

https://svn.apache.org/repos/asf/incubator/activemq/activemq-cpp/tags/active
mq-cpp-1.0



take a look, see if there's anything missing or in need of changing before
we call it done.



Regards

Tim.










--
Regards,
Hiram

Blog: http://hiramchirino.com

ActiveMQ core test suite

[Hiram Chirino]

Hi folks!

I've been looking at the activemq-core test suite and it keep getting
bigger and bigger and takes longer and long to run.  Ideally tests
should only take like 5 minutes to run.  What do you think we should
do about it?

We are currently forking each test case, so if we could avoid that it
should speed it up a bit.  Any other ideas?  Perhaps we can classify
some of the tests as being only needed for integration testing??

--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Commented: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.

[Hiram Chirino (JIRA)]

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

Hiram Chirino commented on AMQ-1026:


timing issues.. if the client reconnect back to the broker before it detects it 
failure, the broker does not properly clean up the previous connection 
resources.

> Sometimes a failover connection on reconnect produces a Client ID:x-1:1 
> already connected error message.
> 
>
> Key: AMQ-1026
> URL: https://issues.apache.org/activemq/browse/AMQ-1026
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0
>    Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
> Fix For: 4.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1026) Sometimes a failover connection on reconnect produces a Client ID:xxxxx-1:1 already connected error message.

[Hiram Chirino (JIRA)]

Sometimes a failover connection on reconnect produces a Client ID:x-1:1 
already connected error message.


 Key: AMQ-1026
 URL: https://issues.apache.org/activemq/browse/AMQ-1026
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Hiram Chirino
 Fix For: 4.1




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Problem with latest 4.1 SNAPSHOT when broker name is set

[Hiram Chirino]

Yep.. looks like problem with the CommandAgent.  The
vm://${brokerName} connector will start up  a broker named
${brokerName} if it is not already running.  I just need to adjust the
start up code so that the command agent is set with the right
connection URI.

On 11/1/06, Jason Dillon <[EMAIL PROTECTED]> wrote:

Folks, there is a problem with the latest 4.1 SNAPSHOT when a broker
name is set.  It causes 2 brokers to be created... and I think it is
because of the newly added CommandAgent service which is added to the
brokers default services when started.  It is using vm://localhost,
which appears to be creating a new Broker using the name "localhost"
when the broker it is attached to has a different name.

For example:


BrokerService broker = new BrokerService();
broker.setBrokerName("foo");
broker.start();


Will end up creating a broker name "foo" and then another named
"localhost".

Where, this will create one broker, named "localhost":


BrokerService broker = new BrokerService();
broker.start();


I'm not really sure how vm://* works with respect to broker names...
so I can not say for sure what the fix is, or why this is happening.
But I can say for sure that the above snips create 2 and 1 brokers
respectively.

We noticed this while trying to track down a rouge activemq-data
directory which kept popping up in Geronimo, which for some reason
had its broker gbean set to create a broker with the name "possibly-
unique-broker".  I've fixed this by only setting the broker name if
it is non-null, and then commenting out the brokerName attributed in
the plan, but something is definitely broke on your side of the fence
wrt broker names and vm:// transports.

--jason






--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: activemq-cpp build on linux

[Hiram Chirino]

Hi Nathan,

build with:

make check

that will run the unit tests and build but not run the integration
tests.  You should see the integration tests.

On 10/29/06, Nathan Mittler <[EMAIL PROTECTED]> wrote:

Hey guys, I've got all the unit tests running with make check and would now
like to run the integ tests against the 4.0.2 broker.  This way we can draw
a line in the sand that says the activemq-cpp client works against all
brokers >= 4.0.2.  How do I run the integration tests with the new automake
environment?  I'm not seeing an executable around anywhere.

Thanks,
Nate

On 10/26/06, Nathan Mittler <[EMAIL PROTECTED]> wrote:
>
> That worked - Thanks guys!
>
> On 10/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
> >
> > I'd suggest removing all the old makefiles  before running
> > the ./configure, that will avoid any confusion of makefiles.  You
> > shouldn't need to older OSTYPE etc stuff with the new ones.
> >
> > --
> > Timothy A. Bish
> > [EMAIL PROTECTED]
> >
> >
> > - Original Message -
> > From: Nathan Mittler <[EMAIL PROTECTED]>
> > Date: Monday, October 23, 2006 2:54 pm
> > Subject: activemq-cpp build on linux
> > To: activemq-dev@geronimo.apache.org
> >
> > > I'm stumbling through the new build system on linux ... here's
> > > what I did
> > > after a fresh check-out ...
> > >
> > > ./autogen.sh
> > > ./configure
> > > make -f Makefile
> > >
> > > The first thing that I noticed was that I have to have the
> > environment
> > > variables CONFIG and OSTYPE defined, as it appears to be looking
> > > for the
> > > makefile-linux-debug.cfg file.  Is this expected?  It seems that
> > > that was
> > > how the old makefile worked - I didn't expect that to be used by
> > > the new
> > > setup.
> > >
> > > If I define CONFIG=debug and OSTYPE=linux, then I get an error
> > > saying that
> > > no target "all-recursive" has been defined:
> > >
> > > [EMAIL PROTECTED] activemq-cpp]$ make -f Makefile
> > > make  all-recursive
> > > make[1]: Entering directory
> > > `/home/nmittler/activemq-cpp-workspace/activemq-cpp'
> > > make[1]: *** No rule to make target `all-recursive'.  Stop.
> > > make[1]: Leaving directory
> > > `/home/nmittler/activemq-cpp-workspace/activemq-cpp'
> > > make: *** [all] Error 2
> > >
> > > ... does anyone have an idea of what I might be doing wrong?
> > >
> > > Thanks,
> > > Nate
> > >
> >
>
>





--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: All new committers and PMC members in the last quarter please reply

[Hiram Chirino]

Now on the pmc list.

On 10/27/06, Jeff Genender <[EMAIL PROTECTED]> wrote:

I figured this will get some people's attention.

If you have recently become a committer or PMC member since July, please
reply to this thread.

Thanks!

Jeff




--
Regards,
Hiram

Blog: http://hiramchirino.com

[jira] Created: (AMQ-1004) Upgrade to spring 2.0 and xbean 2.7

[Hiram Chirino (JIRA)]

Upgrade to spring 2.0 and xbean 2.7
---

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




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1004) Upgrade to spring 2.0 and xbean 2.7

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1004.


Resolution: Fixed

fix in 467783

> Upgrade to spring 2.0 and xbean 2.7
> ---
>
> Key: AMQ-1004
> URL: https://issues.apache.org/activemq/browse/AMQ-1004
> Project: ActiveMQ
>  Issue Type: Improvement
>        Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
> Fix For: 4.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-978) No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java JMS Producer/Consumer

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-978.
---

Fix Version/s: 4.1
   4.0.2
   Resolution: Fixed

> No Messaged delivery when mixing Perl stomp client Producer/Consumer and Java 
> JMS Producer/Consumer
> ---
>
> Key: AMQ-978
> URL: https://issues.apache.org/activemq/browse/AMQ-978
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
> Environment: This problem seems platform independent: It happens in 
> Linux, Mac OSX, and Windows.
> Software Used: ActiveMQ 4.0, Java 5.0, JMS, Perl 5.8.7, Perl CPAN module 
> Net-Stomp-0.31
>Reporter: Sileshi Kassa
> Assigned To: Hiram Chirino
> Fix For: 4.1, 4.0.2
>
> Attachments: Net-Stomp-0.31-bytemessage-support.patch, 
> Net-Stomp-0.31-bytemessage-support.sileshi-patch, Publisher.pl, Subscriber.pl
>
>
> Facts: Perl Stomp client Producer and Consumer works fine
>Java JMS client Producer and Consumer works fine
> I have also used other Perl Stomp protocol implementation with no problem.
> The problem happens when I mix Java and Perl clients
> Scenario Test 1:
> A. Perl Stomp client Consumer
> B. Java JMS client Producer
> Scenario Test 2:
> A. Java JMS client Consumer
> B. Perl Stomp client Producer
> I have looked into it via Java JMX management jconsole, and it seems to me 
> there is a wall between
> the stomp server and default server. It the stomp server only passes messages 
> coming from stomp lients
> and default server also does the same.
> If this is truly the case, and this is by design, I will be very 
> disappointed. There should not be any wall.
> A message is message irrespective of its source and should be delivered to 
> any one that is listening
> on the same destination.
> I will attach the Perl clients testcases.
> For Java client,  a simple JMS client Producer and Consumer with the same 
> topic used as
> the perl side will do the job. The topic I used on the perl side: 
> "/topic/Test.CrossDelivery"
> and the Java side topic is  "Test.CrossDelivery"
> This problem is a show stopper for us.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1002) org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml

[Hiram Chirino (JIRA)]

org.apache.activemq.spring.SpringTest.testSenderWithSpringXmlUsingSpring2NamespacesWithEmbeddedBrokerConfiguredViaXml
-

 Key: AMQ-1002
 URL: https://issues.apache.org/activemq/browse/AMQ-1002
 Project: ActiveMQ
  Issue Type: Test
Reporter: Hiram Chirino
 Fix For: 4.1


Upgrading to spring 2.0 broker this test.  Commenting out till we can fix it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1001) Allow the openwire value cache size to be configurable.

[Hiram Chirino (JIRA)]

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

Hiram Chirino resolved AMQ-1001.


Resolution: Fixed

Added in revision 467676 in trunk

> Allow the openwire value cache size to be configurable.
> ---
>
> Key: AMQ-1001
> URL: https://issues.apache.org/activemq/browse/AMQ-1001
> Project: ActiveMQ
>  Issue Type: New Feature
>        Reporter: Hiram Chirino
>     Assigned To: Hiram Chirino
> Fix For: 4.1
>
>
> This means that the cache size needs to be a negociated option between the 
> client and broker.  We should also default the cache size to be much smaller 
> like 1024 since every connection was using too much memory for cached objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira