date:20150319


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

方春柳 updated AMQ-5667:
-
Comment: was deleted

(was: Yes, I have tested in the latest version.

And I see the new code is also did not modify the bug)

> Asynchronous sending non persistence messages,it will error,please see 
> description
> --
>
> Key: AMQ-5667
> URL: https://issues.apache.org/jira/browse/AMQ-5667
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.0
>Reporter: 方春柳
>
> Asynchronous sending non persistence messages
> 1、Set the connection‘s producerWindowSize parameter larger than zero.
> 2、Set the sendFailIfNoSpaceAfterTimeout parameter larger than zero.
> 3、Use VMQueueCursor as a message storeage
> 4、Start producer and Send a lot of messages until the broker memory occupied.
> 5、Start consumer spending all the messages.
> 6、You’ll find the producer did not continue to send message but has been 
> blocked
> Reason:No memoryUsage calls the decreaseUsage method on the client broker to 
> remove the timeout message, resulting in producer has been blocked in the 
> waitForSpace method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5667) Asynchronous sending non persistence messages,it will error,please see description


[ 
https://issues.apache.org/jira/browse/AMQ-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370608#comment-14370608
 ] 

方春柳 commented on AMQ-5667:
--

Yes, I have tested in the latest version.
And I see the new code is also did not modify the bug

> Asynchronous sending non persistence messages,it will error,please see 
> description
> --
>
> Key: AMQ-5667
> URL: https://issues.apache.org/jira/browse/AMQ-5667
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.0
>Reporter: 方春柳
>
> Asynchronous sending non persistence messages
> 1、Set the connection‘s producerWindowSize parameter larger than zero.
> 2、Set the sendFailIfNoSpaceAfterTimeout parameter larger than zero.
> 3、Use VMQueueCursor as a message storeage
> 4、Start producer and Send a lot of messages until the broker memory occupied.
> 5、Start consumer spending all the messages.
> 6、You’ll find the producer did not continue to send message but has been 
> blocked
> Reason:No memoryUsage calls the decreaseUsage method on the client broker to 
> remove the timeout message, resulting in producer has been blocked in the 
> waitForSpace method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMQ-5667) Asynchronous sending non persistence messages,it will error,please see description


[ 
https://issues.apache.org/jira/browse/AMQ-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370531#comment-14370531
 ] 

方春柳 edited comment on AMQ-5667 at 3/20/15 1:39 AM:
---

Yes, I have tested in the latest version.

And I see the new code is also did not modify the bug


was (Author: qq7689791):
Yes, I have tested in the latest version.

and i see the new code is not modified.

> Asynchronous sending non persistence messages,it will error,please see 
> description
> --
>
> Key: AMQ-5667
> URL: https://issues.apache.org/jira/browse/AMQ-5667
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.0
>Reporter: 方春柳
>
> Asynchronous sending non persistence messages
> 1、Set the connection‘s producerWindowSize parameter larger than zero.
> 2、Set the sendFailIfNoSpaceAfterTimeout parameter larger than zero.
> 3、Use VMQueueCursor as a message storeage
> 4、Start producer and Send a lot of messages until the broker memory occupied.
> 5、Start consumer spending all the messages.
> 6、You’ll find the producer did not continue to send message but has been 
> blocked
> Reason:No memoryUsage calls the decreaseUsage method on the client broker to 
> remove the timeout message, resulting in producer has been blocked in the 
> waitForSpace method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5667) Asynchronous sending non persistence messages,it will error,please see description


[ 
https://issues.apache.org/jira/browse/AMQ-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370531#comment-14370531
 ] 

方春柳 commented on AMQ-5667:
--

Yes, I have tested in the latest version.

and i see the new code is not modified.

> Asynchronous sending non persistence messages,it will error,please see 
> description
> --
>
> Key: AMQ-5667
> URL: https://issues.apache.org/jira/browse/AMQ-5667
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.0
>Reporter: 方春柳
>
> Asynchronous sending non persistence messages
> 1、Set the connection‘s producerWindowSize parameter larger than zero.
> 2、Set the sendFailIfNoSpaceAfterTimeout parameter larger than zero.
> 3、Use VMQueueCursor as a message storeage
> 4、Start producer and Send a lot of messages until the broker memory occupied.
> 5、Start consumer spending all the messages.
> 6、You’ll find the producer did not continue to send message but has been 
> blocked
> Reason:No memoryUsage calls the decreaseUsage method on the client broker to 
> remove the timeout message, resulting in producer has been blocked in the 
> waitForSpace method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

2015-03-19 Thread Hadrian Zbarcea


That is very true. -1 as well.
Hadrian

On 03/19/2015 08:57 PM, artnaseef wrote:

I will continue to look at this as I can find time.

One question I'm seeing now - the artifact naming is using activemq- for the
prefix, and a greater concern is the overlap of the artifacts like the
followin:

* activemq-ra
* activemq-web

I'm concerned that Maven central will have two sets of artifacts with the
activemq name, which will lead to confusion for users.  And, I'm especially
concerned that two totally different artifacts with the same name will be in
maven central.

Until HornetQ becomes a replacement for ActiveMQ and we decide to stop
maintaining ActiveMQ, I'm concerned that we need to avoid this type of
confusion.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693512.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

I will continue to look at this as I can find time.

One question I'm seeing now - the artifact naming is using activemq- for the
prefix, and a greater concern is the overlap of the artifacts like the
followin:

* activemq-ra
* activemq-web

I'm concerned that Maven central will have two sets of artifacts with the
activemq name, which will lead to confusion for users.  And, I'm especially
concerned that two totally different artifacts with the same name will be in
maven central.

Until HornetQ becomes a replacement for ActiveMQ and we decide to stop
maintaining ActiveMQ, I'm concerned that we need to avoid this type of
confusion.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693512.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Hadrian Zbarcea

+1
Hadrian

On 03/19/2015 06:04 PM, Rob Davies wrote:

At some point, it could well make sense to call the HornetQ release ActiveMQ 6
- but not yet. This has caused a lot of confusion- it should be called
something else ??

On 19 Mar 2015, at 19:40, Kevin Burton wrote:

Actually, this is probably the right way to phrase it. Maybe just on the
HOME PAGE of AMQ 6 just have a call out.

I think it’s fair to work on a new broker because ActiveMQ 5 would need a
lot of work in a lot of areas to modernize it.

That said. It think the 5.x series should also be maintained for a while.
So maybe just having them clearly explained that they are different things.

Also, is Apollo dead and development officially moving to AMQ6 ? if so
perhaps the best strategy is to mark it as so.

On Thu, Mar 19, 2015 at 9:26 AM, artnaseef wrote:

ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
5.x.

The ActiveMQ 6 name was once used for Apollo and now it's used for HornetQ.
Yes, it's confusing.

