[jira] [Commented] (AMQNET-440) IObjectMessage.ToObjectT is not working

2013-08-06 Thread Tamilmaran (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730419#comment-13730419
 ] 

Tamilmaran commented on AMQNET-440:
---

Hi Claudio Corsi

thanks for your suggestion but there is no method available with name toObject 
for Body

 IObjectMessage.ToObjectT is not working
 -

 Key: AMQNET-440
 URL: https://issues.apache.org/jira/browse/AMQNET-440
 Project: ActiveMQ .Net
  Issue Type: Bug
Affects Versions: 1.6.0
 Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran

 Hi
 I am working on NMS API 1.6.0. i am not able to deserizile using the 
 following object deserilization mechanism
 objMessage.ToObjectT or
 objMessage.ToObject() as T 
 Please help us to overcome the issue.
 Please find our codes below.
 The code sample:
 {code} 
_consumer.Listener += new MessageListener(OnMessage);   
 Employee emp = new Employee();
 emp.FirstName = raj;
 emp.LastName = esh;
   
IObjectMessage objectMessage = producer.CreateObjectMessage(emp);
objectMessage.NMSType = emp.GetType().ToString();
producer.Send(objectMessage);
 {code}
 {code}
 protected static void OnMessage(IMessage receivedMsg)
 {
 IObjectMessage objMessage = receivedMsg as IObjectMessage;
 //Following code is not working
 IEmployee emp = objMessage.ToObjectIEmployee();
 //Following code is not working
 IEmployee emp1 = objMessage.ToObject() as IEmployee;
 //Following code is working
 IEmployee iEmp = objMessage.Body as IEmployee;//This code only is working
 }
 {code}
 {code}
 public interface IEmployee
 {
 string FirstName { get; set; }
 string LastName { get; set; }
 }
 {code}
 {code}
 [Serializable]
 public class Employee : IEmployee
 {
 #region IEmployee Members
 private string _firstName;
 private string _lastName;
 public string FirstName
 {
 get
 {
 return this._firstName;
 }
 set
 {
 this._firstName = value;
 }
 }
 public string LastName
 {
 get
 {
 return this._lastName;
 }
 set
 {
 this._lastName = value;
 }
 }
 #endregion
 }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (AMQNET-440) IObjectMessage.ToObjectT is not working

2013-08-06 Thread Tamilmaran (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730421#comment-13730421
 ] 

Tamilmaran commented on AMQNET-440:
---

Thanks Jim Gomes

Your suggestion is good


 IObjectMessage.ToObjectT is not working
 -

 Key: AMQNET-440
 URL: https://issues.apache.org/jira/browse/AMQNET-440
 Project: ActiveMQ .Net
  Issue Type: Bug
Affects Versions: 1.6.0
 Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran

 Hi
 I am working on NMS API 1.6.0. i am not able to deserizile using the 
 following object deserilization mechanism
 objMessage.ToObjectT or
 objMessage.ToObject() as T 
 Please help us to overcome the issue.
 Please find our codes below.
 The code sample:
 {code} 
_consumer.Listener += new MessageListener(OnMessage);   
 Employee emp = new Employee();
 emp.FirstName = raj;
 emp.LastName = esh;
   
IObjectMessage objectMessage = producer.CreateObjectMessage(emp);
objectMessage.NMSType = emp.GetType().ToString();
producer.Send(objectMessage);
 {code}
 {code}
 protected static void OnMessage(IMessage receivedMsg)
 {
 IObjectMessage objMessage = receivedMsg as IObjectMessage;
 //Following code is not working
 IEmployee emp = objMessage.ToObjectIEmployee();
 //Following code is not working
 IEmployee emp1 = objMessage.ToObject() as IEmployee;
 //Following code is working
 IEmployee iEmp = objMessage.Body as IEmployee;//This code only is working
 }
 {code}
 {code}
 public interface IEmployee
 {
 string FirstName { get; set; }
 string LastName { get; set; }
 }
 {code}
 {code}
 [Serializable]
 public class Employee : IEmployee
 {
 #region IEmployee Members
 private string _firstName;
 private string _lastName;
 public string FirstName
 {
 get
 {
 return this._firstName;
 }
 set
 {
 this._firstName = value;
 }
 }
 public string LastName
 {
 get
 {
 return this._lastName;
 }
 set
 {
 this._lastName = value;
 }
 }
 #endregion
 }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Issue Comment Deleted] (AMQNET-440) IObjectMessage.ToObjectT is not working

