• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 972
  • Last Modified:

weblogic 6.0 deplying ear, xml parsing error occurs in a repeating deployment of the files !

Hello there !

I am using WLS 6.0 and deploying our application (developed on jboss)
now on weblogic.I am receiving the attached message at the end of this
mail. The Strange thing is, it keeps compiling  and generating
wl_comp<nnnnnn>.ear files non-stop in the wl_temp_do_not_delete
directory. I have to delete the ear file that this behavior will stop.
so two questions:

- is there a way to stop this "repeating" behavior, because it only
uses diskpace? Is this a bug in the 6.0 version?
- what exactly is this error, what I have done wrong in my ear, which
xml ?

Thanks for your time.
Regards
Mark

Weblogic Error Message (taken from the log file):
Apr 18, 2002 2:49:03 PM CEST Info Management
MBean=(BankingCSFB:Name=seprosift,Type=Application)
Attribute=(LastModified) modified from (1019134139382) to
(1019134143132).
Apr 18, 2002 2:49:03 PM CEST Error Management Error parsing XML
descriptor for application BankingCSFB:Name=seprosift,Type=Application
weblogic.xml.process.ProcessorFactoryException: XML document does not
appear to contain a properly formed DOCTYPE header
      at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:189)
      at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:164)
      at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:83)
      at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:67)
      at weblogic.management.mbeans.custom.Application.getDD(Application.java:358)
      at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:284)
      at weblogic.management.mbeans.custom.Application.load(Application.java:230)
      at java.lang.reflect.Method.invoke(Native Method)
      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
      at $Proxy15.load(Unknown Source)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:528)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
      at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
      at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)
--------------- nested within: ------------------
weblogic.xml.process.XMLProcessingException: XML document does not
appear to contain a properly formed DOCTYPE header - with nested
exception:
[weblogic.xml.process.ProcessorFactoryException: XML document does not
appear to contain a properly formed DOCTYPE header]
      at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
      at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:67)
      at weblogic.management.mbeans.custom.Application.getDD(Application.java:358)
      at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:284)
      at weblogic.management.mbeans.custom.Application.load(Application.java:230)
      at java.lang.reflect.Method.invoke(Native Method)
      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
      at $Proxy15.load(Unknown Source)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:528)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
      at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
      at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)


--------------------------------------------------------------------------------
0
megloff
Asked:
megloff
  • 5
  • 3
1 Solution
 
saxabooCommented:
Did you check all your DOCTYPE headers in your deployment descriptors ?

I checked my WL 6.0 web apps, the required DTD in web.xml is :

<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">

Indeed, AFAIK WL6.0 supports the Servlet 2.2 specs.

For ejb-jar.xml and weblogic-*.xml, look at this page :

http://e-docs.bea.com/wls/docs60/ejb/EJB_reference.html#1048022

and check that your doctypes match those given by BEA.

And finally application.xml :
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN" "http://java.sun.com/dtd/application_1_2.dtd">

Hope this helps,

-S
0
 
megloffAuthor Commented:
Thanks for your help, but all the DOCTYPE has the right values. I rewrite the files completly by hand and after that it works... I guess from the copying from solaris to pc and back a strange ascii character has nested in...

howewer I get now another error, see below.
Could someone explain me what this is and how I can solve this?

Thanks for every suggestion.
Best Regards
Mark


Apr 19, 2002 10:42:07 AM CEST Info EJB EJB Deploying file:
SeproSIFT.jar
Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying EJB Component
: SeproSIFT
weblogic.ejb20.EJBDeploymentException: EJB Deployment errors:; nested
exception is:
      
      com/sepro/cse/STCSERecord
      com/sepro/cse/STCSERecord

      com/sepro/cse/STCSERecord
      com/sepro/cse/STCSERecord
      at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:220)
      at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:185)
      at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:295)
      at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:252)
      at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:135)
      at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
      at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
      at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
      at weblogic.j2ee.Application.addComponent(Application.java:126)
      at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
      at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:283)
      at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:109)
      at java.lang.reflect.Method.invoke(Native Method)
      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:409)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:287)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:866)
      at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:853)
      at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:566)
      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
      at $Proxy21.addTarget(Unknown Source)
      at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:486)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:557)
      at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
      at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
      at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
      at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)
 
Apr 19, 2002 10:42:08 AM CEST Error J2EE Error deploying application
SeproSIFT: Could not deploy: 'SeproSIFT.jar':
      com/sepro/cse/STCSERecord
      com/sepro/cse/STCSERecord
Apr 19, 2002 10:42:08 AM CEST Info Management
MBean=(BankingCSFB:Name=seprosift,Type=Application)
Attribute=(Deployed) modified from (true) to (true).

0
 
saxabooCommented:
Hi,

just an idea : the error comes from an internal WL "EJBComplianceChecker" in runEJBC()
To my knowledge, EJBC is the EJB2.0 compiler, so WebLogic is trying to deploy your bean as an EJB 2.0-compliant bean.

If your beans comply to the 1.1 specs, then you should use the following command line :

java weblogic.deploy -port 7001 -host localhost deploy  myweblogicpassword CMP_example  c:\myejb\

(EJB 2.0 deployment involove the weblogic.ejbc command-line tool)

HTH,

-S
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
megloffAuthor Commented:
Thabnk you
seêms to be a very good hint...Yes I'm using EJB1.1
I' am starting weblogic with this commandline:

/usr/bin/nohup/app/java/jdk1.3/java/bin/java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=BillingCSFB -Dweblogic.Name=BillingCSFBServer -Dbea.
home=$WL_BINARY_HOME -Djava.security.policy==$APP_HOME/weblogic.policy -Dweblogic.management.password=$WLS_PW $BANKINGDEFS weblogic.Server > /app/Bankin
gCSFB/BillingCSFB/log/BillingCSFB.out 2>&1 &

Do you have any further hints to me how I can set up the ejb 1.1 compilance?

regards
mark


0
 
megloffAuthor Commented:
I tried now to deploy with the java.weblogic.deploy tool:

java -cp /app/bea/WebLogic600sp1/lib/weblogic.jar weblogic.deploy -port 9202 -host localhost deploy weblogic SeproSIFT SeproSift.jar

The result:

Undeclared checked exception

any suggestions?

Regards
Mark
0
 
megloffAuthor Commented:
ok i get the solution for my problem... there was multiple .jar's in the ear file. So weblogic did not find the class files when it was deploying....

0
 
megloffAuthor Commented:
Your Hint with the command line tool gave me indirect a solution. And after that I was able to see what was really wrong. Thank you
0
 
saxabooCommented:
Glad you made it through those cryptic error messages !

Thanks

-S
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now