Personally, I will be referring to the existing ActiveMQ
(https://github.com/apache/activemq), and only that code base, as
ActiveMQ -
until we have a plan that somehow one replaces the other. If you catch me
using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack me
in the back of the head ;-).

I'm sorry for your confusion. It is a major concern that you were confused
and spent time and effort to work on HornetQ when you thought you were
upgrading ActiveMQ.

--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693463.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

Regardless of being an issue or not.. please go further on your
analysis. place the output on /tmp or anywhere else.. and lets us know
if this is the only issue you see.

On Thu, Mar 19, 2015 at 7:32 PM, artnaseef  wrote:
> There is a bigger concern here.  Apache project releases are source code
> releases.  The intent is for folks to be able to work in these directories.
>
> Failing the build on license checks on non-build files is going to be a
> concern.  It just doesn't make sense - and it should be easy to fix.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693508.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

I agree it's an issue. I disagree it's a blocker.

as I said anyone can just switch the directory to any other folder for
the log output.

On Thu, Mar 19, 2015 at 7:32 PM, artnaseef  wrote:
> There is a bigger concern here.  Apache project releases are source code
> releases.  The intent is for folks to be able to work in these directories.
>
> Failing the build on license checks on non-build files is going to be a
> concern.  It just doesn't make sense - and it should be easy to fix.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693508.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

There is a bigger concern here.  Apache project releases are source code
releases.  The intent is for folks to be able to work in these directories.

Failing the build on license checks on non-build files is going to be a
concern.  It just doesn't make sense - and it should be easy to fix.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693508.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

2015-03-19 Thread Clebert

We can fix that. But it's not a reason to hold the release.  Just send it to 
/tmp/build.log 

-- Clebert Suconic typing on the iPhone. 

> On Mar 19, 2015, at 18:56, artnaseef  wrote:
> 
> -1
> 
> First off, please start a new thread for the next vote.  This is getting
> confusing.  (That has nothing to do with the -1).
> 
> Second, I have to -1 on this vote because of a build failure while trying to
> build the project using the following command which captures the full
> output:
> 
>script BUILD.log mvn clean install
> 
> The error indicates the file BUILD.log is missing a license header.
> 
> I look forward to the next RC!
> 
> 
> 
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693505.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

2015-03-19 Thread Clebert

This is not a failure.  Send the build.log to another directory. 

-- Clebert Suconic typing on the iPhone. 

> On Mar 19, 2015, at 18:56, artnaseef  wrote:
> 
> -1
> 
> First off, please start a new thread for the next vote.  This is getting
> confusing.  (That has nothing to do with the -1).
> 
> Second, I have to -1 on this vote because of a build failure while trying to
> build the project using the following command which captures the full
> output:
> 
>script BUILD.log mvn clean install
> 
> The error indicates the file BUILD.log is missing a license header.
> 
> I look forward to the next RC!
> 
> 
> 
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693505.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 6.0.0 (RC3)

-1

First off, please start a new thread for the next vote.  This is getting
confusing.  (That has nothing to do with the -1).

Second, I have to -1 on this vote because of a build failure while trying to
build the project using the following command which captures the full
output:

script BUILD.log mvn clean install

The error indicates the file BUILD.log is missing a license header.

I look forward to the next RC!



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-tp4692911p4693505.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: ActiveMQ 6.0.0 required Java 8?

+1

I think the point at which HornetQ becomes ActiveMQ 6 is a great question.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693504.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Memory Usage Test Plugin #1275

2015-03-19 Thread Apache Jenkins Server

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: Performance Test Plugin #1275

2015-03-19 Thread Apache Jenkins Server

See

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy #1275

2015-03-19 Thread Apache Jenkins Server

See

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Clebert

I believe there is a jira.  I will lookup later and if I can't find it will 
create it. 

-- Clebert Suconic typing on the iPhone. 

> On Mar 19, 2015, at 17:38, Krzysztof Sobkowiak  
> wrote:
> 
> Hi
> 
> Will ActiveMQ6 support OSGi like ActiveMQ5?
> 
> Regards
> Krzysztof
> 
>> On 19.03.2015 22:05, Clebert Suconic wrote:
>> the page is staged as part of the vote thread BTW. it should be
>> uploaded after being approved.
>> 
>>> On Thu, Mar 19, 2015 at 4:50 PM, artnaseef  wrote:
>>> Hey - where is this home page for "AMQ 6"?
>>> 
>>> Searching via google and browsing the ActiveMQ site, I only found an old
>>> Apollo page.
>>> 
>>> BTW - I don't know the state of Apollo, but I do know it's a totally
>>> separate set of source code from ActiveMQ and HornetQ.  Stating more clearly
>>> - there are three separate source repositories: ActiveMQ, Apollo, and
>>> HornetQ.
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693494.html
>>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
> 
> -- 
> Krzysztof Sobkowiak
> 
> JEE & OSS Architect
> Senior Solution Architect @ Capgemini SSC 
> Apache ServiceMix  Committer & PMC

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Rob Davies

At some point, it could well make sense to call the HornetQ release ActiveMQ 6 
- but not yet. This has caused a lot of confusion- it should be called 
something else ??

> On 19 Mar 2015, at 19:40, Kevin Burton  wrote:
> 
> Actually, this is probably the right way to phrase it.  Maybe just on the
> HOME PAGE of AMQ 6 just have a call out.
> 
> I think it’s fair to work on a new broker because ActiveMQ 5 would need a
> lot of work in a lot of areas to modernize it.
> 
> That said. It think the 5.x series should also be maintained for a while.
> So maybe just having them clearly explained that they are different things.
> 
> Also, is Apollo dead and development officially moving to AMQ6 ?  if so
> perhaps the best strategy is to mark it as so.
> 
>> On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:
>> 
>> ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
>> 5.x.
>> 
>> The ActiveMQ 6 name was once used for Apollo and now it's used for HornetQ.
>> Yes, it's confusing.
>> 
>> Personally, I will be referring to the existing ActiveMQ
>> (https://github.com/apache/activemq), and only that code base, as
>> ActiveMQ -
>> until we have a plan that somehow one replaces the other.  If you catch me
>> using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack me
>> in the back of the head ;-).
>> 
>> I'm sorry for your confusion.  It is a major concern that you were confused
>> and spent time and effort to work on HornetQ when you thought you were
>> upgrading ActiveMQ.
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693463.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> 
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> 
>

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Krzysztof Sobkowiak

Hi

Will ActiveMQ6 support OSGi like ActiveMQ5?

Regards
Krzysztof

