[Beginners Corner] - Re: Cant deply an .ear file into the JBOSS.
by muggels_mark
I'm also getting the same parse exceptions trying to deploy the mule-examples.war file to a freshly installed 5.0.1GA. BTW - this works fine on 4.2.3GA.
Thanks - Mark
11:29:54,905 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/j2ee/dtds/ejb
-jar_1_1.dtd
11:30:01,595 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/D/jboss-5.0.1.GA/server/default
/deploy/mule-examples.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/D/jboss-5.0.1.GA/server/defaul
t/deploy/mule-examples.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:269)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWith
Output.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(Thread.java:595)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Connection timed out: connect
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(AbstractParsingDepl
oyerWithOutput.java:323)
... 22 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:520)
at java.net.Socket.connect(Socket.java:470)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
at sun.net.www.http.HttpClient.(HttpClient.java:231)
at sun.net.www.http.HttpClient.New(HttpClient.java:304)
at sun.net.www.http.HttpClient.New(HttpClient.java:321)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.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
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229129#4229129
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229129
16 years, 12 months
[Beginners Corner] - Problems Deploying Mule in 5.0.1GA
by muggels_mark
We're moving from WebLogic to JBoss and I'm trying to deploy the Mule ESB as a webapp into 5.0.1. I've dropped the war into the server/default/deploy folder and get the following error.
10:27:46,655 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd
10:27:52,751 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/D/jboss-5.0.1.GA/server/default/deploy/muleexamples.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/D/jboss-5.0.1.GA/server/defaul
t/deploy/mule-examples.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
with a root cause of
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Connection timed out: connect
Anyone know why. I can post more of the exceptions if needed.
By the way, I grabbed 4.2.3GA and the exact same Mule .war with the exact same deployment procedure works fine.
Thanks - Mark
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229118#4229118
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229118
16 years, 12 months
[JBoss Cache: Core Edition] - Re: JBoss cache instances fail to join cluster after bounce
by setatum
Well I just realized something that may be important. Originally I had tried using Pojo Cache for our implementation but ran into serious memory leak issues. I switched the implementation to use core cache, and this got rid of our memory leak problems.
However, the config file we use now is based on the config file from section 8.2 of the Pojo Cache User's Guide. Looking it this and comparing it to the configuration files from section 12.1 of the Core Cache User's Guide, it is totally different! However, core cache seems to load this configuration file ok (if I intentionally mess up the file format, the loader complains).
I'll now attempt to setup a new configuration file based on the core cache examples.
Is there a tuning guide separate from the User's Guide which recommends settings based on your setup? For example, my setup is 3 servers all close together on a high speed network, where speed is more important than throughput (our cached datasets are currently very small). The instances themselves should be reliable, but if an instance properly shuts itself down with stop/destroy for ~5 minutes and then attempts to rejoin the group, it should be allowed to do so (this seems to be my problem now).
-Scott
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229116#4229116
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229116
16 years, 12 months