2013-08-06 Thread Tamilmaran (JIRA)

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

Tamilmaran updated AMQNET-440:
--

Comment: was deleted

(was: Thanks Jim Gomes

Your suggestion is good
)

 IObjectMessage.ToObjectT is not working
 -

 Key: AMQNET-440
 URL: https://issues.apache.org/jira/browse/AMQNET-440
 Project: ActiveMQ .Net
  Issue Type: Bug
Affects Versions: 1.6.0
 Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran

 Hi
 I am working on NMS API 1.6.0. i am not able to deserizile using the 
 following object deserilization mechanism
 objMessage.ToObjectT or
 objMessage.ToObject() as T 
 Please help us to overcome the issue.
 Please find our codes below.
 The code sample:
 {code} 
_consumer.Listener += new MessageListener(OnMessage);   
 Employee emp = new Employee();
 emp.FirstName = raj;
 emp.LastName = esh;
   
IObjectMessage objectMessage = producer.CreateObjectMessage(emp);
objectMessage.NMSType = emp.GetType().ToString();
producer.Send(objectMessage);
 {code}
 {code}
 protected static void OnMessage(IMessage receivedMsg)
 {
 IObjectMessage objMessage = receivedMsg as IObjectMessage;
 //Following code is not working
 IEmployee emp = objMessage.ToObjectIEmployee();
 //Following code is not working
 IEmployee emp1 = objMessage.ToObject() as IEmployee;
 //Following code is working
 IEmployee iEmp = objMessage.Body as IEmployee;//This code only is working
 }
 {code}
 {code}
 public interface IEmployee
 {
 string FirstName { get; set; }
 string LastName { get; set; }
 }
 {code}
 {code}
 [Serializable]
 public class Employee : IEmployee
 {
 #region IEmployee Members
 private string _firstName;
 private string _lastName;
 public string FirstName
 {
 get
 {
 return this._firstName;
 }
 set
 {
 this._firstName = value;
 }
 }
 public string LastName
 {
 get
 {
 return this._lastName;
 }
 set
 {
 this._lastName = value;
 }
 }
 #endregion
 }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Issue Comment Deleted] (AMQNET-440) IObjectMessage.ToObjectT is not working

2013-08-06 Thread Tamilmaran (JIRA)

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

Tamilmaran updated AMQNET-440:
--

Comment: was deleted

(was: Hi Claudio Corsi

thanks for your suggestion but there is no method available with name toObject 
for Body)

 IObjectMessage.ToObjectT is not working
 -

 Key: AMQNET-440
 URL: https://issues.apache.org/jira/browse/AMQNET-440
 Project: ActiveMQ .Net
  Issue Type: Bug
Affects Versions: 1.6.0
 Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran

 Hi
 I am working on NMS API 1.6.0. i am not able to deserizile using the 
 following object deserilization mechanism
 objMessage.ToObjectT or
 objMessage.ToObject() as T 
 Please help us to overcome the issue.
 Please find our codes below.
 The code sample:
 {code} 
_consumer.Listener += new MessageListener(OnMessage);   
 Employee emp = new Employee();
 emp.FirstName = raj;
 emp.LastName = esh;
   
