Problemas ao migrar projeto WEB do tomcat 6 para o jboss 6

5 de setembro de 2011 11 respostas

Kleber-rr 5 de setembro de 2011

Olá gujeiros, bom dia a todos.

Estou passando por uma dificuldade em migrar minha aplicação web do tomcat 6 para o jboss 6, por motivos de força maior...

já fiz a instalação do jboss no eclipse, seguindo o tutorial do Bruno (http://brunorota.wordpress.com/2011/05/04/instalar-jboss-6-no-eclipse/). Até aqui tudo certo.

Removi o tomcat 6, instalei o jboss 6 conforme o orientado no tutorial acima citado, adicionei o projeto, corrigi as libraries do build path do projeto, marquei o jboss 6 Runtime como default nas propriedades do projeto web, apliquei e em seguida, tentei inicializar o servidor, porém, logo de cara ele me dá um erro:

Publishing to JBoss 6.0 Runtime Server ... has encountered a problem. 
An internal error occurred during: "Publishing to JBoss 6.0 Runtime Server...".
org/jboss/ide/eclipse/as/core/extensions/events/ServerLog

E depois de 450 segundos, me retorna esse outro erro:

Starting JBoss 6.0 Runtime Server: 
Server JBoss 6.0 Runtime Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor.

Stoping JBoss 6.0 Runtime Server: 
An internal error occurred during: "Stopping JBoss 6.0 Runtime Server".
java.lang.NoClassDefFoundError: org/jboss/ide/eclipse/as/core/extensions/events/ServerLog

No console do eclipse, me aparece esse log, porém sem erro algum:

11:34:10,159 INFO  [AbstractJBossASServerBase] Server Configuration:

	JBOSS_HOME URL: file:/home/viper/workspace/jboss-6.0.0.Final/
	Bootstrap: $JBOSS_HOME/server/standard/conf/bootstrap.xml
	Common Base: $JBOSS_HOME/common/
	Common Library: $JBOSS_HOME/common/lib/
	Server Name: standard
	Server Base: $JBOSS_HOME/server/
	Server Library: $JBOSS_HOME/server/standard/lib/
	Server Config: $JBOSS_HOME/server/standard/conf/
	Server Home: $JBOSS_HOME/server/standard/
	Server Data: $JBOSS_HOME/server/standard/data
	Server Log: $JBOSS_HOME/server/standard/log/
	Server Temp: $JBOSS_HOME/server/standard/tmp

11:34:10,168 INFO  [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]
11:34:14,262 INFO  [ServerInfo] Java version: 1.6.0_18,Sun Microsystems Inc.
11:34:14,262 INFO  [ServerInfo] Java Runtime: OpenJDK Runtime Environment (build 1.6.0_18-b18)
11:34:14,262 INFO  [ServerInfo] Java VM: OpenJDK Server VM 16.0-b13,Sun Microsystems Inc.
11:34:14,263 INFO  [ServerInfo] OS-System: Linux 2.6.28-15-generic,i386
11:34:14,264 INFO  [ServerInfo] VM arguments: -Dprogram.name=JBossTools: JBoss 6.0 Runtime -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=/home/viper/workspace/jboss-6.0.0.Final/lib/endorsed -Djava.library.path=/home/viper/workspace/jboss-6.0.0.Final/bin/native: -Dfile.encoding=UTF-8 
11:34:14,420 INFO  [JMXKernel] Legacy JMX core initialized
11:34:25,934 INFO  [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA
11:34:27,919 INFO  [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]
11:34:35,526 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
11:34:41,368 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
11:34:42,021 WARN  [config] jacorb.home unset! Will use '.'
11:34:42,021 WARN  [config] File ./jacorb.properties for configuration jacorb not found
11:34:42,023 INFO  [config] configuration jacorb loaded from classpath
11:34:42,283 INFO  [orb] Property "jacorb.hashtable_class" is set to: java.util.Hashtable
11:34:42,397 WARN  [config] jacorb.home unset! Will use '.'
11:34:42,398 WARN  [config] File ./jacorb.properties for configuration jacorb not found
11:34:42,399 INFO  [config] configuration jacorb loaded from classpath
11:34:42,400 INFO  [singleton] created ORBSingleton
11:34:42,708 INFO  [interceptors] InterceptorManager started with 2 Server Interceptors, 2 Client Interceptors and 4 IOR Interceptors
11:34:42,992 INFO  [orb] ORB run
11:34:43,303 INFO  [JMXConnector] starting JMXConnector on host localhost:1090
11:34:43,539 INFO  [poa] oid: 
72 6F 6F 74                                                 root
object is activated
11:34:43,913 INFO  [CorbaNamingService] CORBA Naming Started
11:34:43,928 INFO  [MailService] Mail Service bound to java:/Mail
11:34:45,898 INFO  [HornetQServerImpl] live server is starting..
11:34:46,142 INFO  [JournalStorageManager] Using NIO Journal
11:34:46,215 WARNING [HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
11:34:48,116 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE protocol
11:34:48,171 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455 for CORE protocol
11:34:48,178 INFO  [HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started
11:34:48,275 INFO  [WebService] Using RMI server codebase: http://localhost:8083/
11:34:48,605 INFO  [jbossatx] ARJUNA-32010 JBossTS Recovery Service (tag: JBOSSTS_4_14_0_Final) - JBoss Inc.
11:34:48,612 INFO  [arjuna] ARJUNA-12324 Start RecoveryActivators
11:34:48,640 INFO  [arjuna] ARJUNA-12296 ExpiredEntryMonitor running at Seg, 5 Set 2011 11:34:48
11:34:48,753 INFO  [arjuna] ARJUNA-12310 Recovery manager listening on endpoint 127.0.0.1:4712
11:34:48,755 INFO  [arjuna] ARJUNA-12344 RecoveryManagerImple is ready on port 4712
11:34:48,756 INFO  [jbossatx] ARJUNA-32013 Starting transaction recovery manager
11:34:48,786 INFO  [arjuna] ARJUNA-12163 Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 4713
11:34:48,788 INFO  [arjuna] ARJUNA-12337 TransactionStatusManagerItem host: 127.0.0.1 port: 4713
11:34:48,847 INFO  [arjuna] ARJUNA-12170 TransactionStatusManager started on port 4713 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
11:34:48,993 INFO  [jbossatx] ARJUNA-32017 JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_14_0_Final) - JBoss Inc.
11:34:49,104 INFO  [arjuna] ARJUNA-12202 registering bean jboss.jta:type=ObjectStore.
11:34:50,191 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/viper/workspace/jboss-6.0.0.Final/bin/native:
11:34:50,599 INFO  [ModClusterService] Initializing mod_cluster 1.1.0.Final
11:34:50,734 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/standard/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
11:34:50,796 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/standard/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
11:34:50,824 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/standard/deploy/jms-ra.rar/META-INF/ra.xml
11:34:50,857 INFO  [HornetQResourceAdapter] HornetQ resource adaptor started
11:34:51,639 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
11:34:52,069 INFO  [TomcatDeployment] deploy, ctxPath=/juddi
11:34:52,657 INFO  [RegistryServlet] Loading jUDDI configuration.
11:34:52,684 INFO  [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
11:34:52,684 INFO  [RegistryServlet] Initializing jUDDI components.
11:34:53,131 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
11:34:53,547 INFO  [xnio] XNIO Version 2.1.0.CR2
11:34:53,562 INFO  [nio] XNIO NIO Implementation Version 2.1.0.CR2
11:34:53,950 INFO  [remoting] JBoss Remoting version 3.1.0.Beta2
11:34:54,144 INFO  [TomcatDeployment] deploy, ctxPath=/
11:34:54,194 INFO  [service] Removing bootstrap log handlers
11:34:54,322 INFO  [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
11:34:54,326 INFO  [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
11:34:54,327 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 44s:150ms

Já tentei todas as opções dentro do JBoss Runtime, em window/preferences, mas todas deram o mesmo problema.

Alguma dica pessoal?? Eu não deveria realizar alguma alteração no web.xml?

Agradeço a todos.

11 Respostas

Vini_Fernandes 5 de set. de 2011

Ola, pelo o que eu li, o seu servidor necessita mais de 450 segundos para inicializar, já que esse comportamento esta descrito na seguinte linha so seu log:

Server JBoss 6.0 Runtime Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor.

Para isso voce deve ir até a aba “Servers” e dar um clique duplo. Depois para configurar o “timeout” do seu JBoss.

Kleber-rr 5 de set. de 2011

Vini, obrigado por responder.

Fiz o que sugeriu, mas não resolveu… coloquei o timeout pra 800 segundos e nada…

Como eu disse, ele dá o primeiro erro logo de cara quando vc manda levantar o servidor…

Tá dificil…
Vlw.

Alexandre_Saudate 5 de set. de 2011

Pela descrição do problema como um todo, me parece que o plugin do Eclipse está com problemas para se conectar ao JBoss. Isso faz com que ele consiga mandar sinal para inicializar o servidor mas não consiga reconhecer se deu certo ou não. Ao meu ver, você deve conseguir trabalhar razoavelmente bem mesmo com esse problema, porque o processo de publish (pro JBoss) é feito de maneira independente do servidor ter sido inicializado ou não.

Tente reinstalar o plugin pro JBoss e, se não conseguir, considere usar o JBoss Developer Studio.

[]'s

Kleber-rr 6 de set. de 2011

asaudate:
Pela descrição do problema como um todo, me parece que o plugin do Eclipse está com problemas para se conectar ao JBoss. Isso faz com que ele consiga mandar sinal para inicializar o servidor mas não consiga reconhecer se deu certo ou não. Ao meu ver, você deve conseguir trabalhar razoavelmente bem mesmo com esse problema, porque o processo de publish (pro JBoss) é feito de maneira independente do servidor ter sido inicializado ou não.

Tente reinstalar o plugin pro JBoss e, se não conseguir, considere usar o JBoss Developer Studio.

[]'s

Obrigado por responder.

Amigo, segui sua recomendação, porém os erros de publisher e de timeout do servidor estourando os 450 segundos ainda persistem.

Criei um outro projeto web baseado no jboss (já que li em algum lugar que o recomendado é que o projeto seja criado com base naquele servidor de aplicação), porém, os erros ainda persistem…

Encontrei um post aqui no guj com este mesmo problema, porém sem solução.

Se houver mais alguma sugestão, agradeço.

Ótimo dia a todos.

Kleber-rr 8 de set. de 2011

Olá amigos, bom dia.

Creio que encontrei o problema do JBoss. Eu tinha baixado a versão 3.2.0 que era pro eclipse helios. Estou instalando agora a versão developer 3.3.0 para o eclipse indigo (que é o que uso).

Retorno para dizer se deu certo ou não.

FLws.

Kleber-rr 8 de set. de 2011

Realmente, o problema era aquele mesmo...

Agora, com o servidor jboss 6 levantado, está dando erro no deploy. Segue o log do erro.

08:45:35,397 INFO  [AbstractJBossASServerBase] Server Configuration:

	JBOSS_HOME URL: file:/home/viper/workspace/jboss-6.0.0.Final/
	Bootstrap: $JBOSS_HOME/server/default/conf/bootstrap.xml
	Common Base: $JBOSS_HOME/common/
	Common Library: $JBOSS_HOME/common/lib/
	Server Name: default
	Server Base: $JBOSS_HOME/server/
	Server Library: $JBOSS_HOME/server/default/lib/
	Server Config: $JBOSS_HOME/server/default/conf/
	Server Home: $JBOSS_HOME/server/default/
	Server Data: $JBOSS_HOME/server/default/data/
	Server Log: $JBOSS_HOME/server/default/log/
	Server Temp: $JBOSS_HOME/server/default/tmp/

08:45:35,402 INFO  [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]
08:45:40,083 INFO  [ServerInfo] Java version: 1.6.0_18,Sun Microsystems Inc.
08:45:40,084 INFO  [ServerInfo] Java Runtime: OpenJDK Runtime Environment (build 1.6.0_18-b18)
08:45:40,084 INFO  [ServerInfo] Java VM: OpenJDK Server VM 16.0-b13,Sun Microsystems Inc.
08:45:40,084 INFO  [ServerInfo] OS-System: Linux 2.6.28-15-generic,i386
08:45:40,085 INFO  [ServerInfo] VM arguments: -Dprogram.name=JBossTools: JBoss 6.0 Runtime -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=/home/viper/workspace/jboss-6.0.0.Final/lib/endorsed -Djava.library.path=/home/viper/workspace/jboss-6.0.0.Final/bin/native -Dfile.encoding=UTF-8 
08:45:40,359 INFO  [JMXKernel] Legacy JMX core initialized
08:45:54,033 INFO  [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA
08:45:56,248 INFO  [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]
08:46:09,705 ERROR [AbstractKernelController] Error installing to Parse: name=vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:383) [:2.2.0.GA]
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343) [:2.2.0.GA]
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:315) [:2.2.0.GA]
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:255) [:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
	at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
	at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
	at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2]
	at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2]
	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]
	at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
	at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2]
	at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2]
	at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2]
	at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2]
	at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2]
	at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2]
	at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.0.0.Final]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
	at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war/WEB-INF/lib/jsf-impl-1.2.jar/META-INF/html_basic.tld@1625,19
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:224) [jbossxb.jar:2.0.3.GA]
	at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:178) [jbossxb.jar:2.0.3.GA]
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:257) [jbossxb.jar:2.0.3.GA]
	at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:231) [jbossxb.jar:2.0.3.GA]
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) [:2.2.0.GA]
	at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:64) [:6.0.0.Final]
	at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java:38) [:6.0.0.Final]
	at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) [:2.2.0.GA]
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.handleMultipleFiles(AbstractVFSParsingDeployer.java:446) [:2.2.0.GA]
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:319) [:2.2.0.GA]
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:376) [:2.2.0.GA]
	... 47 more
Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'type'. One of '{"http://java.sun.com/xml/ns/javaee":rtexprvalue, "http://java.sun.com/xml/ns/javaee":deferred-value, "http://java.sun.com/xml/ns/javaee":deferred-method, "http://java.sun.com/xml/ns/javaee":fragment}' is expected. @ vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war/WEB-INF/lib/jsf-impl-1.2.jar/META-INF/html_basic.tld[1625,19]
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.error(SaxJBossXBParser.java:416) [jbossxb.jar:2.0.3.GA]
	at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209) [jbossxb.jar:2.0.3.GA]
	... 57 more