On 19.03.2015 22:05, Clebert Suconic wrote:
> the page is staged as part of the vote thread BTW. it should be
> uploaded after being approved.
>
> On Thu, Mar 19, 2015 at 4:50 PM, artnaseef  wrote:
>> Hey - where is this home page for "AMQ 6"?
>>
>> Searching via google and browsing the ActiveMQ site, I only found an old
>> Apollo page.
>>
>> BTW - I don't know the state of Apollo, but I do know it's a totally
>> separate set of source code from ActiveMQ and HornetQ.  Stating more clearly
>> - there are three separate source repositories: ActiveMQ, Apollo, and
>> HornetQ.
>>
>>
>>
>> --
>> View this message in context: 
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693494.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>

-- 
Krzysztof Sobkowiak

JEE & OSS Architect
Senior Solution Architect @ Capgemini SSC 
Apache ServiceMix  Committer & PMC

Re: ActiveMQ 6.0.0 required Java 8?

It is not released *yet*:

http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-6-0-0-td4692911.html;cid=1426798955679-329


the page should be up after the release, then we can add anything
there about apollo, 6 and 5

On Thu, Mar 19, 2015 at 4:50 PM, artnaseef  wrote:
> Hey - where is this home page for "AMQ 6"?
>
> Searching via google and browsing the ActiveMQ site, I only found an old
> Apollo page.
>
> BTW - I don't know the state of Apollo, but I do know it's a totally
> separate set of source code from ActiveMQ and HornetQ.  Stating more clearly
> - there are three separate source repositories: ActiveMQ, Apollo, and
> HornetQ.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693494.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

Re: ActiveMQ 6.0.0 required Java 8?

the page is staged as part of the vote thread BTW. it should be
uploaded after being approved.

On Thu, Mar 19, 2015 at 4:50 PM, artnaseef  wrote:
> Hey - where is this home page for "AMQ 6"?
>
> Searching via google and browsing the ActiveMQ site, I only found an old
> Apollo page.
>
> BTW - I don't know the state of Apollo, but I do know it's a totally
> separate set of source code from ActiveMQ and HornetQ.  Stating more clearly
> - there are three separate source repositories: ActiveMQ, Apollo, and
> HornetQ.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693494.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

Re: ActiveMQ 6.0.0 required Java 8?

Hey - where is this home page for "AMQ 6"?

Searching via google and browsing the ActiveMQ site, I only found an old
Apollo page.

BTW - I don't know the state of Apollo, but I do know it's a totally
separate set of source code from ActiveMQ and HornetQ.  Stating more clearly
- there are three separate source repositories: ActiveMQ, Apollo, and
HornetQ.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693494.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: ActiveMQ 6.0.0 required Java 8?

On Thu, Mar 19, 2015 at 4:47 PM, Kevin Burton  wrote:
> When I get more time to look at 6.0.0 I’ll write up a post from an ActiveMQ
> perspective about what’s missing.  What I’m worried about is that ActiveMQ
> has a LOT of features (advisories for example) that would need some sort of
> support in 6.0.0 to make a migration from 5.0 to 6.0 possible.

http://people.apache.org/~martyntaylor/docs/6.0.0/management.html#management-notifications



>
> The reason we selected AMQ 5.x was because of these features and that they
> are *required* for our product to even work.
>
> On Thu, Mar 19, 2015 at 1:15 PM, Petter Nordlander <
> petter.nordlan...@enfo.se> wrote:
>
>> I can only agree.
>>
>> ActiveMQ 6.0.0, by the name, suggests that it¹s a successor to ActiveMQ,
>> which it¹s not as it¹s a successor to HornetQ with some elements from
>> ActiveMQ. Great work though, I like the initiative as such.
>>
>> As long as there is no upgrade path, the name will confuse users. A lot of
>> people will try it out just to find that half of the features they were
>> used to are gone. I guess a good start would be to clarify things on the
>> ActiveMQ homepage.
>>
>> BR Petter
>>
>> Den 2015-03-19 20:40 skrev Kevin Burton :
>>
>> >Actually, this is probably the right way to phrase it.  Maybe just on the
>> >HOME PAGE of AMQ 6 just have a call out.
>> >
>> >I think it¹s fair to work on a new broker because ActiveMQ 5 would need a
>> >lot of work in a lot of areas to modernize it.
>> >
>> >That said. It think the 5.x series should also be maintained for a while.
>> >So maybe just having them clearly explained that they are different
>> >things.
>> >
>> >Also, is Apollo dead and development officially moving to AMQ6 ?  if so
>> >perhaps the best strategy is to mark it as so.
>> >
>> >On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:
>> >
>> >> ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
>> >> 5.x.
>> >>
>> >> The ActiveMQ 6 name was once used for Apollo and now it's used for
>> >>HornetQ.
>> >> Yes, it's confusing.
>> >>
>> >> Personally, I will be referring to the existing ActiveMQ
>> >> (https://github.com/apache/activemq), and only that code base, as
>> >> ActiveMQ -
>> >> until we have a plan that somehow one replaces the other.  If you catch
>> >>me
>> >> using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack
>> >>me
>> >> in the back of the head ;-).
>> >>
>> >> I'm sorry for your confusion.  It is a major concern that you were
>> >>confused
>> >> and spent time and effort to work on HornetQ when you thought you were
>> >> upgrading ActiveMQ.
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> >>
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp46
>> >>93434p4693463.html
>> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Founder/CEO Spinn3r.com
>> >Location: *San Francisco, CA*
>> >blog: http://burtonator.wordpress.com
>> >Š or check out my Google+ profile
>> >
>> >
>>
>>
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> 
> 



-- 
Clebert Suconic
http://community.jboss.org/people/clebert.suco...@jboss.com
http://clebertsuconic.blogspot.com

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Kevin Burton

When I get more time to look at 6.0.0 I’ll write up a post from an ActiveMQ
perspective about what’s missing.  What I’m worried about is that ActiveMQ
has a LOT of features (advisories for example) that would need some sort of
support in 6.0.0 to make a migration from 5.0 to 6.0 possible.

The reason we selected AMQ 5.x was because of these features and that they
are *required* for our product to even work.

On Thu, Mar 19, 2015 at 1:15 PM, Petter Nordlander <
petter.nordlan...@enfo.se> wrote:

