Aplicação eSUS com JBOSS não navega.

13. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 11:48h

Desculpe a demora, segue arquivo:

/opt/e-SUS/jboss-as-7.2.0.Final/standalone/logging.properties
#
# JBoss, Home of Professional Open Source.
# Copyright 2010, Red Hat, Inc., and individual contributors
# as indicated by the @author tags. See the copyright.txt file in the
# distribution for a full listing of individual contributors.
#
# This is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of
# the License, or (at your option) any later version.
#
# This software is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this software; if not, write to the Free
# Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
# 02110-1301 USA, or see the FSF site: http://www.fsf.org.
#

# Additional loggers to configure (the root logger is always configured)
loggers=com.arjuna,jacorb,org.jboss.as.config,org.apache.tomcat.util.modeler,sun.rmi,jacorb.config

logger.level=INFO
logger.handlers=CONSOLE,FILE

logger.com.arjuna.level=WARN
logger.com.arjuna.useParentHandlers=true

logger.jacorb.level=WARN
logger.jacorb.useParentHandlers=true

logger.org.jboss.as.config.level=DEBUG
logger.org.jboss.as.config.useParentHandlers=true

logger.org.apache.tomcat.util.modeler.level=WARN
logger.org.apache.tomcat.util.modeler.useParentHandlers=true

logger.sun.rmi.level=WARN
logger.sun.rmi.useParentHandlers=true

logger.jacorb.config.level=ERROR
logger.jacorb.config.useParentHandlers=true

handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.level=INFO
handler.CONSOLE.formatter=CONSOLE
handler.CONSOLE.properties=autoFlush,target
handler.CONSOLE.autoFlush=true
handler.CONSOLE.target=SYSTEM_OUT

handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
handler.FILE.level=ALL
handler.FILE.formatter=FILE
handler.FILE.properties=autoFlush,append,fileName,suffix
handler.FILE.constructorProperties=fileName,append
handler.FILE.autoFlush=true
handler.FILE.append=true
handler.FILE.fileName=${org.jboss.boot.log.file:boot.log}
handler.FILE.suffix=.yyyy-MM-dd

formatter.CONSOLE=org.jboss.logmanager.formatters.PatternFormatter
formatter.CONSOLE.properties=pattern
formatter.CONSOLE.pattern=%K{level}%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n

formatter.FILE=org.jboss.logmanager.formatters.PatternFormatter
formatter.FILE.properties=pattern
formatter.FILE.constructorProperties=pattern
formatter.FILE.pattern=%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n



  


14. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 12:22h

Blz, sem problemas.

Apenas para efeito de testes, no seu standalone.xml altere a seguinte linha:

De:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

Para:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:1}">

e reinicie a aplicação.

Depois de reiniciado me mande um #netstat -nltp

Att



15. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 14:59h

root@saude:/# netstat -nltp
Conexões Internet Ativas (sem os servidores)
Proto Recv-Q Send-Q Endereço Local Endereço Remoto Estado PID/Program name
tcp 0 0 127.0.0.1:3306 0.0.0.0:* OUÇA 2975/mysqld
tcp 0 0 0.0.0.0:139 0.0.0.0:* OUÇA 2954/smbd
tcp 0 0 0.0.0.0:10000 0.0.0.0:* OUÇA 3309/perl
tcp 0 0 189.xxx.xxx.78:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:4661 0.0.0.0:* OUÇA 4611/sshd
tcp 0 0 10.1.1.2:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 172.16.8.254:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:3128 0.0.0.0:* OUÇA 5538/(squid)
tcp 0 0 0.0.0.0:25 0.0.0.0:* OUÇA 3710/master
tcp 0 0 127.0.0.1:5433 0.0.0.0:* OUÇA 2951/postgres
tcp 0 0 127.0.0.1:953 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:445 0.0.0.0:* OUÇA 2954/smbd
tcp6 0 0 :::5222 :::* OUÇA 8204/java
tcp6 0 0 :::5223 :::* OUÇA 8204/java
tcp6 0 0 :::139 :::* OUÇA 2954/smbd
tcp6 0 0 :::5229 :::* OUÇA 8204/java
tcp6 0 0 :::80 :::* OUÇA 3329/apache2
tcp6 0 0 :::7443 :::* OUÇA 8204/java
tcp6 0 0 :::5269 :::* OUÇA 8204/java
tcp6 0 0 :::4661 :::* OUÇA 4611/sshd
tcp6 0 0 :::53 :::* OUÇA 2496/named
tcp6 0 0 :::25 :::* OUÇA 3710/master
tcp6 0 0 ::1:5433 :::* OUÇA 2951/postgres
tcp6 0 0 ::1:953 :::* OUÇA 2496/named
tcp6 0 0 :::443 :::* OUÇA 3329/apache2
tcp6 0 0 :::445 :::* OUÇA 2954/smbd
tcp6 0 0 :::7070 :::* OUÇA 8204/java
tcp6 0 0 :::7777 :::* OUÇA 8204/java
tcp6 0 0 :::9090 :::* OUÇA 8204/java



16. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 15:48h

É parece que não subiu também , mas to vendo que agora conflitaria com a porta 10000 que um serviço perl já está usando, faça o seguinte:

Altere agora

De:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:1}">

Para:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:5}">

E reinicie a aplicação novamente.

Att


17. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 15:58h

Conexões Internet Ativas (sem os servidores)
Proto Recv-Q Send-Q Endereço Local Endereço Remoto Estado PID/Program name
tcp 0 0 127.0.0.1:3306 0.0.0.0:* OUÇA 2975/mysqld
tcp 0 0 0.0.0.0:139 0.0.0.0:* OUÇA 2954/smbd
tcp 0 0 0.0.0.0:10000 0.0.0.0:* OUÇA 3309/perl
tcp 0 0 189.xxx.xxx.78:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:4661 0.0.0.0:* OUÇA 4611/sshd
tcp 0 0 10.1.1.2:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 172.16.8.254:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:3128 0.0.0.0:* OUÇA 5538/(squid)
tcp 0 0 0.0.0.0:25 0.0.0.0:* OUÇA 3710/master
tcp 0 0 127.0.0.1:5433 0.0.0.0:* OUÇA 2951/postgres
tcp 0 0 127.0.0.1:953 0.0.0.0:* OUÇA 2496/named
tcp 0 0 0.0.0.0:445 0.0.0.0:* OUÇA 2954/smbd
tcp6 0 0 :::5222 :::* OUÇA 8204/java
tcp6 0 0 :::5223 :::* OUÇA 8204/java
tcp6 0 0 :::139 :::* OUÇA 2954/smbd
tcp6 0 0 :::5229 :::* OUÇA 8204/java
tcp6 0 0 :::80 :::* OUÇA 3329/apache2
tcp6 0 0 :::7443 :::* OUÇA 8204/java
tcp6 0 0 :::5269 :::* OUÇA 8204/java
tcp6 0 0 :::4661 :::* OUÇA 4611/sshd
tcp6 0 0 :::53 :::* OUÇA 2496/named
tcp6 0 0 :::25 :::* OUÇA 3710/master
tcp6 0 0 ::1:5433 :::* OUÇA 2951/postgres
tcp6 0 0 ::1:953 :::* OUÇA 2496/named
tcp6 0 0 :::443 :::* OUÇA 3329/apache2
tcp6 0 0 :::445 :::* OUÇA 2954/smbd
tcp6 0 0 :::7070 :::* OUÇA 8204/java
tcp6 0 0 :::7777 :::* OUÇA 8204/java
tcp6 0 0 :::9090 :::* OUÇA 8204/java



18. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 16:09h

Uma dúvida, essa é toda saida? ou tem mais algum dado que não está na tela?

Att


19. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 16:14h

Com base nos primeiros comandos que pedi para executar listando processos java, pode fazer um outro favor:

#ps aux | grep jboss -v grep

poste para mim todo retorno, pegue o PID do processo retornado e rode o netstat filtrando por esse PID.

#netstat -nltp | grep "pid"

Att


20. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 16:27h

é toda saída, não faltou nada, vou colocar o comando de inicialização dele e o respectivo script:

sh /opt/e-SUS/jboss-as-7.2.0.Final/bin/init.d/jboss-as-standalone-lsb.sh stop
[....] Stopping JBoss AS 7.2.0 - Server: JBoss_AS_7_2_0*** JBossAS process (11582) received TERM signal ***
. ok


sh /opt/e-SUS/jboss-as-7.2.0.Final/bin/init.d/jboss-as-standalone-lsb.sh start
[....] Starting JBoss AS 7.2.0 - Server: JBoss_AS_7_2_0Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
. ok


