[JBoss JIRA] Created: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
3:08 p.m.
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1138:
----------------------------------------------
Testcase for this:
Add this on ObjectMessageTest:
public void testVecorOnObjectMessage() throws Exception
{
java.util.Vector vectorOnMessage = new java.util.Vector();
vectorOnMessage.add("world!");
((ObjectMessage)message).setObject(vectorOnMessage);
queueProd.send(message);
ObjectMessage r = (ObjectMessage) queueCons.receive(5000);
assertNotNull(r);
java.util.Vector v2 = (java.util.Vector) r.getObject();
assertEquals(vectorOnMessage.get(0), v2.get(0));
}
A Fix would be to not use containerTypes on ObjectMessages. Object*Stream will be more
optimized to handle these lists and maps anyway.
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:34 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Clebert Suconic updated JBMESSAGING-1138:
-----------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122882
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:42 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1138:
----------------------------------------------
This is fixed on stable branch already...
I'm just waiting the conclusion if I should merge this change on trunk, or wait for
the release to merge the whole release.
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:04 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1138:
--------------------------------------
Ok, I don't think this bug should be fixed that way, otherwise Java serialization will
be used for non Object messages !
Also, I'm wondering why JBAS performance tests are using ObjectMessages?
ObjectMessages use serialization so you don't use them if you want the best
performance. Use the basic message types instead.
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:56 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Clebert Suconic closed JBMESSAGING-1138.
----------------------------------------
Resolution: Done
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1138:
----------------------------------------------
I changed this as discussed on the forums.
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:59 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox reopened JBMESSAGING-1138:
----------------------------------
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: Stable branch
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox updated JBMESSAGING-1138:
---------------------------------
Fix Version/s: 1.4.0.SP2
(was: Stable branch)
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.4.0.SP2
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox closed JBMESSAGING-1138.
--------------------------------
Resolution: Done
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.4.0.SP2
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox reopened JBMESSAGING-1138:
----------------------------------
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.4.0.SP2
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox updated JBMESSAGING-1138:
---------------------------------
Priority: Major (was: Blocker)
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.4.0.SP2
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1138) Setting Vector in an ObjectMessage returns a different Object
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1138?page=all ]
Tim Fox closed JBMESSAGING-1138.
--------------------------------
Resolution: Done
Setting Vector in an ObjectMessage returns a different Object
-------------------------------------------------------------
Key: JBMESSAGING-1138
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1138
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.4.0.SP2
Phillip Thurmond reported me this bug:
If you create an ObjectMessage and set a Vector as the Object, when you receive the
message you will aways get an ArrayList.
Besides this, each element on the ArrayList corresponds to a new writeObject. Case there
are references between those messages the graph references are lost.
I'm setting this as blocker as 4.3 can't be released with this bug, as JBAS
performance tests are failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6261
days inactive
6270
days old
12 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Tim Fox (JIRA)