Error loading deployment descriptors

Actually reading your message again, it seems you've already looked at the server.log. Is there anything else related to this problem in the server log than what you've already posted?

It's hard to tell what the problem is from the information you've posted. Are you able to reproduce this problem consistently? Is it possible for you to provide the war file for us to take a look?

One thing you could do from your side is to turn the log level of deployment to "FINE" and deploy the application again and see what additional information you have in the server.log.

To turn the log level to FINE:

1. Stop the server

2. in AS_INSTALL/domains/domain1/config/domain.xml, find the "module-log-levels" element, and change the deployment="INFO" to deployment="FINE"

3. Clean the server log, move the old server.log (AS_INSTALL/domains/domains1/logs/server.log) to something else.

4. Start the server again

5. Deploy your application and look at the server.log for additional information.

hongzhang at 2007-7-6 19:04:27 >

hong.zhang:

I forgot to add:

The results are 100% repeatable for two completely separate projects.

Both the project war files generated with JSC2_EA deploy instantly.

Both the project war files generated with JSC2 fail.

This has been repeated several times with the same results.

There is DEFINITELY something different between the "default" deployment between the two versions.

BeaverCleaver at 2007-7-6 19:04:27 >

Actually, I think the sun-web.xml file is missing from the war file.

I looked at it with winzip, That makes all the files visible regardless of path.

The file is not among the items in the war file.

But, if what you say is correct it may be a moot point if the file is not required.

This is becoming REALLY painful.

I thought the object was to be able to build a war file and deploy it on ANY of several supported servers.

I can only imagine what a nightmare this must be if I was to use any of the Non-Sun servers.

The problem with trying various "what-if's" is that I do not have easy access to the system with the server.

Each iteration takes at least a day to be able to test.

I downloaded and installed JSC2_Update1 to see if that would resolve the

issue. I can compile and create a war file, but it still does not have the sun-web.xml file that I can find.

The problem I have now, is that I can't get the bundled 8.2 server to start within the IDE.

I made sure that the bundled 8.1 server was turned off before I shut down JSC2 (just in case it did not shut it down automatically).

I did a standard download and install using all the defaults.

I can access my application, compile and create a war file, but I cannot start the 8.2 server manually from within the IDE or by having the application start it at build time.

The reason I bring this up is that I am running out of straws to grasp.

I wanted to download the 8.1 server on my machine so I could test locally, but it is no longer available in the PE version, just the Enterprise version.

So I figured I would download the 8.2 version and compatible JSC2_Update1 to have a complete develop and test deployment environment.

If that worked, I could upgrade the server to 8.2 and be done with it.

I FINALLY got everything downloaded and end up running into another wall.

Really frustrating...

I'll try what you suggest and see if that works.

Otherwise, my only options are:

1) Try and finish the migration to JSC2_Update1 with 8.2 server

2) Migrate my project to Eclipse or JDeveloper and hope that works. I know it will certainly be faster than trying to use JSC2

BeaverCleaver at 2007-7-6 19:04:27 >

Can't provide the war file, but I can give you a test secnario that you should be able to reproduce.

I just went through the exercise of bringing everything up on a virgin system.

Here are the steps we did:

1) Brand new Dell Inspiron 6600 laptop with NO other applications installed.

2) Downloaded and installed Application Server 8.2 - used defaults

3) Downloaded and installed JSC2_Update1. used defaualts.

4) Loaded "JumpStartCycles" from the demo package.

5) Built and exported "JumpStartCycles" war file using Export War File.

6) Started App Server.

7) Dropped war file into autodeploy folder

8) Deployment failed - dump listed below.

9) Went back to JSC2 and ran program with bundled server

10) Program ran ok

You can't get any cleaner or simpler than that.

Sample file worked on JSC and deployment failed for same sample on AppServer 8.2

