[jira] [Commented] (AMQ-4945) IllegalArgumentException When No Destination Specified On Admin Screen

2014-04-25 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on AMQ-4945:
-

GitHub user zmhassan opened a pull request:

https://github.com/apache/activemq/pull/20

AMQ-4945 : IllegalArgumentException When No Destination Specified On Adm...

Description of problem:

This is a UI issue.
If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp' 
it throws an exception, instead of simply putting out a message that a queue 
destination/name is required.


Jira issue:
https://issues.apache.org/jira/browse/AMQ-4945



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zmhassan/activemq AMQ-4945

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 5b86a6edbf5a2d269547cb086e41ddf96be94b09
Author: zmhassan 
Date:   2014-04-26T04:40:16Z

AMQ-4945 : IllegalArgumentException When No Destination Specified On Admin 
Screen




> IllegalArgumentException When No Destination Specified On Admin Screen
> --
>
> Key: AMQ-4945
> URL: https://issues.apache.org/jira/browse/AMQ-4945
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0, 5.9.0
> Environment: Linux
>Reporter: Jerome Lumpkin
>Priority: Trivial
>
> This is a UI issue.  
> If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp'  it 
> throws an exception, instead of simply putting out a message that a queue 
> destination/name is required.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[GitHub] activemq pull request: AMQ-4945 : IllegalArgumentException When No...

2014-04-25 Thread zmhassan
GitHub user zmhassan opened a pull request:

https://github.com/apache/activemq/pull/20

AMQ-4945 : IllegalArgumentException When No Destination Specified On Adm...

Description of problem:

This is a UI issue.
If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp' 
it throws an exception, instead of simply putting out a message that a queue 
destination/name is required.


Jira issue:
https://issues.apache.org/jira/browse/AMQ-4945



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zmhassan/activemq AMQ-4945

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 5b86a6edbf5a2d269547cb086e41ddf96be94b09
Author: zmhassan 
Date:   2014-04-26T04:40:16Z

AMQ-4945 : IllegalArgumentException When No Destination Specified On Admin 
Screen




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


Build failed in Jenkins: ActiveMQ-Trunk-Deploy #934

2014-04-25 Thread Apache Jenkins Server
See 

--
Started by timer
Building remotely on ubuntu1 (Ubuntu ubuntu) in workspace 

Fetching changes from the remote Git repository
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/activemq.git
ERROR: Timeout after 10 minutes
FATAL: Failed to fetch from https://git-wip-us.apache.org/repos/asf/activemq.git
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/activemq.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:621)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:853)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:878)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1320)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
at hudson.model.Run.execute(Run.java:1689)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/activemq.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 143:
stdout: 
stderr: remote: Counting objects: 149, done.
remote: Compressing objects:   1% (1/69)   
remote: Compressing objects:   2% (2/69)   
remote: Compressing objects:   4% (3/69)   
remote: Compressing objects:   5% (4/69)   
remote: Compressing objects:   7% (5/69)   
remote: Compressing objects:   8% (6/69)   
remote: Compressing objects:  10% (7/69)   
remote: Compressing objects:  11% (8/69)   
remote: Compressing objects:  13% (9/69)   
remote: Compressing objects:  14% (10/69)   
remote: Compressing objects:  15% (11/69)   
remote: Compressing objects:  17% (12/69)   
remote: Compressing objects:  18% (13/69)   
remote: Compressing objects:  20% (14/69)   
remote: Compressing objects:  21% (15/69)   
remote: Compressing objects:  23% (16/69)   
remote: Compressing objects:  24% (17/69)   
remote: Compressing objects:  26% (18/69)   
remote: Compressing objects:  27% (19/69)   
remote: Compressing objects:  28% (20/69)   
remote: Compressing objects:  30% (21/69)   
remote: Compressing objects:  31% (22/69)   
remote: Compressing objects:  33% (23/69)   
remote: Compressing objects:  34% (24/69)   
remote: Compressing objects:  36% (25/69)   
remote: Compressing objects:  37% (26/69)   
remote: Compressing objects:  39% (27/69)   
remote: Compressing objects:  40% (28/69)   
remote: Compressing objects:  42% (29/69)   
remote: Compressing objects:  43% (30/69)   
remote: Compressing objects:  44% (31/69)   
remote: Compressing objects:  46% (32/69)   
remote: Compressing objects:  47% (33/69)   
remote: Compressing objects:  49% (34/69)   
remote: Compressing objects:  50% (35/69)   
remote: Compressing objects:  52% (36/69)   
remote: Compressing objects:  53% (37/69)   
remote: Compressing objects:  55% (38/69)   
remote: Compressing objects:  56% (39/69)   
remote: Compressing objects:  57% (40/69)   
remote: Compressing objects:  59% (41/69)   
remote: Compressing objects:  60% (42/69)   
remote: Compressing objects:  62% (43/69)   
remote: Compressing objects:  63% (44/69)   
remote: Compressing objects:  65% (45/69)   
remote: Compressing objects:  66% (46/69)   
remote: Compressing objects:  68% (47/69)   
remote: Compressing objects:  69% (48/69)   
remote: Compressing objects:  71% (49/69)   
remote: Compressing objects:  72% (50/69)   
remote: Compressing objects:  73% (51/69)   
remote: Compressing objects:  75% (52/69)   
remote: Compressing objects:  76% (53/69)   
remote: Compressing objects:  78% (54/69)   
remote: Compressing objects:  79% (55/69)   
remote: Compressing objects:  81% (56/69)   
remote: Compressing objects:  82% (57/69)   
remote: Compressing objects:  84% (58/69)   
remote: Compressing objects:  85% (59/69)   
remote: Compressing objects:  86% (60/69)   
remote: Compressing objects:  88% (61/69)   
remote: Compressing objects:  89% (62/69)   
remote: Compressing objects:  91% (63/69)   
rem

[jira] [Commented] (AMQ-4945) IllegalArgumentException When No Destination Specified On Admin Screen

2014-04-25 Thread zmhassan (JIRA)

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

zmhassan commented on AMQ-4945:
---

Okay I'm gonna work on this and send in a pull request tonight. 

> IllegalArgumentException When No Destination Specified On Admin Screen
> --
>
> Key: AMQ-4945
> URL: https://issues.apache.org/jira/browse/AMQ-4945
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.8.0, 5.9.0
> Environment: Linux
>Reporter: Jerome Lumpkin
>Priority: Trivial
>
> This is a UI issue.  
> If I click the 'CREATE' queue button on the screen at '/admin/queues.jsp'  it 
> throws an exception, instead of simply putting out a message that a queue 
> destination/name is required.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


AMQ performance at 30000 subscribers

2014-04-25 Thread surfnerd
I have very unique PubSub requirement.
One one side there are only 5 publishers on 5 topics.
Those 5 topics are subscribed by around 3 clients.
Only 1-5 messages (sized 5 kbs) are published at every hour and clients will
be long-lived TCP connections.

Is it really possible with AMQ ?
What are recommended settings for performance tweaks ?

Anyone ever tried large number of subscriptions ?

Thanks,
SS



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/AMQ-performance-at-3-subscribers-tp4680570.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


[jira] [Updated] (AMQ-5160) Wildcard subscriptions bypass Authentication / Authorization

2014-04-25 Thread Surf (JIRA)

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

Surf updated AMQ-5160:
--

Summary: Wildcard subscriptions bypass Authentication / Authorization  
(was: MQTT messages bypass Authentication / Authorization)

> Wildcard subscriptions bypass Authentication / Authorization
> 
>
> Key: AMQ-5160
> URL: https://issues.apache.org/jira/browse/AMQ-5160
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: MQTT
>Affects Versions: 5.9.1
>Reporter: Surf
>Priority: Critical
>  Labels: authentication, authorization, mqtt, security
> Attachments: activemq.xml, groups.properties, login.config, 
> users.properties
>
>
> I am using MQTT on AMQ 5.9.1
> After latest MQTT hardening from [~dhirajsb] , there is an issue of MQTT 
> retained messages.
> Simple case:
> Set Authentication / Authorization for two different TOPICS.
> Send retained message to one topic.
> Try to subscribe "#" with other second user.
> It will show retained messages published by TOPIC 1. 
> here i have attached test configurations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (AMQ-5162) Slave broker does not shutdown after persistence store lockout.