08:46:10,081 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
08:46:18,946 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
08:46:19,573 INFO  [JMXConnector] starting JMXConnector on host localhost:1090
08:46:20,083 INFO  [MailService] Mail Service bound to java:/Mail
08:46:22,831 INFO  [HornetQServerImpl] live server is starting..
08:46:23,051 INFO  [JournalStorageManager] Using NIO Journal
08:46:23,119 WARNING [HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
08:46:25,001 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455 for CORE protocol
08:46:25,003 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE protocol
08:46:25,024 INFO  [HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started
08:46:25,194 INFO  [WebService] Using RMI server codebase: http://localhost:8083/
08:46:25,759 INFO  [jbossatx] ARJUNA-32010 JBossTS Recovery Service (tag: JBOSSTS_4_14_0_Final) - JBoss Inc.
08:46:25,769 INFO  [arjuna] ARJUNA-12324 Start RecoveryActivators
08:46:25,796 INFO  [arjuna] ARJUNA-12296 ExpiredEntryMonitor running at Qui, 8 Set 2011 08:46:25
08:46:25,946 INFO  [arjuna] ARJUNA-12310 Recovery manager listening on endpoint 127.0.0.1:4712
08:46:25,954 INFO  [arjuna] ARJUNA-12344 RecoveryManagerImple is ready on port 4712
08:46:25,955 INFO  [jbossatx] ARJUNA-32013 Starting transaction recovery manager
08:46:25,994 INFO  [arjuna] ARJUNA-12163 Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 4713
08:46:26,014 INFO  [arjuna] ARJUNA-12337 TransactionStatusManagerItem host: 127.0.0.1 port: 4713
08:46:26,095 INFO  [arjuna] ARJUNA-12170 TransactionStatusManager started on port 4713 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
08:46:26,203 INFO  [jbossatx] ARJUNA-32017 JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_14_0_Final) - JBoss Inc.
08:46:26,347 INFO  [arjuna] ARJUNA-12202 registering bean jboss.jta:type=ObjectStore.
08:46:27,166 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/viper/workspace/jboss-6.0.0.Final/bin/native
08:46:27,683 INFO  [TomcatDeployment] deploy, ctxPath=/invoker
08:46:28,728 INFO  [ModClusterService] Initializing mod_cluster 1.1.0.Final
08:46:28,908 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
08:46:28,980 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
08:46:29,010 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/jms-ra.rar/META-INF/ra.xml
08:46:29,053 INFO  [HornetQResourceAdapter] HornetQ resource adaptor started
08:46:29,065 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/mail-ra.rar/META-INF/ra.xml
08:46:29,135 INFO  [RARDeployment] Required license terms exist, view vfs:/home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
08:46:29,414 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2
08:46:29,533 INFO  [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
08:46:29,534 INFO  [QuartzScheduler] Quartz Scheduler v.1.8.3 created.
08:46:29,538 INFO  [RAMJobStore] RAMJobStore initialized.
08:46:29,542 INFO  [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.3) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

08:46:29,542 INFO  [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.
08:46:29,542 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.8.3
08:46:29,543 INFO  [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started.
08:46:30,263 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
08:46:30,696 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
08:46:31,360 INFO  [xnio] XNIO Version 2.1.0.CR2
08:46:31,380 INFO  [nio] XNIO NIO Implementation Version 2.1.0.CR2
08:46:31,818 INFO  [remoting] JBoss Remoting version 3.1.0.Beta2
08:46:32,015 INFO  [TomcatDeployment] deploy, ctxPath=/
08:46:32,313 INFO  [service] Removing bootstrap log handlers
08:46:32,541 ERROR [ProfileServiceBootstrap] Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS IN ERROR:
  Deployment "vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war" is in error due to the following reason(s): org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'type'. One of '{"http://java.sun.com/xml/ns/javaee":rtexprvalue, "http://java.sun.com/xml/ns/javaee":deferred-value, "http://java.sun.com/xml/ns/javaee":deferred-method, "http://java.sun.com/xml/ns/javaee":fragment}' is expected. @ vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war/WEB-INF/lib/jsf-impl-1.2.jar/META-INF/html_basic.tld[1625,19]

	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
	at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
	at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
	at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]

08:46:32,690 INFO  [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
08:46:32,811 INFO  [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
08:46:32,812 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 57s:403ms

Creio que deve ser problemas de imcompatibilidade do projeto, já que originalmente, ele foi criado para o tomcat 6.

Alguem já passou por isso e conseguiu solucionar?

Agradeço contato.

Kleber-rr 8 de set. de 2011

Pessoal, abri o arquivo “html_basic.tld” que foi mencionado no erro pelo eclipse, e o mesmo acusou o erro na linha 1625,19:

<type> java.lang.String </type>

Erro: vc-complex-type.2.4.a: Invalid content was found starting with element 'type'. One of '{"http://java.sun.com/xml/ns/ javaee":rtexprvalue, "http://java.sun.com/xml/ns/javaee":deferred-value, "http://java.sun.com/xml/ns/javaee":deferred-method, "http:// java.sun.com/xml/ns/javaee":fragment}' is expected.

O que devo fazer pessoal?

Vlw.

Kleber-rr 9 de set. de 2011

Olá Gujeiros, bom dia.

Removi as libs "jsf-api.jar" e "jsf-impl.jar" seguindo a orientação do Alessandro Lazarotti (http://www.guj.com.br/java/136259-migracao-de-servidor-tomcat-para-jboss), e o meu erro mudou para esse:

DEPLOYMENTS IN ERROR:
  Deployment "vfs:///home/viper/workspace/jboss-6.0.0.Final/server/default/deploy/segias.war" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema binding for QName taglib with schemaLocation=taglib

	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
	at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
	at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
	at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
	at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
	at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]

08:04:17,087 INFO  [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
08:04:17,095 INFO  [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
08:04:17,130 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final "Neo"] Started in 1m:34s:669ms

Está muito difícil encontrar alguma solução na net... será que eu vou ter que criar o projeto do zero?

Vlw.

Kleber-rr 12 de set. de 2011

Pessoal, criei um novo projeto baseado no jboss 6, transferi o meu projeto baseado no tomcat pra ele, realizando as modificações que foram se mostrando necessárias, dei um “limpa” nas lib’s que estavam conflitando com as do jboss, e consegui dar o deploy sem problemas. Entretanto, quando eu tento abrir a aplicação pelo navegador, me aparece este erro;

09:18:45,307 INFO [org.hibernate.cfg.Environment] Hibernate 3.2.5 09:18:45,311 INFO [org.hibernate.cfg.Environment] hibernate.properties not found 09:18:45,313 INFO [org.hibernate.cfg.Environment] Bytecode provider name : cglib 09:18:45,314 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling 09:18:45,320 INFO [org.hibernate.cfg.Configuration] configuring from resource: /hibernate.cfg.xml 09:18:45,320 INFO [org.hibernate.cfg.Configuration] Configuration resource: /hibernate.cfg.xml 09:18:45,330 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/segias4jboss].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception: org.hibernate.MappingException: An AnnotationConfiguration instance is required to use <mapping class="br.gov.rr.setrabes.estrutura.Funcionario"/> at org.hibernate.cfg.Configuration.parseMappingElement(Configuration.java:1600) [:3.2.5.ga] at org.hibernate.cfg.Configuration.parseSessionFactory(Configuration.java:1555) [:3.2.5.ga] at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1534) [:3.2.5.ga] at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1508) [:3.2.5.ga] at org.hibernate.cfg.Configuration.configure(Configuration.java:1428) [:3.2.5.ga] at org.hibernate.cfg.Configuration.configure(Configuration.java:1414) [:3.2.5.ga] at br.gov.rr.setrabes.util.HibernateUtil.<clinit>(HibernateUtil.java:21) [:] at br.gov.rr.setrabes.util.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:17) [:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]

Não fiz nenhuma modificação no meu hibernate.cfg.xml, desde o tomcat. Alguma alteração é necessária?

Obrigado.

Kleber-rr 14 de set. de 2011

Bom dia a todos.

Apesar de conseguir resolver esses problemas e fazer a aplicação rodar no JBoss, estou agora com uns problemas que até então, no tomcat 6 não existiam:

1- Fui obrigado a modificar no meu hibernate.cfg.xml o cache provider de org.hibernate.EhCacheProvider para net.sf.ehcache.hibernate.EhCacheProvider, devido ao hibernate-core não possuir essa classe. A partir daí, quando eu levanto a aplicação, ela só funciona se eu limpar a pasta do deploy do jboss, caso contrário, ela dá um erro acusando a linha que contem um sessionHttp.setAttribute (lembrando que no tomcat funcionava normalmente...);

2- Quando realizo uma consulta, é criada uma página com o resultado da consulta como nome seguida do .jsf, gerando o erro Http 404. Se atualizo a página, exibe normalmente.

HTTP Status 404 - /segias4jboss/pages/funcionario/[ANDREIA de tal, ...].jsf

type Status report

message /segias4jboss/pages/funcionario/[ANDREIA de tal, ...].jsf

description The requested resource (/segias4jboss/pages/funcionario/[ANDREIA de tal, ...].jsf) is not available.
JBoss Web/3.0.0-CR1

Estou achando que deve ser algum problema relacionado à versão do facelets ou do javax.servlet nativo do JBoss.

Se alguem puder contribuir, agradeço.

Ótimo dia a todos.

Kleber-rr 19 de set. de 2011

Eae pessoal, ninguém colabora?

Criado 5 de setembro de 2011

Ultima resposta 19 de set. de 2011

Respostas 11

Participantes 3

11 Respostas

Topicos relacionados