March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-208) Example of custom client-side/server-side interceptors

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-208?page=all ] Ovidiu Feodorov updated JBMESSAGING-208: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Example of custom client-side/server-side interceptors > ------------------------------------------------------ > > Key: JBMESSAGING-208 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-208 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Provide an example of writing and configuring a custom client-side and server-side AOP interceptor. > Add the example to docs/examples so it can be used as an integration test. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-153) JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred)

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ] Ovidiu Feodorov updated JBMESSAGING-153: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred) > --------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-153 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.0.0 alpha PR3 > Reporter: Karl de Boer > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications. -- 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, 1 month

1
0
0 / 0

[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: Unscheduled (was: 1.2.1) > 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: Unscheduled > > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-134) Implement memory sensitive channels

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-134?page=all ] Ovidiu Feodorov updated JBMESSAGING-134: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Implement memory sensitive channels > ----------------------------------- > > Key: JBMESSAGING-134 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-134 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core Persistence > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Extend the message caching to spill messages on to disk when memory is tight, a la JBossMQ. > Probably re-use much of JBossMQ implementation here. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-377) Competing consumer on subscriptions

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ] Ovidiu Feodorov updated JBMESSAGING-377: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Competing consumer on subscriptions > ----------------------------------- > > Key: JBMESSAGING-377 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Ovidiu Feodorov updated JBMESSAGING-412: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-87) Light-weight JMS 1.1 / JGroups package

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-87?page=all ] Ovidiu Feodorov updated JBMESSAGING-87: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Light-weight JMS 1.1 / JGroups package > -------------------------------------- > > Key: JBMESSAGING-87 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-87 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Bela Ban > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > > Motivation: people want to use JGroups, but need to program against a standard API, like JMS 1.1. > Create a distribution which includes only the relevant parts of the JMS 1.1 implementation that runs on top of JGroups (the 'Serverless JMS' part, not the client/server part). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Ovidiu Feodorov updated JBMESSAGING-375: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-138) Adapt performance test harness to be automated by JRUnit

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-138?page=all ] Ovidiu Feodorov updated JBMESSAGING-138: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Adapt performance test harness to be automated by JRUnit > -------------------------------------------------------- > > Key: JBMESSAGING-138 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-138 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > > Adapt jms perf testing framework with a JRUnit wrapper so it can automated as part of QA run, and data can be output to perf data database -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-340) Static selector queues

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-340?page=all ] Ovidiu Feodorov updated JBMESSAGING-340: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Static selector queues > ---------------------- > > Key: JBMESSAGING-340 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-340 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > We should consider adding functionality to allow a selector to be associated with a queue in the deployment descriptor. The queue then does not accept any messages that do not match the selector. This is in addition to the standard jms functionality of specifying selectors on message consumers. > It should give better performance in those cases where it is possible to know a selector to apply to an entire queue in advance. -- 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, 1 month

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