Taglib Error

Recently we have had authors reporting that they are getting an error whenever they use one particular CTD.

The following application error(s) occurred: An unexpected error occurred during the start of the taglib: null.

A bit of research shows that this CTD is unique because it is the only one we have that calls custom code from the “Content Editor –JSP URI:” field of the Extensibility section of the CTD’s General tab. We have other CTD’s that reference “/vgn-wcm-up/cif/defaultcif.jsp“ in this filed but they are all working as expected.

As my first troubleshooting step I decided to delete the custom app that we created for the problematic CTD to use and replace it with the same code that the other CTDs are accessing. To do this I downloaded the vgn-wcm-up.war file from the /opt/vignette/Content/7_6/deployedExtns/wars directory. I then renamed this war to match the name of our custom app and redeployed this base war. The first time I tried this I got a ClassDefNotFound error and remembered I needed to copy the following jars from the /opt/vignette/Content/7_6/lib/sdk and place them in the WEB-INF/lib directory of my war file: thirdparty-combined.jar, vgn-appsvcs-cce.jar, and vgn-appsvcs-cma.jar. After I did this the war deployed successfully. Unfortunately the tag lib error still occurs.

In the logs the error I see is:

<Jun 28, 2010 3:30:13 PM EDT> <Error> <HTTP> <BEA-101362> <[weblogic.servlet.internal.WebAppServletContext@2756933 - appName: 'map.war', name: 'map.war', context-path: '/map'] could not deserialize the request scoped attribute with name: "propertyPage_61a53a183829d5b81ddb8ae4dbcb6b3b"

java.lang.ClassCastException: cannot assign instance of

com.vignette.as.ui.common.property.commands.CommandMapping to field

com.vignette.as.ui.common.property.BasePropertySheet._cmds of type

com.vignette.as.ui.common.property.commands.CommandMapping in instance of

com.vignette.otm.descriptor.DescriptorObjectEditor

at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004)

at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184)

at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)

Truncated. see log file for complete stacktrace

java.lang.ClassCastException: cannot assign instance of

com.vignette.as.ui.common.property.commands.CommandMapping to field

com.vignette.as.ui.common.property.BasePropertySheet._cmds of type

com.vignette.as.ui.common.property.commands.CommandMapping in instance of

com.vignette.otm.descriptor.DescriptorObjectEditor

at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004)

at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184)

at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)

Truncated. see log file for complete stacktrace

running Filter: /vgn-ext-links/HyperLink16.gif

running Filter: /vgn-ext-links/InsertImage16.gif

Since the base code is breaking as well, I’m not sure where to start trouble shooting the errors reported.

The weird thing is that we only recently encountered this issue but we don’t know of any changes what we made before this issue started that could have caused it. At this point I am stumped and could really use some help. Thanks.

Find more posts tagged with

Comments

Ruhul_Alam

