IdentifiantMot de passe
Loading...
Mot de passe oublié ?Je m'inscris ! (gratuit)
Navigation

Inscrivez-vous gratuitement
pour pouvoir participer, suivre les réponses en temps réel, voter pour les messages, poser vos propres questions et recevoir la newsletter

Wildfly/JBoss Java Discussion :

probleme avec jbosse


Sujet :

Wildfly/JBoss Java

Vue hybride

Message précédent Message précédent   Message suivant Message suivant
  1. #1
    Membre confirmé
    Inscrit en
    Juillet 2009
    Messages
    81
    Détails du profil
    Informations personnelles :
    Âge : 37

    Informations forums :
    Inscription : Juillet 2009
    Messages : 81
    Par défaut probleme avec jbosse
    Salut,

    je travail avec jboss et ejb3 des que je le demarre il m'affiche ces erreurs:



    info
    info
    .....
    10:47:35,900 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/ state=Not Installed mode=Manual requiredState=Parse
    org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/
    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
    at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
    at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
    at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
    at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
    at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
    at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
    at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
    at org.jboss.Main.boot(Main.java:209)
    at org.jboss.Main$1.run(Main.java:547)
    at java.lang.Thread.run(Unknown Source)
    Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence
    at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
    at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
    at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
    at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
    at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
    at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
    at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
    at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
    at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323)
    ... 22 more
    Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
    at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
    at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
    at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
    at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
    at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
    ... 30 more
    10:47:42,029 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
    10:47:42,231 INFO [MailService] Mail Service bound to java:/Mail
    10:47:44,578 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
    10:47:44,604 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
    10:47:44,789 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
    10:47:44,789 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
    10:47:45,136 INFO [TransactionManagerService] Initializing recovery manager
    10:47:45,396 INFO [TransactionManagerService] Recovery manager configured
    10:47:45,396 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
    10:47:45,427 INFO [TransactionManagerService] Starting transaction recovery manager
    10:47:46,657 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080
    10:47:46,658 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
    10:47:46,658 INFO [StandardService] D�marrage du service jboss.web
    10:47:46,663 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
    10:47:46,730 INFO [Catalina] Server startup in 725 ms
    10:47:46,753 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
    10:47:47,470 INFO [TomcatDeployment] deploy, ctxPath=/web-console
    10:47:47,864 INFO [TomcatDeployment] deploy, ctxPath=/invoker
    10:47:48,034 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
    10:47:48,072 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
    10:47:48,102 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
    10:47:48,129 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
    10:47:48,160 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
    10:47:48,299 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
    10:47:48,334 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
    10:47:48,338 INFO [RAMJobStore] RAMJobStore initialized.
    10:47:48,338 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
    10:47:48,338 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
    10:47:48,339 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
    10:47:49,517 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'javaefaultDS'
    10:47:50,096 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
    10:47:50,255 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
    10:47:50,255 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1bd8575 started
    10:47:50,278 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
    10:47:50,287 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
    10:47:50,287 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1867584 started
    10:47:50,288 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
    10:47:50,288 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
    10:47:50,289 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
    10:47:50,289 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@250536 started
    10:47:50,291 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
    10:47:50,432 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
    10:47:50,461 INFO [TomcatDeployment] deploy, ctxPath=/
    10:47:50,525 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
    10:47:50,626 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

    DEPLOYMENTS IN ERROR:
    Deployment "vfszip:/C:/jboss-5.0.1.GA/server/default/deploy/Bdejb3.jar/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence

    10:47:50,641 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080
    10:47:50,714 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
    10:47:50,721 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 32s:724ms
    10:48:26,437 ERROR [STDERR] Failed to load preferences. Proceeding with defaults:
    10:51:02,124 ERROR [STDERR] Stopping.

    et il ne construit pas mes tables a partir les entity Bean
    Merci a vous

  2. #2
    Membre confirmé Avatar de yashiro
    Inscrit en
    Mars 2004
    Messages
    214
    Détails du profil
    Informations forums :
    Inscription : Mars 2004
    Messages : 214
    Par défaut
    Ce que je peux te proposer, c'est d'arrêter ton serveur, d'aller dans le répertoire de base de ton instance de serveur (default, all ou minimal), de supprimer les répertoires log, work et tmp. Puis d'aller dans ton répertoire de déploiement et de supprimer BdEjb3.jar.
    Une fois que tu as fait ces opérations, tu peux redémarrer ton serveur JBoss et reprendre tes déploiements.

Discussions similaires

  1. Probleme avec JBoss 4.2
    Par ramijrad dans le forum Wildfly/JBoss
    Réponses: 1
    Dernier message: 17/11/2010, 15h22
  2. probleme avec jboss tools 3 et eclipse 3.4.2
    Par belha00 dans le forum JSF
    Réponses: 5
    Dernier message: 10/05/2009, 09h52
  3. Probleme avec Jboss AOP
    Par DidierRock dans le forum Wildfly/JBoss
    Réponses: 6
    Dernier message: 26/01/2008, 12h25
  4. probleme avec jboss
    Par hind28 dans le forum Wildfly/JBoss
    Réponses: 1
    Dernier message: 07/02/2007, 12h11
  5. Problème avec JBoss
    Par fouad406 dans le forum Hibernate
    Réponses: 1
    Dernier message: 05/05/2005, 08h39

Partager

Partager
  • Envoyer la discussion sur Viadeo
  • Envoyer la discussion sur Twitter
  • Envoyer la discussion sur Google
  • Envoyer la discussion sur Facebook
  • Envoyer la discussion sur Digg
  • Envoyer la discussion sur Delicious
  • Envoyer la discussion sur MySpace
  • Envoyer la discussion sur Yahoo