Skip to main content

I am trying to customize an object in the order module. When I try to expand the module, it hangs up and shows Please Wait FOREVER.

I’ve tried this on multiple computers. I’ve tried deleting the %AppData%\DeveloperStudio\10.82 folder and recreating it. I’ve tried creating a new Project. I’ve tried uninstalling and reinstalling developer studio. I’ve tried clearing any caches I can find.

Anyone else seen this? Any other ideas on what to try?

 

We are using IFS Developer Studio 10.82.736511.20200828.

 

I noticed this in the Developer Studio log file. It looks like it might be related.

 

INFO ifs.dev.nb.project.ui.explorer.version2.model.ComponentDataModel]: Initializing data model for order component
SEVERE org.openide.util.RequestProcessor]: Error in RequestProcessor org.openide.nodes.AsynchChildren
java.lang.NullPointerException
    at java.lang.Enum.compareTo(Enum.java:178)
    at java.lang.Enum.compareTo(Enum.java:55)
    at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:320)
    at java.util.ComparableTimSort.sort(ComparableTimSort.java:188)
    at java.util.Arrays.sort(Arrays.java:1246)
    at java.util.Arrays.sort(Arrays.java:1433)
    at java.util.List.sort(List.java:478)
    at java.util.Collections.sort(Collections.java:141)
    at ifs.dev.nb.project.ui.explorer.BuildHomeNodeIx$BuildHomeComponentChildFactory.createKeys(BuildHomeNodeIx.java:372)
    at org.openide.nodes.AsynchChildren.run(AsynchChildren.java:215)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
    at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
kcatch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
INFO nifs.dev.nb.logging.impl.IFSErrorHandler]: Partner mode active: Error message dialog box disabled - java.lang.NullPointerException 

Found the problem.

 

There was a BAK file in our build_home\model\order directory. Removing this file and rebuilding the index solved the issue.

Reply


Terms & ConditionsCookie settings