March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-395) JNDI lookups fail with ClassCastException

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-395?page=all ] Ovidiu Feodorov updated JBMESSAGING-395: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > JNDI lookups fail with ClassCastException > ----------------------------------------- > > Key: JBMESSAGING-395 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-395 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade > Affects Versions: 1.0.1.CR1 > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: Unscheduled > > > Changes introduced by http://jira.jboss.org/jira/browse/JBMESSAGING-390 cause JNDI lookups to fail with ClassCastException > To replicate: run the MDB smoke tests with 4.0.4.GA. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-387) Modify the admin console to work with Messaging while keeping JBossMQ compatibility

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-387?page=all ] Ovidiu Feodorov updated JBMESSAGING-387: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Modify the admin console to work with Messaging while keeping JBossMQ compatibility > ----------------------------------------------------------------------------------- > > Key: JBMESSAGING-387 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-387 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > > JSR77 > Charles -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-373) Different persistance destinations for different JMS destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ] Ovidiu Feodorov updated JBMESSAGING-373: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Different persistance destinations for different JMS destinations > ----------------------------------------------------------------- > > Key: JBMESSAGING-373 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373 > Project: JBoss Messaging > Issue Type: Feature Request > Affects Versions: 1.0.0, 1.0.1.CR1 > Reporter: Milena > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 4 days > Remaining Estimate: 4 days > > We need to store the messages from different queues into a different tables, ot at least to separate them somehow. > This is not possible with the current JBOSS Messaging as I was told. > The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-402) Update the EJB3 example so it work with the latest EJB3 release.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-402?page=all ] Ovidiu Feodorov updated JBMESSAGING-402: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Update the EJB3 example so it work with the latest EJB3 release. > ---------------------------------------------------------------- > > Key: JBMESSAGING-402 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-402 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR2 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently, it works with EJB 3.0 RC5 - PFD , but seems to break for EJB 3.0 RC7 - FD -- 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, 2 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: Unscheduled (was: 1.2.1) > 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 > Fix For: Unscheduled > > 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-242) Investigate requirements for different routing strategies

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-242?page=all ] Ovidiu Feodorov updated JBMESSAGING-242: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Investigate requirements for different routing strategies > --------------------------------------------------------- > > Key: JBMESSAGING-242 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-242 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Investigate whether we need to provide routers with different strategies, a la ReceiversImpl in JBossMQ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-216) Prepare Messaging to replace JBossMQ in the JBoss Mail distribution

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-216?page=all ] Ovidiu Feodorov updated JBMESSAGING-216: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Prepare Messaging to replace JBossMQ in the JBoss Mail distribution > ------------------------------------------------------------------- > > Key: JBMESSAGING-216 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-216 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > Andy's input: > does jboss messaging: > 1. recover from outages with incomplete blobs being written? > 2. avoid making 3 copies of a message in memory? > 3. install cleanly on JBoss 4.0.3SP1/JDK5? > 4. work with Postgresql, MySQL, Hypersonic? > 5. perform better/on par with JBossMQ when used locally (no remote invocation) > 6. Have a reasonably simple method of swapping out its persistence layer ? > #1 is a particularly bad problem (in my view it should be detected and moved to the DMQ with a the blob truncated and a reference to the orgininal record [which should be excluded from mainstream processing by a flag]) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-220) Add the possibility to drop a destination.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-220?page=all ] Ovidiu Feodorov updated JBMESSAGING-220: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Add the possibility to drop a destination. > ------------------------------------------ > > Key: JBMESSAGING-220 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-220 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Destination Manager > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add the possiblity to administratively (and possibly programmatically) drop a destination. > Dropping a destination means that all persistent messages maintained by the destination are discarded. This is not what happens during the current deployment/undeployment of a destiantion, which currently have an activation/de-activation semantics. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Ovidiu Feodorov updated JBMESSAGING-381: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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, 2 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: Unscheduled (was: 1.2.1) > 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: Unscheduled > > 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

19 years, 2 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 March 2007