> I can only agree.
>
> ActiveMQ 6.0.0, by the name, suggests that it¹s a successor to ActiveMQ,
> which it¹s not as it¹s a successor to HornetQ with some elements from
> ActiveMQ. Great work though, I like the initiative as such.
>
> As long as there is no upgrade path, the name will confuse users. A lot of
> people will try it out just to find that half of the features they were
> used to are gone. I guess a good start would be to clarify things on the
> ActiveMQ homepage.
>
> BR Petter
>
> Den 2015-03-19 20:40 skrev Kevin Burton :
>
> >Actually, this is probably the right way to phrase it.  Maybe just on the
> >HOME PAGE of AMQ 6 just have a call out.
> >
> >I think it¹s fair to work on a new broker because ActiveMQ 5 would need a
> >lot of work in a lot of areas to modernize it.
> >
> >That said. It think the 5.x series should also be maintained for a while.
> >So maybe just having them clearly explained that they are different
> >things.
> >
> >Also, is Apollo dead and development officially moving to AMQ6 ?  if so
> >perhaps the best strategy is to mark it as so.
> >
> >On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:
> >
> >> ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
> >> 5.x.
> >>
> >> The ActiveMQ 6 name was once used for Apollo and now it's used for
> >>HornetQ.
> >> Yes, it's confusing.
> >>
> >> Personally, I will be referring to the existing ActiveMQ
> >> (https://github.com/apache/activemq), and only that code base, as
> >> ActiveMQ -
> >> until we have a plan that somehow one replaces the other.  If you catch
> >>me
> >> using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack
> >>me
> >> in the back of the head ;-).
> >>
> >> I'm sorry for your confusion.  It is a major concern that you were
> >>confused
> >> and spent time and effort to work on HornetQ when you thought you were
> >> upgrading ActiveMQ.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> >>
> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp46
> >>93434p4693463.html
> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
> >>
> >
> >
> >
> >--
> >
> >Founder/CEO Spinn3r.com
> >Location: *San Francisco, CA*
> >blog: http://burtonator.wordpress.com
> >Š or check out my Google+ profile
> >
> >
>
>


-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile

[jira] [Updated] (AMQ-5679) Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic

2015-03-19 Thread Justin Reock (JIRA)


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

Justin Reock updated AMQ-5679:
--
Description: 
The fix for AMQ-4899 seems to have created an undesired side effect.  Because 
all consumer selectors issued against a Virtual Topic are now cached, this 
means that even the Wildcard selector used when browsing the Virtual Topic is 
cached as well.  This effectively nullifies the selectorAware attribute of the 
Virtual Topic, as once the browse happens, every message will be retained in 
the Topic, regardless of whether they match a desired consumer selector.

To validate, create a selectorAware Virtual Topic and attach a consumer with a 
selector active on the Topic.  Produce some messages which don't match the 
selector, and note that they are properly discarded.  Then, browse the Virtual 
Topic using the web console, and produce some messages that don't match the 
selector again.  They will be retained on the Virtual Topic.

  was:
The fix for AMQ-4899 seems to have created an undesired side effect.  Because 
all consumer selectors issued against a Virtual Topic are now cached, this 
means that even the Wildcard selector used when browsing the Virtual Topic is 
cached as well.  This effectively nullifies the selectorAware attribute of the 
Virtual Topic, as once the browse happens, every message will be retained in 
the Topic.

To validate, create a selectorAware Virtual Topic and attach a consumer with a 
selector active on the Topic.  Produce some messages which don't match the 
selector, and note that they are properly discarded.  Then, browse the Virtual 
Topic using the web console, and produce some messages that don't match the 
selector again.  They will be retained on the Virtual Topic.


> Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic
> -
>
> Key: AMQ-5679
> URL: https://issues.apache.org/jira/browse/AMQ-5679
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.9.1
> Environment: Any
>Reporter: Justin Reock
>Priority: Minor
>
> The fix for AMQ-4899 seems to have created an undesired side effect.  Because 
> all consumer selectors issued against a Virtual Topic are now cached, this 
> means that even the Wildcard selector used when browsing the Virtual Topic is 
> cached as well.  This effectively nullifies the selectorAware attribute of 
> the Virtual Topic, as once the browse happens, every message will be retained 
> in the Topic, regardless of whether they match a desired consumer selector.
> To validate, create a selectorAware Virtual Topic and attach a consumer with 
> a selector active on the Topic.  Produce some messages which don't match the 
> selector, and note that they are properly discarded.  Then, browse the 
> Virtual Topic using the web console, and produce some messages that don't 
> match the selector again.  They will be retained on the Virtual Topic.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5679) Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic

2015-03-19 Thread Justin Reock (JIRA)

Justin Reock created AMQ-5679:
-

 Summary: Wildcard Selector is Cached Against Virtual Topic when 
Browsing the Topic
 Key: AMQ-5679
 URL: https://issues.apache.org/jira/browse/AMQ-5679
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.9.1
 Environment: Any
Reporter: Justin Reock
Priority: Minor


The fix for AMQ-4899 seems to have created an undesired side effect.  Because 
all consumer selectors issued against a Virtual Topic are now cached, this 
means that even the Wildcard selector used when browsing the Virtual Topic is 
cached as well.  This effectively nullifies the selectorAware attribute of the 
Virtual Topic, as once the browse happens, every message will be retained in 
the Topic.

To validate, create a selectorAware Virtual Topic and attach a consumer with a 
selector active on the Topic.  Produce some messages which don't match the 
selector, and note that they are properly discarded.  Then, browse the Virtual 
Topic using the web console, and produce some messages that don't match the 
selector again.  They will be retained on the Virtual Topic.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Weiqi Gao


All,

I agree that at some point (probably before the official ActiveMQ 6.0.0 
release) the fact that ActiveMQ 6.0.0 is the successor of HornetQ 
2.4.5.Final, not ActiveMQ 5.x needs to be publicized.


I'm a HornetQ (via JBoss/WildFly) user, and I only found this out 
through twitter because I follow Clebert already.


There are probably users of HornetQ 2.4.x who are not aware of the 
Apache donation and are wondering why the development activity on the 
HornetQ GitHub repo has slowed down.


--
Weiqi Gao
weiqi...@gmail.com
http://weiqigao.blogspot.com

On 3/19/2015 3:15 PM, Petter Nordlander wrote:

I can only agree.

ActiveMQ 6.0.0, by the name, suggests that it¹s a successor to ActiveMQ,
which it¹s not as it¹s a successor to HornetQ with some elements from
ActiveMQ. Great work though, I like the initiative as such.

As long as there is no upgrade path, the name will confuse users. A lot of
people will try it out just to find that half of the features they were
used to are gone. I guess a good start would be to clarify things on the
ActiveMQ homepage.

BR Petter

Den 2015-03-19 20:40 skrev Kevin Burton :


Actually, this is probably the right way to phrase it.  Maybe just on the
HOME PAGE of AMQ 6 just have a call out.

I think it¹s fair to work on a new broker because ActiveMQ 5 would need a
lot of work in a lot of areas to modernize it.

That said. It think the 5.x series should also be maintained for a while.
So maybe just having them clearly explained that they are different
things.

Also, is Apollo dead and development officially moving to AMQ6 ?  if so
perhaps the best strategy is to mark it as so.

On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:


ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
5.x.

The ActiveMQ 6 name was once used for Apollo and now it's used for
HornetQ.
Yes, it's confusing.

