[jira] [Created] (AMQ-4653) IObjectMessage.ToObjectT is not working
Tamilmaran created AMQ-4653:
---
Summary: IObjectMessage.ToObjectT is not working
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
//Following code is working
iEmp = objMessage.Body as IEmployee;
}
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
//Following code is working
iEmp = objMessage.Body as IEmployee;
}
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
//Following code is working
iEmp = objMessage.Body as IEmployee;
}
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
//Following code is working
iEmp = objMessage.Body as IEmployee;
}
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
iEmp = objMessage.Body as IEmployee;//This code is working
}
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
//Following code is working
iEmp = objMessage.Body as IEmployee;
}
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
iEmp = objMessage.Body as IEmployee;//This code is working
}
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
= null;
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
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
= null;
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
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
IEmployee iEmp = null;
objMessage = receivedMsg as IObjectMessage;
//Following code is not working
IEmployee emp = objMessage.ToObjectIEmployee();
//Following code is not working
IEmployee emp1 = objMessage.ToObject() as IEmployee;
if (objMessage != null)
{
iEmp = objMessage.Body as IEmployee;//This code is working
}
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
= null;
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
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
bq.
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
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
--
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] [Updated] (AMQ-4653) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQ-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran updated AMQ-4653:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
bq.
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
}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
IObjectMessage.ToObjectT is not working
-
Key: AMQ-4653
URL: https://issues.apache.org/jira/browse/AMQ-4653
Project: ActiveMQ
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
bq.
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
}
--
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] [Moved] (AMQNET-440) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish moved AMQ-4653 to AMQNET-440:
--
Key: AMQNET-440 (was: AMQ-4653)
Project: ActiveMQ .Net (was: ActiveMQ)
IObjectMessage.ToObjectT is not working
-
Key: AMQNET-440
URL: https://issues.apache.org/jira/browse/AMQNET-440
Project: ActiveMQ .Net
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
--
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] [Updated] (AMQNET-440) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQNET-440:
Affects Version/s: 1.6.0
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
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
{code}
protected static void OnMessage(IMessage receivedMsg)
{
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}
--
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] [Updated] (AMQNET-440) IObjectMessage.ToObjectT is not working
[
https://issues.apache.org/jira/browse/AMQNET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQNET-440:
Description:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
{code}
protected static void OnMessage(IMessage receivedMsg)
{
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}
was:
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
protected static void OnMessage(IMessage receivedMsg)
{
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
}
IObjectMessage.ToObjectT is not working
-
Key: AMQNET-440
URL: https://issues.apache.org/jira/browse/AMQNET-440
Project: ActiveMQ .Net
Issue Type: Bug
Environment: activeMQ 5.8.0, C# API NMS 1.6.0
Reporter: Tamilmaran
IObjectMessage.ToObjectT is not working to achieve deserialization.
The code sample:
{code}
protected static void OnMessage(IMessage receivedMsg)
{
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}
--
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] [Updated] (AMQNET-354) Add new NMS Provider Implementation that provides Pooling for NMS Provider Connection Resources
[ https://issues.apache.org/jira/browse/AMQNET-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-354: Fix Version/s: (was: 1.6.0) 1.6.1 Add new NMS Provider Implementation that provides Pooling for NMS Provider Connection Resources --- Key: AMQNET-354 URL: https://issues.apache.org/jira/browse/AMQNET-354 Project: ActiveMQ .Net Issue Type: Improvement Components: NMS Reporter: Timothy Bish Assignee: Timothy Bish Priority: Minor Fix For: 1.6.1 Create a new NMS Provider that serves as a wrapper around NMS Provider Connections and acts to pool the Connection and its associated resources for use in long running applications which may create and close connections over time or for applications that create and destroy lots of connections and sessions. -- 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] [Updated] (AMQNET-327) Upgrade solution to VisualStudio 2010
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-327: Fix Version/s: (was: 1.6.0) 1.6.1 Upgrade solution to VisualStudio 2010 - Key: AMQNET-327 URL: https://issues.apache.org/jira/browse/AMQNET-327 Project: ActiveMQ .Net Issue Type: Task Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF Reporter: Jim Gomes Assignee: Jim Gomes Labels: net-2.0, net-3.5, net-4.0, vs2010 Fix For: 1.6.1 Original Estimate: 72h Time Spent: 2.5h Remaining Estimate: 66h The solution files should be upgraded to VisualStudio 2010. At the same time, now projects will be created to target specific .NET versions. The existing projects will be renamed to XXX-net2.0.csproj or XXX-net3.5.csproj, as appropriate. For example, the vs2008-nms.csproj will be renamed to vs2010-nms-net2.0.csproj. It will then be duplicated to vs2010-nms-net4.0.csproj to target the .NET 4.0 framework. Other platform specific versions can be created on an as-needed basis. These individual project files will all be included in the single vs2010-nms.sln file. -- 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] [Updated] (AMQ-4375) JoramJmsTest UnifiedSessionTest hangs on Windows or when run with SSL
[ https://issues.apache.org/jira/browse/AMQ-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4375: - Summary: JoramJmsTest UnifiedSessionTest hangs on Windows or when run with SSL (was: org.apache.activemorg.apache.activemq.transport.amqp.joram.JoramJmsTest UnifiedSessionTest hangs on Windowsq.transport.amqp.jorJoramJmsTest UnifiedSessionTest hangs on Windows) JoramJmsTest UnifiedSessionTest hangs on Windows or when run with SSL - Key: AMQ-4375 URL: https://issues.apache.org/jira/browse/AMQ-4375 Project: ActiveMQ Issue Type: Bug Components: Test Cases Environment: Windows 7 and Windows 2008 Server Reporter: Kevin Earls This test suite results in a hang when run on windows. I'll attach a patch which excludes it on Windows for now. -- 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] [Updated] (AMQ-4375) org.apache.activemorg.apache.activemq.transport.amqp.joram.JoramJmsTest UnifiedSessionTest hangs on Windowsq.transport.amqp.jorJoramJmsTest UnifiedSessionTest hangs on Wind
[ https://issues.apache.org/jira/browse/AMQ-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4375: - Summary: org.apache.activemorg.apache.activemq.transport.amqp.joram.JoramJmsTest UnifiedSessionTest hangs on Windowsq.transport.amqp.jorJoramJmsTest UnifiedSessionTest hangs on Windows (was: org.apache.activemq.transport.amqp.joram.JoramJmsTest UnifiedSessionTest hangs on Windows) org.apache.activemorg.apache.activemq.transport.amqp.joram.JoramJmsTest UnifiedSessionTest hangs on Windowsq.transport.amqp.jorJoramJmsTest UnifiedSessionTest hangs on Windows --- Key: AMQ-4375 URL: https://issues.apache.org/jira/browse/AMQ-4375 Project: ActiveMQ Issue Type: Bug Components: Test Cases Environment: Windows 7 and Windows 2008 Server Reporter: Kevin Earls This test suite results in a hang when run on windows. I'll attach a patch which excludes it on Windows for now. -- 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] [Created] (AMQ-4654) JoramJmsTest TopicConnectionTest hangs when run with amqp+ssl
Kevin Earls created AMQ-4654: Summary: JoramJmsTest TopicConnectionTest hangs when run with amqp+ssl Key: AMQ-4654 URL: https://issues.apache.org/jira/browse/AMQ-4654 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor This test case hangs in PubSubTestCase.tearDown when run with amqp+ssl -- 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] [Closed] (AMQ-4652) Test failed under Java 8
[ https://issues.apache.org/jira/browse/AMQ-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-4652. - Resolution: Incomplete Java 8 isn't slated for release until next march, so at this point its a bit early to worry about test failures. Test failed under Java 8 Key: AMQ-4652 URL: https://issues.apache.org/jira/browse/AMQ-4652 Project: ActiveMQ Issue Type: Bug Environment: Ubuntu 13.04, version: 3.8.0-26-generic, arch: i386 OpenJDK 8b99 Maven 3.1.0 Reporter: Greg Bakos Priority: Minor I've tried to make a build under OpenJDK 8b99 and I've got these testing errors: Running org.apache.activemq.transport.mqtt.MQTTNioTest Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 162.262 sec FAILURE! Running org.apache.activemq.transport.mqtt.MQTTSSLTest Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 160.224 sec FAILURE! Running org.apache.activemq.transport.mqtt.MQTTTest Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 156.354 sec FAILURE! Results : Tests in error: testPingOnMQTTNIO(org.apache.activemq.transport.mqtt.MQTTNioTest): The client id MUST be configured when clean session is set to false testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTSSLTest): Command from server contained an invalid message id: 1 testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTTest): Command from server contained an invalid message id: 1 -- 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] [Updated] (AMQ-4375) JoramJmsTest UnifiedSessionTest hangs on Windows or when run with AMQP+SSL
[ https://issues.apache.org/jira/browse/AMQ-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4375: - Summary: JoramJmsTest UnifiedSessionTest hangs on Windows or when run with AMQP+SSL (was: JoramJmsTest UnifiedSessionTest hangs on Windows or when run with SSL) JoramJmsTest UnifiedSessionTest hangs on Windows or when run with AMQP+SSL -- Key: AMQ-4375 URL: https://issues.apache.org/jira/browse/AMQ-4375 Project: ActiveMQ Issue Type: Bug Components: Test Cases Environment: Windows 7 and Windows 2008 Server Reporter: Kevin Earls Attachments: UnifiedSessionTestWithSSL.txt This test suite results in a hang when run on windows. I'll attach a patch which excludes it on Windows for now. -- 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] [Updated] (AMQ-4654) JoramJmsTest TopicConnectionTest hangs when run with amqp+ssl
[ https://issues.apache.org/jira/browse/AMQ-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4654: - Attachment: TopicConnectionTestWithSSL.txt Stack trace attached JoramJmsTest TopicConnectionTest hangs when run with amqp+ssl - Key: AMQ-4654 URL: https://issues.apache.org/jira/browse/AMQ-4654 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: TopicConnectionTestWithSSL.txt This test case hangs in PubSubTestCase.tearDown when run with amqp+ssl -- 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] [Comment Edited] (AMQ-4375) JoramJmsTest UnifiedSessionTest hangs on Windows or when run with AMQP+SSL
[ https://issues.apache.org/jira/browse/AMQ-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720814#comment-13720814 ] Kevin Earls edited comment on AMQ-4375 at 7/26/13 2:15 PM: --- Stack trace attached from run with ampq+ssl was (Author: kearls): Stack trace attached JoramJmsTest UnifiedSessionTest hangs on Windows or when run with AMQP+SSL -- Key: AMQ-4375 URL: https://issues.apache.org/jira/browse/AMQ-4375 Project: ActiveMQ Issue Type: Bug Components: Test Cases Environment: Windows 7 and Windows 2008 Server Reporter: Kevin Earls Attachments: UnifiedSessionTestWithSSL.txt This test suite results in a hang when run on windows. I'll attach a patch which excludes it on Windows for now. -- 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] [Created] (AMQ-4655) We should run JoramJmsTests with amqp+ssl
Kevin Earls created AMQ-4655: Summary: We should run JoramJmsTests with amqp+ssl Key: AMQ-4655 URL: https://issues.apache.org/jira/browse/AMQ-4655 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor We should run the JoramJmsTests using amqp+ssl. I will attach a patch. -- 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] [Updated] (AMQ-4655) We should run JoramJmsTests with amqp+ssl
[ https://issues.apache.org/jira/browse/AMQ-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Earls updated AMQ-4655: - Attachment: AMQ-4655.patch We should run JoramJmsTests with amqp+ssl - Key: AMQ-4655 URL: https://issues.apache.org/jira/browse/AMQ-4655 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor Attachments: AMQ-4655.patch We should run the JoramJmsTests using amqp+ssl. I will attach a patch. -- 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] (AMQ-4652) Test failed under Java 8
[ https://issues.apache.org/jira/browse/AMQ-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720860#comment-13720860 ] Martijn Verburg commented on AMQ-4652: -- Hi Timothy, A volunteer group of technologists are testing major projects early with Java 8 to avoid situations like the Apache Lucene/Solr crashes when Java 7 first came out. You can see more details about this programme at https://java.net/projects/adoptopenjdk/pages/TestingJava8 We'd be grateful if this issue could be re-opened so that we can track the general readiness of applications for Java 8 as the March date gets closer :-). Cheers, Martijn Test failed under Java 8 Key: AMQ-4652 URL: https://issues.apache.org/jira/browse/AMQ-4652 Project: ActiveMQ Issue Type: Bug Environment: Ubuntu 13.04, version: 3.8.0-26-generic, arch: i386 OpenJDK 8b99 Maven 3.1.0 Reporter: Greg Bakos Priority: Minor I've tried to make a build under OpenJDK 8b99 and I've got these testing errors: Running org.apache.activemq.transport.mqtt.MQTTNioTest Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 162.262 sec FAILURE! Running org.apache.activemq.transport.mqtt.MQTTSSLTest Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 160.224 sec FAILURE! Running org.apache.activemq.transport.mqtt.MQTTTest Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 156.354 sec FAILURE! Results : Tests in error: testPingOnMQTTNIO(org.apache.activemq.transport.mqtt.MQTTNioTest): The client id MUST be configured when clean session is set to false testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTSSLTest): Command from server contained an invalid message id: 1 testReceiveMessageSentWhileOffline(org.apache.activemq.transport.mqtt.MQTTTest): Command from server contained an invalid message id: 1 -- 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] [Resolved] (AMQ-4655) We should run JoramJmsTests with amqp+ssl
[ https://issues.apache.org/jira/browse/AMQ-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4655. --- Resolution: Fixed Fix Version/s: 5.9.0 Assignee: Timothy Bish patch applied, thanks. We should run JoramJmsTests with amqp+ssl - Key: AMQ-4655 URL: https://issues.apache.org/jira/browse/AMQ-4655 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Assignee: Timothy Bish Priority: Minor Fix For: 5.9.0 Attachments: AMQ-4655.patch We should run the JoramJmsTests using amqp+ssl. I will attach a patch. -- 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
Re: How do you configure anonymous access for REST API?
Thanks Dejan, that worked. My listener on the consumer side is now able to see messages from my producer app via the REST API, but for some reason the messages are coming across empty (meaning TextMessage.getText() returns null). I created my own HTTP interface, which simply takes the body of the HTTP message and sends it to activemq via JMS. This works perfectly, and allows me to retrieve the text from the HTTP body without any problems. If I simply point my producer to activemq's REST URL, I get the empty messages. Any thoughts? -- View this message in context: http://activemq.2283324.n4.nabble.com/How-do-you-configure-anonymous-access-for-REST-API-tp4669616p4669800.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQ-4097) Broker-to-Broker Reconnect fails wrongly due to duplicate name
[
https://issues.apache.org/jira/browse/AMQ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721132#comment-13721132
]
Vee commented on AMQ-4097:
--
Hi Ron,
I am also facing the same issue in 5.6.0.
you said you solved the problem set the property for socat, i did not find this
property anywhere can you please
tell me where I can set up the socat value to reconnect the client again with
Broker
To solve my problem I added a connection delay into my socat
Thanks,
Vee
Broker-to-Broker Reconnect fails wrongly due to duplicate name
--
Key: AMQ-4097
URL: https://issues.apache.org/jira/browse/AMQ-4097
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.7.0
Environment: A central broker to which a lot (50+) of external
brokers connect with a duplex bridge. A special routing/firewall is used
which can affect timing but not order of TCP packets. This can be simulated
by using socat.
Actually we are using 5.7-SNAPSHOT of 2012-08-31.
Reporter: Ron Koerner
The situation is as follows:
- an external broker A connects
- time passes
- a lot of external brokers disconnect including A
- A reconnects (as well as all the other external brokers)
- wrong message about duplicate name is generated
In the log it looks like this:
{code}
2012-10-08 17:11:19,835 INFO .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#278 and
tcp:///127.0.0.1:54191(cbox-56BU902442) has been established.
[StartLocalBridge: localBroker=vm://c04ptec#278]
...
... a lot more of the following with different ports
2012-10-08 17:37:01,958 WARN .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#278 and tcp:///127.0.0.1:54191 shutdown due
to a remote error: java.io.EOFException [ActiveMQ NIO Worker 193]
... more of these
2012-10-08 17:37:03,438 INFO emq.broker.TransportConnection - Started
responder end of duplex bridge cBox 56BU902442 to cBox
Proxy@ID:P013SPWMK1WN-39320-1349704902319-0:1 [ActiveMQ NIO Worker 215]
...
2012-10-08 17:37:03,922 WARN emq.broker.TransportConnection - Failed to add
Connection ID:c04ptec-51799-1349706422094-242:2, reason:
javax.jms.InvalidClientIDException: Broker: c04ptec - Client: cBox 56BU902442
to cBox Proxy_cbox-56BU902442_inbound_c04ptec already connected from
vm://c04ptec#278 [StartLocalBridge: localBroker=vm://c04ptec#478]
2012-10-08 17:37:03,923 INFO .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#478 and tcp:///127.0.0.1:56529 shutdown due
to a local error: javax.jms.InvalidClientIDException: Broker: c04ptec -
Client: cBox 56BU902442 to cBox Proxy_cbox-56BU902442_inbound_c04ptec already
connected from vm://c04ptec#278 [StartLocalBridge:
localBroker=vm://c04ptec#478]
...
2012-10-08 17:37:04,036 INFO .DemandForwardingBridgeSupport - c04ptec bridge
to cbox-56BU902442 stopped [ActiveMQ Task-182]
...
2012-10-08 17:37:06,540 INFO emq.broker.TransportConnection - Started
responder end of duplex bridge cBox 56BU902442 to cBox
Proxy@ID:P013SPWMK1WN-39320-1349704902319-0:1 [ActiveMQ NIO Worker 207]
...
2012-10-08 17:37:06,548 WARN emq.broker.TransportConnection - Failed to add
Connection ID:c04ptec-51799-1349706422094-292:1, reason:
javax.jms.InvalidClientIDException: Broker: c04ptec - Client: cBox 56BU902442
to cBox Proxy_cbox-56BU902442_inbound_c04ptec already connected from
vm://c04ptec#278 [StartLocalBridge: localBroker=vm://c04ptec#570]
2012-10-08 17:37:06,548 INFO .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#570 and tcp:///127.0.0.1:56576 shutdown due
to a local error: javax.jms.InvalidClientIDException: Broker: c04ptec -
Client: cBox 56BU902442 to cBox Proxy_cbox-56BU902442_inbound_c04ptec already
connected from vm://c04ptec#278 [StartLocalBridge:
localBroker=vm://c04ptec#570]
...
2012-10-08 17:37:06,559 INFO .DemandForwardingBridgeSupport - c04ptec bridge
to cbox-56BU902442 stopped [ActiveMQ Task-204]
...
2012-10-08 17:37:24,417 INFO .DemandForwardingBridgeSupport - c04ptec bridge
to cbox-56BU902442 stopped [ActiveMQ Task-73]
...
2012-10-08 17:37:25,103 INFO emq.broker.TransportConnection - Started
responder end of duplex bridge cBox 56BU902442 to cBox
Proxy@ID:P013SPWMK1WN-39320-1349704902319-0:1 [ActiveMQ NIO Worker 268]
...
2012-10-08 17:37:29,110 INFO .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#594 and
tcp:///127.0.0.1:56656(cbox-56BU902442) has been established.
[StartLocalBridge: localBroker=vm://c04ptec#594]
...
2012-10-08 17:37:59,669 WARN .DemandForwardingBridgeSupport - Network
connection between vm://c04ptec#594 and
tcp:///127.0.0.1:56656(cbox-56BU902442) was interrupted during establishment.
[StartLocalBridge:
[jira] [Created] (AMQ-4656) Pending Queue Counter is incorrect when using durable topics
Timothy Bish created AMQ-4656:
-
Summary: Pending Queue Counter is incorrect when using durable
topics
Key: AMQ-4656
URL: https://issues.apache.org/jira/browse/AMQ-4656
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.8.0
Reporter: Timothy Bish
Fix For: 5.9.0
When using a durable topics the Pending Queue Counter provides an incorrect
value for pending messages.
Steps to recreate
Set up the durable subscriber
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
Stop the subscriber
Send 20 persistent messages
{noformat}
ant producer -Ddurable=true -Durl=tcp://localhost:61616 -Dtopic=true
-Dsubject=MYSUB -Dmax=20
{noformat}
Consume 2 messages
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
View the counter stats.
The result is the following:
{noformat}
Pending Queue Size = 38
Dispatched Queue Size = 0
Dispatched Counter = 20
Enqueue Counter = 20
Dequeue Counter = 2
{noformat}
--
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] [Updated] (AMQ-4656) Pending Queue Counter is incorrect when using durable topics
[
https://issues.apache.org/jira/browse/AMQ-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-4656:
--
Attachment: AMQ4656Test.java
Test case that reproduces.
Pending Queue Counter is incorrect when using durable topics
Key: AMQ-4656
URL: https://issues.apache.org/jira/browse/AMQ-4656
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.8.0
Reporter: Timothy Bish
Fix For: 5.9.0
Attachments: AMQ4656Test.java
When using a durable topics the Pending Queue Counter provides an incorrect
value for pending messages.
Steps to recreate
Set up the durable subscriber
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
Stop the subscriber
Send 20 persistent messages
{noformat}
ant producer -Ddurable=true -Durl=tcp://localhost:61616 -Dtopic=true
-Dsubject=MYSUB -Dmax=20
{noformat}
Consume 2 messages
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
View the counter stats.
The result is the following:
{noformat}
Pending Queue Size = 38
Dispatched Queue Size = 0
Dispatched Counter = 20
Enqueue Counter = 20
Dequeue Counter = 2
{noformat}
--
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
