Problem with JBoss 6 EAP web application deployment.

[pottis]

I am facing a problem with JBoss 6 EAP in deploying the webapplication. It tries to validates the TLD files and tries to find the classes defined. Some classes are not present and hence it throws class not found exception.

I want to know if there is any configuration in JBoss 6 EAP through which we can skip the XML validation.

Also i need to understand why it tries to parse the values in the tag. Is there any configuration through which we can stop the parsing of values of tags?

Please help me with this issue

Thanks,

Senthil Naathan P M

[mac2009]

Which TLDs exactly?

We had similar issue with struts. For example struts changed package structure from 1.1 to 1.3.

In one of our webapps upgrade to struts 1.3.x wasn't made completely and JBoss 7 now parses files much better...my opinion.

Good chance to get a clean deployment.

[pottis]

Thanks Carsten for the response.

I am using tag lib version 1.0 in my application. Will that make any difference in the JBoss 6 EAP deployment?

Thanks,

Senthil Naathan P M

[mac2009]

Well, would be easier if you show the exception (stack trace), taglib tld and jar.

Anything customized?

[pottis]

In our application we use the TLD and specify the schema for the same .

below is the tld file and the exception we get when we try to deploy the application in JBoss

?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN" "file://./web-jsptaglibrary_1_1.dtd">

<?xml-stylesheet type="text/xsl" href="referenceLink.xsl"?>

<!-- Confidential Property of Documentum, Inc.                             -->

<!-- (c) Copyright Documentum, Inc. 2001.                                  -->

<!-- All Rights reserved.                                                  -->

<!-- May not be used without prior written agreement                       -->

<!-- signed by a Documentum corporate officer.                             -->

<!--                                                                       -->

<!-- Component: DA Tag Library                                             -->

<!-- Scope: None                                                           -->

<!-- Created by: Steve Wagner ([e-mail])                      -->

<!-- Revision    $Revision: $ -->

<!-- Modified on $Date: $ -->

<taglib>

   <tlibversion>1.0</tlibversion>

   <jspversion>1.1</jspversion>

   <shortname>dmda</shortname>

<tag>

      <name>writeaccessvalidator</name>

      <tagclass>com.documentum.webcomponent.admin.control.accessvalidator.WriteAccessValidatorTag</tagclass>

      <bodycontent>empty</bodycontent>

      <attribute>

         <name>id</name>

         <required>false</required>

         <rtexprvalue>true</rtexprvalue>

         <description>

            TBD.

         </description>

      </attribute>

      <attribute>

         <name>name</name>

         <required>true</required>

         <rtexprvalue>true</rtexprvalue>

         <description>

            TBD.

         </description>

      </attribute>

   </tag>

.

.

.

</taglib>

0:51:29,611 INFO  [org.jboss.as.repository] (management-handler-thread - 6) JBAS014900: Content added at location C:\Program Files\EAP-6.0.0.GA\jboss-eap-6.0\standalone\data\content\1a\8701d21729736e8911d26761f0549e0574b462\content

00:51:29,620 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "wt.war"

00:54:05,313 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry xerces-J_1.4.0.jar in /C:/Program Files/EAP-6.0.0.GA/jboss-eap-6.0/bin/content/wt.war/WEB-INF/lib/castor-1.1-xml.jar  does not point to a valid jar for a Class-Path reference.

00:54:05,315 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/Program Files/EAP-6.0.0.GA/jboss-eap-6.0/bin/content/wt.war/WEB-INF/lib/jaxb-impl.jar  does not point to a valid jar for a Class-Path reference.

00:54:05,316 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/Program Files/EAP-6.0.0.GA/jboss-eap-6.0/bin/content/wt.war/WEB-INF/lib/jaxb-impl.jar  does not point to a valid jar for a Class-Path reference.

00:54:05,320 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry relaxngDatatype.jar in /C:/Program Files/EAP-6.0.0.GA/jboss-eap-6.0/bin/content/wt.war/WEB-INF/lib/xsdlib.jar  does not point to a valid jar for a Class-Path reference.

00:54:23,991 WARN  [org.jboss.as.ee] (MSC service thread 1-3) JBAS011006: Not installing optional component com.documentum.webcomponent.admin.control.accessvalidator.WriteAccessValidatorTag due to exception: java.lang.ClassNotFoundException: com.documentum.webcomponent.admin.control.accessvalidator.WriteAccessValidatorTag from [Module "deployment.wt.war:main" from Service Module Loader]

          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)

          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)

          at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_32]

          at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_32]

          at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54)

          at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_32]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_32]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]

.

.

.

.

.

.

00:54:24,582 ERROR [stderr] (MSC service thread 1-4) Warning: XXXX application could not be started, error msg= null, error type=java.lang.ExceptionInInitializerError. This message can be ignored during the installation.

00:54:24,583 ERROR [stderr] (MSC service thread 1-4) java.lang.ExceptionInInitializerError

00:54:24,583 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.client.DfClient.<clinit>(DfClient.java:734)

00:54:24,583 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43)

00:54:24,584 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.web.env.NotificationManager.contextInitialized(NotificationManager.java:101)

00:54:24,584 ERROR [stderr] (MSC service thread 1-4)           at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392)

00:54:24,585 ERROR [stderr] (MSC service thread 1-4)           at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850)

00:54:24,585 ERROR [stderr] (MSC service thread 1-4)           at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)

00:54:24,586 ERROR [stderr] (MSC service thread 1-4)           at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