This looks like to be a serialization versioning issue. The map.war contains a version of CommandMapping that is not in sync with what is in the request. Likely, another part of the VCM created the object, added it to the request and then a cross-context forward occurred which is triggering the serialization.I would verify that the JARs in map.war that contain CommandMapping are the same as the rest of the system..r.On Jun 30, 2010, at 7:27 AM, eLink Entry: Vignette V7 and V8 Web Content Management wrote:> Taglib Error Posted by millisa.eubanks@bhsi.com (Eubanks, Millisa) On 2010/06/30 08:22> > Recently we have had authors reporting that they are getting an error whenever they use one particular CTD.> > The following application error(s) occurred: An unexpected error occurred during the start of the taglib: null.> > A bit of research shows that this CTD is unique because it is the only one we have that calls custom code from the ?Content Editor ?JSP URI:? field of the Extensibility section of the CTD?s General tab. We have other CTD?s that reference ?/vgn-wcm-up/cif/defaultcif.jsp? in this filed but they are all working as expected.> > As my first troubleshooting step I decided to delete the custom app that we created for the problematic CTD to use and replace it with the same code that the other CTDs are accessing. To do this I downloaded the vgn-wcm-up.war file from the /opt/vignette/Content/7_6/deployedExtns/wars directory. I then renamed this war to match the name of our custom app and redeployed this base war. The first time I tried this I got a ClassDefNotFound error and remembered I needed to copy the following jars from the /opt/vignette/Content/7_6/lib/sdk and place them in the WEB-INF/lib directory of my war file: thirdparty-combined.jar, vgn-appsvcs-cce.jar, and vgn-appsvcs-cma.jar. After I did this the war deployed successfully. Unfortunately the tag lib error still occurs.> > In the logs the error I see is:> > <[weblogic.servlet.internal.WebAppServletContext@2756933 - appName: 'map.war', name: 'map.war', context-path: '/map'] could not deserialize the request scoped attribute with name: "propertyPage_61a53a183829d5b81ddb8ae4dbcb6b3b"> java.lang.ClassCastException: cannot assign instance of> com.vignette.as.ui.common.property.commands.CommandMapping to field> com.vignette.as.ui.common.property.BasePropertySheet._cmds of type> com.vignette.as.ui.common.property.commands.CommandMapping in instance of> com.vignette.otm.descriptor.DescriptorObjectEditor> at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004)> at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184)> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914)> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)> Truncated. see log file for complete stacktrace> > > <[weblogic.servlet.internal.WebAppServletContext@2756933 - appName: 'map.war', name: 'map.war', context-path: '/map'] could not deserialize the request scoped attribute with name: "VgnSessionTransfer"> java.lang.ClassCastException: cannot assign instance of> com.vignette.as.ui.common.property.commands.CommandMapping to field> com.vignette.as.ui.common.property.BasePropertySheet._cmds of type> com.vignette.as.ui.common.property.commands.CommandMapping in instance of> com.vignette.otm.descriptor.DescriptorObjectEditor> at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004)> at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184)> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914)> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)> Truncated. see log file for complete stacktrace> > > running Filter: /vgn-ext-links/HyperLink16.gif> running Filter: /vgn-ext-links/InsertImage16.gif> > Since the base code is breaking as well, I?m not sure where to start trouble shooting the errors reported.> > The weird thing is that we only recently encountered this issue but we don?t know of any changes what we made before this issue started that could have caused it. At this point I am stumped and could really use some help. Thanks.> > > Attachment Links:> taglib-error.jpg (24 KB)> [To post a comment, use the normal reply function]> Forum: Vignette V7 and V8 Web Content Management> Livelink Server: knowledge-wlweb01>

Millisa_Eubanks

Additional information on the issue.

Looking at changes that were made around the time this issue presented itself it looks like the most likely culprit was the install of the OTM (Object Type Modeler) extention. I'm going back though the documentation for this install to see what if any jar files were used. I'm also going to look at the taglib for this extention to make sure that it matches what is being used by the vgn-wcm-up.war file.

Steve_Coffman

Hey, I know this is old, and you probably solved it by now, but we have had to remove some of the OTM Type specifications to avoid getting this error. We weren't using them, so we just deleted them all and then things worked again. Not sure if there's a better way to prevent conflicts, but I'd love to hear it if you found them.

Millisa_Eubanks

Actally I'm still pulling my hair out over this! When you say OTM Type Spcifications where are those located? We just installed a new QA environment and we arn't getting the error there. I would love to see if it was because those specifications were never installed on that environment. Any additaionl info you could give me would be a big plus.

Thanks!!!

Millisa

Mario_DAnna

My friend, is this an env that I can reach from outside ?

From: eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Thu Sep 30 20:55:05 2010
Subject: Re Taglib Error

Re Taglib Error

Posted bymillisa.eubanks@bhsi.com (Eubanks, Millisa)On 2010/09/30 14:50

[To post a comment, use the normal reply function]
Topic:	Taglib Error
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

Millisa_Eubanks

Would a web-ex work? I have a meeting now for about an hour but I should be done at 4:30 EDT. Any time after that I'm free and I'm totally free tomorrow. I would gladly take any information/assistance I can get.

Steve_Coffman

I had the exact same problem, with one tier working (DEV) and one not (QA). I did a config dump using the VCM Tools and then compared them using Scooter Software's excellent Beyond Compare tool.
I did a find replace on all the tier specific stuff (DEV->QA) and just looked for discrepancies. The OTM stuff was the only real discrepancy and sure enough removing it fixed my problem.

To remove the OTM related stuff, remove the OTM Type Specs from the following node in configconsole,
Vignette Configuration Console > Vignette Content > Vignette Content Management Services > Vignette Management Console > Service Provider Framework > Type Specification Registry > Customer Extension Type Specification Registry

(The ports may be off by one if you are not using SSL the way we are)
VCM Tools Config Dump
https://vcmserver:27002/vcmtools/jsp/cfgdump.jsp

Config Console
https://vcmserver.lsa.umich.edu:27111/configconsole/

We do use some OTM classes, so I have left them deployed (cmaext_ear.ear is deployed containing a fusion of OTM and VPS Inline Links).

Good luck. Report back if you solve your issue.

-Steve

Millisa_Eubanks

Thanks for the reply.

I'm actually working with 3 environments. I have this problem on 2 (Prod and dev) and not on the third (QA). I've checked and all 3 have the OTM Type specifications but since our QA is a new install it is missing other things. One of them is the Rich Media services add-on. I did find a KB (17555250) about VCM 7_6 and RMS. I tried following this KB and added the otm.jar in the richmedia.war file but that didn't seem to help. My next test is to try to remove RMS to see if that stops the errors.

At this point I figure removing the OTM Type specifications will work but I'm bound and determined to find the root cause. I'll keep you posted.

Millisa_Eubanks

Good News, we just installed the EphoxEditor with Inline links into our QA environment which was not thowing the taglib error and now it is. That means the issue is problaby somewhere in the steps we took to install that extention. We are going to look at what we did and see if we can track down the issue. Any insight anyone might have that would help us to track down the issue would be greatly appreciated.

Mario_DAnna

First thing to check is the BEA log to see if there are errors related to conflicting class versions.

Most common error when deployeing extensions is to take a war/ear and deploy as it is without recompiling nor substituting the system jars

-m

From: eLink Entry: Vignette V7 and V8 Web Content Management [v7webcontentmanagement@elinkkc.opentext.com]
Sent: Thursday, October 07, 2010 2:30 PM
To: eLink Recipient
Subject: Re Taglib Error

Re Taglib Error

Posted by millisa.eubanks@bhsi.com (Eubanks, Millisa) On 2010/10/07 08:28

[To post a comment, use the normal reply function]
Topic:	Taglib Error
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

Steve_Coffman

Ah, the Inline Links widget. I feel your pain. Are you using VMCEXT in 7.6? Those conflict with the inline links widget and cause a similar problem.

Also, if you have a config dump from before you installed it on QA, you might want to save it and do a comparison. Sometimes you can see the broken bits of whatever you changed.
We had the same exact problem (among others), and we ended up using Avalon consulting to help us after many struggles. We now have a cmaext_ear.ear that is a merger of OTM and VPS Inline Links, and they did some other nice tweaks.

Since the consultants helped us with our issue, I don't know entirely know what caused it.
I do have some things that may be helpful with the Inline Links for you in the future.

One problem is that upgrading to 6.7.3.16 and later breaks the inline links widget as per KB10722:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17554727&objAction=ArticleView

And that KB is also wrong because the XSL file has com.behr.goe.utils.ELJUtils.getELJConfigText when it needs to have com.vignette.goe.utils.ELJUtils.getELJConfigText

Plus, that KB has not had the XSL updated to the newer(est?) version (6.7.5.25), not that this appears to cause problems, but might miss some benefits of the upgrade.

Ephox EditLive! Version 6.7.5.25 via KB 10547:

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17553864&objAction=ArticleView

By the way, the Inline Links widget is really popular with our users, I don't mean to dump on it. If it works, it's great.

It's just really complicated to get it working correctly, isn't supported by VOLSS, and can easily be broken even by doing an upgrade. It's easy to have broken links in content with an inline link to a content item/channel that has been deleted (or not migrated).

If I find the time I'll complete the inline link cleaner that I'm working on.

Good luck.
-Steve