March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1423) EAP init scripts don't detach jbossas process

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFCORE-1423: ------------------------------------------------ Summary: EAP init scripts don't detach jbossas process Key: WFCORE-1423 URL: https://issues.jboss.org/browse/WFCORE-1423 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko When starting WF via wildfly-init-redhat.sh, the init script and runuser commands are never disconnected and stay in the process tree. Reproduce: - create a new OS user "jbossadm" - unzip WF in his home directory - copy docs/contrib/scripts/init.d/wildfly.conf to /etc/default configure it with: JBOSS_HOME=/home/jbossadm/wildfly JBOSS_USER=jbossadm JBOSS_CONSOLE_LOG=/home/jbossadm/console.log JBOSS_MODE=domain - copy docs/contrib/scripts/init.d/wildfly-init-redhat.sh to /etc/init.d - become su, and start with: /etc/init.d/wildfly-init-redhat.sh start -run: ps axfo pid,ppid,user,command | grep jboss {noformat} PID PPID USER COMMAND 479 1 root /bin/sh /etc/init.d/wildfly-init-redhat.sh start 481 479 root \_ runuser -s /bin/bash jbossadm -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run 482 481 jbossadm \_ bash -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run/wildfly/wildfly.pid 483 482 jbossadm \_ /bin/sh /home/jbossadm/jboss-eap-7/bin/domain.sh --domain-config=domain.xml --host-config=host.xml 579 483 jbossadm \_ java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack 596 579 jbossadm \_ java -D[Host Controller] -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/host-control 677 579 jbossadm \_ java -D[Server:server-one] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - 727 579 jbossadm \_ java -D[Server:server-two] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - {noformat} Expectation: "domain.sh" to become detached and have "1" as its parent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1422) EAP init scripts don't detach jbossas process

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1422?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko commented on WFCORE-1422: -------------------------------------------------- process tree with the fix: {noformat} [root@939b8b0f5247 /]# ps axfo pid,ppid,user,command PID PPID USER COMMAND 1 0 root /bin/bash 1394 1 jbossadm /bin/sh /home/jbossadm/jboss-eap-7/bin/domain.sh --domain-config=domain.xml --host-config=host.xml 1491 1394 jbossadm \_ java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/process-controller.log -Dlogging.configuration=file:/home/jbossadm/jboss-eap-7/domain/configuration/logging.properties -jar /home/jbossadm/jboss-eap-7/jboss-modules.jar -mp /home/jbossadm/jboss-eap-7/modules org.jboss.as.process-controller -jboss-home /home/jbossadm/jboss-eap-7 -jvm java -mp /home/jbossadm/jboss-eap-7/modules -- -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/host-controller.log -Dlogging.configuration=file:/home/jbossadm/jboss-eap-7/domain/configuration/logging.properties -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -- -default-jvm java --domain-config=domain.xml --host-config=host.xml 1508 1491 jbossadm \_ java -D[Host Controller] -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/host-controller.log -Dlogging.configuration=file:/home/jbossadm/jboss-eap-7/domain/configuration/logging.properties -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -jar /home/jbossadm/jboss-eap-7/jboss-modules.jar -mp /home/jbossadm/jboss-eap-7/modules org.jboss.as.host-controller -mp /home/jbossadm/jboss-eap-7/modules --pc-address 127.0.0.1 --pc-port 43929 -default-jvm java --domain-config=domain.xml --host-config=host.xml -Djboss.home.dir=/home/jbossadm/jboss-eap-7 1584 1491 jbossadm \_ java -D[Server:server-one] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djboss.home.dir=/home/jbossadm/jboss-eap-7 -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.log.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-one/log -Djboss.server.temp.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-one/tmp -Djboss.server.data.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-one/data -Dlogging.configuration=file:/home/jbossadm/jboss-eap-7/domain/servers/server-one/data/logging.properties -jar /home/jbossadm/jboss-eap-7/jboss-modules.jar -mp /home/jbossadm/jboss-eap-7/modules org.jboss.as.server 1656 1491 jbossadm \_ java -D[Server:server-two] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djboss.home.dir=/home/jbossadm/jboss-eap-7 -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.log.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-two/log -Djboss.server.temp.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-two/tmp -Djboss.server.data.dir=/home/jbossadm/jboss-eap-7/domain/servers/server-two/data -Dlogging.configuration=file:/home/jbossadm/jboss-eap-7/domain/servers/server-two/data/logging.properties -jar /home/jbossadm/jboss-eap-7/jboss-modules.jar -mp /home/jbossadm/jboss-eap-7/modules org.jboss.as.server {noformat} > EAP init scripts don't detach jbossas process > --------------------------------------------- > > Key: WFCORE-1422 > URL: https://issues.jboss.org/browse/WFCORE-1422 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > When starting WF via wildfly-init-redhat.sh, the init script and runuser commands are never disconnected and stay in the process tree. > Reproduce: > - create a new OS user "jbossadm" > - unzip WF in his home directory > - copy docs/contrib/scripts/init.d/wildfly.conf to /etc/default > configure it with: > JBOSS_HOME=/home/jbossadm/wildfly > JBOSS_USER=jbossadm > JBOSS_CONSOLE_LOG=/home/jbossadm/console.log > JBOSS_MODE=domain > - copy docs/contrib/scripts/init.d/wildfly-init-redhat.sh to /etc/init.d > - become su, and start with: > /etc/init.d/wildfly-init-redhat.sh start > -run: ps axfo pid,ppid,user,command | grep jboss > {noformat} > PID PPID USER COMMAND > 479 1 root /bin/sh /etc/init.d/wildfly-init-redhat.sh start > 481 479 root \_ runuser -s /bin/bash jbossadm -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run > 482 481 jbossadm \_ bash -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run/wildfly/wildfly.pid > 483 482 jbossadm \_ /bin/sh /home/jbossadm/jboss-eap-7/bin/domain.sh --domain-config=domain.xml --host-config=host.xml > 579 483 jbossadm \_ java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack > 596 579 jbossadm \_ java -D[Host Controller] -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/host-control > 677 579 jbossadm \_ java -D[Server:server-one] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - > 727 579 jbossadm \_ java -D[Server:server-two] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - > {noformat} > Expectation: "domain.sh" to become detached and have "1" as its parent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1422) EAP init scripts don't detach jbossas process

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFCORE-1422: ------------------------------------------------ Summary: EAP init scripts don't detach jbossas process Key: WFCORE-1422 URL: https://issues.jboss.org/browse/WFCORE-1422 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko When starting WF via wildfly-init-redhat.sh, the init script and runuser commands are never disconnected and stay in the process tree. Reproduce: - create a new OS user "jbossadm" - unzip WF in his home directory - copy docs/contrib/scripts/init.d/wildfly.conf to /etc/default configure it with: JBOSS_HOME=/home/jbossadm/wildfly JBOSS_USER=jbossadm JBOSS_CONSOLE_LOG=/home/jbossadm/console.log JBOSS_MODE=domain - copy docs/contrib/scripts/init.d/wildfly-init-redhat.sh to /etc/init.d - become su, and start with: /etc/init.d/wildfly-init-redhat.sh start -run: ps axfo pid,ppid,user,command | grep jboss {noformat} PID PPID USER COMMAND 479 1 root /bin/sh /etc/init.d/wildfly-init-redhat.sh start 481 479 root \_ runuser -s /bin/bash jbossadm -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run 482 481 jbossadm \_ bash -c ulimit -S -c 0 >/dev/null 2>&1 ; LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=/var/run/wildfly/wildfly.pid 483 482 jbossadm \_ /bin/sh /home/jbossadm/jboss-eap-7/bin/domain.sh --domain-config=domain.xml --host-config=host.xml 579 483 jbossadm \_ java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack 596 579 jbossadm \_ java -D[Host Controller] -Dorg.jboss.boot.log.file=/home/jbossadm/jboss-eap-7/domain/log/host-control 677 579 jbossadm \_ java -D[Server:server-one] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - 727 579 jbossadm \_ java -D[Server:server-two] -Xms64m -Xmx512m -server -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m - {noformat} Expectation: "domain.sh" to become detached and have "1" as its parent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6317) No database-specific validation will be performed (JPA Problem)

