February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1389) Align domain.sh and standalone.sh logic about adding -server

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1389?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-769 to WFCORE-1389: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1389 (was: WFLY-769) Component/s: Scripts (was: Scripts) Fix Version/s: (was: Awaiting Volunteers) > Align domain.sh and standalone.sh logic about adding -server > ------------------------------------------------------------ > > Key: WFCORE-1389 > URL: https://issues.jboss.org/browse/WFCORE-1389 > Project: WildFly Core > Issue Type: Task > Components: Scripts > Reporter: Brian Stansberry > > The domain.sh script has a number of JVM vendor checks it uses to decide whether to add -server to the jvm launch command. In standalone.sh it's simpler; it simply checks for OSX. > I can't see any reason this logic should be significantly different between the two cases, either the JVM vendor checks are needed in both or they aren't needed in either. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1383) Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1383?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-5366 to WFCORE-1383: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1383 (was: WFLY-5366) Component/s: Scripts (was: Scripts) Affects Version/s: 2.0.0.CR1 (was: 10.0.0.CR1) Fix Version/s: (was: Awaiting Volunteers) > Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently. > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1383 > URL: https://issues.jboss.org/browse/WFCORE-1383 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.0.0.CR1 > Environment: Linux/Debian > Reporter: Thorsten Moeller > > If the property `jboss.server.base.dir` and the environment variable `JBOSS_HOME` point to different directories (which we do, for instance, to start multiple JBoss/Wildfly instances, each with its own standalone directory) then the startup success detection mechanism implemented by the script <WILDFLY_HOME>/bin/init.d/wildfly-init-debian.sh wrongly reports startup as failed even if it actually succeeded. > Tracing it down, I found that since Wildly 10 the startup script searches for the file `<JBOSS_HOME>/standalone/tmp/startup-marker`. However, that file is actually written to `jboss.server.base.dir/tmp/startup-marker`; hence, it is not found if the directories are not the same. > I don't see a way how to fix this. As far as I can seen, it's not possible to access the jboss.server.base.dir property within the startup script. But the use case of having separate directories should be supported and it should work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1384) Passing -Djboss.boot.server.log.level=DEBUG to standalone.sh script is ignored

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1384?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-672 to WFCORE-1384: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1384 (was: WFLY-672) Component/s: Scripts (was: Scripts) Fix Version/s: (was: Awaiting Volunteers) > Passing -Djboss.boot.server.log.level=DEBUG to standalone.sh script is ignored > ------------------------------------------------------------------------------ > > Key: WFCORE-1384 > URL: https://issues.jboss.org/browse/WFCORE-1384 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Fedora 14, java-1.6.0-openjdk, jboss-as-7.1.0.Alpha2-SNAPSHOT > Reporter: Rich Lucente > Priority: Minor > Labels: eap6-ux > > Attempting to change boot log level via a script argument to standalone.sh is ignored. I can edit standalone.conf (set value in JAVA_OPTS) or edit logging.properties directly. Other -D parameters are honored, so there seems to be some startup/timing issue with this specific setting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1385) init script creates unrotatable log file

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1385?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-3378 to WFCORE-1385: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1385 (was: WFLY-3378) Component/s: Scripts (was: Scripts) Fix Version/s: (was: Awaiting Volunteers) > init script creates unrotatable log file > ---------------------------------------- > > Key: WFCORE-1385 > URL: https://issues.jboss.org/browse/WFCORE-1385 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Shawn Goff > > The JBOSS init script redirects stdout of the jboss process to a file, then polls the file for a marker. The file it creates cannot be rotated without restarting the jboss project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1386) Accept properties file in scripts for starting as a service

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1386?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-5149 to WFCORE-1386: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1386 (was: WFLY-5149) Component/s: Scripts (was: Scripts) Affects Version/s: 2.0.0.Beta1 (was: 10.0.0.Beta1) Fix Version/s: (was: Awaiting Volunteers) > Accept properties file in scripts for starting as a service > ----------------------------------------------------------- > > Key: WFCORE-1386 > URL: https://issues.jboss.org/browse/WFCORE-1386 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Affects Versions: 2.0.0.Beta1 > Environment: Microsoft Windows > Reporter: Roman Syroeshko > > Currently $JBOSS_HOME\bin\service\service.bat does not allow passing properties file. We run WildFly in domain mode using the followed command. > {code} > domain.bat --properties=jboss.properties > {code} > Now, it's impossible to install WildFly as a service like that without hacking out-of-the-box files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1387) Add VisualVm launch scripts to the AS7 distribution

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1387?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-1129 to WFCORE-1387: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1387 (was: WFLY-1129) Component/s: Scripts (was: Scripts) > Add VisualVm launch scripts to the AS7 distribution > --------------------------------------------------- > > Key: WFCORE-1387 > URL: https://issues.jboss.org/browse/WFCORE-1387 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Environment: All > Reporter: John O'Hara > Priority: Optional > > Launching VisualVM with remoting-jmx requires additional jars to be on the classpath, in the same way that launching jconsole does. > Can we provice a .sh and a .bat with the correct classpath in the AS7 distribution to launch visualvm -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1388) jboss_init_redhat.sh needs to be more robust

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1388?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-1157 to WFCORE-1388: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1388 (was: WFLY-1157) Component/s: Scripts (was: Scripts) > jboss_init_redhat.sh needs to be more robust > -------------------------------------------- > > Key: WFCORE-1388 > URL: https://issues.jboss.org/browse/WFCORE-1388 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Reporter: Henrik Aronsen > Attachments: etc_default_jboss.txt, etc_init.d_jboss.txt > > > I have tried to address the shortcomings of the current JBoss init script for RHEL5: > - Uses PID file > - Supports chkconfig > - Supports start, stop, force-stop, reload, force-reload, status > - Supports custom user and password on shutdown > - Supports custom jndi host/port on shutdown > - Does not allow second instance to start when one is already running > - Does not rely on other files such as run.sh and run.conf > - Verifies successful startup > - The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead > - Runs out of the box when no configuration is provided > - Should support most Linuces > All feedback is welcome -- I'm sure I forgot something in the provided script > The init script is currently maintained at http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc > (This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1381) wildfly-init-debian.sh fails on Ubuntu 15.04

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1381?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-4570 to WFCORE-1381: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1381 (was: WFLY-4570) Component/s: Scripts (was: Scripts) Affects Version/s: 1.0.0.Beta6 1.0.0.CR1 (was: 9.0.0.CR1) (was: 9.0.0.Beta2) Fix Version/s: (was: Awaiting Volunteers) > wildfly-init-debian.sh fails on Ubuntu 15.04 > -------------------------------------------- > > Key: WFCORE-1381 > URL: https://issues.jboss.org/browse/WFCORE-1381 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 1.0.0.Beta6, 1.0.0.CR1 > Environment: Ubuntu 15.04, Oracle JDK_1.8.0_45-b14 > Reporter: Dennis Gesker > Priority: Minor > > Init script "wildfly-init-debian.sh" fails on Ubuntu 15.04 but standalone.sh works fine. Env is jdk_1.8.0_45-b14 and wildfly_9.0.0.Beta2. The error returned is: > Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory. > Had no issue with the above script on Ubuntu 14.04 so guessing a change in Ubuntu ("Upstart" Maybe?) But, I'm far from an upstart or bash expert. bash -x seems to at least create the pid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1382) AS fails to start with colon in path

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1382?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-909 to WFCORE-1382: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1382 (was: WFLY-909) Component/s: Scripts (was: Scripts) > AS fails to start with colon in path > ------------------------------------ > > Key: WFCORE-1382 > URL: https://issues.jboss.org/browse/WFCORE-1382 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: James Livingston > > standalone.sh and domain.sh create the module path passed to JBoss Modules -mp option with: > JBOSS_MODULEPATH="$JBOSS_HOME/modules" > The value passed to -mp is a File.pathSeparator (colon on Linux and semicolon on Windows) delimited list of paths, not a single path, so this does not work correctly when JBOSS_HOME contains a colon on Linux, which is a legal but rare character to use in a path. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6226) Consider request body encoding when creating PartImpl

