April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-453) Change signature of Channel.down() to return Object, rename downcall() to down()

by Bela Ban (JIRA)

Change signature of Channel.down() to return Object, rename downcall() to down() -------------------------------------------------------------------------------- Key: JGRP-453 URL: http://jira.jboss.com/jira/browse/JGRP-453 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We had to make Channel.down() return void, otherwise JGroups would not have been backwards compatible with JBoss 4.0.5 -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Deleted: (JGRP-927) FLUSH: pass a result code with unblock

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-927?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-927: -------------------------- > FLUSH: pass a result code with unblock > -------------------------------------- > > Key: JGRP-927 > URL: https://issues.jboss.org/browse/JGRP-927 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > > So we know whether an unblock was the result of a crash or a normal termination -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9147) Deployment-related OperationHandler improvements

by Brian Stansberry (JIRA)

Deployment-related OperationHandler improvements ------------------------------------------------ Key: JBAS-9147 URL: https://issues.jboss.org/browse/JBAS-9147 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta3 Primary goal is to eliminate the need for a separate "deploy" operation following an "add" for a deployment resource. Plus minor cleanups. In all cases, the output of the DescriptionProvider associated with the handler must be updated to match changes to the handler. org.jboss.as.server.deployment: DeploymentAddHandler a) After updating the model, if context.getRuntimeContext() != null and subModel.get(ENABLED).asBoolean() == true, deploy the deployment. See DeploymentDeployHandler for how to deploy b) Update StandaloneXml (in controller module) so it doesn't create a "deploy" operation at boot, since "add" will now deploy c) lesser priority: handle other ways of providing the deployment content, depending on what param users provided: -- HASH (i.e. content already uploaded) -- this is already implemented -- INPUT_STREAM_INDEX (i.e. stream is attached to OperationContext) -- this is already implemented -- BYTES (param value is a byte[] of content) -- see DeploymentUploadBytesHandler for how to store the content in the repo -- URL (server is to read content from URL) -- see DeploymentUploadURLHandler for how to store the content in the repo DeploymentFullReplaceHandler lesser priority: handle other ways of providing the deployment content, depending on what param users provided Same details as for DeploymentAddHandler DeploymentRemoveHandler remove the existing if (model.get(ENABLED).asBoolean()) {...} branch; the code should always execute the current "else {...}" branch org.jboss.as.domain.controller.operations.deployment: DeploymentAddHandler lesser priority: handle other ways of providing the deployment content, depending on what param users provided Same details as for org.jboss.as.server.deployment.DeploymentAddHandler DeploymentFullReplaceHandler lesser priority: handle other ways of providing the deployment content, depending on what param users provided Same details as for org.jboss.as.server.deployment.DeploymentAddHandler -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-612) ChannelFactory should have only channel create methods

by Vladimir Blagojevic (JIRA)

ChannelFactory should have only channel create methods ------------------------------------------------------ Key: JGRP-612 URL: http://jira.jboss.com/jira/browse/JGRP-612 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.6, 2.7, 2.x Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 3.0 ChannelFactory should not have setMultiplexerConfig methods but rather only create channel methods. Multiplexer configuration can be initialized through implementors constructor. -- 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

15 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1185) JChannel: remove mq

by Bela Ban (JIRA)

JChannel: remove mq ------------------- Key: JGRP-1185 URL: https://jira.jboss.org/jira/browse/JGRP-1185 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Remove message queue, as it is not needed anymore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1850) Message Consumer receive(timeout) may wait there even after timeout has expired

by Yong Hao Gao (JIRA)

Message Consumer receive(timeout) may wait there even after timeout has expired ------------------------------------------------------------------------------- Key: JBMESSAGING-1850 URL: https://issues.jboss.org/browse/JBMESSAGING-1850 Project: JBoss Messaging Issue Type: Bug Components: JMS Client Manager Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP12, 1.4.8.GA If a client uses receive messages using receive(timeout) where timeout > 0 and the ack mode is auto_ack, when a message arrived at the client and the acknowledge takes a long time (either network problem or the server is busy like retrying a db connection), the receive(timeout) may not return after timeout has expired. That doesn't conform to the JMS API spec. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-9262) Turn the upload content operation name into something meaningful

by Heiko Braun (JIRA)

Turn the upload content operation name into something meaningful ---------------------------------------------------------------- Key: JBAS-9262 URL: https://issues.jboss.org/browse/JBAS-9262 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Braun Fix For: 7.0.0.Beta4 Currently the operation name is "upload-deployment-url" (Taken from DomainHttpServer.java) final ModelNode dmr = new ModelNode(); dmr.get("operation").set("upload-deployment-url"); dmr.get("address").setEmptyList(); dmr.get("url").set(tempUploadFile.toURI().toURL().toString()); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1108) Replace JChannelFactory with one based on the JBoss AS impl

by Brian Stansberry (JIRA)

Replace JChannelFactory with one based on the JBoss AS impl ----------------------------------------------------------- Key: JGRP-1108 URL: https://jira.jboss.org/jira/browse/JGRP-1108 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0 As part of JGRP-612, modify JChannelFactory to work more like the JBAS JChannelFactory -- ensuring channels have a singleton name etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-743) Remove Multiplexer, MuxChannel

by Bela Ban (JIRA)

Remove Multiplexer, MuxChannel ------------------------------ Key: JGRP-743 URL: http://jira.jboss.com/jira/browse/JGRP-743 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 Replaced by shared transport -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-994) JChannel: remove AUTO_RECONNECT and AUTO_GETSTATE options

by Bela Ban (JIRA)

JChannel: remove AUTO_RECONNECT and AUTO_GETSTATE options --------------------------------------------------------- Key: JGRP-994 URL: https://jira.jboss.org/jira/browse/JGRP-994 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
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 April 2011