September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-361) WireFormatTest.testNullResponse(), testDeactivateResponse() fragments invalid

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-361?page=all ] Ovidiu Feodorov updated JBMESSAGING-361: ---------------------------------------- Assignee: Clebert Suconic (was: Ovidiu Feodorov) > WireFormatTest.testNullResponse(), testDeactivateResponse() fragments invalid > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-361 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-361 > Project: JBoss Messaging > Issue Type: Sub-task > Components: JMS Facade > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: 1.0.1.CR5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Switching to jboss-serialization 1.0.0.CR7 uncovered what apparently seems to be an invalid test section in WireFormatTest > public void testNullResponse() throws Exception > { > MessagingMarshallable mm = new MessagingMarshallable((byte)77, null); > InvocationResponse resp = new InvocationResponse(null, mm, false, null); > ByteArrayOutputStream bos = new ByteArrayOutputStream(); > JBossObjectOutputStream oos = new JBossObjectOutputStream(bos); > > wf.write(resp, oos); > oos.flush(); > > ByteArrayInputStream bis = new ByteArrayInputStream(bos.toByteArray()); > DataInputStream dis = new DataInputStream(bis); > > // First byte should be version > assertEquals(77, dis.readByte()); > ........... > } > It doesn't make sense to me to write stuff to a JBossObjectOutputStream and then try to read the serialized content using a DataInputStream, and yet this is what this test section does. JBoss Serialization doesn't guarantee this in its public contract. > Excerpt form a conversation with Clebert: > flanker707: Does JBossSerialization guarantee that something written with on a JBossObjectOutuptStream can be read with DataInputStream? > Clebert Suconic: no... I didn't mean to > flanker707: is this in the public contract? > Clebert Suconic: If you use the same thing with ObjectInputStream.. you would have the same problem > testNullResponse(), testDeactivateResponse() sections commented out until clarified. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-431) Socket transports should use configurable port

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-431?page=all ] Ovidiu Feodorov updated JBMESSAGING-431: ---------------------------------------- Assignee: Clebert Suconic (was: Ron Sigal) > Socket transports should use configurable port > ---------------------------------------------- > > Key: JBMESSAGING-431 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-431 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR4 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Fix For: 1.0.1.CR5 > > > Currently, for the socket and ssl transports, callbackservers will be opened on the next available port obtained. > Very occasionally this can fail since some other service uses the port before the callback server can. > Instead, the user should be able to configure a port used by the callbackserver to listen. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1051) NPE if no session information exists when trying to update the user cookies

by Chris Laprun (JIRA)

NPE if no session information exists when trying to update the user cookies --------------------------------------------------------------------------- Key: JBPORTAL-1051 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1051 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final, 2.6.Alpha1 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final, 2.6.Alpha1 -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-528) Update user manual to include details on configuring remoting's serverBindAddress

by Ovidiu Feodorov (JIRA)

Update user manual to include details on configuring remoting's serverBindAddress --------------------------------------------------------------------------------- Key: JBMESSAGING-528 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-528 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.0.1.CR5 -- 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

19 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-682) create test for JBossTS

by William DeCoste (JIRA)

create test for JBossTS ----------------------- Key: EJBTHREE-682 URL: http://jira.jboss.com/jira/browse/EJBTHREE-682 Project: EJB 3.0 Issue Type: Task Reporter: William DeCoste Assigned To: William DeCoste -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-540) A testsuite testing client and server on different IPs

by Clebert Suconic (JIRA)

A testsuite testing client and server on different IPs ------------------------------------------------------ Key: JBMESSAGING-540 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-540 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 The current testsuite tests both client and server on the same network. We should have a way to test client and server using different IPs, and possibility different network cards. -- 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

19 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-546) org.jboss.test.messaging.jms.DurableSubscriberTest times out

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.DurableSubscriberTest times out ------------------------------------------------------------ Key: JBMESSAGING-546 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-546 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.0.1.CR5 -- 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

19 years, 10 months

1
10
0 / 0

[JBoss JIRA] Created: (JBREM-596) Lease doesn't work if client has two connections opened when using callbacks

by Clebert Suconic (JIRA)

Lease doesn't work if client has two connections opened when using callbacks ---------------------------------------------------------------------------- Key: JBREM-596 URL: http://jira.jboss.com/jira/browse/JBREM-596 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: callbacks Reporter: Clebert Suconic Assigned To: Tom Elrod If you have two connections, one of them is using CallBack the Lease is just stopped. I don't know how to reproduce this with a pure JBossRemoting testcase, but there is a testcase @ JBossMEssaging (Branch_1_0) which reproduces this really easily. Download JBossMessaging SVN @ Branch_1, and execute ant crash-tests within /testsuite. You can look at cruisecontrol results at this URL: http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220... and http://cruisecontrol.jboss.com/cc/artifacts/jms-1.0-testsuite/20060907220... I have added a couple of messages on JBossRemoting code and I could see that with the code bellow, the lease is stopped. During addCallBAck the client copy calls disconnect and the lease thread never comes back. Here is the code: public void testSimplestDurableSubscription() throws Exception { ConnectionFactory cf = (ConnectionFactory)ic.lookup("ConnectionFactory"); Topic topic = (Topic)ic.lookup("/topic/TopicCrash"); Connection conn = cf.createConnection(); conn.setClientID("client1"); conn.start(); Connection conn2 = cf.createConnection(); conn2.setClientID("client2"); conn2.start(); Session s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE); Session s2 = conn2.createSession(true, Session.AUTO_ACKNOWLEDGE); MessageProducer prod = s.createProducer(topic); prod.setDeliveryMode(DeliveryMode.PERSISTENT); MessageConsumer durable = s.createDurableSubscriber(topic, "subs1"); MessageConsumer durable2 = s2.createDurableSubscriber(topic, "subs2"); //conn2.close(); -- do not remote this comment. It was meant to not close the connection for (int i=0;i<10;i++) { prod.send(s.createTextMessage("k"+i)); } s.commit(); conn.close(); conn = cf.createConnection(); conn.setClientID("client1"); conn.start(); s = conn.createSession(true, Session.AUTO_ACKNOWLEDGE); durable = s.createDurableSubscriber(topic, "subs1"); for (int i=0;i<2;i++) { TextMessage tm = (TextMessage)durable.receive(1000); assertNotNull(tm); s.commit(); System.out.println(tm.getText()); assertEquals("k" + i, tm.getText()); } //conn.close();-- do not remote this comment. It was meant to not close the connection //System.exit(0); -- this is not needed as there is not tearDown, the client VM will simply be finished the same way an exit would do, and this is better since it will keep proper JUNIT report outputs } -- 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

19 years, 10 months

2
13
0 / 0

[JBoss JIRA] Resolved: (JBFORUMS-31) Migration to Portal 2.4

by Ryszard Kozmik (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-31?page=all ] Ryszard Kozmik resolved JBFORUMS-31. ------------------------------------ Resolution: Done > Migration to Portal 2.4 > ----------------------- > > Key: JBFORUMS-31 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-31 > Project: JBoss Forums > Issue Type: Task > Reporter: Ryszard Kozmik > Assigned To: Ryszard Kozmik > Fix For: 1.0.0 Alpha > > Time Spent: 1 day, 6 hours, 10 minutes > > Because of that JBForums have many dependencies on JBPortal and it is still changing there is a need to keep up to those changes. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Attachment: jboss-aop.jar jboss-aop-jdk50.jar These files contain what will be in JBoss AOP 2.0.0.alpha1 > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha1 > > Attachments: jboss-aop-jdk50.jar, jboss-aop.jar > > -- 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

19 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006