IObjectMessage objectMessage = producer.CreateObjectMessage(emp);
objectMessage.NMSType = emp.GetType().ToString();
producer.Send(objectMessage);
 {code}
 {code}
 protected static void OnMessage(IMessage receivedMsg)
 {
 IObjectMessage objMessage = receivedMsg as IObjectMessage;
 //Following code is not working
 IEmployee emp = objMessage.ToObjectIEmployee();
 //Following code is not working
 IEmployee emp1 = objMessage.ToObject() as IEmployee;
 //Following code is working
 IEmployee iEmp = objMessage.Body as IEmployee;//This code only is working
 }
 {code}
 {code}
 public interface IEmployee
 {
 string FirstName { get; set; }
 string LastName { get; set; }
 }
 {code}
 {code}
 [Serializable]
 public class Employee : IEmployee
 {
 #region IEmployee Members
 private string _firstName;
 private string _lastName;
 public string FirstName
 {
 get
 {
 return this._firstName;
 }
 set
 {
 this._firstName = value;
 }
 }
 public string LastName
 {
 get
 {
 return this._lastName;
 }
 set
 {
 this._lastName = value;
 }
 }
 #endregion
 }
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache activemq 5.2.0

2013-08-06 Thread Venkat
Hi all, 
I am using apache activemq 5.2.0 with ibm java 1.6 

My question is , can i continue to use this on Oracle java 1.7?Will there be
any issues if i make the change? 

Venkat
PS:I am resending this message since i am new to forum and i was told to
subscribe to mailing list and post again 



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


Re: Apache activemq 5.2.0

2013-08-06 Thread Christian Posta
Not sure. You'll have to give it a shot yourself. I think the community
version of 5.2.0 is EOL and we definitely don't test it out on 1.7 afaik.
Should be alright theoretically, but your best bet is to thoroughly test it
yourself. Or upgrade to a newer version.


On Mon, Aug 5, 2013 at 6:51 PM, Venkat br.ven...@gmail.com wrote:

 Hi all,
 I am using apache activemq 5.2.0 with ibm java 1.6

 My question is , can i continue to use this on Oracle java 1.7?Will there
 be
 any issues if i make the change?

 Venkat
 PS:I am resending this message since i am new to forum and i was told to
 subscribe to mailing list and post again



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




-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta


[jira] [Commented] (AMQ-4595) QueueBrowser hangs when browsing large queues

2013-08-06 Thread Nicholas Rahn (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQ-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730864#comment-13730864
 ] 

Nicholas Rahn commented on AMQ-4595:


I verified that this works in the latest 5.9-SNAPSHOT.

@Torsten - I don't have rights to comment on support cases at RH anymore since 
my subscription expired. You can close the support ticket there too.


 QueueBrowser hangs when browsing large queues
 -

 Key: AMQ-4595
 URL: https://issues.apache.org/jira/browse/AMQ-4595
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.8.0
 Environment: All
Reporter: Nicholas Rahn
Assignee: Timothy Bish
Priority: Critical
  Labels: QueueBrowser
 Fix For: 5.9.0

 Attachments: AMQ4595Test.java, AMQ580BrowsingBug.java, 
 amq-test-20130621T155120.log


 When trying to browse a queue with a QueueBrowser, the browsing will hang and 
 never complete. This appears to happen only with a lot of message in the 
 queue. 1000 messages works correctly, but 1 hangs.
 I have attached a unit test that exhibits the problem. Change the 
 messageToSend variable in the test method to see the difference between 
 small queue size and large queue size. 
 I've attached the unit test code as well as the output from one of the runs 
 with 1 messages. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (AMQNET-194) Async error occurred: javax.jms.JMSException: Unmatched acknowledege when Acknowledgemode of Transactional used

2013-08-06 Thread Volker Kleinschmidt (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQNET-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730913#comment-13730913
 ] 

Volker Kleinschmidt commented on AMQNET-194:


