August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-365) Cannot send messages to a destination configured with a security role other than "guest", using UsersRolesLoginModule

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-365?page=all ] Ovidiu Feodorov updated JBMESSAGING-365: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Cannot send messages to a destination configured with a security role other than "guest", using UsersRolesLoginModule > --------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-365 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-365 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Security > Affects Versions: 1.0.0 > Environment: Windows 2000, JDK 1.4.1_05 > Reporter: Oliver Hernandez > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > A JMS client errors out with the following when a queue is configured with a security role other than "guest": > 2006-04-28 14:33:42,313 WARN [outbound] An exception occurred on the server side when making remote invocation. The exception returned from server does not include a stack trace. Original server side exception message is User jms is NOT authenticated > javax.jms.JMSSecurityException: User jms is NOT authenticated > Messaging is configured to use UsersRolesLoginModule. See forum post for details on reproducing the problem. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-352) @Consumer example

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-352?page=all ] Ovidiu Feodorov updated JBMESSAGING-352: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > @Consumer example > ----------------- > > Key: JBMESSAGING-352 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-352 > Project: JBoss Messaging > Issue Type: Sub-task > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add a Consumer example, as described in http://docs.jboss.org/ejb3/app-server/tutorial/consumer/consumer.html -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-357) Update the Messaging Core documentation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-357?page=all ] Ovidiu Feodorov updated JBMESSAGING-357: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.2) > Update the Messaging Core documentation > --------------------------------------- > > Key: JBMESSAGING-357 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-357 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-266) Remove Routable

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-266?page=all ] Ovidiu Feodorov updated JBMESSAGING-266: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Remove Routable > --------------- > > Key: JBMESSAGING-266 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-266 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Remove Routable interface. > Have interface MessageReference which represents things that can be routed. > Have interface Payload (TBD) which every MessageReference has, this contains data that is not necessarty for routing. > We would then have a subclass of Payload called JMSPayload which contains all the jms stuff,not needed for routing. > A jms message would extend Message Reference and contain fields such as delivery count. > The jms message would contain a Payload interface and delegate for that for other attributes -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ] Ovidiu Feodorov updated JBMESSAGING-287: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.2) > RemotingTest.testConnectionListener() invalid > --------------------------------------------- > > Key: JBMESSAGING-287 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid. > After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove it. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-222) Run "findbugs" on the code base

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-222?page=all ] Ovidiu Feodorov updated JBMESSAGING-222: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.2) > Run "findbugs" on the code base > ------------------------------- > > Key: JBMESSAGING-222 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-222 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: rajdeep dua > Priority: Minor > Fix For: 1.2.1 > > Attachments: build.xml, findbugs-0.9.5.zip, findbugs.patch, findbugs.patch, report-fb.xml > > > Run "findbugs" or similar regularily on the code base. Integrate it in the continous build process. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-275) Move Selector processing IN the Channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ] Ovidiu Feodorov updated JBMESSAGING-275: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.2) > Move Selector processing IN the Channel > --------------------------------------- > > Key: JBMESSAGING-275 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector. > This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers. > A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-140) Move responsibility for management of delivery list from receiver into channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-140?page=all ] Ovidiu Feodorov updated JBMESSAGING-140: ---------------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.0.3) > Move responsibility for management of delivery list from receiver into channel > ------------------------------------------------------------------------------ > > Key: JBMESSAGING-140 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-140 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.0.Beta1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently each receiver has the responsibility for managing it's list of deliveries. This is to avoid a race condition whereby the message can be acked before the call to handle has returned. > This is a high burden of responsibility for the receiver and results in a lot of unnecessary code in the receiver implementation, plus an extra hashmap lookup > We should consider whether we can give the responsibiltty to the channel. > We could still acknowledge and cancel throught the delivery object, by creating one when required and calling cancel/acknowledge on it. > the instance of delivery won't contain a message reference but just a message id. then inside delivery.cancel()/acknowledge(), it calls > channel.cancel(this) and the channel is smart enought to lookup the delivery/reference as required. > This won't require ANY changes to the receiver/channel interface and will allow us to get rid of the delivery list -- 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

18 years, 5 months

1
0
0 / 0

[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: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.2) > 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: Tim Fox > Fix For: 1.2.0.Alpha1 > > 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-288) Add POJO messaging examples

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-288?page=all ] Ovidiu Feodorov updated JBMESSAGING-288: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.3) > Add POJO messaging examples > --------------------------- > > Key: JBMESSAGING-288 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-288 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.2.1 > > > Add an example that shows how to write and run a POJO MDB to docs/examples and ship it with the distribution. -- 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

18 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006