jboss-as-standalone-lsb.sh:
#!/bin/sh
#
# LSB Linux. Examples: Ubuntu

NAME=JBoss_AS_7_2_0
DESC="JBoss AS 7.2.0 - Server"
DEFAULT=/etc/default/$NAME

# Check privileges
if [ `id -u` -ne 0 ]; then
echo "You need root privileges to run this script"
exit 1
fi

# Make sure jboss is started with system locale
if [ -r /etc/default/locale ]; then
. /etc/default/locale
export LANG
fi

. /lib/lsb/init-functions

if [ -r /etc/default/rcS ]; then
. /etc/default/rcS
fi

# Overwrite settings from default file
if [ -f "$DEFAULT" ]; then
. "$DEFAULT"
fi

# Location of java

# Load Java configuration.
[ -r /etc/java.conf ] && . /etc/java.conf
if [ -z "$JAVA_HOME" ]; then
log_failure_msg "JAVA_HOME is not defined in this environment"
exit 1
fi
export JAVA_HOME

# Check if java is installed
if [ ! -f "$JAVA_HOME/bin/java" ]; then
log_failure_msg "Java is not installed in $JAVA_HOME"
exit 1
fi

# Location of jboss
JBOSS_HOME=/opt/e-SUS/jboss-as-7.2.0.Final
export JBOSS_HOME

# Check if jboss is installed
if [ ! -f "$JBOSS_HOME/jboss-modules.jar" ]; then
log_failure_msg "$NAME is not installed in $JBOSS_HOME"
exit 1
fi

# Run as jboss user
JBOSS_USER=root
if [ -z "$JBOSS_USER" ]; then
JBOSS_USER=root
fi

# Check jboss user
id $JBOSS_USER > /dev/null 2>&1
if [ $? -ne 0 -o -z "$JBOSS_USER" ]; then
log_failure_msg "User $JBOSS_USER does not exist..."
log_end_msg 1
exit 1
fi

# Check startup file
JBOSS_SCRIPT=$JBOSS_HOME/bin/standalone.sh
if [ ! -x $JBOSS_SCRIPT ]; then
log_failure_msg "$JBOSS_SCRIPT is not an executable!"
exit 1
fi

# Check shutdown file
JBOSS_SH_SHUTDOWN=$JBOSS_HOME/bin/jboss-cli.sh
if [ ! -x $JBOSS_SH_SHUTDOWN ]; then
log_failure_msg "$JBOSS_SH_SHUTDOWN is not an executable!"
exit 1
fi

# The amount of time to wait for startup
if [ -z "$STARTUP_WAIT" ]; then
STARTUP_WAIT=30
fi

# The amount of time to wait for shutdown
if [ -z "$SHUTDOWN_WAIT" ]; then
SHUTDOWN_WAIT=30
fi

# Location to keep the console log
export JBOSS_CONSOLE_LOG=$JBOSS_HOME/standalone/log/console.log
# Location to set the pid file
export JBOSS_PIDFILE=$JBOSS_HOME/standalone/esus.pid
# Launch jboss in background
export LAUNCH_JBOSS_IN_BACKGROUND=true

# Helper function to check status of jboss service
check_status() {
start-stop-daemon --status --name java --user $JBOSS_USER \
--pidfile "$JBOSS_PIDFILE" >/dev/null 2>&1
return $?
}

case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
check_status
status_start=$?
if [ $status_start -eq 3 ]; then
mkdir -p $(dirname $JBOSS_PIDFILE)
mkdir -p $(dirname $JBOSS_CONSOLE_LOG)
chown $JBOSS_USER $(dirname $JBOSS_PIDFILE)
cat /dev/null > $JBOSS_CONSOLE_LOG

start-stop-daemon --start --user "$JBOSS_USER" \
--chuid "$JBOSS_USER" --chdir "$JBOSS_HOME" --pidfile "$JBOSS_PIDFILE" \
--exec "$JBOSS_SCRIPT" 2>&1 > $JBOSS_CONSOLE_LOG &

count=0
launched=false
until [ $count -gt $STARTUP_WAIT ]
do
grep 'JBAS015874:' $JBOSS_CONSOLE_LOG > /dev/null
if [ $? -eq 0 ] ; then
launched=true
break
fi
sleep 1
count=$(($count + 1));
done