by Bauke Scholtz (JIRA)

[ https://issues.jboss.org/browse/WFLY-6226?page=com.atlassian.jira.plugin.... ] Bauke Scholtz updated WFLY-6226: -------------------------------- Description: When {{request.getCharacterEncoding()}} returns non-{{null}}, please consider it while creating {{PartImpl}} instead of falling back to {{<servlet-container name="default" default-encoding="UTF-8">}}. Related Q&A: http://stackoverflow.com/q/35413585/157882 was: When `request.getCharacterEncoding()` returns non-`null`, please consider it while creating `PartImpl` instead of falling back to `<servlet-container name="default" default-encoding="UTF-8">`. Related Q&A: http://stackoverflow.com/q/35413585/157882 > Consider request body encoding when creating PartImpl > ----------------------------------------------------- > > Key: WFLY-6226 > URL: https://issues.jboss.org/browse/WFLY-6226 > Project: WildFly > Issue Type: Enhancement > Reporter: Bauke Scholtz > Assignee: Jason Greene > > When {{request.getCharacterEncoding()}} returns non-{{null}}, please consider it while creating {{PartImpl}} instead of falling back to {{<servlet-container name="default" default-encoding="UTF-8">}}. > Related Q&A: http://stackoverflow.com/q/35413585/157882 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
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 February 2016