[Resolvido]Migrando do Tomcat para o Jboss

Front-end
#1

Pessoal,

Possuo um aplicação web (Servlets + Jsp’s) que roda normalzinha no servidor tomcat. Surgiu a necessidade de mudar para o jboss. Assim, já baixei o jboss 7.1 aqui e gostaria de saber o que devo configurar antes para a aplicação funcionar no Jboss, que arquivos do Jboss devo configurar ? É só gerar o .war e colocar no Jboss ? Minha aplicação quando rodo no eclipse não conseguer dar o deploy.

[code]16:04:28,431 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit.“projeto.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war”
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [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(Unknown Source) [rt.jar:1.7.0_06]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_06]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_06]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/web.xml” at [4,5]
at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:114)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
… 5 more

16:04:28,439 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:04:28,440 ERROR [org.jboss.as] (MSC service thread 1-7) JBAS015875: JBoss AS 7.1.1.Final “Brontes” started (with errors) in 23278ms - Started 136 of 212 services (1 services failed or missing dependencies, 74 services are passive or on-demand)
16:04:28,441 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment “projeto.war” was rolled back with failure message {“JBAS014671: Failed services” => {“jboss.deployment.unit.“projeto.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war””}}
16:04:28,628 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment projeto.war in 186ms
16:04:28,629 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit.“projeto.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war”

16:04:28,631 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {“JBAS014653: Composite operation failed and was rolled back. Steps that failed:” => {“Operation step-2” => {“JBAS014671: Failed services” => {“jboss.deployment.unit.“projeto.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war””}}}}[/code]

Se possuirem algum tutorial ou material para que eu possa estudar, ficaria agradecido.

Obrigado

#2

Eu utilizo o jboss 4.2.3GA e sempre coloco o projeto.war na pasta deploy, ou seja, no caminho: jboss-4.2.3.GA\server\default\deploy.

  • Após colocar o projeto lá dentro, abra a overview do jboss, clicando duas vezes sobre o servidor jboss que foi adicionado no eclipse.
  • clique em Open launch configuration.
  • Selecione a aba source.
  • Clique em add.
  • Java Project.
  • Selecione seu projeto.
  • Ok.
  • Ok.
  • Agora só startar o jboss.
#3

Aqui usando jboss 7.1 não funciona. Sou iniciante no jboss, minha aplicação faz uso de banco de dados, devo configurar algo no jboss ?

#4

Olá rafrl13,

Você poderia postar o seu web.xml?

Abs

#5

E sim o ideal é que você deixe o JBoss gerenciar as suas conexões com o banco de dados. Então será necessário criar um datasource.

Vai postando as dúvidas que se eu souber vou te ajudando senão existem outras pessoas aqui muito boas.

Abs

#6

Jmag segue o meu xml.

[code]<?xml version="1.0" encoding="UTF-8"?>

<display-name>Sistema</display-name>
<distributable />
<filter>
	<filter-name>ResponseOverrideFilter</filter-name>
	<filter-class>org.displaytag.filter.ResponseOverrideFilter</filter-class>
</filter>
<filter-mapping>
	<filter-name>ResponseOverrideFilter</filter-name>
	<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
	<filter-name>ResponseOverrideFilter</filter-name>
	<url-pattern>*.jsp</url-pattern>
</filter-mapping>	<servlet>
	<servlet-name>ImageServlet</servlet-name>
	<servlet-class>net.sf.jasperreports.j2ee.servlets.ImageServlet</servlet-class>
</servlet>
<servlet>
	<description>This is the servlet needed for cache.type servlet, returns the packed resources</description>
	<display-name>PackServlet</display-name>
	<servlet-name>PackServlet</servlet-name>
	<servlet-class>net.sf.packtag.servlet.PackServlet</servlet-class>
</servlet>
<servlet>
	<servlet-name>teste</servlet-name>
	<servlet-class>Controleteste</servlet-class>
</servlet>
<servlet>
	<servlet-name>lista</servlet-name>
	<servlet-class>Lista</servlet-class>
</servlet>
<servlet>
	<servlet-name>controleteste1</servlet-name>
	<servlet-class>ControleTeste1</servlet-class>
</servlet>
<servlet>
	<servlet-name>controleteste2</servlet-name>
	<servlet-class>ControleTeste2</servlet-class>
</servlet>
<servlet>
	<servlet-name>controleteste3</servlet-name>
	<servlet-class>ControleTeste3</servlet-class>
</servlet>
<servlet>
	<servlet-name>cadastroTeste4</servlet-name>
	<servlet-class>crud.cad.Teste4</servlet-class>
</servlet>
<servlet>
	<servlet-name>controleautenticacao</servlet-name>
	<servlet-class>seguranca.ControleAutenticacao</servlet-class>
	<load-on-startup>1</load-on-startup>
</servlet>
    <servlet-mapping>
	<servlet-name>PackServlet</servlet-name>
	<url-pattern>*.pack</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controleteste1</servlet-name>
	<url-pattern>/controleteste1</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controleteste2</servlet-name>
	<url-pattern>/controleteste2</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>cadastroteste1</servlet-name>
	<url-pattern>/cadastroteste1</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controleteste3</servlet-name>
	<url-pattern>/controleteste4</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controlerelatorioteste1</servlet-name>
	<url-pattern>/controlerelatorioteste1</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controlerelatorioteste2</servlet-name>
	<url-pattern>/controlerelatorioteste2</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controlerelatorioteste3</servlet-name>
	<url-pattern>/controlerelatorioteste3</url-pattern>
</servlet-mapping>
<servlet-mapping>
	<servlet-name>controleautenticacao</servlet-name>
	<url-pattern>/controleautenticacao</url-pattern>
</servlet-mapping>

[/code]

#7

E ai rafrl13 blz?

Cara no seu web.xml troque essa declaração:

[code]

<?xml version="1.0" encoding="UTF-8"?>

[/code]

Por essa declaração:

<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">

Faz o deploy da sua aplicação e me diz se funcionou.

Vlw

#8

jmag agora está dando erro em um .jar da packtag que uso. Ainda não entendi o que fazer para resolver, estou olhando aqui. Se você saber o que pode ser.

[code]09:58:24,844 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
09:58:25,099 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
09:58:25,152 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final “Brontes” starting
09:58:26,326 INFO [org.xnio] XNIO Version 3.0.3.GA
09:58:26,326 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
09:58:26,337 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
09:58:26,347 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
09:58:26,372 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
09:58:26,375 INFO [org.jboss.as.configadmin] (ServerService Thread Pool – 25) JBAS016200: Activating ConfigAdmin Subsystem
09:58:26,388 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 29) JBAS010280: Activating Infinispan subsystem.
09:58:26,396 INFO [org.jboss.as.osgi] (ServerService Thread Pool – 37) JBAS011940: Activating OSGi Subsystem
09:58:26,418 INFO [org.jboss.as.webservices] (ServerService Thread Pool – 46) JBAS015537: Activating WebServices Extension
09:58:26,423 INFO [org.jboss.as.security] (ServerService Thread Pool – 42) JBAS013101: Activating Security Subsystem
09:58:26,490 INFO [org.jboss.as.naming] (ServerService Thread Pool – 36) JBAS011800: Activating Naming Subsystem
09:58:26,493 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
09:58:26,505 INFO [org.jboss.as.connector] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
09:58:26,579 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
09:58:26,584 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
09:58:26,691 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
09:58:26,762 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
09:58:27,111 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\M1\Desktop\jboss-as-7.1.1.Final\standalone\deployments
09:58:27,115 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on localhost/127.0.0.1:4447
09:58:27,115 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
09:58:27,294 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
09:58:27,294 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final “Brontes” started in 3022ms - Started 129 of 203 services (74 services are passive or on-demand)
09:58:27,324 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found projeto.war in deployment directory. To trigger deployment create a file called projeto.war.dodeploy
09:58:27,379 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of “projeto.war”
09:58:29,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry iText-toolbox.jar in “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/iText-2.1.1.jar” does not point to a valid jar for a Class-Path reference.
09:58:29,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry iText-toolbox-2.1.1.jar in “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/iText-2.1.1.jar” does not point to a valid jar for a Class-Path reference.
09:58:29,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry bcmail-jdk14-138.jar in “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/iText-2.1.1.jar” does not point to a valid jar for a Class-Path reference.
09:58:29,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry bcprov-jdk14-138.jar in “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/iText-2.1.1.jar” does not point to a valid jar for a Class-Path reference.
09:58:30,001 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xbean.jar in “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/rhino-1.6R7.jar” does not point to a valid jar for a Class-Path reference.
09:58:30,090 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.“projeto.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war”
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [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(Unknown Source) [rt.jar:1.7.0_06]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_06]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_06]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor “/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/packtag-3.7.jar/META-INF/packtag.tld” at [15,17]
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:128)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:107)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:83)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
… 5 more