if check_status; then
log_end_msg 0
else
log_end_msg 1
fi
elif [ $status_start -eq 1 ]; then
log_failure_msg "$DESC is not running but the pid file exists"
log_end_msg 1
exit 1
elif [ $status_start -eq 0 ]; then
log_success_msg "$DESC (already running)"
log_end_msg 0
fi
;;
stop)
check_status
status_stop=$?
if [ $status_stop -eq 0 ]; then
read kpid < $JBOSS_PIDFILE
log_daemon_msg "Stopping $DESC" "$NAME"
start-stop-daemon --start --chuid "$JBOSS_USER" \
--exec "$JBOSS_SH_SHUTDOWN" -- --connect --command=:shutdown \
>/dev/null 2>&1

if [ $? -eq 1 ]; then
kill -15 $kpid
fi

count=0
until [ $count -gt $SHUTDOWN_WAIT ]
do
check_status
if [ $? -eq 3 ]; then
break
fi
sleep 1
count=$(($count + 1));
done

if [ $count -gt $SHUTDOWN_WAIT ]; then
kill -9 $kpid
fi
elif [ $status_stop -eq 1 ]; then
log_daemon_msg "$DESC is not running but the pid file exists, cleaning up"
rm -f $JBOSS_PIDFILE
elif [ $status_stop -eq 3 ]; then
log_daemon_msg "$DESC is not running"
fi

log_end_msg 0
;;
restart|reload|force-reload)
check_status
status_restart=$?
if [ $status_restart -eq 0 ]; then
$0 stop
fi
$0 start
;;
status)
check_status
status=$?
if [ $status -eq 0 ]; then
log_success_msg "$DESC is running with pid `cat $JBOSS_PIDFILE`"
exit 0
elif [ $status -eq 1 ]; then
log_success_msg "$DESC is not running and the pid file exists"
exit 1
elif [ $status -eq 3 ]; then
log_success_msg "$DESC is not running"
exit 3
else
log_success_msg "Unable to determine $NAME status"
exit 4
fi
;;
*)
log_action_msg "Usage: $0 {start|stop|restart|status}"
exit 2
;;
esac

exit 0


Retorno do que você me pediu:

root@saude:/# ps aux | grep jboss -v grep
grep: grep: Arquivo ou diretório não encontrado



21. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 16:35h

Desculpe

#ps aux | grep jboss | grep -v grep



22. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 17:04h

postgres  2951  0.0  0.1 200240 13912 ?        S    Jan26   0:00 /opt/e-SUS/jboss-as-7.2.0.Final/PostgreSQL/9.3/bin/postgres -D /opt/e-SUS/jboss-as-7.2.0.Final/PostgreSQL/9.3/data
root 13532 0.0 0.0 4188 696 pts/0 S 15:56 0:00 /bin/sh /opt/e-SUS/jboss-as-7.2.0.Final/bin/standalone.sh
root 13588 99.7 0.9 3725708 77440 pts/0 Sl 15:56 68:22 /usr/lib/jvm/java-8-oracle/jre/bin/java -D[Standalone] -XX:+UseCompressedOops -XX:+TieredCompilation -server -Xms2048m -Xmx2048m -XX:MaxPermSize=256m -XX:PermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/opt/e-SUS/jboss-as-7.2.0.Final/standalone/log/boot.log -Dlogging.configuration=file:/opt/e-SUS/jboss-as-7.2.0.Final/standalone/configuration/logging.properties -jar /opt/e-SUS/jboss-as-7.2.0.Final/jboss-modules.jar -mp /opt/e-SUS/jboss-as-7.2.0.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/opt/e-SUS/jboss-as-7.2.0.Final


root@saude:/# netstat -nltp | grep 2951
tcp 0 0 127.0.0.1:5433 0.0.0.0:* OUÇA 2951/postgres
tcp6 0 0 ::1:5433 :::* OUÇA 2951/postgres


Nos outros 2 não retornou nada.


23. Re: Aplicação eSUS com JBOSS não navega.

Remington Santos
remingtonsb

(usa Red Hat)

Enviado em 30/01/2017 - 17:06h

#netstat -nltp | grep 13588
#netstat -nltp | grep 13532



24. Re: Aplicação eSUS com JBOSS não navega.

Silas Matos
silasmg

(usa Debian)

Enviado em 30/01/2017 - 17:09h

Não retornou nada:

root@saude:/# netstat -nltp | grep 13588
root@saude:/#


root@saude:/# netstat -nltp | grep 13532
root@saude:/#




01 02 03



Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts