October 2009 - jboss-user - Jboss List Archives

[Clustering] - mod_cluster + 503 Service Temporarily Unavailable error

by babazs

Hi I use the latest mod_cluster(1.0.2 GA) with JBoss 5.1.0.GA server(all) clustered mod_cluster configuration. My testing envirnoment is: I created a loopback network interface for testing and added 3 ip addresses on Vista. 1:192.168.1.101:http load balancer 2:192.168.1.102:jboss node1 3:192.168.1.103:jboss node2 I get 503 Service Temporarily Unavailable error by the following cases, and I must wait about 30-60 sec to the httpd begin to route the request to the nodes. 1.when all jboss nodes started and the ear deploy process is finished.(I rarely get 503 error if I delete temp/works directories) 2.sometimes when either node is killed 3.when I killed a node, and try to restart the killed node. after ~30-60sec it begin to work all cases. Do you hava any idea? thx. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262110#4262110 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262110

16 years, 6 months

1
0
0 / 0

[jBPM Users] - JBPM process timers in Multi Server deployment -3.2.6

by sarish

Excuse me for the post, but have done enough searches and dont find info regarding this. Help needed!! I am hitting some issues related to using EJB Timer service for deployment, i have used Out of the box config recommended for enterprise deployment. First the details of Deployment 1. 3 jboss 5.1.0 servers hitting the same database 2. Using JBPM 3.2.6SP1 3. Oracle is database. 4. Using Database persisted timers(ejb2 timers), in the same database table TIMERS on all servers, below is the jbpm.cfg.xml | <jbpm-configuration> | | <jbpm-context> | <service name="persistence" factory="org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory" /> | <service name="message" factory="org.jbpm.msg.jms.JmsMessageServiceFactory" /> | <service name="scheduler" factory="org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory" /> | <service name="tx" factory="org.jbpm.tx.TxServiceFactory" /> |  | <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" /> | </jbpm-context> | |  | |  | <null name="jbpm.job.executor" /> | | </jbpm-configuration> | | EJB timer configuration is standard with database persistence JNDI name changed to Oracle database. Issues/Observations 1. I see no issues with async continuations(have 2-3 such async exclusive nodes in my process definition) 2. But for timers, a) Every once in a while these errors show up in server console,I see that this stack is present in more than one servers (which shows the timer fired on more than one server). b) On server startup StaleObject Exception related to timer save are seen in plenty.Note only one server is started and stopped at a time. I definitely feel that something is wrong with the way it is deployed, as when i looked into EJBTimerService code and i see that on server startup all timers persisted are deleted and reinserted. At this point if some other server already had a timer assigned(it is a thread based implementation), that timer would continue to run and another one would be started on server just restarted as well. And when time comes to fire, both servers would fire the timer. This would result in staleobject exception and hence certainly cause a problem. Sorry if my post was not clear, as i have avoided lot of details so that the post is readable. I can provide more info as required. But please recommend if something can be done for this. Also it can be treated as more of a problem with EJBTimerService, but again i am looking at ways in which i can make JBPM timers work in multi server environment. I can not use local database hsql, as that is not allowed in production enviroment. Worst case i am thinking of implementing a SingleServerPersistencePlugin for timers, and add an additional column with the server owner name, so that restoreTimers is clearly separated from all other servers. There is a definite problem with failover in such implementation but better get something working then nothing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262109#4262109 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262109

16 years, 6 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Undeploying multiple wars inside an ear causes NameAlrea

by daniele.ulrich

"jaikiran" wrote : If it's possible, could you please attach the application which reproduces this issue, to that JIRA? Sorry, this is not possible because there are a) too many dependencies and b) I am not allowed to post code of the enterprise I'm working for. It is exactly the same behaviour like described in https://jira.jboss.org/jira/browse/JBAS-7092, the first *.war gets deployed but on deploying the second ".war the exception occurs and the deployment of the following components stops. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262108#4262108 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262108

16 years, 6 months

1
0
0 / 0

[Installation, Configuration & Deployment] - unable to deploy app in jboss 5

by maruthi.sura

Hi All, when am trying to deploy the spring app in jboss 5 .i am getting the following error.Please any body help me in resolve this issue | | 14:08:16,584 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/les/WEB-INF/classes/applicationContext-hibernate.xml state=Not Installed mode=Manual requiredState=Parse | org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/les/WEB-INF/classes/applicationContext-hibernate.xml | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) | 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:1631) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) | 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:702) | at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) | at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) | at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) | at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) | 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.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) | at org.jboss.Main.boot(Main.java:221) | at org.jboss.Main$1.run(Main.java:556) | at java.lang.Thread.run(Unknown Source) | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://www.springframework.org/dtd/spring-beans.dtd | 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.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) | at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:355) | ... 33 more | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://www.springframework.org/dtd/spring-beans.dtd | at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:293) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:274) | 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.dtd.XMLDTDValidator.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) | ... 41 more | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 45:3 The markup in the document preceding the root element must be well-formed. | at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40) | at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source) | at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source) | at org.jboss.xb.binding.Util.loadSchema(Util.java:395) | at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:176) | at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:147) | at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:285) | ... 57 more | | | Thanks in Advance Maruthi Pramod Sura View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262106#4262106 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262106

16 years, 6 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: JBoss 4.2.2 Deployment/class loader problem

by chrismm

For various reasons each EJB is in its own jar file, all the jar files are in the ear file in the deploy directory. Strange thing is it dosnt always happen. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262105#4262105 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262105

16 years, 6 months

1
0
0 / 0

[Installation, Configuration & Deployment] - AS 5.1.0.GA fails to parse Spring schemas, on AS 4.2.3.GA al

by nesyarug

Hi, I'm trying to migrate my Spring-based webapp from JBoss AS 4.2.3.GA to JBoss AS 5.1.0.GA. I'm running into the following on startup: Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to parse schema for nsURI=http://www.springframework.org/schema/context, baseURI=null, schemaLocation=null Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for nsURI=http://www.springframework.org/schema/context, baseURI=null, schemaLocation=null Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 1:55 White spaces are required between publicId and systemId. Would anyone here know why? This is the header of for example applicationContext.xml: <?xml version="1.0" encoding="UTF-8"?> | <beans | xmlns="http://www.springframework.org/schema/beans" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xmlns:context="http://www.springframework.org/schema/context" | xmlns:aop="http://www.springframework.org/schema/aop" | xsi:schemaLocation=" | http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd | http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd | http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd"> Many thanks for your support, Nes View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262103#4262103 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262103

16 years, 6 months

1
0
0 / 0

[jBPM Users] - Re: Does the jBPM deployer works?

by camunda

If he want to deploy bar files, he is talking about jbpm 4. The deployer works, but not yet how it should in the end (the lifecycle is not yet clear). It is marked as experimental at the moment. Better deploy via Ant for the moment... Cheers Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262102#4262102 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262102

16 years, 6 months

1
0
0 / 0

[JBoss Messaging Users] - Re: Connection pool for ClusteredConnectionFactory, how to ?

by timfox

http://www.jboss.org/community/wiki/ShouldIcacheJMSconnectionsandJMSsessions View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262099#4262099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262099

16 years, 6 months

1
0
0 / 0

[JBoss Messaging Users] - Re: Connection pool for ClusteredConnectionFactory, how to ?

by bershath27

"roman.mandeleil(a)gmail.com" wrote : "timfox" wrote : If you're using a stateless session bean that means you're running on a server so you can just use JCA pooling. | | | | There are various wiki pages on this. | | | You mean: to pool JMS stub with JCA it interesting , have you tried it ? Tim is referring to the JMS session pool. In other words, obtaining connections from the factory bound at java:/JmsXA. Like Tim has clearly stated,there are n+1 examples + wiki's on the web..forum references etc etc View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262098#4262098 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262098

16 years, 6 months

1
0
0 / 0

[JBoss Messaging Users] - Re: Connection pool for ClusteredConnectionFactory, how to ?

by timfox

This is actually mandated by the JEE spec. Any JMS connections you create from a SLSB must be created (and pooled) by a JCA managed connection factory. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262097#4262097 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262097

16 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user October 2009