09:58:30,100 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment “projeto.war” was rolled back with failure message {“JBAS014671: Failed services” => {“jboss.deployment.unit.“projeto.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war””}}
09:58:30,101 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit.“projeto.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war”

09:58:30,104 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {“JBAS014653: Composite operation failed and was rolled back. Steps that failed:” => {“Operation step-2” => {“JBAS014671: Failed services” => {“jboss.deployment.unit.“projeto.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.unit.“projeto.war”.PARSE: Failed to process phase PARSE of deployment “projeto.war””}}}}
09:58:30,199 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment projeto.war in 97ms[/code]

Valeu, muito obrigado.

#9

Então blz o web.xml foi resolvido… agora é algum tag do seu packtag.tld que tá dando pau…

JBAS018014: Failed to parse XML descriptor "/C:/Users/M1/Desktop/jboss-as-7.1.1.Final/standalone/deployments/projeto.war/WEB-INF/lib/packtag-3.7.jar/META-INF/packtag.tld"

Que jar é essse packtag-3.7.jar? é projeto seu mesmo ou é algum framework?

Abs

#10

É um framework mesmo.

#11

Tendi… é rafrl13 tenho que realizar alguns testes o problema é que hoje estou muito ocupado :confused:

O objetivo é fazer esse framework rodar no JBoss 7 :smiley:

Vai testando e tentando descobrir mais sobre a compatibilidade dele com o JBoss 7.

Mas hoje a noite bem a noite vou arrumar um tempinho pra testar rsrs

Abs

#12

jmag, tudo bem, muito obrigado pela sua ajuda.Eu entrei aqui no ponto .jar e no arquivo que está dando erro, segue ele para sua análise assim que der.

[code]<?xml version="1.0" encoding="UTF-8"?>

3.5 1.2 pack http://packtag.sf.net JSP pack:tag Library 
<tag>
	<name>script</name>
	<tag-class>net.sf.packtag.tag.ScriptTag</tag-class>
	<body-content>jsp</body-content>
	<attribute>
		<name>src</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
	<attribute>
		<name>enabled</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
	<attribute>
		<name>minify</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
</tag>

<tag>
	<name>style</name>
	<tag-class>net.sf.packtag.tag.StyleTag</tag-class>
	<body-content>jsp</body-content>
	<attribute>
		<name>src</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
	<attribute>
		<name>enabled</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
	<attribute>
		<name>minify</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
	<attribute>
		<name>media</name>
		<required>false</required>
		<rtexprvalue>true</rtexprvalue>
	</attribute>
</tag>

[/code]

Muito obrigado.

#13

jmag consegui resolver o meu problema. A minha aplicação utiliza o framework packtag 3.7. Andei pesquisando e vi que era um problema de interpretação do arquivo .tld do framework. Seguindo dicas fiz a atualização do packtag 3.7 para o 3.8 e ai o jboss interpretou corretamente. Agora estou começando os estudos para implantar aqui um cluster para duas máquinas diferentes, estive no seu blog e ate mandei um msg la sobre um material.

Abraços, obrigado

#14

Que Legal Rafael parabéns :slight_smile:

Desculpe nao ter visto sobre isso mas essa semana tá corrida demais rsrs

Eu vi a sua mensagem e já deixei um outro recado lá mesmo nos comentários… e sempre que precisar é só dizer :slight_smile:

Grande Abraço

#15