Personally, I will be referring to the existing ActiveMQ
(https://github.com/apache/activemq), and only that code base, as
ActiveMQ -
until we have a plan that somehow one replaces the other.  If you catch
me
using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack
me
in the back of the head ;-).

I'm sorry for your confusion.  It is a major concern that you were
confused
and spent time and effort to work on HornetQ when you thought you were
upgrading ActiveMQ.



--
View this message in context:

http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp46
93434p4693463.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
Š or check out my Google+ profile

[GitHub] activemq-6 pull request: Doc changes and placing the main method b...

2015-03-19 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-6/pull/192


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Petter Nordlander

I can only agree.

ActiveMQ 6.0.0, by the name, suggests that it¹s a successor to ActiveMQ,
which it¹s not as it¹s a successor to HornetQ with some elements from
ActiveMQ. Great work though, I like the initiative as such.

As long as there is no upgrade path, the name will confuse users. A lot of
people will try it out just to find that half of the features they were
used to are gone. I guess a good start would be to clarify things on the
ActiveMQ homepage.

BR Petter

Den 2015-03-19 20:40 skrev Kevin Burton :

>Actually, this is probably the right way to phrase it.  Maybe just on the
>HOME PAGE of AMQ 6 just have a call out.
>
>I think it¹s fair to work on a new broker because ActiveMQ 5 would need a
>lot of work in a lot of areas to modernize it.
>
>That said. It think the 5.x series should also be maintained for a while.
>So maybe just having them clearly explained that they are different
>things.
>
>Also, is Apollo dead and development officially moving to AMQ6 ?  if so
>perhaps the best strategy is to mark it as so.
>
>On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:
>
>> ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
>> 5.x.
>>
>> The ActiveMQ 6 name was once used for Apollo and now it's used for
>>HornetQ.
>> Yes, it's confusing.
>>
>> Personally, I will be referring to the existing ActiveMQ
>> (https://github.com/apache/activemq), and only that code base, as
>> ActiveMQ -
>> until we have a plan that somehow one replaces the other.  If you catch
>>me
>> using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack
>>me
>> in the back of the head ;-).
>>
>> I'm sorry for your confusion.  It is a major concern that you were
>>confused
>> and spent time and effort to work on HornetQ when you thought you were
>> upgrading ActiveMQ.
>>
>>
>>
>> --
>> View this message in context:
>> 
>>http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp46
>>93434p4693463.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>
>
>
>-- 
>
>Founder/CEO Spinn3r.com
>Location: *San Francisco, CA*
>blog: http://burtonator.wordpress.com
>Š or check out my Google+ profile
>
>

[jira] [Commented] (AMQ-5678) Would like to be able to limit queue depth by # of messages vs memory limits

2015-03-19 Thread Christian Posta (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369987#comment-14369987
 ] 

Christian Posta commented on AMQ-5678:
--

Damn! I couldn't find it searching the JIRA. Thanks for linking them.

> Would like to be able to limit queue depth by # of messages vs memory limits
> 
>
> Key: AMQ-5678
> URL: https://issues.apache.org/jira/browse/AMQ-5678
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Christian Posta
>Priority: Minor
>
> Right now we can place limits on our destinations/brokers based on memory and 
> messages sizes. It would be useful to reason about a queue depth by # of 
> messages ... so to be able to limit messages by "# of messages" and "max 
> message size" in a policy entry. These settings should still respect global 
> broker memory values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ActiveMQ 6.0.0 required Java 8?

2015-03-19 Thread Kevin Burton

Actually, this is probably the right way to phrase it.  Maybe just on the
HOME PAGE of AMQ 6 just have a call out.

I think it’s fair to work on a new broker because ActiveMQ 5 would need a
lot of work in a lot of areas to modernize it.

That said. It think the 5.x series should also be maintained for a while.
So maybe just having them clearly explained that they are different things.

Also, is Apollo dead and development officially moving to AMQ6 ?  if so
perhaps the best strategy is to mark it as so.

On Thu, Mar 19, 2015 at 9:26 AM, artnaseef  wrote:

> ActiveMQ *is* what we can only distinguish clearly right now as ActiveMQ
> 5.x.
>
> The ActiveMQ 6 name was once used for Apollo and now it's used for HornetQ.
> Yes, it's confusing.
>
> Personally, I will be referring to the existing ActiveMQ
> (https://github.com/apache/activemq), and only that code base, as
> ActiveMQ -
> until we have a plan that somehow one replaces the other.  If you catch me
> using "AMQ 6" or "AMQ 5" outside the discussion of naming, please smack me
> in the back of the head ;-).
>
> I'm sorry for your confusion.  It is a major concern that you were confused
> and spent time and effort to work on HornetQ when you thought you were
> upgrading ActiveMQ.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-0-required-Java-8-tp4693434p4693463.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile

[jira] [Commented] (AMQ-5678) Would like to be able to limit queue depth by # of messages vs memory limits

2015-03-19 Thread Petter Nordlander (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369974#comment-14369974
 ] 

Petter Nordlander commented on AMQ-5678:


I guess this is very similar to the AMQ-5522 case. Great idea though

> Would like to be able to limit queue depth by # of messages vs memory limits
> 
>
> Key: AMQ-5678
> URL: https://issues.apache.org/jira/browse/AMQ-5678
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: Christian Posta
>Priority: Minor
>
> Right now we can place limits on our destinations/brokers based on memory and 
> messages sizes. It would be useful to reason about a queue depth by # of 
> messages ... so to be able to limit messages by "# of messages" and "max 
> message size" in a policy entry. These settings should still respect global 
> broker memory values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQCPP-569) thread creation leak with failover transport after disconnect

2015-03-19 Thread Arthur Naseef (JIRA)

Arthur Naseef created AMQCPP-569:


 Summary: thread creation leak with failover transport after 
disconnect
 Key: AMQCPP-569
 URL: https://issues.apache.org/jira/browse/AMQCPP-569
 Project: ActiveMQ C++ Client
  Issue Type: Bug
Affects Versions: 3.8.4
 Environment: CentOS Linux 7, example activemq-cpp client from the 
website
Reporter: Arthur Naseef
Assignee: Timothy Bish


As reported here: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-High-number-of-threads-td4693185.html#a4693477

The following steps lead to a thread leak:

* Start client with failover transport with at least 2 brokers in the URL
* Wait for the client to successfully connect to the broker
* Shutdown the broker
* Watch the number of threads in the process

Using GDB, I found the following stack trace in a good number of the most 
recent threads:

