Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 184306 - [69cat] [69cat] AssertionError at org.netbeans.modules.xml.xdm.XDMModel.<init>
[69cat] [69cat] AssertionError at org.netbeans.modules.xml.xdm.XDMModel.<init>
Product: xml
Classification: Unclassified
Component: XDM
All All
: P2 (vote)
: 6.x
Assigned To: Nikita Krjukov
: 172444 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2010-04-15 20:34 UTC by host
Modified: 2011-11-15 13:49 UTC (History)
10 users (show)

See Also:
Issue Type: DEFECT

stacktrace (998 bytes, text/plain)
2010-04-15 20:35 UTC, host
stacktrace (998 bytes, text/plain)
2010-04-22 19:19 UTC, host
stacktrace (998 bytes, text/plain)
2010-04-26 12:26 UTC, Exceptions Reporter
stacktrace (998 bytes, text/plain)
2010-04-29 04:35 UTC, Baiazid
screenshot_bug184306_modified_faces-config-xml.png (75.30 KB, image/png)
2010-05-27 13:22 UTC, _ alexpetrov
stacktrace (998 bytes, text/plain)
2010-06-01 09:20 UTC, big_al

Note You need to log in before you can comment on or make changes to this bug.
Description host 2010-04-15 20:34:58 UTC
Build: NetBeans IDE Dev (Build 201004150201)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-101, Java(TM) SE Runtime Environment, 1.6.0_17-b04-248-10M3025
OS: Mac OS X

   at org.netbeans.modules.xml.xdm.XDMModel.<init>(
   at org.netbeans.modules.xml.xdm.xam.XDMAccess.<init>(
   at org.netbeans.modules.xml.xdm.xam.XDMAccessProvider.createModelAccess(
   at org.netbeans.modules.xml.xam.dom.AbstractDocumentModel.getAccess(
   at org.netbeans.modules.xml.xam.dom.AbstractDocumentModel.getAccess(
   at org.netbeans.modules.xml.xam.AbstractModel.isAutoSyncActive(
Comment 1 host 2010-04-15 20:35:03 UTC
Created attachment 97488 [details]
Comment 2 host 2010-04-22 19:19:50 UTC
Created attachment 97875 [details]
Comment 3 Exceptions Reporter 2010-04-22 19:20:12 UTC
This bug already has 5 duplicates 
Comment 4 Exceptions Reporter 2010-04-26 12:26:07 UTC
Created attachment 98022 [details]

finding string in faces-config.xml
Comment 5 Baiazid 2010-04-29 04:35:17 UTC
Created attachment 98239 [details]

Edit faces-config.xml to add new:

Comment 6 Exceptions Reporter 2010-05-03 19:32:18 UTC
This bug already has 10 duplicates 
Comment 7 Exceptions Reporter 2010-05-25 16:25:12 UTC
This bug already has 20 duplicates 
Comment 8 Sergey Lunegov 2010-05-25 16:46:51 UTC
Alex, please take a look.
Comment 9 _ alexpetrov 2010-05-27 13:21:48 UTC
I'm not able to reproduce this bug on:
Product Version: NetBeans IDE Dev (Build 201005260001)
Java: 1.6.0_18; Java HotSpot(TM) Client VM 16.0-b13
System: Windows XP version 5.1 running on x86

My steps:
- download and install the plugin "Java Web and EE", including the JSF module
- create a sample JSF project "TravelCenter"
- open its "faces-config.xml" and add at the beginning of this file several XML tags (see the attached "screenshot_bug184306_modified_faces-config-xml.png"):

- no exceptions were thrown.

Need more info (all details are very important): 
 - attach a JSF project, which is edited
 - describe steps, which allow to reproduce this bug

I've seen that some exception reports (UI Actions XML/Messages Log) contain exception messages:
   Log Session: Wednesday, May 26, 2010 7:03:49 PM CDT
   Product Version         = NetBeans IDE 6.9 Beta (Build 201004200117) <= old build
        <message>Could not lock document</message>
            <message> File faces-config.xml is read-only!</message> JAR entry com/jaspersoft/ireport/com-jaspersoft-ireport-designer-menu-DatasourcesAction_1.shadow not found in C:\Archivos de programa\NetBeans 6.9 Beta\ireport\modules\com-jaspersoft-ireport.jar

WARNING [org.openide.filesystems.JarFileSystem]: cannot open C:\Documents and Settings\mircea.stanciu\.m2\repository\javax\javaee-api\6.0\javaee-api-6.0-sources.jar
INFO [org.openide.filesystems.JarFileSystem]: error in opening zip file error in opening zip file

Maybe mentioned troubles cause this bug.
Comment 10 _ alexpetrov 2010-05-27 13:22:54 UTC
Created attachment 99542 [details]
Comment 11 Nikita Krjukov 2010-05-28 13:17:00 UTC
It's not clear yet, which part of code is responsible for the Exception. 

The initial reason of exception is absence of an org.netbeans.editor.BaseDocument instance in model's source. The ModelSource object is required for construction of a new XAM-based model or getting an existing model from the internal cache (see AbstractModelFactory class). 

According to ModelSource.getLookup() method's documentation, the lookup has to contain javax.swing.text.Document. The XDMModel requires a BaseDocument instance instead, which is a descendant of Document. There is a contradiction here. And it can cause the exception if some external code put a Document to the lookup instead of a BaseDocument. I'm going to figure out it and maybe do some corrections. But this contradiction doesn't look like the main or the only reason of the Exception. 

Another possible reason can be an incorrect code out of XAM/XDM models, which constructs a ModelSource without required BaseDocument. I don't think that the code does it intentionally. Most likely an exception happens while loading a document and the exception is ignored or processed with a wrong way. It's necessary to analyze logs more detailed. 

Also there is a difficulty, which prevents easily understand real reason. You can see that all stack traces are started from the RequestProcessor. So it's impossible to know which code has requested a XAM model. It would be helpful to have special customizable mode in which the Task class obtains stack trace in its constructor and saves it somewhere inside.
Comment 12 Nikita Krjukov 2010-05-28 19:51:54 UTC
I analyzed different logs (almost all) and it seems I've found a regularity. 
The bug always relates to JSF Config file. It's initiated when the file is being closed - JSFConfigEditorSupport.notifyClosed()

The method seems is called after closing the JSF Config file. The JSF Config model is requested in order to do synch() according to the fix of the issue #116315. It looks like the requested model isn't loaded yet and it tries loading and failed. An IOException happens, but it's caught in the method and lost. 

I suppose the assertion exception maybe is reasonable in such case. It worth to understand what is the reason of IOException first. And it's necessary to uncomment the line, where the exception is lost: 
    } catch (IOException ex) {
        // Logger.getLogger("global").log(Level.INFO, null, ex);

It should be more clear to the owners of corresponding JSF module, why the IOException happens, so I reopen the issue and switch it to them.
Comment 13 Nikita Krjukov 2010-05-28 19:57:35 UTC
I forgot to say that always there is another exception before AssertionError. 
It can be found in any log and it contains line: 

[catch] at org.netbeans.modules.web.jsf.JSFConfigEditorSupport$
Comment 14 Alexey Butenko 2010-05-31 07:13:35 UTC
From debugger I've found that IOException happens in org.netbeans.modules.xml.xam.AbstractModel.sync(). It should be more clear to the owners of corresponding module, why the
IOException happens.
Comment 15 Nikita Krjukov 2010-05-31 18:16:09 UTC
It looks like the mentioned AssertionError and Exception are not hardly related. They rather have the same reason. The AssertionError happens inside of auto-sync procedure. A modification of the JSF Config file makes it so invalid, that it can't be loaded to text document. Because the model for the file is already loaded, it causes the AssertionError when the document is requested again. 
I suppose the same changes can be done not only with JSF Config file, so the problem is more general. 

It's not clear what exactly happens. I know that the JSF Config file is located in a temporary folder and the attempt to load it comes to an IOExceptin with "FileObject is invalid" message. 

The solution I tried to use is throwing an artificial IOExceprion in the method org.netbeans.modules.xml.retriever.catalog.Utilities._getDocument(). It comes to similar results without reproducing the bug itself.
Comment 16 big_al 2010-06-01 09:20:58 UTC
Created attachment 99699 [details]

opened faces-config.xml
Comment 17 Nikita Krjukov 2010-06-01 12:48:13 UTC
Fixed in trunk

Now the XAM model gets NOT_SYNCED status if the underlaying XML document becomes inaccessible.
Comment 18 Quality Engineering 2010-06-03 06:08:58 UTC
Integrated into 'main-golden', will be available in build *201006030001* on (upload may still be in progress)
Log: #184306 - AssertionError at ...xml.xdm.XDMModel.<init>
Comment 19 Nikita Krjukov 2010-06-18 17:07:02 UTC
There isn't reliable way to reproduce the issue. So it's tested with JUnit tests.
Comment 20 Nikita Krjukov 2010-06-18 17:08:41 UTC
The fix is simple and not dangerous so I'm going to move it to relase691
Comment 21 Nikita Krjukov 2010-06-18 20:22:34 UTC
transplanted modification from trunk to release691
Comment 22 Svata Dedic 2011-11-15 13:49:28 UTC
*** Bug 172444 has been marked as a duplicate of this bug. ***

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo