November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-837) Static Discovery/Route Deployer

by David Lloyd (JIRA)

Static Discovery/Route Deployer ------------------------------- Key: JBREM-837 URL: http://jira.jboss.com/jira/browse/JBREM-837 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M3 Mechanism to allow static Discoveries to be deployed/undeployed for a given Endpoint. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-182) Integrate VFS ClassLoader into new deployers and jboss-head

by Adrian Brock (JIRA)

Integrate VFS ClassLoader into new deployers and jboss-head ----------------------------------------------------------- Key: JBMICROCONT-182 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-182 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Integrate VFSClassLoader into JBoss Head, including OSGi dependencies/versioning -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3928) Replace jmx-invoker-service.xml with jmx-remoting.sar

by Scott M Stark (JIRA)

Replace jmx-invoker-service.xml with jmx-remoting.sar ----------------------------------------------------- Key: JBAS-3928 URL: http://jira.jboss.com/jira/browse/JBAS-3928 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Remoting Reporter: Scott M Stark Assigned To: Scott M Stark We need to complete the org.jboss.mx.remoting.service.JMXConnectorServerService jmx invoker to be at least as complete as the RMIAdaptor so we can replace the jmx-invoker-service.xml with the jmx-remoting.sar. -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1132) Use blocking mode for callbacks with Remoting http transport

by Ron Sigal (JIRA)

Use blocking mode for callbacks with Remoting http transport ------------------------------------------------------------ Key: JBMESSAGING-1132 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1132 Project: JBoss Messaging Issue Type: Task Reporter: Ron Sigal Assigned To: Tim Fox Fix For: 2.0.0 Alpha In response to JBREM-641 "re-implement the callback polling for http transport to reduce latency", an alternative way of handling callbacks was introduced in Remoting. In particular, instead of the client periodically polling for callbacks, in "blocking" mode, the request to download callbacks blocks on the server until either (1) a callback is available, or (2) the timeout period has expired. The advantage is reduced latency in retrieving callbacks. In fact, some JBM http transport stress tests which fail in "nonblocking" mode now pass in "blocking" mode. 1. The default mode is "nonblocking", so it is necessary to explicitly configure "blocking" mode. One way to do so is to add the appropriate parameter to the metadata map when installing the callback listener. E.g., add the following line to org.jboss.jms.client.remoting.JMSRemotingConnection.createCallbackMetadata(): if (reportPollingStatistics != null) { metadata.put(CallbackPoller.REPORT_STATISTICS, reportPollingStatistics); } metadata.put(ServerInvoker.BLOCKING_MODE, ServerInvoker.BLOCKING); // <<=== add this line metadata.put(ServerInvoker.BLOCKING_TIMEOUT, "7777"); // optional: default is 5000 milliseconds 2. The line <attribute name="callbackPollPeriod" isParam="true">102</attribute> may be removed from remoting-http-service.xml, since it's no longer relevant. -- 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

16 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1048) Test DB2 config against Hudson

by Tim Fox (JIRA)

Test DB2 config against Hudson ------------------------------ Key: JBMESSAGING-1048 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1048 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 -- 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

16 years, 2 months

3
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1122) *MessageCountersAsHTML LastAdd uses wrong value

by Aslak (JIRA)

*MessageCountersAsHTML LastAdd uses wrong value ----------------------------------------------- Key: JBMESSAGING-1122 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Reporter: Aslak Assigned To: Tim Fox ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value. -- 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

16 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-439) Abiltity to change priority of messages in a queue/durable sub

by Tim Fox (JIRA)

Abiltity to change priority of messages in a queue/durable sub -------------------------------------------------------------- Key: JBMESSAGING-439 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-439 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.0.2 A "nice to have" would be to allow the priority of messages in a destination to be changed by an administrator - this should be available via the normal management interfaces. -- 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

16 years, 2 months

5
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-732) Improve message counter functionality

by Tim Fox (JIRA)

Improve message counter functionality ------------------------------------- Key: JBMESSAGING-732 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-732 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.2.1 MessageCounter functionality can be improved by returning counters and history as XML as well as HTML, or in some other "machine friendly" format. Also the history should be made "rolling", so only a moving window of data is retained to prevent a large buildup -- 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

16 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-4814) Refactor the conf/jboss-service.xml services

by Scott M Stark (JIRA)

Refactor the conf/jboss-service.xml services -------------------------------------------- Key: JBAS-4814 URL: http://jira.jboss.com/jira/browse/JBAS-4814 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR1 The legacy/conf/jboss-service.xml needs to be stripped down, possibly removed as there are too many non-core services in this currently. -- 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

16 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-856) Use Buddy Replication for clustered SFSBs

by Brian Stansberry (JIRA)

Use Buddy Replication for clustered SFSBs ----------------------------------------- Key: EJBTHREE-856 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC11 - FD Optimize the replicated SFSB cache for use with Buddy Replication. Basically means checking cache calls to ensure unwanted data gravitations do not occur. -- 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

16 years, 2 months

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007