{noformat}
#0  0x768a2705 in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib64/libpthread.so.0
#1  0x7774087b in 
decaf::internal::util::concurrent::PlatformThread::interruptibleWaitOnCondition 
(
condition=0x7fffc8002790, mutex=0x7fffc8000a20, complete=...)
at decaf/internal/util/concurrent/unix/PlatformThread.cpp:210
#2  0x7773f5c5 in doWaitOnMonitor (interruptible=true, nanos=, mills=0, thread=0x7fffc8003a40, 
monitor=0x618310) at decaf/internal/util/concurrent/Threading.cpp:754
#3  decaf::internal::util::concurrent::Threading::waitOnMonitor 
(monitor=0x618310, mills=0, nanos=)
at decaf/internal/util/concurrent/Threading.cpp:1558
#4  0x777a7e5c in decaf::util::TimerImpl::run (this=0x7fffc8000d20) at 
decaf/util/Timer.cpp:79
#5  0x7773cb72 in (anonymous namespace)::runCallback 
(arg=0x7fffc8003a40)
at decaf/internal/util/concurrent/Threading.cpp:266
#6  0x7773d47c in (anonymous namespace)::threadEntryMethod 
(arg=0x7fffc8003a40)
at decaf/internal/util/concurrent/Threading.cpp:254
#7  0x7689edf3 in start_thread () from /lib64/libpthread.so.0
#8  0x75ba91ad in clone () from /lib64/libc.so.6
{noformat}

I tested with a slightly-modified version of the example C++ program from the 
ActiveMQ wiki (http://activemq.apache.org/cms/example.html).  The modifications 
consist of adding a delay after producing each message (to slow down the 
program in order to make testing easier), and accepting the broker URL from the 
command-line.

Note that watching the threads with "ps" over a period of time, the leak does 
not appear to occur with 100% consistency; at least a couple of times, the 
number of threads dropped back down and then increased again -- this is in the 
same run in which the number of threads did grow more than once.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
=
ActiveMQ and tomcat hosted on the same machine
=
Unable to create ConnectionFactory from activemq web console.


 PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
connection factory which is permanent on activemq 
http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue
==
context.xml
==


  

  

  ConnectionFactory
  jms/ConnectionFactory
  org.apache.activemq.ActiveMQConnectionFactory
  Container
  
   
  Topic
  jms/topic/MyTopic
  javax.jms.Topic
  Container
  
   
  Queue
  jms/queue/MyQueue
  javax.jms.Queue
  Container
  

=
jmsSend.jsp
=
<%@page import="javax.naming.*, javax.jms.*, java.util.*" %> 
<%
try{

Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setProperty(Context.PROVIDER_URL,"tcp://127.0.0.1:61616");
InitialContext initCtx = new InitialContext(props);  
Context envContext = (Context) initCtx.lookup("java:comp/env");  
ConnectionFactory connectionFactory = (ConnectionFactory) 
envContext.lookup("jms/ConnectionFactory");  
Connection connection = connectionFactory.createConnection();  
Session ss = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);  
Destination destination = ss.createTopic("jms/topic/MyTopic");  
MessageProducer producer = ss.createProducer(destination);  
TextMessage msg=ss.createTextMessage();  
msg.setText("Message sent");
out.println("Message sent successfully");  
producer.send(msg);
}catch(Exception e){
 e.printStackTrace();
}
%>
==
tomcat - logs
===

javax.naming.NamingException: Cannot create resource instance


  was:
Unable to create ConnectionFactory from activemq web console.


 PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
connection factory which is permanent on activemq 
http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue
==
context.xml
==


  

  

  ConnectionFactory
  jms/ConnectionFactory
  org.apache.activemq.ActiveMQConnectionFactory
  Container
  
   
  Topic
  jms/topic/MyTopic
  javax.jms.Topic
  Container
  
   
  Queue
  jms/queue/MyQueue
  javax.jms.Queue
  Container
  

=
jmsSend.jsp
=
<%@page import="javax.naming.*, javax.jms.*, java.util.*" %> 
<%
try{

Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setProperty(Context.PROVIDER_URL,"tcp://127.0.0.1:61616");
InitialContext initCtx = new InitialContext(props);  
Context envContext = (Context) initCtx.lookup("java:comp/env");  
ConnectionFactory connectionFactory = (ConnectionFactory) 
envContext.lookup("jms/ConnectionFactory");  
Connection connection = connectionFactory.createConnection();  
Session ss = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);  
Destination destination = ss.createTopic("jms/topic/MyTopic");  
MessageProducer producer = ss.createProducer(destination);  
TextMessage msg=ss.createTextMessage();  
msg.setText("Message sent");
out.println("Message sent successfully");  
producer.send(msg);
}catch(Exception e){
 e.printStackTrace();
}
%>
==
tomcat - logs
===

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: naray

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
Unable to create ConnectionFactory from activemq web console.


 PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
connection factory which is permanent on activemq 
http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue
==
context.xml
==


  

  

  ConnectionFactory
  jms/ConnectionFactory
  org.apache.activemq.ActiveMQConnectionFactory
  Container
  
   
  Topic
  jms/topic/MyTopic
  javax.jms.Topic
  Container
  
   
  Queue
  jms/queue/MyQueue
  javax.jms.Queue
  Container
  

=
jmsSend.jsp
=
<%@page import="javax.naming.*, javax.jms.*, java.util.*" %> 
<%
try{

Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setProperty(Context.PROVIDER_URL,"tcp://127.0.0.1:61616");
InitialContext initCtx = new InitialContext(props);  
Context envContext = (Context) initCtx.lookup("java:comp/env");  
ConnectionFactory connectionFactory = (ConnectionFactory) 
envContext.lookup("jms/ConnectionFactory");  
Connection connection = connectionFactory.createConnection();  
Session ss = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);  
Destination destination = ss.createTopic("jms/topic/MyTopic");  
MessageProducer producer = ss.createProducer(destination);  
TextMessage msg=ss.createTextMessage();  
msg.setText("Message sent");
out.println("Message sent successfully");  
producer.send(msg);
}catch(Exception e){
 e.printStackTrace();
}
%>
==
tomcat - logs
===

javax.naming.NamingException: Cannot create resource instance


  was:
Unable to create ConnectionFactory from activemq web console.


 PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