00:54:24,586 ERROR [stderr] (MSC service thread 1-4)           at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

00:54:24,586 ERROR [stderr] (MSC service thread 1-4)           at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

00:54:24,587 ERROR [stderr] (MSC service thread 1-4)           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

00:54:24,587 ERROR [stderr] (MSC service thread 1-4)           at java.lang.Thread.run(Thread.java:662)

00:54:24,588 ERROR [stderr] (MSC service thread 1-4) Caused by: java.lang.NullPointerException

00:54:24,588 ERROR [stderr] (MSC service thread 1-4)           at java.util.Hashtable.put(Hashtable.java:394)

00:54:24,588 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.common.impl.preferences.PreferencesManager.readPersistentProperties(PreferencesManager.java:343)

00:54:24,589 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.common.impl.preferences.PreferencesManager.<init>(PreferencesManager.java:41)

00:54:24,589 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.common.DfPreferences.initialize(DfPreferences.java:64)

00:54:24,590 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.common.DfPreferences.getInstance(DfPreferences.java:43)

00:54:24,590 ERROR [stderr] (MSC service thread 1-4)           at com.documentum.fc.impl.RuntimeContext.<clinit>(RuntimeContext.java:177)

00:54:24,591 ERROR [stderr] (MSC service thread 1-4)           ... 11 more

00:54:24,614 INFO  [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /wt

00:54:24,685 INFO  [org.jboss.as.server] (management-handler-thread - 6) JBAS018559: Deployed "wt.war"

I am getting the above warning and error and it says that application is deployed. But i am not able to access the application.

My question is why JBoss 6. is trying to parse some values specified in the TAG and how can we skip that. Here in this above scenario i dont have the class specified in the TLD in our application package.

This was never a problem till 5.1 JBoss.

We have not customized TAG libraries JAR.

Thanks,

Senthil Naathan P M

[mac2009]

Well, you wrote the solution already. "...i dont have the class specified in the TLD in our application package..."

As far as I know either add the class file (or a lib with all the com.documentum.* classes) to your application package

or do you need the WriteAccessValidatorTag ? If not, just remove it from TLD.

This would be the way I do it.

Don't know if there is a "special" configuration to skip parsing.

[pottis]

Thats what my problem is. This TLD file is working fine when we deploy in 5.1 But when it comes to 6 we are unable to deploy it due to this error.

We have this class for future purpose.

The problem is JBoss 6 parsing the TLD and the values specified in the tags. which is unacceptable. Is there a way to stop the schema validation for 6.0 JBoss to skip parsing the values in the tag?

I have seen some configuration in JBoss 5.1. But i am not able to find it in JBoss 6.

Is ther a configuration in JBoss thro which we can skip parsing the values specified in the tld file tags?

[mac2009]

Ok, once more. I think its not a good idea to skip parsing.

Is there a lib in WEB-INF/lib containing the com.documentum.* classes or not?

If you deploy a "clean" application, you won't have this prob.

[pottis]

I understand.

But the application is built on the top of a frame work and these TLDs are defined in the Frame work. We cant remove this classes def in the TLDs as there are other applications which has the specific classes are built on top of the frame work. We cant have different TLDs for different applications as its building on the same frame work

So again, i  need some configuration in JBoss which can skip parsing the values in the TLDs.

Thanks,

Senthil Naathan P M

[mac2009]

??? but the framework which contains the TLD should contain the class WriteAccessValidatorTag as well.
Anyway ...a structural problem.

Maybe there is a way if you play around with some module.xml.

A hint is in your stack trace org.jboss.as.ee

For my part everything is said. I am out here.

Cheers and good luck.

[mmusaji]

Hi

If you are using JBoss EAP 6 you are welcome to raise a support case with Red Hat Support regarding this question if the suggested solution(s) have not yet worked for you. Just head over to https://access.redhat.com/home and log in.

Thanks

Mustafa

[pottis]

Hi Mustafa,

Thanks .. Can you tel me how can i raise a support case .. with the URL provided i am not able to get JBoss support can i raise in RedHat Network of Redhat Customer portal ??

Thanks,

Senthil Naathan P M

[mmusaji]

Hi Senthil

If you are using JBoss EAP (as opposed to JBoss AS which is the community edition) then you probably have a support subscription with us. You need to log in to http://access.redhat.com and go to the Support pages where there is a link for you to raise a support case. Talk to your team and you should have an org admin (whoever gave you JBoss EAP) with log in details.

Regards

Mustafa

[pottis]

Hi Mustafa,

Thanks for the response i was able to get some answers from the JBoss team which resolved the issue i was getting. But i am facing a new problem now. In our application we have same name for the package name and the class name and when it is trying to compile the jsp using the class specified in the package it tries to resolve the other class name and it fails.

The reason is the JBoss doesnot support case sensitivity by default. We were using -DJBoss.vfs.forcecasesensitive=true till the JBoss 5.1 EAP version. Now that option is not working in JBoss 6 EAP. We were able to replicate the same issue in JBoss 7.0/7/1 and 7.2 community edition of JBoss.

Can some one help me in introducing case sensitivity in the JBoss 6 EAP or 7 community edition.

Thanks,
Senthil Naathan P M

[mmusaji]

I think the problem is not the lack of this option but the fact that you have " same name for the package name and the class name "

I would suggest you don't allow duplicate naming in your application as a form of best practice.  Always observe case sensitivity. As always, the best place to get official wording for EAP version is via a support case.

Regards

Mustafa