April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6940) Add support for static connectors

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6940?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned AS7-6940: --------------------------------------- Assignee: Bartosz Baranowski (was: Harald Pehl) > Add support for static connectors > --------------------------------- > > Key: AS7-6940 > URL: https://issues.jboss.org/browse/AS7-6940 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > There is no way to declare cluster connection in messaging subsystem as "static" > http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html_single/inde... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6940) Add support for static connectors

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created AS7-6940: --------------------------------------- Summary: Add support for static connectors Key: AS7-6940 URL: https://issues.jboss.org/browse/AS7-6940 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Bartosz Baranowski Assignee: Harald Pehl Priority: Minor Fix For: 8.0.0.Alpha1 There is no way to declare cluster connection in messaging subsystem as "static" http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html_single/inde... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned AS7-6939: --------------------------------------- Assignee: Bartosz Baranowski > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] Harald Pehl updated AS7-6939: ----------------------------- Component/s: Console > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6939: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=908720 > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created AS7-6939: --------------------------------------- Summary: Remove direct connections parameter Key: AS7-6939 URL: https://issues.jboss.org/browse/AS7-6939 Project: Application Server 7 Issue Type: Feature Request Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.3.Final (EAP) Reporter: Bartosz Baranowski Priority: Minor Fix For: 8.0.0.Alpha1 The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6938) Add and deploy does not fail if runtimeName already exists

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6938?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6938: -------------------------------- Component/s: OSGi > Add and deploy does not fail if runtimeName already exists > ---------------------------------------------------------- > > Key: AS7-6938 > URL: https://issues.jboss.org/browse/AS7-6938 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > The ServerDeploymentHelper has this code > {code} > public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { > ServerDeploymentActionResult actionResult; > try { > DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); > builder = builder.add(runtimeName, input).andDeploy(); > DeploymentPlan plan = builder.build(); > DeploymentAction action = builder.getLastAction(); > Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); > ServerDeploymentPlanResult planResult = future.get(); > actionResult = planResult.getDeploymentActionResult(action.getId()); > } catch (Exception ex) { > throw new ServerDeploymentException(ex); > } > if (actionResult.getDeploymentException() != null) > throw new ServerDeploymentException(actionResult); > return runtimeName; > } > {code} > which does not fail if the runtimeName already exists > There is a debug log like this > {code} > 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]" > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6938) Add and deploy does not fail if runtimeName already exists

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6938?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6938: -------------------------------- Description: The ServerDeploymentHelper has this code {code} public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { ServerDeploymentActionResult actionResult; try { DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); builder = builder.add(runtimeName, input).andDeploy(); DeploymentPlan plan = builder.build(); DeploymentAction action = builder.getLastAction(); Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); ServerDeploymentPlanResult planResult = future.get(); actionResult = planResult.getDeploymentActionResult(action.getId()); } catch (Exception ex) { throw new ServerDeploymentException(ex); } if (actionResult.getDeploymentException() != null) throw new ServerDeploymentException(actionResult); return runtimeName; } {code} which does not fail if the runtimeName already exists There is a debug log like this {code} 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]" {code} was: The ServerDeploymentHelper has this code {code} public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { ServerDeploymentActionResult actionResult; try { DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); builder = builder.add(runtimeName, input).andDeploy(); DeploymentPlan plan = builder.build(); DeploymentAction action = builder.getLastAction(); Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); ServerDeploymentPlanResult planResult = future.get(); actionResult = planResult.getDeploymentActionResult(action.getId()); } catch (Exception ex) { throw new ServerDeploymentException(ex); } if (actionResult.getDeploymentException() != null) throw new ServerDeploymentException(actionResult); return runtimeName; } {code} which does not fail if the runtimeName already exists > Add and deploy does not fail if runtimeName already exists > ---------------------------------------------------------- > > Key: AS7-6938 > URL: https://issues.jboss.org/browse/AS7-6938 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Jason Greene > Fix For: 8.0.0.Alpha1 > > > The ServerDeploymentHelper has this code > {code} > public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { > ServerDeploymentActionResult actionResult; > try { > DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); > builder = builder.add(runtimeName, input).andDeploy(); > DeploymentPlan plan = builder.build(); > DeploymentAction action = builder.getLastAction(); > Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); > ServerDeploymentPlanResult planResult = future.get(); > actionResult = planResult.getDeploymentActionResult(action.getId()); > } catch (Exception ex) { > throw new ServerDeploymentException(ex); > } > if (actionResult.getDeploymentException() != null) > throw new ServerDeploymentException(actionResult); > return runtimeName; > } > {code} > which does not fail if the runtimeName already exists > There is a debug log like this > {code} > 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]" > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6938) Add and deploy does not fail if runtimeName already exists

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6938?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned AS7-6938: ----------------------------------- Assignee: Brian Stansberry (was: Jason Greene) > Add and deploy does not fail if runtimeName already exists > ---------------------------------------------------------- > > Key: AS7-6938 > URL: https://issues.jboss.org/browse/AS7-6938 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > The ServerDeploymentHelper has this code > {code} > public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { > ServerDeploymentActionResult actionResult; > try { > DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); > builder = builder.add(runtimeName, input).andDeploy(); > DeploymentPlan plan = builder.build(); > DeploymentAction action = builder.getLastAction(); > Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); > ServerDeploymentPlanResult planResult = future.get(); > actionResult = planResult.getDeploymentActionResult(action.getId()); > } catch (Exception ex) { > throw new ServerDeploymentException(ex); > } > if (actionResult.getDeploymentException() != null) > throw new ServerDeploymentException(actionResult); > return runtimeName; > } > {code} > which does not fail if the runtimeName already exists > There is a debug log like this > {code} > 11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1) JBAS014616: Operation ("add") failed - address: ([("deployment" => "v200.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"v200.jar\")]" > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6938) Add and deploy does not fail if runtimeName already exists

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6938: ----------------------------------- Summary: Add and deploy does not fail if runtimeName already exists Key: AS7-6938 URL: https://issues.jboss.org/browse/AS7-6938 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 8.0.0.Alpha1 The ServerDeploymentHelper has this code {code} public String deploy(String runtimeName, InputStream input) throws ServerDeploymentException { ServerDeploymentActionResult actionResult; try { DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan(); builder = builder.add(runtimeName, input).andDeploy(); DeploymentPlan plan = builder.build(); DeploymentAction action = builder.getLastAction(); Future<ServerDeploymentPlanResult> future = deploymentManager.execute(plan); ServerDeploymentPlanResult planResult = future.get(); actionResult = planResult.getDeploymentActionResult(action.getId()); } catch (Exception ex) { throw new ServerDeploymentException(ex); } if (actionResult.getDeploymentException() != null) throw new ServerDeploymentException(actionResult); return runtimeName; } {code} which does not fail if the runtimeName already exists -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013