by mohamed baya chatti (JIRA)

mohamed baya chatti created WFLY-6317: ----------------------------------------- Summary: No database-specific validation will be performed (JPA Problem) Key: WFLY-6317 URL: https://issues.jboss.org/browse/WFLY-6317 Project: WildFly Issue Type: Bug Environment: Wildfly 9 Maven project {ejb who contain JPA and web.war} Reporter: mohamed baya chatti Assignee: Jason Greene Can someone help me im new in dev Java-ee and i cant deploy my project (maven project) i think the cuz is this jpa problem " {color:red}No database-specific validation will be performed{color}" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2023) Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/JGRP-2023?page=com.atlassian.jira.plugin.... ] Richard Janík commented on JGRP-2023: ------------------------------------- After discussion with Bela and some checking of route tables, it seems that this might be caused by misconfiguration. I'll be trying to tune my own routing table and will check back with results. > Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified > ----------------------------------------------------------------------------------------------- > > Key: JGRP-2023 > URL: https://issues.jboss.org/browse/JGRP-2023 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.7, 3.6.8 > Environment: $ java -version > java version "1.8.0_45" > Java(TM) SE Runtime Environment (build 1.8.0_45-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) > Reporter: Richard Janík > Assignee: Bela Ban > > When setting {{-bind_addr}} to localhost (either 127.0.0.1 or ::1) without specifying {{-Djava.net.preferIPv4Stack=true}}, JGroups fail to connect. The following errors are logged: > {code} > ------------------------------------------------------------------- > GMS: address=rjanik-24069, cluster=draw, physical address=0:0:0:0:0:0:0:1:37921 > ------------------------------------------------------------------- > Mar 03, 2016 11:41:12 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage > SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (108 bytes): java.io.IOException: Network is unreachable, headers: PING: [type=GET_MBRS_REQ, cluster=draw], TP: [cluster_name=draw] > ** View=[rjanik-24069|0] (1) [rjanik-24069] > Mar 03, 2016 11:41:15 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage > SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (56 bytes): java.io.IOException: Network is unreachable, headers: NAKACK2: [MSG, seqno=1], TP: [cluster_name=draw] > {code} > I'm not sure if there's some other configuration option that I forgot to add, but the example (in Steps to Reproduce) works with previous versions (3.6.6 for example), so I assume not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3515) Wildfly High Availability Guide: Refurbish Cluster and Domain Quickstart

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3515?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3515: --------------------------------- Fix Version/s: (was: No Release) > Wildfly High Availability Guide: Refurbish Cluster and Domain Quickstart > ------------------------------------------------------------------------ > > Key: WFLY-3515 > URL: https://issues.jboss.org/browse/WFLY-3515 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The origina document is at > https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto > The 8 version is (currently) at > https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto > The document needs some refurbishing for WildFly. > It however also introduces some confusion refering to master/slave which gets people confused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3515) Wildfly High Availability Guide: Refurbish Cluster and Domain Quickstart

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3515?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3515: --------------------------------- Description: The original document is at https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto The 8 version is (currently) at https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto The document needs some refurbishing for WildFly. It however also introduces some confusion refering to master/slave which gets people confused. was: The origina document is at https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto The 8 version is (currently) at https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto The document needs some refurbishing for WildFly. It however also introduces some confusion refering to master/slave which gets people confused. > Wildfly High Availability Guide: Refurbish Cluster and Domain Quickstart > ------------------------------------------------------------------------ > > Key: WFLY-3515 > URL: https://issues.jboss.org/browse/WFLY-3515 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The original document is at > https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto > The 8 version is (currently) at > https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto > The document needs some refurbishing for WildFly. > It however also introduces some confusion refering to master/slave which gets people confused. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1829) Wildfly High Availability Guide: EJB Services/Subsystem write up

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1829?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz reassigned WFLY-1829: ----------------------------------------- Assignee: Richard Achmatowicz > Wildfly High Availability Guide: EJB Services/Subsystem write up > ---------------------------------------------------------------- > > Key: WFLY-1829 > URL: https://issues.jboss.org/browse/WFLY-1829 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Richard Achmatowicz > > https://docs.jboss.org/author/display/WFLY8/EJB+Subsystem -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1725) Update The WildFly High Availability Guide

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1725?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-1725: --------------------------------- Summary: Update The WildFly High Availability Guide (was: Update The Wildfly High Availability Guide ) > Update The WildFly High Availability Guide > ------------------------------------------- > > Key: WFLY-1725 > URL: https://issues.jboss.org/browse/WFLY-1725 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha3 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > > The main source of clustering-related documentation for a Wildfly user is the High Availability Guide in the Wildfly 8 documentation on docs.jboss.org. > Update this document into a quality document which will aid the user's understanding of new features and configuration in Wildfly 8 clustering. > https://docs.jboss.org/author/display/WFLY8/High+Availability+Guide -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBCOMMON-134) typo in prompt

by Valery Sorokin (JIRA)

Valery Sorokin created JBCOMMON-134: --------------------------------------- Summary: typo in prompt Key: JBCOMMON-134 URL: https://issues.jboss.org/browse/JBCOMMON-134 Project: JBoss Common Issue Type: Enhancement Reporter: Valery Sorokin Assignee: Dimitris Andreadis Priority: Trivial prompt on 'jboss-cli.sh --connect controller=https-remoting://localhost:8443 ' displays: ------------------------------------------------------------------- Accept certificate? [N]o, [T]emporarily, [P]ermenantly : P ------------------------------------------------------------------- (not 'permanently') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016