October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBASMP-73) Duplicate deployment error if both reload and deploy goals are bind to the same maven phase

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/JBASMP-73?page=com.atlassian.jira.plugin.... ] Martin Basovnik updated JBASMP-73: ---------------------------------- Attachment: jbasmp-deploy-reproducer.zip reproducer > Duplicate deployment error if both reload and deploy goals are bind to the same maven phase > ------------------------------------------------------------------------------------------- > > Key: JBASMP-73 > URL: https://issues.jboss.org/browse/JBASMP-73 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Reporter: Martin Basovnik > Assignee: James Perkins > Attachments: jbasmp-deploy-reproducer.zip > > > If I try to deploy a deployment just after the server reloading it sometimes fails: > {code} > 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" > {code} > https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-73) Duplicate deployment error if both reload and deploy goals are bind to the same maven phase

by Martin Basovnik (JIRA)

Martin Basovnik created JBASMP-73: ------------------------------------- Summary: Duplicate deployment error if both reload and deploy goals are bind to the same maven phase Key: JBASMP-73 URL: https://issues.jboss.org/browse/JBASMP-73 Project: JBoss AS Maven Plugins Issue Type: Bug Components: deploy Reporter: Martin Basovnik Assignee: James Perkins If I try to deploy a deployment just after the server reloading it sometimes fails: {code} 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" {code} https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4034) Upgrade HAL to 2.4.5.Final

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4034?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4034: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/6772) > Upgrade HAL to 2.4.5.Final > -------------------------- > > Key: WFLY-4034 > URL: https://issues.jboss.org/browse/WFLY-4034 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4034) Upgrade HAL to 2.4.5.Final

by Heiko Braun (JIRA)

Heiko Braun created WFLY-4034: --------------------------------- Summary: Upgrade HAL to 2.4.5.Final Key: WFLY-4034 URL: https://issues.jboss.org/browse/WFLY-4034 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Heiko Braun Assignee: Harald Pehl Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4033) Upgrade HAL to 2.4.5.Final

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-4033?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-4033: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/6773) > Upgrade HAL to 2.4.5.Final > -------------------------- > > Key: WFLY-4033 > URL: https://issues.jboss.org/browse/WFLY-4033 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 8.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4033) Upgrade HAL to 2.4.5.Final

by Heiko Braun (JIRA)

Heiko Braun created WFLY-4033: --------------------------------- Summary: Upgrade HAL to 2.4.5.Final Key: WFLY-4033 URL: https://issues.jboss.org/browse/WFLY-4033 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Heiko Braun Assignee: Harald Pehl Fix For: 8.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-79) ExplodedDeploymentMarker is not set for sub deployments

by Jacob Ilsø (JIRA)

[ https://issues.jboss.org/browse/WFCORE-79?page=com.atlassian.jira.plugin.... ] Jacob Ilsø commented on WFCORE-79: ---------------------------------- We're seeing issue WLFY-3765 in WildFly 8.1.0.Final. How was this fixed in 9.0.0.Alpha1? I can't see any code changes related to this (WFCORE-79) issue. > ExplodedDeploymentMarker is not set for sub deployments > ------------------------------------------------------- > > Key: WFCORE-79 > URL: https://issues.jboss.org/browse/WFCORE-79 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha5 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha6 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-79) ExplodedDeploymentMarker is not set for sub deployments

by Jacob Ilsø (JIRA)

[ https://issues.jboss.org/browse/WFCORE-79?page=com.atlassian.jira.plugin.... ] Jacob Ilsø edited comment on WFCORE-79 at 10/30/14 4:47 AM: ------------------------------------------------------------ We're seeing issue WFLY-3765 in WildFly 8.1.0.Final. How was this fixed in 9.0.0.Alpha1? I can't see any code changes related to this (WFCORE-79) issue. was (Author: jacobilsoe): We're seeing issue WLFY-3765 in WildFly 8.1.0.Final. How was this fixed in 9.0.0.Alpha1? I can't see any code changes related to this (WFCORE-79) issue. > ExplodedDeploymentMarker is not set for sub deployments > ------------------------------------------------------- > > Key: WFCORE-79 > URL: https://issues.jboss.org/browse/WFCORE-79 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha5 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha6 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-171) File handlers should not allow already existing directories as a file name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-171?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-171: ------------------------------------------------ Nikoleta Ziakova <nziakova(a)redhat.com> changed the Status of [bug 915670|https://bugzilla.redhat.com/show_bug.cgi?id=915670] from ON_QA to VERIFIED > File handlers should not allow already existing directories as a file name > -------------------------------------------------------------------------- > > Key: WFCORE-171 > URL: https://issues.jboss.org/browse/WFCORE-171 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha11 > > > File handler resources allow existing directories to be used as the path name for the file. An exception is thrown in the logmanager, but the operation succeeds. Validation of the path should be done in the operations. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4032) Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)

by Duc Quoc (JIRA)

Duc Quoc created WFLY-4032: ------------------------------ Summary: Standalone.bat not support log dir with spaces in path (jboss.server.log.dir) Key: WFLY-4032 URL: https://issues.jboss.org/browse/WFLY-4032 Project: WildFly Issue Type: Bug Components: Batch, Logging, Scripts Affects Versions: 8.1.0.Final Environment: Windows 7 Reporter: Duc Quoc Assignee: James Perkins Priority: Minor I tried to specify a custom log folder for WildFly, by overriding property jboss.server.log.dir https://docs.jboss.org/author/display/WFLY8/Command+line+parameters But it only works for folder without space in path. The ones with space when used with "jboss.server.log.dir" will prevent wildfly from starting. Working: C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Windows" Not working (server can not start): C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" (More info: JBoss AS 7.1 works: C:\> start C:\jboss-as-7.1.1.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" JBoss EAP 6 and WildFly 8.0 not working either: C:\> start C:\jboss-eap-6.2\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" C:\> start C:\wildfly-8.0.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" Aready tried setting jboss.server.log.dir="C:\Program Files" in JAVA_OPTS but did not work either. Should have been fixed in WFLY-1358 or WFLY-2348. ) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014