Discussoes de Programacao e Tecnologia

[RESOLVIDO]Problemas na inicialização JBoss 7 no Debian com Java 1.7

2 respostas
G
gilsonk

Senhores,
estou com problemas na inicialização JBoss 7 no Debian com Java 1.7.
Explicando:
- a instalação transcorreu normalmente;
- consigo fazer deploy e acesar os sitemas no servidor sem problemas;

Onde esta o erro?

quando inicializo o JBOSS com o comando:

/var/opt/jboss/bin/standalone.sh
Ele inicia o servidor de aplicação, porem não finaliza o processo de incialização, fica rodando na console aberta, caso eu encere a console ele encerra o serviço.

Ja coloquei o script na inicialização do LINUX porem sem sucesso.

Em anexo deixo um print da console de inicialização do standalone.sh .

Abaixo a saida da execução do script standalone.sh

root@XXXXXXXXX:~# sh /var/opt/jboss/bin/standalone.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /var/opt/jboss/

  JAVA: /usr/local/jdk1.7/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=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

=========================================================================

11:26:59,392 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
11:26:59,545 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
11:26:59,585 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
11:27:00,256 INFO  [org.xnio] XNIO Version 3.0.3.GA
11:27:00,257 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
11:27:00,276 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
11:27:00,290 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
11:27:00,290 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
11:27:00,292 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
11:27:00,314 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
11:27:00,327 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
11:27:00,365 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
11:27:00,373 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
11:27:00,376 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
11:27:00,381 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
11:27:00,388 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
11:27:00,392 INFO  [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
11:27:00,401 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
11:27:00,481 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
11:27:00,606 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
11:27:00,637 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Error initializing endpoint: java.net.BindException: Endereço já em uso /10.12.34.34:8080
        at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:983) [jbossweb-7.0.13.Final.jar:]
        at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.13.Final.jar:]
        at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.13.Final.jar:]
        at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

11:27:00,680 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
        at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: LifecycleException:  Protocol handler initialization failed: java.net.BindException: Endereço já em uso /10.12.34.34:8080
        at org.apache.catalina.connector.Connector.init(Connector.java:985)
        at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
        ... 5 more

11:27:00,930 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Endereço já em uso /10.12.34.34:4447
        at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.net.BindException: Endereço já em uso
        at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:344) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:336) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_21]
        at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
        at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
        at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
        at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
        ... 5 more

11:27:00,939 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "sijud.war"
11:27:00,929 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Endereço já em uso /10.12.34.34:9999
        at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:109)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.net.BindException: Endereço já em uso
        at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:344) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:336) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) [rt.jar:1.7.0_21]
        at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
        at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
        at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
        at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
        ... 5 more

11:27:00,947 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /var/opt/jboss/standalone/deployments
11:27:00,954 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Endereço já em uso /10.12.34.34:9990
        at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:210) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.net.BindException: Endereço já em uso
        at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:344) [rt.jar:1.7.0_21]
        at sun.nio.ch.Net.bind(Net.java:336) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) [rt.jar:1.7.0_21]
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_21]
        at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
        at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
        at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
        at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
        at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:145) [jboss-as-domain-http-interface-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:177) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        ... 5 more

11:27:01,032 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
11:27:01,684 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/jldap-4.3.jar in "/content/sijud.war/WEB-INF/lib/loginx_ldap.jar"  does not point to a valid jar for a Class-Path reference.
11:27:01,685 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry lib/jldap-4.3.jar in "/content/sijud.war/WEB-INF/lib/loginx_ldap.jar"  does not point to a valid jar for a Class-Path reference.
11:27:01,792 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
11:27:01,793 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
11:27:02,197 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 8.4)
11:27:02,284 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
11:27:02,351 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Inicializando Mojarra 2.1.7-jbossorg-1 (20120227-1401) para o contexto '/sijud'
11:27:02,994 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-4) Hibernate Validator 4.2.0.Final
11:27:03,276 INFO  [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /sijud
11:27:03,689 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "sijud.war"
11:27:03,692 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
      service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Endereço já em uso /10.12.34.34:9990
      service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Endereço já em uso /10.12.34.34:9999
      service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Endereço já em uso /10.12.34.34:4447

11:27:03,793 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
11:27:03,794 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 4606ms - Started 428 of 512 services (7 services failed or missing dependencies, 76 services are passive or on-demand)
[i]-------> Aqui deveria vir a Conclusão da incialização, porem ele para na linha de cima![/i]

Alura Desenvolvimento Back-End Java Sua Carreira em desenvolvimento back-end Java: dos fundamentos à arquitetura de sistemas...

2 Respostas

A
Ataxexe

Vamos lá:

1- O script standalone.sh não é um script de serviço, ou seja, você terá que fazer o seu (na pasta bin/init.d existe um que pode ser usado pra isso, mas leia o script e veja o arquivo de configurações que ele utiliza antes de tentar usá-lo)
2- Pelo log, você já tem algum serviço utilizando as portas que o JBoss utiliza por padrão, verifique isso também
3- Se ainda assim quiser usar o “standalone.sh”, use-o com o comando “nohup” e mantendo-o em background com o “&” ao final (redirecionar as saídas para arquivos é uma boa também)

G
gilsonk

Ataxexe, obrigado pelas respostas.

1 - Adequei o script bin/init.d, o mesmo esta rodando;

2 - Eu tinha o jboss rodando em outra console, por isso ele reclamou das portas;

3 - Valeu a dica.

caso alguem tenha problemas similares: http://alexander.holbreich.org/2011/11/jboss-7-setup-linux/

Criado 6 de junho de 2013
Ultima resposta 6 de jun. de 2013
Respostas 2
Participantes 2

Topicos relacionados

Qual um salário para Analista Programador Java jr.? 60 respostas Exemplo de Java2D - Simulador de Autômatos 30 respostas Simulador de Futebol 31 respostas Arquivos "fantasmas" 18 respostas Curso superior correto para futuro programador 13 respostas
Alura Git Flow: entenda o que é, como e quando utilizar Entenda o que é Git Flow, como funciona seu fluxo com branches como Master, Develop, Feature, Release e Hotfix, além de vantagens e desvantagens.
Fiap Graduacao em Tecnologia — FIAP Analise e Desenvolvimento de Sistemas, Engenharia de Software e mais