[jira] [Created] (AMQ-4813) Viewing message details when message ID contains a plus results in " No message could be found for ID {messageID}"
Michael Bildner created AMQ-4813:
Summary: Viewing message details when message ID contains a plus
results in " No message could be found for ID {messageID}"
Key: AMQ-4813
URL: https://issues.apache.org/jira/browse/AMQ-4813
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Michael Bildner
Priority: Minor
Steps to reproduce:
# Using the admin console, go to the Queues page.
# Click on one of the queues to get to the queue's browse page.
# Click on a message ID that contains a plus sign (+).
Expected:
See the message's headers, properties, actions, and details.
Actual:
Get a page with the error message "No message could be found for ID
{messageID}", where {messageID} contains the message ID clicked on. Note that
the message ID displayed in the error message replaces the plus sign (+) with a
space.
Underlying cause:
The html link that is created for each message ID in the queue's browse page
does not properly URL encode the message ID. In my particular example, the
link for message ID "AgXkceW74zCq+kZB1llPos1QcmTfOziGAmWRuk1forI=" is:
http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}+{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
when it should be:
http://localhost:8161/admin/message.jsp?id=AgXkceW74zCq{color:red}%2B{color}kZB1llPos1QcmTfOziGAmWRuk1forI=&JMSDestination=AMQPTest
The trouble area is shown with a red font.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (AMQ-4383) ActiveMQ dependency not present in central maven repository ??
[ https://issues.apache.org/jira/browse/AMQ-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798027#comment-13798027 ] Scot Hale commented on AMQ-4383: - When using a maven proxy the fuse repository has to be explicitly added to the maven proxy ( Nexus in our case ). Fuse has duplicates of many common jars found in the public repository. So it is not easy to add the http://repo.fusesource.com repository to our proxy, due to trust and security issues with common jars. This means we have to resort to manually adding the fuse dependencies to our proxy just to bring in the activemq-apollo dependency successfully. It seems like a bad practice to have a public repository artifact depend on third party repositories. > ActiveMQ dependency not present in central maven repository ?? > -- > > Key: AMQ-4383 > URL: https://issues.apache.org/jira/browse/AMQ-4383 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.8.0 > Environment: Linux >Reporter: Bhanu > > We're facing issues while trying to upgrade to ActiveMQ v5.8. The maven build > is failing with the following error:- > > org.apache.activemq > activemq-all > 5.8.0 > > mvn package -Dmaven.test.skip=true > [INFO] Scanning for projects... > [INFO] > > [INFO] Building common > [INFO]task-segment: [package] > [INFO] > > [INFO] [resources:resources] > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /prod/desflow-qa/dflowdev/test/desflow/common/src/main/resources > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar > Downloading: > http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) org.apache.qpid:proton-jms:jar:0.3.0-fuse-2 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.qpid > -DartifactId=proton-jms -Dversion=0.3.0-fuse-2 -Dpackaging=jar > -Dfile=/path/to/file > Is something broken here ? > Thanks, > Bhanu -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.1 #2
+1 On Wed, Oct 16, 2013 at 11:04 AM, Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1 > > New in this release: > > * Improved Discovery Transport and Agent API > * Improved the multicast discovery agent. > * Added new HTTP based discovery agent. > * Minor bug fixes and stability improvements. > > The binaries and source bundles for the Release Candidate can be found here: > http://people.apache.org/~tabish/nms-1.6.0 > > The Wiki Page for this release is here: > http://activemq.apache.org/nms/apachenmsactivemq-v161.html > > The list of issues resolved is here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792 > > Please cast your votes (the vote will be open for 72 hrs): > > [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.1 > [ ] -1 Veto the release (provide specific comments) > > Here's my +1 > > Regards > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino blog: Hiram Chirino's Bit Mojo
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.1 #2
+1 On 16 October 2013 16:04, Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1 > > New in this release: > > * Improved Discovery Transport and Agent API > * Improved the multicast discovery agent. > * Added new HTTP based discovery agent. > * Minor bug fixes and stability improvements. > > The binaries and source bundles for the Release Candidate can be found here: > http://people.apache.org/~tabish/nms-1.6.0 > > The Wiki Page for this release is here: > http://activemq.apache.org/nms/apachenmsactivemq-v161.html > > The list of issues resolved is here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792 > > Please cast your votes (the vote will be open for 72 hrs): > > [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.1 > [ ] -1 Veto the release (provide specific comments) > > Here's my +1 > > Regards > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > -- http://redhat.com http://blog.garytully.com
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.1 #2
+1 On Thu, Oct 17, 2013 at 2:12 AM, Dejan Bosanac wrote: > +1 > > Regards > -- > Dejan Bosanac > -- > Red Hat, Inc. > FuseSource is now part of Red Hat > dbosa...@redhat.com > Twitter: @dejanb > Blog: http://sensatic.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > On Thu, Oct 17, 2013 at 10:44 AM, Claus Ibsen > wrote: > > > +1 > > > > On Wed, Oct 16, 2013 at 5:04 PM, Timothy Bish > wrote: > > > Hello > > > > > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1 > > > > > > New in this release: > > > > > > * Improved Discovery Transport and Agent API > > > * Improved the multicast discovery agent. > > > * Added new HTTP based discovery agent. > > > * Minor bug fixes and stability improvements. > > > > > > The binaries and source bundles for the Release Candidate can be found > > here: > > > http://people.apache.org/~tabish/nms-1.6.0 > > > > > > The Wiki Page for this release is here: > > > http://activemq.apache.org/nms/apachenmsactivemq-v161.html > > > > > > The list of issues resolved is here: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792 > > > > > > Please cast your votes (the vote will be open for 72 hrs): > > > > > > [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.1 > > > [ ] -1 Veto the release (provide specific comments) > > > > > > Here's my +1 > > > > > > Regards > > > > > > -- > > > Tim Bish > > > Sr Software Engineer | RedHat Inc. > > > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > > > skype: tabish121 | twitter: @tabish121 > > > blog: http://timbish.blogspot.com/ > > > > > > > > > > > -- > > Claus Ibsen > > - > > Red Hat, Inc. > > Email: cib...@redhat.com > > Twitter: davsclaus > > Blog: http://davsclaus.com > > Author of Camel in Action: http://www.manning.com/ibsen > > > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
[jira] [Updated] (AMQ-4812) Rebalance not working on 5.8.0
[ https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne Evans updated AMQ-4812: - Attachment: Broker2_activemq.xml Broker1_activemq.xml (Example)IsecStateConsumer.properties > Rebalance not working on 5.8.0 > -- > > Key: AMQ-4812 > URL: https://issues.apache.org/jira/browse/AMQ-4812 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 5.8.0 >Reporter: Wayne Evans > Attachments: Broker1_activemq.xml, Broker2_activemq.xml, > (Example)IsecStateConsumer.properties > > > Two brokers networked. > Transport connectors configured on both with: > rebalanceClusterClients="true" updateClusterClients="true" > updateClusterClientsOnRemove="true" > Clients configured with only Broker 1 in Failover string. > Clients all connect to 1st Broker when starting up. > When first broker is stopped all clients fail over to 2nd Broker. > When 1st Broker is brought back up all clients remain on 2nd Broker. > Config files from both Brokers and one sample client config attached. > Related issue - queued messages on 1st Broker that were passed from 2nd > broker initially are not consumed after 1st Broker is brought back up as > rules prevent them from being passed back to 2nd Broker where client > consumers are attached. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (AMQ-4812) Rebalance not working on 5.8.0
[ https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne Evans updated AMQ-4812: - Description: Two brokers networked. Transport connectors configured on both with: rebalanceClusterClients="true" updateClusterClients="true" updateClusterClientsOnRemove="true" Clients configured with only Broker 1 in Failover string. Clients all connect to 1st Broker when starting up. When first broker is stopped all clients fail over to 2nd Broker. When 1st Broker is brought back up all clients remain on 2nd Broker. Config files from both Brokers and one sample client config attached. Related issue - queued messages on 1st Broker that were passed from 2nd broker initially are not consumed after 1st Broker is brought back up as rules prevent them from being passed back to 2nd Broker where client consumers are attached. was: Two brokers networked. Transport connectors configured on both with: rebalanceClusterClients="true" updateClusterClients="true" updateClusterClientsOnRemove="true" Clients configured with only Broker 1 in Failover string. Clients all connect to 1st Broker when starting up. When first broker is stopped all clients fail over to 2nd Broker. When 1st Broker is brought back up all clients remain on 2nd Broker. Related issue - queued messages on 1st Broker that were passed from 2nd broker initially are not consumed after 1st Broker is brought back up as rules prevent them from being passed back to 2nd Broker where client consumers are attached. > Rebalance not working on 5.8.0 > -- > > Key: AMQ-4812 > URL: https://issues.apache.org/jira/browse/AMQ-4812 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 5.8.0 >Reporter: Wayne Evans > > Two brokers networked. > Transport connectors configured on both with: > rebalanceClusterClients="true" updateClusterClients="true" > updateClusterClientsOnRemove="true" > Clients configured with only Broker 1 in Failover string. > Clients all connect to 1st Broker when starting up. > When first broker is stopped all clients fail over to 2nd Broker. > When 1st Broker is brought back up all clients remain on 2nd Broker. > Config files from both Brokers and one sample client config attached. > Related issue - queued messages on 1st Broker that were passed from 2nd > broker initially are not consumed after 1st Broker is brought back up as > rules prevent them from being passed back to 2nd Broker where client > consumers are attached. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (AMQ-4812) Rebalance not working on 5.8.0
[ https://issues.apache.org/jira/browse/AMQ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne Evans updated AMQ-4812: - Description: Two brokers networked. Transport connectors configured on both with: rebalanceClusterClients="true" updateClusterClients="true" updateClusterClientsOnRemove="true" Clients configured with only Broker 1 in Failover string. Clients all connect to 1st Broker when starting up. When first broker is stopped all clients fail over to 2nd Broker. When 1st Broker is brought back up all clients remain on 2nd Broker. Related issue - queued messages on 1st Broker that were passed from 2nd broker initially are not consumed after 1st Broker is brought back up as rules prevent them from being passed back to 2nd Broker where client consumers are attached. > Rebalance not working on 5.8.0 > -- > > Key: AMQ-4812 > URL: https://issues.apache.org/jira/browse/AMQ-4812 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 5.8.0 >Reporter: Wayne Evans > > Two brokers networked. > Transport connectors configured on both with: > rebalanceClusterClients="true" updateClusterClients="true" > updateClusterClientsOnRemove="true" > Clients configured with only Broker 1 in Failover string. > Clients all connect to 1st Broker when starting up. > When first broker is stopped all clients fail over to 2nd Broker. > When 1st Broker is brought back up all clients remain on 2nd Broker. > Related issue - queued messages on 1st Broker that were passed from 2nd > broker initially are not consumed after 1st Broker is brought back up as > rules prevent them from being passed back to 2nd Broker where client > consumers are attached. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4812) Rebalance not working on 5.8.0
Wayne Evans created AMQ-4812: Summary: Rebalance not working on 5.8.0 Key: AMQ-4812 URL: https://issues.apache.org/jira/browse/AMQ-4812 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 5.8.0 Reporter: Wayne Evans -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (AMQ-3303) Standalone Webconsole crashes when accessing master-slave failover activeMQ
[ https://issues.apache.org/jira/browse/AMQ-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-3303. - Resolution: Fixed Fix Version/s: 5.9.0 unit test that validates the fix in https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f5dd1256 > Standalone Webconsole crashes when accessing master-slave failover activeMQ > --- > > Key: AMQ-3303 > URL: https://issues.apache.org/jira/browse/AMQ-3303 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.5.0 > Environment: Webconsole running on tomcat 6 on ubuntu 10.04LTS with > sun jdk. > Options : webconsole.type=properties, > webconsole.jms.url=failover:(tcp://activemq-1:61616,tcp://activemq-2:61616), > webconsole.jms.user=xx, webconsole.jms.password=x, > webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://activemq-1:11099/jmxrmi,service:jmx:rmi:///jndi/rmi://activemq-2:11099/jmxrmi, > webconsole.jmx.user=xxx, webconsole.jmx.password= >Reporter: Arnaud BRAND >Priority: Minor > Fix For: 5.9.0 > > Attachments: RemoteJMXBrokerFacade.patch > > > Null pointer exception when accessing the JSPs if the first jmx server (here > activemq-1) in the jmx url is the slave. > findBrokers in RemoteJMXBrokerFacade finds the slave broker but accessing > some of its attributes results in a NullPointerException. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (AMQ-4811) Page http://activemq.apache.org/hermes-jms.html slightly out-of-date
Martin Lichtin created AMQ-4811: --- Summary: Page http://activemq.apache.org/hermes-jms.html slightly out-of-date Key: AMQ-4811 URL: https://issues.apache.org/jira/browse/AMQ-4811 Project: ActiveMQ Issue Type: Bug Reporter: Martin Lichtin Priority: Minor Page http://activemq.apache.org/hermes-jms.html refers to old versions of ActiveMQ. Can this be updated (perhaps make it version-agnostic). Also there's a link to http://activemq.apache.org/hermes-screenshot.html But that page does not actually show a screenshot. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (AMQ-4181) JMS queue browser returns only page size number of messages
[ https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-4181: Fix Version/s: 5.10.0 > JMS queue browser returns only page size number of messages > --- > > Key: AMQ-4181 > URL: https://issues.apache.org/jira/browse/AMQ-4181 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.7.0 >Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.8.0, 5.10.0 > > > When the number of messages in the queue is larger than set page size, the > jms queue browser will get one page size of messages (200 by default). > Ideally we'd want to send all the messages or at least until we reach the > memory limit set for the queue/broker. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (AMQ-4181) JMS queue browser returns only page size number of messages
[ https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-4181: - think we need a way to make this change configurable based on the existing maxBrowsePageSize. It is now obsolete, but I think using a value of -1 to mean ignore the page limit and use all available memory could make sense. In other words, to remove the browsePageLimit use a value of -1 and when it is specified > 0 it is the hard limit. This means that really large depths can be bounded in a browse. consider a queue with 1m messages and lots of broker memory... our browser will fall over. > JMS queue browser returns only page size number of messages > --- > > Key: AMQ-4181 > URL: https://issues.apache.org/jira/browse/AMQ-4181 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.7.0 >Reporter: Dejan Bosanac >Assignee: Dejan Bosanac > Fix For: 5.8.0, 5.10.0 > > > When the number of messages in the queue is larger than set page size, the > jms queue browser will get one page size of messages (200 by default). > Ideally we'd want to send all the messages or at least until we reach the > memory limit set for the queue/broker. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (AMQ-4802) ActiveMQInputStream does not work for big content
[ https://issues.apache.org/jira/browse/AMQ-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797770#comment-13797770 ] Marc Leineweber commented on AMQ-4802: -- Hello Timothy, have you tried my example classes with a standard ActiveMQ installation? Because I do not use any special configuration in my broker, I think it is not necessary to build a unit test with that special configuration?! Regards, Marc > ActiveMQInputStream does not work for big content > - > > Key: AMQ-4802 > URL: https://issues.apache.org/jira/browse/AMQ-4802 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.8.0 > Environment: Mac OS 10.6.8 >Reporter: Marc Leineweber > > Sending a file with size 4.6 MB with ActiveMQOutputStream works and results > in 71 messages on the ActiveMQ broker. > Trying to receive this file / these messages using an ActiveMQInputStream > fails - after a while (720896 bytes received so far) inputStream.read(buffer) > never answers (it waits in ...). If inputStream is created with a timeout, I > get a ActiveMQInputStream$ReadTimeoutEcxeption. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (AMQNET-453) unable to filter the messages with out names space of the TYpe
[
https://issues.apache.org/jira/browse/AMQNET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797769#comment-13797769
]
Timothy Bish commented on AMQNET-453:
-
So far I don't see anything setting the type field so not sure what you are
expecting to happen here. Best bet is to provide a sample unit test that shows
your problem.
> unable to filter the messages with out names space of the TYpe
> --
>
> Key: AMQNET-453
> URL: https://issues.apache.org/jira/browse/AMQNET-453
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ, NMS
>Affects Versions: 1.6.0
> Environment: C#-2010
> NMS API 1.6.0
>Reporter: Tamilmaran
>Assignee: Jim Gomes
>
> i am going to use filter in activeMQ based on NMSType of message header
> i have two solutions with different names(i.e. namesspace). Both the
> solutions have two same classes like below
> {code}
> namespace Publisher
> {
> public class HitEvent : FloorEvent, IHitEvent
> {
> }
> }
> {code}
> {code}
> namespace Subscriber
> {
> public class HitEvent : FloorEvent, IHitEvent
> {
> }
> }
> {code}
> Created Filter as below for the consumer
> {code}
> //for filter i have to give like below or else filter is not working
> public const string Filter = "JMSType = 'HitEvent'";
> {code}
> but on the consumer side activemq checking for type with names space. so i am
> not receiving the messages
> can you help me to work with out names spaces
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (AMQNET-453) unable to filter the messages with out names space of the TYpe
[
https://issues.apache.org/jira/browse/AMQNET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQNET-453:
--
Description:
i am going to use filter in activeMQ based on NMSType of message header
i have two solutions with different names(i.e. namesspace). Both the solutions
have two same classes like below
{code}
namespace Publisher
{
public class HitEvent : FloorEvent, IHitEvent
{
}
}
{code}
{code}
namespace Subscriber
{
public class HitEvent : FloorEvent, IHitEvent
{
}
}
{code}
Created Filter as below for the consumer
{code}
//for filter i have to give like below or else filter is not working
public const string Filter = "JMSType = 'HitEvent'";
{code}
but on the consumer side activemq checking for type with names space. so i am
not receiving the messages
can you help me to work with out names spaces
was:
we are going to filter messages based on the type sent through NMSType of
message header
I have 5 classes in two solutions. In both the solutions classes are same but
the namespace is different.
Publishing side i am sending the NMSType as JackpotHitEvent.
but on subscription side it is looking for same with Namespace of the class.
so i am unable to filter the messages
Example code
{code}
namespace FloorEventMessagePrototype
{
public class JackpotHitEvent : FloorEvent, IJackpotHitEvent
{
}
}
{code}
{code}
//for filter i have to give like below or else filter is not working
public const string Filter = "JMSType =
'FloorEventMessagePrototype.JackpotHitEvent'";
{code}
> unable to filter the messages with out names space of the TYpe
> --
>
> Key: AMQNET-453
> URL: https://issues.apache.org/jira/browse/AMQNET-453
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ, NMS
>Affects Versions: 1.6.0
> Environment: C#-2010
> NMS API 1.6.0
>Reporter: Tamilmaran
>Assignee: Jim Gomes
>
> i am going to use filter in activeMQ based on NMSType of message header
> i have two solutions with different names(i.e. namesspace). Both the
> solutions have two same classes like below
> {code}
> namespace Publisher
> {
> public class HitEvent : FloorEvent, IHitEvent
> {
> }
> }
> {code}
> {code}
> namespace Subscriber
> {
> public class HitEvent : FloorEvent, IHitEvent
> {
> }
> }
> {code}
> Created Filter as below for the consumer
> {code}
> //for filter i have to give like below or else filter is not working
> public const string Filter = "JMSType = 'HitEvent'";
> {code}
> but on the consumer side activemq checking for type with names space. so i am
> not receiving the messages
> can you help me to work with out names spaces
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (AMQNET-453) unable to filter the messages with out names space of the TYpe
Tamilmaran created AMQNET-453:
-
Summary: unable to filter the messages with out names space of the
TYpe
Key: AMQNET-453
URL: https://issues.apache.org/jira/browse/AMQNET-453
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ, NMS
Affects Versions: 1.6.0
Environment: C#-2010
NMS API 1.6.0
Reporter: Tamilmaran
Assignee: Jim Gomes
we are going to filter messages based on the type sent through NMSType of
message header
I have 5 classes in two solutions. In both the solutions classes are same but
the namespace is different.
Publishing side i am sending the NMSType as JackpotHitEvent.
but on subscription side it is looking for same with Namespace of the class.
so i am unable to filter the messages
Example code
{code}
namespace FloorEventMessagePrototype
{
public class JackpotHitEvent : FloorEvent, IJackpotHitEvent
{
}
}
{code}
{code}
//for filter i have to give like below or else filter is not working
public const string Filter = "JMSType =
'FloorEventMessagePrototype.JackpotHitEvent'";
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.1 #2
+1 Regards -- Dejan Bosanac -- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Thu, Oct 17, 2013 at 10:44 AM, Claus Ibsen wrote: > +1 > > On Wed, Oct 16, 2013 at 5:04 PM, Timothy Bish wrote: > > Hello > > > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1 > > > > New in this release: > > > > * Improved Discovery Transport and Agent API > > * Improved the multicast discovery agent. > > * Added new HTTP based discovery agent. > > * Minor bug fixes and stability improvements. > > > > The binaries and source bundles for the Release Candidate can be found > here: > > http://people.apache.org/~tabish/nms-1.6.0 > > > > The Wiki Page for this release is here: > > http://activemq.apache.org/nms/apachenmsactivemq-v161.html > > > > The list of issues resolved is here: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792 > > > > Please cast your votes (the vote will be open for 72 hrs): > > > > [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.1 > > [ ] -1 Veto the release (provide specific comments) > > > > Here's my +1 > > > > Regards > > > > -- > > Tim Bish > > Sr Software Engineer | RedHat Inc. > > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > > skype: tabish121 | twitter: @tabish121 > > blog: http://timbish.blogspot.com/ > > > > > > -- > Claus Ibsen > - > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen >
Re: {VOTE] Release Apache.NMS.ActiveMQ 1.6.1 #2
+1 On Wed, Oct 16, 2013 at 5:04 PM, Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.1 > > New in this release: > > * Improved Discovery Transport and Agent API > * Improved the multicast discovery agent. > * Added new HTTP based discovery agent. > * Minor bug fixes and stability improvements. > > The binaries and source bundles for the Release Candidate can be found here: > http://people.apache.org/~tabish/nms-1.6.0 > > The Wiki Page for this release is here: > http://activemq.apache.org/nms/apachenmsactivemq-v161.html > > The list of issues resolved is here: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792 > > Please cast your votes (the vote will be open for 72 hrs): > > [ ] +1 Release the source as Apache NMS.ActiveMQ v1.6.1 > [ ] -1 Veto the release (provide specific comments) > > Here's my +1 > > Regards > > -- > Tim Bish > Sr Software Engineer | RedHat Inc. > tim.b...@redhat.com | www.fusesource.com | www.redhat.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