2014-04-25 Thread Dejan Bosanac (JIRA)

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

Dejan Bosanac resolved AMQ-5162.


Resolution: Fixed

Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/d60022ec

> Slave broker does not shutdown after persistence store lockout.
> ---
>
> Key: AMQ-5162
> URL: https://issues.apache.org/jira/browse/AMQ-5162
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.10.0
>
>
> Adding the following exception handler to broker configuration suppose to 
> shutdown broker when persistence store becomes unavailable.
> {code}
> 
> {code}
> This is seems to work for master broker but the slave broker seems to ignore 
> it and continues to work.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (AMQ-5162) Slave broker does not shutdown after persistence store lockout.

2014-04-25 Thread Dejan Bosanac (JIRA)
Dejan Bosanac created AMQ-5162:
--

 Summary: Slave broker does not shutdown after persistence store 
lockout.
 Key: AMQ-5162
 URL: https://issues.apache.org/jira/browse/AMQ-5162
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 5.9.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
 Fix For: 5.10.0


Adding the following exception handler to broker configuration suppose to 
shutdown broker when persistence store becomes unavailable.
{code}

{code}
This is seems to work for master broker but the slave broker seems to ignore it 
and continues to work.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp

2014-04-25 Thread Valeriy V. Argunov (JIRA)
Valeriy V. Argunov created AMQCPP-540:
-

 Summary: Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp
 Key: AMQCPP-540
 URL: https://issues.apache.org/jira/browse/AMQCPP-540
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: Build Support
Reporter: Valeriy V. Argunov
Assignee: Timothy Bish
 Attachments: AbstractDiscoveryAgent.cpp.patch

Here is a patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (AMQCPP-540) Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp

2014-04-25 Thread Valeriy V. Argunov (JIRA)

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

Valeriy V. Argunov updated AMQCPP-540:
--

Attachment: AbstractDiscoveryAgent.cpp.patch

Patch.

> Ambiguous usage of Math::min in AbstractDiscoveryAgent.cpp
> --
>
> Key: AMQCPP-540
> URL: https://issues.apache.org/jira/browse/AMQCPP-540
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Build Support
>Reporter: Valeriy V. Argunov
>Assignee: Timothy Bish
> Attachments: AbstractDiscoveryAgent.cpp.patch
>
>
> Here is a patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (AMQCPP-539) Can't build GIT master on MSVC

2014-04-25 Thread Valeriy V. Argunov (JIRA)

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

Valeriy V. Argunov updated AMQCPP-539:
--

Attachment: PlatformDefs.h.patch

Patch.

> Can't build GIT master on MSVC
> --
>
> Key: AMQCPP-539
> URL: https://issues.apache.org/jira/browse/AMQCPP-539
> Project: ActiveMQ C++ Client
>  Issue Type: Bug
>  Components: Build Support
> Environment: MSVC2012
>Reporter: Valeriy V. Argunov
>Assignee: Timothy Bish
> Attachments: PlatformDefs.h.patch
>
>
> PlatformDefs.h for Windows defines only PLATFORM_DEFAULT_STACK_SIZE, but 
> PlatformThread.cpp tries to use PLATFORM_MIN_STACK_SIZE.
> Here is a patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (AMQCPP-539) Can't build GIT master on MSVC

2014-04-25 Thread Valeriy V. Argunov (JIRA)
Valeriy V. Argunov created AMQCPP-539:
-

 Summary: Can't build GIT master on MSVC
 Key: AMQCPP-539
 URL: https://issues.apache.org/jira/browse/AMQCPP-539
 Project: ActiveMQ C++ Client
  Issue Type: Bug
  Components: Build Support
 Environment: MSVC2012
Reporter: Valeriy V. Argunov
Assignee: Timothy Bish
 Attachments: PlatformDefs.h.patch

PlatformDefs.h for Windows defines only PLATFORM_DEFAULT_STACK_SIZE, but 
PlatformThread.cpp tries to use PLATFORM_MIN_STACK_SIZE.
Here is a patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)