connection factory which is permanent on activemq 
http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: narayana b
>
> Unable to create ConnectionFactory from activemq web console.
>  PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
> connection factory which is permanent on activemq 
> http://localhost:8161
> Queue - Able to create, after restart this queue removed
> Topic  - Able to create, after restart this queue removed
> ConnectionFactory  - Unable to create - no option provided
> How to create ConnectionFactory in the activemq.xml?, please tell me
> Im connecting from Tomcat Application to Activemq but on
> i have activemq client libs in tomcat, configured conection factory, queue, 
> topic on tomcat resource but unable to create on activemq - ConnectionFactory 
> this is  the issue
> ==
> context.xml
> ==
>  type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS 
> connection factory" factory="org.apache.activemq.jndi.JNDIReferenceFactory" 
> brokerURL="tcp://localhost.localdomain:61616" brokerName="ActiveMQBroker" 
> useEmbeddedBroker="false" />
>   
>  type="org.apache.activemq.command.ActiveMQTopic" 
> factory="org.apache.activemq.jndi.JNDIReferenceFactory" 
> physicalName="APP.JMS.TOPIC" />
>   
>  type="org.apache.activemq.command.ActiveMQQueue" 
> factory="org.apache.activemq.jndi.JNDIReferenceFactory" 
> physicalName="APP.JMS.QUEUE" /
> ==
> web.xml
> ==
> 
>   ConnectionFactory
>   jms/ConnectionFactory
>   org.apache.activemq.ActiveMQConnectionFactory

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
Unable to create ConnectionFactory from activemq web console.


 PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
connection factory which is permanent on activemq 
http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance


  was:
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: narayana b
>
> Unable to create ConnectionFactory from activemq web console.
>  PLEASE PROVIDE DETAILED INFORMATION, how to create queue, topic , 
> connection factory which is permanent on activemq 
> http://localhost:8161
> Queue - Able to create, after restart this queue removed
> Topic  - Able to create, after restart this queue removed
> ConnectionFactory  - Unable to create - no option provided
> How to create ConnectionFactory in the activemq.xml?, please tell me
> Im connecting from Tomcat Application to Activemq but on
> i have activemq client libs in tomcat, configured conection factory, queue, 
> topic on tomcat resource but unable to create on activemq - ConnectionFactory 
> this is  the issue
> tomcat - logs
> javax.naming.NamingException: Cannot create resource instance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create, after restart this queue removed
Topic  - Able to create, after restart this queue removed
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance


  was:
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: narayana b
>
> Unable to create ConnectionFactory from activemq web console.
> http://localhost:8161
> Queue - Able to create, after restart this queue removed
> Topic  - Able to create, after restart this queue removed
> ConnectionFactory  - Unable to create - no option provided
> How to create ConnectionFactory in the activemq.xml?, please tell me
> Im connecting from Tomcat Application to Activemq but on
> i have activemq client libs in tomcat, configured conection factory, queue, 
> topic on tomcat resource but unable to create on activemq - ConnectionFactory 
> this is  the issue
> tomcat - logs
> javax.naming.NamingException: Cannot create resource instance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5678) Would like to be able to limit queue depth by # of messages vs memory limits

2015-03-19 Thread Christian Posta (JIRA)

Christian Posta created AMQ-5678:


 Summary: Would like to be able to limit queue depth by # of 
messages vs memory limits
 Key: AMQ-5678
 URL: https://issues.apache.org/jira/browse/AMQ-5678
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker
Reporter: Christian Posta
Priority: Minor


Right now we can place limits on our destinations/brokers based on memory and 
messages sizes. It would be useful to reason about a queue depth by # of 
messages ... so to be able to limit messages by "# of messages" and "max 
message size" in a policy entry. These settings should still respect global 
broker memory values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5677) Karaf features-core.xml - remove loading of 'http' from "activemq" feature

2015-03-19 Thread Martin Lichtin (JIRA)

Martin Lichtin created AMQ-5677:
---

 Summary: Karaf features-core.xml - remove loading of 'http' from 
"activemq" feature
 Key: AMQ-5677
 URL: https://issues.apache.org/jira/browse/AMQ-5677
 Project: ActiveMQ
  Issue Type: Improvement
Affects Versions: 5.11.1
Reporter: Martin Lichtin


Please remove loading of feature "http" from activemq feature.
It's not actually required in this context of starting the broker.

I guess the "http" feature needed for the features in features.xml, but then it 
better be moved there, into "activemq-web-console".





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5667) Asynchronous sending non persistence messages,it will error,please see description

2015-03-19 Thread Timothy Bish (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369726#comment-14369726
 ] 

Timothy Bish commented on AMQ-5667:
---

Have you tested this out on the latest release 5.11.1

> Asynchronous sending non persistence messages,it will error,please see 
> description
> --
>
> Key: AMQ-5667
> URL: https://issues.apache.org/jira/browse/AMQ-5667
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.10.0
>Reporter: 方春柳
>
> Asynchronous sending non persistence messages
> 1、Set the connection‘s producerWindowSize parameter larger than zero.
> 2、Set the sendFailIfNoSpaceAfterTimeout parameter larger than zero.
> 3、Use VMQueueCursor as a message storeage
> 4、Start producer and Send a lot of messages until the broker memory occupied.
> 5、Start consumer spending all the messages.
> 6、You’ll find the producer did not continue to send message but has been 
> blocked
> Reason:No memoryUsage calls the decreaseUsage method on the client broker to 
> remove the timeout message, resulting in producer has been blocked in the 
> waitForSpace method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5675) org.apache.activemq.leveldb.CountDownFuture

2015-03-19 Thread Timothy Bish (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369725#comment-14369725
 ] 

Timothy Bish commented on AMQ-5675:
---

Have you tested this on a newer version like 5.11.1 ?