It appears this was only ever fixed in NMS, and not in plain old ActiveMQ, no? 
We're still seeing it on 5.7.0, and it's not listed in any fix list.

 Async error occurred: javax.jms.JMSException: Unmatched acknowledege when 
 Acknowledgemode of Transactional used
 ---

 Key: AMQNET-194
 URL: https://issues.apache.org/jira/browse/AMQNET-194
 Project: ActiveMQ .Net
  Issue Type: Bug
  Components: ActiveMQ, NMS
Affects Versions: 1.0.0, 1.1.0
 Environment: ActiveMQ 5.2 as Windows Service on Windows Server 2008 
 64-bit.  Client producer and consumer on Windows XP
Reporter: Mark Gellings
Assignee: Timothy Bish
 Fix For: 1.2.0

 Attachments: activemq.xml, CropperCapture[61].jpg, 
 CropperCapture[62].jpg, CropperCapture[63].jpg, debugging.patch, 
 debuggingTrunk.patch, NativeNMSConsumerAndProducer.zip, 
 screenshot-of-captured-exception.jpg


 See 
 http://www.nabble.com/Async-error-occurred--%3E-ActiveMQ-5.2-and-NMS-td25474605.html
  for a primer to this issue.
 After troubleshooting this,  it appears that if a producer sends 65535+ 
 messages to the broker that the consumer gets into an infinite loop after 
 consuming 65535 messages.  
 I will be attaching a test case for this.  Run a producer and a consumer, 
 send 100,000 messages and the test case fails at 65535 messages consumed 
 exactly.
 What appears to be happening is that the NMS provider (or ActiveMQ 5.2) is 
 hitting the upper bound of a ushort and then starting all back over again 
 sending message acknowledgements from message #1.  This message was already 
 dispatched though and the broker lot shows an error that the message is not 
 in the dispatched-list .
 The consumer shows a message acknowledgement going out.
 These errors repeat infinitely it seems.  Once the 65535th message errors out 
 then it starts all over again at the 1st message.
 Notice the ProducerSequenceId growing beyond 65535.  I can't seem to avoid 
 this error, even if I reinstantiate the producer sporadically.
 At the beginning of the source code I have included a loop which shows the 
 behavior of incrementing a ushort beyond 65535.  The variable resets to the 
 lower bound as expected.
 [DEBUG] Apache.NMS.Tracer - Sending Ack: MessageAck[ 
 Destination=queue://testmonday150 TransactionId=LocalTransactionId[ 
 Value=30558 ConnectionId=ConnectionId[ 
 Value=2b6ae5a1-c0e1-4523-8d9c-4143cc9d74e8 ] ] ConsumerId=ConsumerId[ 
 ConnectionId=2b6ae5a1-c0e1-4523-8d9c-4143cc9d74e8 SessionId=1 Value=1 ] 
 AckType=2 FirstMessageId=MessageId[ ProducerId=ProducerId[ 
 ConnectionId=9e256437-df18-44e5-9cb2-b7f3feaebcfd Value=1 SessionId=1 ] 
 ProducerSequenceId=30558 BrokerSequenceId=80280 ] LastMessageId=MessageId[ 
 ProducerId=ProducerId[ ConnectionId=9e256437-df18-44e5-9cb2-b7f3feaebcfd 
 Value=1 SessionId=1 ] ProducerSequenceId=30558 BrokerSequenceId=80280 ] 
 MessageCount=1 ]
  ERROR Service-
  Async error occurred: javax.jms.JMSException: Unmatched acknowledege: 
 MessageAc
 k {commandId = 26140, responseRequired = false, ackType = 2, consumerId = 
 41b092
 97-da4b-4d11-9ed7-09d344825740:1:1, firstMessageId = 
 4128971e-c69b-4892-8be5-d99
 868045881:1:1:30558, lastMessageId = 
 4128971e-c69b-4892-8be5-d99868045881:1:1:30
 558, destination = queue://testwed924, transactionId = 
 TX:41b09297-da4b-4d11-9ed
 7-09d344825740:30558, messageCount = 1}; Could not find Message-ID 
 4128971e-c69b
 -4892-8be5-d99868045881:1:1:30558 in dispatched-list (start of ack)
 INFO   | jvm 1| 2009/10/07 14:03:27 | javax.jms.JMSException: Unmatched 
 ackn
 owledege: MessageAck {commandId = 26140, responseRequired = false, ackType = 
 2,
 consumerId = 41b09297-da4b-4d11-9ed7-09d344825740:1:1, firstMessageId = 
 4128971e
 -c69b-4892-8be5-d99868045881:1:1:30558, lastMessageId = 
 4128971e-c69b-4892-8be5-
 d99868045881:1:1:30558, destination = queue://testwed924, transactionId = 
 TX:41b
 09297-da4b-4d11-9ed7-09d344825740:30558, messageCount = 1}; Could not find 
 Messa
 ge-ID 4128971e-c69b-4892-8be5-d99868045881:1:1:30558 in dispatched-list 
 (start o
 f ack)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 gion.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:4
 38)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 gion.PrefetchSubscription.acknowledge(PrefetchSubscription.java:188)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 

