[Beginner's Corner] - DeploymentExeption in jboss 5.1
by mike tihonchik
mike tihonchik [http://community.jboss.org/people/mike.tihonchik] created the discussion
"DeploymentExeption in jboss 5.1"
To view the discussion, visit: http://community.jboss.org/message/584683#584683
--------------------------------------------------------------
I am getting error on the JBoss 5.1 start up:
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/dev/datatrak/branches/eae_reb
ase/deploy/datatrak.ear/abcfs.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:362)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:322)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:294)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWith
Output.java:234)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
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:
403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileServi
ce.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
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(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://java.sun.com/xml/ns/j2ee}web-a
pp is not bound as a global element.
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:
304)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:
286)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:348)
... 34 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://java.sun.com/xml/ns/j2ee}web-app is not bound a
s a global element.
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
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)
... 43 more
I have seen couple of discussions here pertaining to this problem, and most of them suggested changing web.xml file. This is my original web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http:/java.sun.com/dtd/web-app_2_3.dtd">
<listener>
<listener-class>
org.springframework.web.context.request.RequestContextListener
</listener-class>
</listener>
<servlet>
<servlet-name>springapp</servlet-name>
<servlet-class>com.abcfs.springsupport.ABCDispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>NavServlet</servlet-name>
<servlet-class>com.seqtek.pml.nav.NavServlet</servlet-class>
<init-param>
<param-name>PMLConfigFile</param-name>
<param-value>conf/pml-config.xml</param-value>
</init-param>
<init-param>
<!-- Point back to datatrak dir so that it doesn't default to jboss/server/default/bin -->
<param-name>PMLBaseDir</param-name>
<param-value>C:/dev/datatrak/trunk</param-value>
</init-param>
<init-param>
<param-name>logLevel</param-name>
<param-value>SEVERE</param-value>
</init-param>
<init-param>
<param-name>deleteEventsDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.scheduling.DeleteEventsDaemon</param-value>
</init-param>
<init-param>
<param-name>incrementalServiceDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.pos.IncrementalServiceDaemon</param-value>
</init-param>
<init-param>
<param-name>employeeEventSummaryDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.scheduling.EmployeeEventSummaryDaemon</param-value>
</init-param>
<init-param>
<param-name>autoRunClubAccountDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.pos.AutoRunClubAccountDaemon</param-value>
</init-param>
<init-param>
<param-name>reportDeamon</param-name>
<param-value>com.seqtek.abcfs.dt.reportwizard.ReportDeamon</param-value>
</init-param>
<init-param>
<param-name>reportDeamonThreads</param-name>
<param-value>1</param-value>
</init-param>
<init-param>
<param-name>load-on-startup</param-name>
<param-value>1</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
<servlet>
<servlet-name>SimplePdf</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.common.SimplePdf</servlet-class>
</servlet>
<servlet>
<servlet-name>DatatrakStatus</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.common.DatatrakStatus</servlet-class>
</servlet>
<servlet>
<servlet-name>GatewayListener</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.integration.GatewayListenerServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>dwr-invoker</servlet-name>
<display-name>DWR Servlet</display-name>
<servlet-class>org.directwebremoting.servlet.DwrServlet</servlet-class>
<!--INIT-PARAM = loglevel - The valid values are: FATAL, ERROR, WARN (the default), INFO and DEBUG.-->
<init-param>
<param-name>logLevel</param-name>
<param-value>FATAL</param-value>
</init-param>
<!--INIT-PARAM = debug enables TEST mode should not be used in live deployment (DEVELOPMENT ONLY)
as it could give an attacker a lot of information about the services that you export.-->
<!--
<init-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</init-param>
-->
</servlet>
<servlet-mapping>
<servlet-name>SimplePdf</servlet-name>
<url-pattern>/pdf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>DatatrakStatus</servlet-name>
<url-pattern>/datatrakstatus</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>GatewayListener</servlet-name>
<url-pattern>/gatewaylistener</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>NavServlet</servlet-name>
<url-pattern>*.pml</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>NavServlet</servlet-name>
<url-pattern>/NavServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>dwr-invoker</servlet-name>
<url-pattern>/dwr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>springapp</servlet-name>
<url-pattern>*.spr</url-pattern>
</servlet-mapping>
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/jsp/errorPage.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/jsp/errorPage.jsp</location>
</error-page>
<taglib>
<taglib-uri>widgets</taglib-uri>
<taglib-location>/jsp/widgets.tld</taglib-location>
</taglib>
</web-app>
I changed it to this:
<web-app version="2.5" 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_2_5.xsd">
however, problem still exists. Any suggestions????
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584683#584683]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Web Services] - ssl error on webservice invocation on jboss
by jmartin amaris
jmartin amaris [http://community.jboss.org/people/martin12] created the discussion
"ssl error on webservice invocation on jboss"
To view the discussion, visit: http://community.jboss.org/message/584468#584468
--------------------------------------------------------------
Hi, I'm using jboss 5.1.0 GA as an application server, I have two war applications deployed, both running perfectly. One application, app1.war, it's a web application, that, in some point invokes a webservice from the second one, app2.war. everything works fine until ssl is used.
Both applications are spring java based apps.
The correspondant keystore and truststore are properly installed, in order to a web browser can access the app1.war in its especified url.
The problem comes up, when the app2 webservice it's invoked from the app1, ssl error occurrs
Is it there solution for this situation? What's the necessary ssl configuration on the jboss server?
Thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584468#584468]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[Beginner's Corner] - Point the DeploymentScanner at my project (without copying project to the JBoss deploy folder)
by Kevin Sheedy
Kevin Sheedy [http://community.jboss.org/people/kevinsheedy] created the discussion
"Point the DeploymentScanner at my project (without copying project to the JBoss deploy folder)"
To view the discussion, visit: http://community.jboss.org/message/584639#584639
--------------------------------------------------------------
My understanding of the DeploymentScanner is that it scans the JBoss deploy folder for any folders or archives that end in .war or .ear etc. Depending on the file extension of the archive / folder, it picks a deployer to use eg WARDeployer or EARDeployer.
I'm working on a web project under CVS. We're using an exploded archive so that we can do hot-deploys to a local jBoss. Whenever we want to deploy anything, we use Ant to build and copy files from this folder:
C:\cvs\MyWebProject\
to this folder:
C:\JBoss_4.2.3.GA\.......\deploy\MyWebProject.war\
This copy step seems like a waste of time seeing as both folders are (practically) identical.
Is there any way to tell JBoss to treat "C:\cvs\MyWebProject\" as an exploded war?
(Using symlinks / junction points to keep the folders synched seems to work but I'd prefer a simpler solution that the whole team can share ie with config files that can be added to source control)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584639#584639]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
Ear deploy incredibly slow
by Anton Koldaev
Hi
JbossAS 4-2-3.GA + Seam
I'm trying to deploy my webapp with app.ear file. I put it into
/server/all/farm and its successfully deploing on all other nodes in about
10 minutes. But size of app.ear is just 30Mb. So why deploy proccess is so
slow? I can see how /server/all/tmp/app.ear is growing up from 1 to 30Mb -
it is very slow!
What additional information do I need to provide about my configuration?
--
Best regards,
Koldaev Anton
15 years, 2 months
[JBoss Tools] - Issue in CR1 visual editor
by henk de boer
henk de boer [http://community.jboss.org/people/henk53] created the discussion
"Issue in CR1 visual editor"
To view the discussion, visit: http://community.jboss.org/message/584073#584073
--------------------------------------------------------------
I'm using the JBoss tools visual editor (richfaces) on Eclipse 3.6.1 using JBoss tools 3.2 CR1 on Mac OS X 10.6 64 bits.
I encountered a few small oddities. First of all, after I upgraded from Beta 2 and let Eclipse restart, I opened an .xhtml page and got an editor with no tabs. In this editor, tag completion worked, but I could not navigate into a tag. I checked the name of the editor was "JBoss Tools HTML Editor".
When I restarted Eclipse this morning, I suddenly got a slightly different look in the editor. This time there were tabs. I verified the name was still the same and it was. This is what the tabs look like:
http://community.jboss.org/servlet/JiveServlet/showImage/2-584073-11265/o... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-584073-112...
This is by itself correct. Xulrunner and 64 bits just don't work together (except on Linux) and the fact that the editor now starts is perfect. But I wonder why the first time I didn't had these tabs and after the second restart they suddenly were there.
A few small things to consider here:
* Since Visual/Source and Preview is not available, it might be better to have Source as the default for this platform.
* The message is not really informative. It's just the exception message. I foresee a lot of support questions from users that might be prevented by having a clear message here.
* There is a link to the faq at the bottom, but it does not lead to any info about this situation.
Also strangely enough, I'm now able to navigate into tags, something I wasn't able to do before the second restart.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584073#584073]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