> org.apache.activemq.leveldb.CountDownFuture
> ---
>
> Key: AMQ-5675
> URL: https://issues.apache.org/jira/browse/AMQ-5675
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: activemq-leveldb-store
>Affects Versions: 5.9.1
> Environment: activemq 5.9.1 
> lelveldb 
> zookeeper
>Reporter: gbsnaker
>Priority: Critical
>
> hi 
>lots of threads blocked and tracer by id  5429 thread. 
>here is stack . 
>
> zookeeper-3.4.5
> activemq 5.9.1
> leveldb-1.15.0 
> Thread ID: 4329
> Thread Name: ActiveMQ Transport: tcp:///172.24.139.37:55455@61616
> Waited Count: 1 Waited Time: 1704727ms
> Blocked Count: 0 Blocked Time: 0ms
> Lock Name: java.util.concurrent.CountDownLatch$Sync@198e6601 Lock Class Name: 
> java.util.concurrent.CountDownLatch$Sync Lock Identity Hash Code: 428762625
> Locked Monitors
> Frame: 10 org.apache.activemq.broker.region.Topic .doMessageSend  
> (Topic.java)
> Stack Trace
> sun.misc.Unsafe . park  (Unsafe.java) (Native)
> java.util.concurrent.locks.LockSupport . park  (LockSupport.java:156)
> java.util.concurrent.locks.AbstractQueuedSynchronizer . 
> parkAndCheckInterrupt  (AbstractQueuedSynchronizer.java:811)
> java.util.concurrent.locks.AbstractQueuedSynchronizer . 
> doAcquireSharedInterruptibly  (AbstractQueuedSynchronizer.java:969)
> java.util.concurrent.locks.AbstractQueuedSynchronizer . 
> acquireSharedInterruptibly  (AbstractQueuedSynchronizer.java:1281)
> java.util.concurrent.CountDownLatch . await  (CountDownLatch.java:207)
> org.apache.activemq.leveldb.CountDownFuture . get  
> (DBManager.scala:125)
> org.apache.activemq.leveldb.LevelDBStore$ . waitOn  
> (LevelDBStore.scala:68)
> org.apache.activemq.leveldb.LevelDBStore$LevelDBMessageStore . 
> addMessage  (LevelDBStore.scala:701)
> org.apache.activemq.store.AbstractMessageStore . asyncAddTopicMessage 
>  (AbstractMessageStore.java:105)
> org.apache.activemq.broker.region.Topic . doMessageSend  
> (Topic.java:477)
> org.apache.activemq.broker.region.Topic . send  (Topic.java:441)
> org.apache.activemq.broker.region.AbstractRegion . send  
> (AbstractRegion.java:395)
> org.apache.activemq.broker.region.RegionBroker . send  
> (RegionBroker.java:441)
> org.apache.activemq.broker.jmx.ManagedRegionBroker . send  
> (ManagedRegionBroker.java:297)
> org.apache.activemq.broker.BrokerFilter . send  
> (BrokerFilter.java:147)
> org.apache.activemq.broker.CompositeDestinationBroker . send  
> (CompositeDestinationBroker.java:96)
> org.apache.activemq.broker.TransactionBroker . send  
> (TransactionBroker.java:307)
> org.apache.activemq.broker.MutableBrokerFilter . send  
> (MutableBrokerFilter.java:152)
> org.apache.activemq.broker.TransportConnection . processMessage  
> (TransportConnection.java:493)
> org.apache.activemq.command.ActiveMQMessage . visit  
> (ActiveMQMessage.java:756)
> org.apache.activemq.broker.TransportConnection . service  
> (TransportConnection.java:291)
> org.apache.activemq.broker.TransportConnection$1 . onCommand  
> (TransportConnection.java:145)
> org.apache.activemq.transport.MutexTransport . onCommand  
> (MutexTransport.java:50)
> org.apache.activemq.transport.WireFormatNegotiator . onCommand  
> (WireFormatNegotiator.java:113)
> org.apache.activemq.transport.AbstractInactivityMonitor . onCommand  
> (AbstractInactivityMonitor.java:270)
> org.apache.activemq.transport.TransportSupport . doConsume  
> (TransportSupport.java:83)
> org.apache.activemq.transport.tcp.TcpTransport . doRun  
> (TcpTransport.java:214)
> org.apache.activemq.transport.tcp.TcpTransport . run  
> (TcpTransport.java:196)
> java.lang.Thread . run  (Thread.java:662) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFactory  - Unable to create - no option provided

How to create ConnectionFactory in the activemq.xml?, please tell me
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance


  was:
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFactory  - Unable to create

How to create ConnectionFactory in the activemq.xml?
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: narayana b
>
> Unable to create ConnectionFactory from activemq web console.
> http://localhost:8161
> Queue - Able to create
> Topic  - Able to create
> ConnectionFactory  - Unable to create - no option provided
> How to create ConnectionFactory in the activemq.xml?, please tell me
> Im connecting from Tomcat Application to Activemq but on
> i have activemq client libs in tomcat, configured conection factory, queue, 
> topic on tomcat resource but unable to create on activemq - ConnectionFactory 
> this is  the issue
> tomcat - logs
> javax.naming.NamingException: Cannot create resource instance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ACTIVEMQ6-92) Inject divert and bridge transformer classes

2015-03-19 Thread Jeff Mesnil (JIRA)

Jeff Mesnil created ACTIVEMQ6-92:


 Summary: Inject divert and bridge transformer classes
 Key: ACTIVEMQ6-92
 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-92
 Project: Apache ActiveMQ 6
  Issue Type: Improvement
Affects Versions: 6.0.0
Reporter: Jeff Mesnil


Divert and bridges can have a transformer classes.

They are specified in the divert and bridges configuration using class names 
and loads by ActiveMQ when its server is started.
However in a modular environment (such as WildFly), ActiveMQ may not be aware 
of the modules containing the loaded classes (that can come from the user 
space).

It is not suitable to have the ActiveMQ module depends on these user modules 
(as it breaks any modularity). Instead ActiveMQ should be able to use 
transformer *instances* (loaded by WildFly) from the divert and bridge classes.

There is already such a mechanism for loaded classes such as server interceptor 
and connector services through the ServiceRegistry.
This class should be extended to also work with divert and bridge transformers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMQ-5676) Unable to create ConnectionFactory from admin page


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

narayana b updated AMQ-5676:

Description: 
Unable to create ConnectionFactory from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFactory  - Unable to create

How to create ConnectionFactory in the activemq.xml?
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance


  was:
unable to create Connection from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFsactory  - Unable to create

How to create ConnectionFactory in the activemq.xml?
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance



> Unable to create ConnectionFactory from admin page
> --
>
> Key: AMQ-5676
> URL: https://issues.apache.org/jira/browse/AMQ-5676
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 5.11.1
> Environment: Linux 32 bit centos 6.4
> oracle java 7
>Reporter: narayana b
>
> Unable to create ConnectionFactory from activemq web console.
> http://localhost:8161
> Queue - Able to create
> Topic  - Able to create
> ConnectionFactory  - Unable to create
> How to create ConnectionFactory in the activemq.xml?
> Im connecting from Tomcat Application to Activemq but on
> i have activemq client libs in tomcat, configured conection factory, queue, 
> topic on tomcat resource but unable to create on activemq - ConnectionFactory 
> this is  the issue
> tomcat - logs
> javax.naming.NamingException: Cannot create resource instance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMQ-5676) Unable to create ConnectionFactory from admin page

narayana b created AMQ-5676:
---

 Summary: Unable to create ConnectionFactory from admin page
 Key: AMQ-5676
 URL: https://issues.apache.org/jira/browse/AMQ-5676
 Project: ActiveMQ
  Issue Type: Bug
  Components: webconsole
Affects Versions: 5.11.1
 Environment: Linux 32 bit centos 6.4
oracle java 7


Reporter: narayana b


unable to create Connection from activemq web console.

http://localhost:8161

Queue - Able to create
Topic  - Able to create
ConnectionFsactory  - Unable to create

How to create ConnectionFactory in the activemq.xml?
Im connecting from Tomcat Application to Activemq but on

i have activemq client libs in tomcat, configured conection factory, queue, 
topic on tomcat resource but unable to create on activemq - ConnectionFactory 
this is  the issue

tomcat - logs

javax.naming.NamingException: Cannot create resource instance




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ActiveMQ 6.0.0 required Java 8?