January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1190) Direct delivery optimisation

by Tim Fox (JIRA)

Direct delivery optimisation ---------------------------- Key: JBMESSAGING-1190 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1190 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta If sender and consumer are in same VM, and ack mode = auto_ack we can do an optimisation which delivers and acks the message on the same thread that sends, so we don't need to persist. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1170) Provider adaptors for UDP, SIP etc

by Tim Fox (JIRA)

Provider adaptors for UDP, SIP etc ---------------------------------- Key: JBMESSAGING-1170 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1170 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 2.0.0 Beta We should consider providing some adaptors for UDP->JMS, SIP->JMS etc -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-838) Test scenario where no failover has occurred on server side...

by Tim Fox (JIRA)

Test scenario where no failover has occurred on server side... -------------------------------------------------------------- Key: JBMESSAGING-838 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-838 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Fix For: 1.2.0.GA When a client thinks the server has failed e.g. the netwrk between client--server temporarily fails but the network between server--server is ok, the server will return -1 to say no failover is occurring or times out then the client will retry the orginal node after a pause. The pause needs to be made configurable and a test devised to test this situation -- 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

17 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1081) Allow configuration of distribution policy for queues with multiple consumers

by Julian Scheid (JIRA)

Allow configuration of distribution policy for queues with multiple consumers ----------------------------------------------------------------------------- Key: JBMESSAGING-1081 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1081 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.0 CR3 Reporter: Julian Scheid Assigned To: Tim Fox Priority: Minor The distribution policy for queues is currently hardwired to RoundRobinDistributor (in MessagingQueue.java) like this: localDistributor = new DistributorWrapper(new RoundRobinDistributor()); remoteDistributor = new DistributorWrapper(new RoundRobinDistributor()); distributor = new ClusterRoundRobinDistributor(localDistributor, remoteDistributor); This is a good default for when multiple clients are consuming a queue for purposes of load balancing. However, when there are multiple consumers for purposes of fail-over it can be desirable to use the FirstReceiverDistributor policy instead so that a second consumer only gets messages when the first consumer fails. (I am aware that this is simplifying matters a bit, FirstReceiverDistributor makes no such guarantees.) This policy can currently only be changed by patching the source code and recompiling. It would be great if it would be possible to configure the distribution policy in a configuration file instead, ideally on a per-queue basis in destinations-service.xml. This would ideally allow specifying arbitrary class names so that it's possible to install custom distributors. All of this would obviously be useful for topics as well once JBMESSAGING-377 is implemented. -- 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

17 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1049) Exceptions in logs after clustering test run

by Tim Fox (JIRA)

Exceptions in logs after clustering test run -------------------------------------------- Key: JBMESSAGING-1049 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1049 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.GA After running clustering tests, several exceptions are found in the logs. These seem innocuous since the test suite passes but we should investigate. -- 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

17 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-963) Find a better place to put config files

by Tim Fox (JIRA)

Find a better place to put config files --------------------------------------- Key: JBMESSAGING-963 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-963 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.SP2 Currently config files in the source tree are store in source/etc/server/default/deploy/... This seems unintuitive and somewhat clunky. Find a better more intuitive place to put them and update scripts accordingly. -- 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

17 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-958) Ability to replay queues

by Tim Fox (JIRA)

Ability to replay queues ------------------------ Key: JBMESSAGING-958 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-958 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 It would be good to have an ability to "replay" queues. I.e. when messages are acked, they don't necessarily get removed from the queue, instead a pointer on the queue just moves to the next element. This would allow recovery scenarios where the queue can be replayed, by resetting the pointer and redelivering messages. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-742) Message.getJMSDestination could be null on redeployment of a queue

by Clebert Suconic (JIRA)

Message.getJMSDestination could be null on redeployment of a queue ------------------------------------------------------------------ Key: JBMESSAGING-742 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-742 Project: JBoss Messaging Issue Type: Support Patch Affects Versions: 1.0.1.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.0.2.CR1, 1.0.2.GA, 1.0.1.SP2 -- 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

17 years, 9 months

3
27
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1219) Messages are not redelivered after reconnection of message bridge

by Tyronne Wickramarathne (JIRA)

Messages are not redelivered after reconnection of message bridge ----------------------------------------------------------------- Key: JBMESSAGING-1219 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1219 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.SP3 Environment: JBoss-EAP-4.2_CP1 , JBM-1.4.0-SP3, RHEL5 Reporter: Tyronne Wickramarathne Assigned To: Tim Fox Fix For: Stable branch JBM Bridge reconnection happens successfully but messages are not delivered to the destination via the bridge. however this problem doesn't occur on Windows environment. modify the attached jms-ds.xml file with your remote machine's IP address, for the remote provider. SourceProviderLoader is the remote machine, and our TargetProviderLoader is the local machine. deploy the test-bridge-service.xml file on your local machine. it has two bridges defined : TestBridgeA remote queue/A -> local queue/C TestBridgeB remote queue/B -> local queue/D Add 10 messages to both queue A and queue B on the remote machine (we used a JSP page on the remote machine to do that) in order to establish everything is working. Add 20000 (or more) messages to queue A on the remote machine. wait until some of the messages have been delivered to queue C on the local machine. disconnect the local machine from the network by pulling the network cable. wait a couple of minutes. re-connect the local machine to the network. after a few seconds the message delivery should start again. wait for all of the message to be delivered. now - try sending 500 messages to queue/B on the remote machine those 500 messages will never be delivered ! -- 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

17 years, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1222) Remote-bisocket JMS test fail on Mac OSX

by Aaron Walker (JIRA)

Remote-bisocket JMS test fail on Mac OSX ---------------------------------------- Key: JBMESSAGING-1222 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1222 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Affects Versions: 1.4.0.SP3 Environment: Mac OSX 10.4.11 Apple JVM 1.5.0_13 Mac OSX 10.5.1 Apple JVM 1.5.0_13 Reporter: Aaron Walker Assigned To: Aaron Walker Priority: Minor I get a NullPointerException from the following in the ServerContainer.java and LocalTestServer.java when running the remote tests ServerContainer.java ...... private void readConfigurationFile() throws Exception { InputStream cs = getClass().getClassLoader().getResourceAsStream(CONFIGURATION_FILE_NAME); ..... and LocalTestServer.java ..... public void poisonTheServer(int type) throws Exception { URL url = this.getClass().getClassLoader().getResource("poison.xml"); return null when running the remote tests -- 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

17 years, 9 months

3
8
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 January 2008