-
1. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
rpatel@salmon.com wrote:
I tried to hot deploy the ear but their isnt any option to provide custom config.xml as we can easily provide in 10gAS using -Dslim.config option.
For hot deployment, you can just "touch" (i.e. change the last modified time) of the top level deployment descriptor of the application. For an .ear, it's the META-INF/application.xml and for .war it's the WEB-INF/web.xml.
-
2. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hi,
Thanks for your immediate reply.
I didnt get your context for application.xml for .ear and web.xml for .war. the J2ee app is deployed in the form of .ear and within .ear there is a web module for web interface. My application depends on the config.xml which we supply it during startup. the config.xml has got parameters and values required by the application. I am not sure how do I deploy application with an option to feed the config xml during startup.
regards
Raj
-
3. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hmm, i misunderstood your question then. You mentioned you wanted hot deployment, so i thought you wanted to redeploy your application when the server is still started.
rpatel@salmon.com wrote:
My application depends on the config.xml which we supply it during startup. the config.xml has got parameters and values required by the application. I am not sure how do I deploy application with an option to feed the config xml during startup.
So you want to pass the location of the config.xml file (which is NOT packaged in the .ear) to your application?
-
4. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hi,
Thats right, I want to deploy ear and want to feed config.xml to it which it loads after deployment (startup). In Oracle 10gAS, its very easy as you can set -Dslim.config in the startup parameters for OC4J and then when you deploy ear into it using admin_client.jar (I am missing such type of command line tool), it unpack the ear and war inside it, deploy/compile the EJB's inside it and then during startup, it reads/parse the config.xml file and connect to the database, after which you can load the application homepage.
I am sure JBoss ia capable enuff to host enterprise application, may be I have not done much of study or lack of my knowledge.
Wait, i have an idea, can I create another application instance of JBoss and in its $JBOSS_HOME/bin/run.conf script, I can specify the -Dslim.config parameter in the JAVA_OPTS. I think, it should work. We use to do the same in standalone OC4J before using full blown ORacle 10gAS.
regards
Raj
-
5. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
rpatel@salmon.com wrote:
Wait, i have an idea, can I create another application instance of JBoss and in its $JBOSS_HOME/bin/run.conf script, I can specify the -Dslim.config parameter in the JAVA_OPTS. I think, it should work.
Yes, that's what you have to do. Then it's upto your code to use that slim.config system property to do whatever it wants to do with it (in this case read a file from that location).
-
6. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hi,
Thanks a lot... I'll try and will update the post with the results and issues.
regards
Raj
-
7. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hi,
I tried to feed the config.xml in run.conf and it worked fine but deploying error using hot deployment didnt work and have got no idea what the error is pointing to. See if you can help me please:
java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/LOIS_Web.war/
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/" is in error due to the following reason(s): java.lang.IllegalArgumentException: Wrong arguments. setLoadOnStartup for target org.jboss.metadata.web.spec.ServletMetaData@2c45f9ae expected=[int] actual=[java.lang.String]
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:120)
at org.rhq.plugins.jbossas5.AbstractManagedDeploymentComponent.invokeOperation(AbstractManagedDeploymentComponent.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/LOIS_Web.war/
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.04.ear/" is in error due to the following reason(s): java.lang.IllegalArgumentException: Wrong arguments. setLoadOnStartup for target org.jboss.metadata.web.spec.ServletMetaData@2c45f9ae expected=[int] actual=[java.lang.String]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
... 15 more
-
8. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Post the contents of your LOIS_Web.war/WEB-INF/web.xml. I am mainly interested in the load-on-startup elements in that file. And when you post logs or xml content or code, please remember to use the forum editor formatting options.
-
9. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"> <web-app id="WebApp"> <display-name>LOIS Web</display-name> <servlet> <servlet-name>LOISNavigationServlet</servlet-name> <display-name>LOISNavigationServlet</display-name> <servlet-class>com.lois.servlets.LOISNavigationServlet</servlet-class> <load-on-startup/> </servlet> <servlet> <servlet-name>Apache-AxisServlet</servlet-name> <display-name>Apache-AxisServlet</display-name> <servlet-class>com.lois.servlets.WsServlet</servlet-class> <load-on-startup/> </servlet> <servlet> <servlet-name>BatchStartServlet</servlet-name> <display-name>BatchStartServlet</display-name> <description></description> <servlet-class>com.lois.servlets.BatchStartServlet</servlet-class> </servlet> <servlet> <servlet-name>LiveCycleServlet</servlet-name> <display-name>LiveCycleServlet</display-name> <description></description> <servlet-class>com.lois.servlets.LiveCycleServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>LOISNavigationServlet</servlet-name> <url-pattern>/nav</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Apache-AxisServlet</servlet-name> <url-pattern>/ws/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>BatchStartServlet</servlet-name> <url-pattern>/batchstarter</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>LiveCycleServlet</servlet-name> <url-pattern>/livecycle</url-pattern> </servlet-mapping> <session-config> <session-timeout>60</session-timeout> </session-config> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> <error-page> <error-code>404</error-code> <location>/nav?errortype=404</location> </error-page> </web-app>
-
10. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
This looks like a bug in the metadata creation for ServletMetaData. As per the web-app dtd/xsd:
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.So what you have in the web.xml:
<load-on-startup/>is valid. However, the metadata creation is expecting a int value to be present for this element.
As a workaround, set some positive value (as explained in the xsd/dtd) for this element. You have a couple of startup servlets in the web.xml, so you will have to set unique values for each of them. Something like:
<load-on-startup>1</load-on-startup>
-
11. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
jaikiran wrote:
This looks like a bug in the metadata creation for ServletMetaData.
-
12. Re: Unable to port J2EE app from Oracle 10gAS to JBOSS 5
Hi,
This is not working again:
2010-03-01 11:31:43,153 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.07/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/opt/JBoss/jboss-5.1.0.GA/server/default/deploy/riskwrite-5.7.07/ 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(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: QName load-on-startup error setting property loadOnStartup with value to org.jboss.metadata.web.spec.ServletMetaData@570848003 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:188) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) ... 33 more Caused by: java.lang.RuntimeException: QName load-on-startup error setting property loadOnStartup with value to org.jboss.metadata.web.spec.ServletMetaData@570848003 at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:65) at org.jboss.xb.builder.runtime.AbstractPropertyHandler.doHandle(AbstractPropertyHandler.java:98) at org.jboss.xb.builder.runtime.BeanHandler.setParent(BeanHandler.java:207) at org.jboss.xb.builder.runtime.BuilderParticleHandler.setParent(BuilderParticleHandler.java:80) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.setParent(SundayContentHandler.java:1328) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1227) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:236) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:373) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(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: java.lang.IllegalArgumentException: Wrong arguments. setLoadOnStartup for target org.jboss.metadata.web.spec.ServletMetaData@1c7cd70c expected=[int] actual=[java.lang.String] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:69) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) at org.jboss.beans.info.plugins.DefaultPropertyInfo.set(DefaultPropertyInfo.java:143) at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95) at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61) ... 61 more 2010-03-01 11:31:49,606 WARN [org.jboss.system.server.profileservice.persistence.deployer.ProfileServicePersistenceDeployer] (main) Failed to update the persisted attachment information java.lang.IllegalStateException: could not find deployment XAOracleDS at org.jboss.resource.deployers.management.MCFDGComponentMapper.getComponent(MCFDGComponentMapper.java:79) at org.jboss.system.server.profileservice.persistence.component.AbstractComponentMapper.updateComponent(AbstractComponentMapper.java:163) at org.jboss.system.server.profileservice.persistence.component.AbstractComponentMapper.restoreComponent(AbstractComponentMapper.java:83) at org.jboss.system.server.profileservice.persistence.AbstractPersistenceFactory.restorePersistenceRoot(AbstractPersistenceFactory.java:100) at org.jboss.system.server.profileservice.persistence.deployer.ProfileServicePersistenceDeployer.applyPersistentChanges(ProfileServicePersistenceDeployer.java:128) at org.jboss.system.server.profileservice.persistence.deployer.ProfileServicePersistenceDeployer.internalDeploy(ProfileServicePersistenceDeployer.java:93) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) 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(Thread.java:595)