[jira] [Commented] (AMQNET-194) Async error occurred: javax.jms.JMSException: Unmatched acknowledege when Acknowledgemode of Transactional used

2013-08-06 Thread Timothy Bish (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQNET-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13730954#comment-13730954
 ] 

Timothy Bish commented on AMQNET-194:
-

Try with 5.8 which is the latest release, or a 5.9-SNAPSHOT.  Unit tests and 
jira issues are they way to go if you can reproduce a bug. 

 Async error occurred: javax.jms.JMSException: Unmatched acknowledege when 
 Acknowledgemode of Transactional used
 ---

 Key: AMQNET-194
 URL: https://issues.apache.org/jira/browse/AMQNET-194
 Project: ActiveMQ .Net
  Issue Type: Bug
  Components: ActiveMQ, NMS
Affects Versions: 1.0.0, 1.1.0
 Environment: ActiveMQ 5.2 as Windows Service on Windows Server 2008 
 64-bit.  Client producer and consumer on Windows XP
Reporter: Mark Gellings
Assignee: Timothy Bish
 Fix For: 1.2.0

 Attachments: activemq.xml, CropperCapture[61].jpg, 
 CropperCapture[62].jpg, CropperCapture[63].jpg, debugging.patch, 
 debuggingTrunk.patch, NativeNMSConsumerAndProducer.zip, 
 screenshot-of-captured-exception.jpg


 See 
 http://www.nabble.com/Async-error-occurred--%3E-ActiveMQ-5.2-and-NMS-td25474605.html
  for a primer to this issue.
 After troubleshooting this,  it appears that if a producer sends 65535+ 
 messages to the broker that the consumer gets into an infinite loop after 
 consuming 65535 messages.  
 I will be attaching a test case for this.  Run a producer and a consumer, 
 send 100,000 messages and the test case fails at 65535 messages consumed 
 exactly.
 What appears to be happening is that the NMS provider (or ActiveMQ 5.2) is 
 hitting the upper bound of a ushort and then starting all back over again 
 sending message acknowledgements from message #1.  This message was already 
 dispatched though and the broker lot shows an error that the message is not 
 in the dispatched-list .
 The consumer shows a message acknowledgement going out.
 These errors repeat infinitely it seems.  Once the 65535th message errors out 
 then it starts all over again at the 1st message.
 Notice the ProducerSequenceId growing beyond 65535.  I can't seem to avoid 
 this error, even if I reinstantiate the producer sporadically.
 At the beginning of the source code I have included a loop which shows the 
 behavior of incrementing a ushort beyond 65535.  The variable resets to the 
 lower bound as expected.
 [DEBUG] Apache.NMS.Tracer - Sending Ack: MessageAck[ 
 Destination=queue://testmonday150 TransactionId=LocalTransactionId[ 
 Value=30558 ConnectionId=ConnectionId[ 
 Value=2b6ae5a1-c0e1-4523-8d9c-4143cc9d74e8 ] ] ConsumerId=ConsumerId[ 
 ConnectionId=2b6ae5a1-c0e1-4523-8d9c-4143cc9d74e8 SessionId=1 Value=1 ] 
 AckType=2 FirstMessageId=MessageId[ ProducerId=ProducerId[ 
 ConnectionId=9e256437-df18-44e5-9cb2-b7f3feaebcfd Value=1 SessionId=1 ] 
 ProducerSequenceId=30558 BrokerSequenceId=80280 ] LastMessageId=MessageId[ 
 ProducerId=ProducerId[ ConnectionId=9e256437-df18-44e5-9cb2-b7f3feaebcfd 
 Value=1 SessionId=1 ] ProducerSequenceId=30558 BrokerSequenceId=80280 ] 
 MessageCount=1 ]
  ERROR Service-
  Async error occurred: javax.jms.JMSException: Unmatched acknowledege: 
 MessageAc
 k {commandId = 26140, responseRequired = false, ackType = 2, consumerId = 
 41b092
 97-da4b-4d11-9ed7-09d344825740:1:1, firstMessageId = 
 4128971e-c69b-4892-8be5-d99
 868045881:1:1:30558, lastMessageId = 
 4128971e-c69b-4892-8be5-d99868045881:1:1:30
 558, destination = queue://testwed924, transactionId = 
 TX:41b09297-da4b-4d11-9ed
 7-09d344825740:30558, messageCount = 1}; Could not find Message-ID 
 4128971e-c69b
 -4892-8be5-d99868045881:1:1:30558 in dispatched-list (start of ack)
 INFO   | jvm 1| 2009/10/07 14:03:27 | javax.jms.JMSException: Unmatched 
 ackn
 owledege: MessageAck {commandId = 26140, responseRequired = false, ackType = 
 2,
 consumerId = 41b09297-da4b-4d11-9ed7-09d344825740:1:1, firstMessageId = 
 4128971e
 -c69b-4892-8be5-d99868045881:1:1:30558, lastMessageId = 
 4128971e-c69b-4892-8be5-
 d99868045881:1:1:30558, destination = queue://testwed924, transactionId = 
 TX:41b
 09297-da4b-4d11-9ed7-09d344825740:30558, messageCount = 1}; Could not find 
 Messa
 ge-ID 4128971e-c69b-4892-8be5-d99868045881:1:1:30558 in dispatched-list 
 (start o
 f ack)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 gion.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:4
 38)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 gion.PrefetchSubscription.acknowledge(PrefetchSubscription.java:188)
 INFO   | jvm 1| 2009/10/07 14:03:27 |   at 
 org.apache.activemq.broker.re
 

jmsSelector issue when querying for double/float values

2013-08-06 Thread neilcwilkinson
I have an interesting issue with the jmsSelector:

if I enter messages in a queue where I set a 'Val' property to 1.1300, the
following selector works for both a consumer or queue browser:
String jmsSelector = Val  1.1200;

If however I set the value in code (i.e. in a loop) e.g.

double val = 1.1190;

// Create a messages
for (int i = 0; i  1000; i++) {
String text = Hello world! From:  +
Thread.currentThread().getName() +  :  +  
 
this.hashCode();
TextMessage message = session.createTextMessage(text);

val += 0.0001;

message.setDoubleProperty(Val, val);

// Tell the producer to send the message
//System.out.println(Sent message:  +
message.hashCode() +  :  + Thread.currentThread().getName());
producer.send(message);
}

I get no results when using the previously mentioned jmsSelector. Anyone
have any ideas?

Thanks,

Neil.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/jmsSelector-issue-when-querying-for-double-float-values-tp4670135.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.