[#|2006-05-24T12:23:44.499-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.to ols.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]

[#|2006-05-24T12:23:44.549-0500|INFO|sun-appserver-pe8.2|javax.enterprise.tools .launcher|_ThreadID=10;|

C:/j2sdk1.4.2_03\bin\java

-client

-Xmx512m

-XX:NewRatio=2

-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log

-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed

-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy

-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login .conf

-Dsun.rmi.dgc.server.gcInterval=3600000

-Dsun.rmi.dgc.client.gcInterval=3600000

-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks

-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks

-Djava.ext.dirs=C:/j2sdk1.4.2_03/jre/lib/ext;C:/Sun/AppServer/domains/domain1/l ib/ext;C:/Sun/AppServer/derby/lib

-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver

-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.App ServerMBeanServerBuilder

-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise .config.serverbeans.AppserverConfigEnvironmentFactory

-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar

-Dcom.sun.enterprise.taglisteners=jsf-impl.jar

-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SA XParserFactoryImpl

-Dcom.sun.aas.configName=server-config

-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter

-Ddomain.name=domain1

-Djmx.invoke.getters=true

-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.j axp.DocumentBuilderFactoryImpl

-Dcom.sun.aas.promptForIdentity=true

-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser

-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1

-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xslt c.trax.TransformerFactoryImpl

-Dcom.sun.aas.domainName=domain1

-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager

-Dproduct.name=Sun-Java-System/Application-Server

-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.js tl,javax.xml.bind,javax.help

-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config

-Djava.library.path=C:\j2sdk1.4.2_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun \AppServer\lib;C:\j2sdk1.4.2_03\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppS erver\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\ AppServer\bin;C:\Sun\AppServer\bin;C:\Program Files\Common Files\Sonic Shared;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\PROGRA~1\CA\Common\SCANEN~1;C:\Program Files\Visual Networks\Dial Analysis\;C:\Sun\AppServer\bin

-Dcom.sun.aas.instanceName=server

-Dcom.sun.aas.processLauncher=SE

-cp

C:/Sun/AppServer/lib/appserv-rt.jar;C:/j2sdk1.4.2_03/lib/tools.jar;C:/Sun/AppSe rver/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\ appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\apps erv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-u pgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\common s-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/ Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/l ib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-a pi.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C :/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/S un/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib \relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-a pi.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/ AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/li b/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar; C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar

com.sun.enterprise.server.PEMain

start

display

native|#]

[#|2006-05-24T12:23:56.577-0500|INFO|sun-appserver-pe8.2|javax.enterprise.resou rce.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]

[#|2006-05-24T12:23:56.607-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]

[#|2006-05-24T12:23:59.781-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.admin|_ThreadID=10;|ADM0047:The Platform MBeanServer is not available. Platform MBeans will not be available for browsing while using standard JMX Console.|#]

[#|2006-05-24T12:24:00.853-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]

[#|2006-05-24T12:24:01.624-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

[#|2006-05-24T12:24:03.316-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|Created virtual server server|#]

[#|2006-05-24T12:24:03.347-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|Created virtual server __asadmin|#]

[#|2006-05-24T12:24:06.221-0500|INFO|sun-appserver-pe8.2|javax.enterprise.resou rce.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]

[#|2006-05-24T12:24:06.301-0500|INFO|sun-appserver-pe8.2|javax.enterprise.resou rce.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]

[#|2006-05-24T12:24:06.301-0500|INFO|sun-appserver-pe8.2|javax.enterprise.resou rce.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]

[#|2006-05-24T12:24:08.113-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]

[#|2006-05-24T12:24:18.118-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]

[#|2006-05-24T12:24:20.101-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75267119433908224|#]

[#|2006-05-24T12:24:20.521-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]

[#|2006-05-24T12:24:21.032-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75267120291708928|#]

[#|2006-05-24T12:24:21.713-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]

[#|2006-05-24T12:24:21.713-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]

[#|2006-05-24T12:24:22.114-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]

[#|2006-05-24T12:24:22.424-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]|#]

[#|2006-05-24T12:24:23.065-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.sy stem.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]

[#|2006-05-24T12:24:23.265-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]|#]

[#|2006-05-24T12:24:23.275-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]|#]

[#|2006-05-24T12:24:23.285-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.sy stem.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]

[#|2006-05-24T12:24:23.285-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [/com_sun_web_ui]|#]

[#|2006-05-24T12:24:23.536-0500|INFO|sun-appserver-pe8.2|org.apache.catalina.co re.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]

[#|2006-05-24T12:24:30.135-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]

[#|2006-05-24T12:24:30.135-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]

[#|2006-05-24T12:24:30.145-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]

[#|2006-05-24T12:24:30.375-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]

[#|2006-05-24T12:24:30.375-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]

[#|2006-05-24T12:24:30.385-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]

[#|2006-05-24T12:24:30.455-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]

[#|2006-05-24T12:24:30.455-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]

[#|2006-05-24T12:24:30.455-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]

[#|2006-05-24T12:24:31.968-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.admin|_ThreadID=10;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://SPDemoLap.transcore.com:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]

[#|2006-05-24T12:24:31.968-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.admin|_ThreadID=10;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]

[#|2006-05-24T12:24:32.208-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.core|_ThreadID=10;|Application server startup complete.|#]

[#|2006-05-24T12:25:02.271-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.deployment|_ThreadID=11;|[AutoDeploy] Selecting file C:\Sun\AppServer\domains\domain1\autodeploy\JumpStartCycles.war for autodeployment.|#]

[#|2006-05-24T12:25:09.962-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.deployment|_ThreadID=11;|Total Deployment Time: 7060 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]

[#|2006-05-24T12:25:09.962-0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.sys tem.tools.deployment|_ThreadID=11;|Exception occured in J2EEC Phase

com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for JumpStartCycles -- null

at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:32 5)

at com.sun.enterprise.deployment.backend.WebModuleDeployer.deploy(WebModuleDeploye r.java:170)

at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDepl oyer.java:138)

at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:148)

at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPh ase.java:71)

at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeplo ymentService.java:639)

at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentSe rvice.java:185)

at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConf igMBean.java:519)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:305 )

at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:360 )

at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213 )

at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServer Interceptor.java:815)

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)

at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)

at $Proxy1.invoke(Unknown Source)

at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterce ptor.java:272)

at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(A utoDeployer.java:504)

at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployModule(AutoDeployer .java:485)

at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployWarModule(AutoDeplo yer.java:433)

at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployWarModule(AutoDeplo yer.java:426)

at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.ja va:246)

at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTas k.run(AutoDeployControllerImpl.java:345)

at java.util.TimerThread.mainLoop(Timer.java:432)

at java.util.TimerThread.run(Timer.java:382)

Caused by: java.lang.NullPointerException

at com.sun.enterprise.deployment.node.web.ServletMappingNode.setElementValue(Servl etMappingNode.java:55)

at com.sun.enterprise.deployment.node.SaxParserHandler.endElement(SaxParserHandler .java:355)

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Abstrac tSAXParser.java:585)

at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement (XMLNSDocumentScannerImpl.java:560)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragment ContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1555)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocu ment(XMLDocumentFragmentScannerImpl.java:341)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Config uration.java:828)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Config uration.java:758)

at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXP arser.java:1178)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescri ptorFile.java:256)

at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescri ptorFile.java:186)

at com.sun.enterprise.deployment.archivist.Archivist.readStandardDeploymentDescrip tor(Archivist.java:230)

at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Arc hivist.java:195)

at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:131)

at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(Applic ationArchivist.java:673)

at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(Applic ationArchivist.java:654)

at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:27 8)

... 31 more

|#]

[#|2006-05-24T12:25:09.962-0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.sys tem.tools.deployment|_ThreadID=11;|"DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for JumpStartCycles -- null

"|#]

[#|2006-05-24T12:25:09.972-0500|INFO|sun-appserver-pe8.2|javax.enterprise.syste m.tools.deployment|_ThreadID=11;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\domains\domain1\autodeploy\JumpStartCycles.war.|#]

BeaverCleaver at 2007-7-6 19:04:28 >

From the stack trace here:

Caused by: java.lang.NullPointerException

at com.sun.enterprise.deployment.node.web.ServletMappingNode.setElementValue(Servl etMappingNode.java:55)

I've looked at the source code, it's trying to parse the url-pattern element. Could you check if the url-pattern elements are composed correctly, and under the right parent elements? And is it possible to post your web.xml?

hongzhang at 2007-7-6 19:04:28 >

Could you please add the DOCTYPE (attached below) to your web.xml and try again? It should go right before the <web-app> element.

<!DOCTYPE web-app PUBLIC

"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"

"http://java.sun.com/dtd/web-app_2_3.dtd">

This allowed the application to deploy.

What did this do?

Does this have to be done Manually EVERY TIME?

Was this a setting that needed to be set somewhere?

Was I supposed to know this had to be done?

Is there any documentation that explains what this did?

Why wasn't this automatically done by JSC2?

It's ONLY been a week and a half of wasted time, so I guess I shouldn't complain.

BeaverCleavera at 2007-7-21 15:06:16 >

I DO appreciate your help with this. Especially since it is NOT an App Server problem.

However, you can understand my frustration when I got NO response from the JSC team regarding what I consider to be a BUG.

When you can take an application that deployed successfully under JSC2_EA and then it stops deploying under JSC2 there is a serious bug somewhere.

Thanks again for identifyiing the problem, I will take my complaints back to the JSC forum.

BeaverCleavera at 2007-7-21 15:06:16 >

The web.xml is generated by JSC.

I have never touched it in either JSC2_EA or JSC2.

That was the source of the irritation. The default behavior changed between the two.

Looking at older war files created by JSC2_EA, the web.xml does have the DOCTYPE line.

My problem is that I am not familiar enough with web applications to know what to look for.

BeaverCleavera at 2007-7-21 15:06:16 >

Hi,

Im facing the same kind of error. The exact error is as follows:

Deplyment Application in domain failed; Error loading Deployment Descriptors for MyMdb -- Referencing Error: This bundle has no bean of name [MyMDBBean]; Requested operation cannot be completed.

Here, MyMdb is my ejbmodule project. and MyMDB is the name of the class in the project.

I tried to delete the references for this class and the project in the domain.xml. However the problem exits.

please help.

SUN_JAVA_STUDIO_EJB_MODULES_ at 2007-7-21 15:06:16 >