Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Null Pointer Errors on CFCOLLECTION/CFINDEX operations

Description

CFCOLLECTION and CFINDEX tags are returning null pointer errors for many operations. Given the code snippet attached, the first time I run it there is a java.lang.NullPointerException on line 15 (the index create). However, it still appears to create the collection. The collection shows up in the Lucee admin and the folder is created in the collection folder. The second time I run it, it detects that the collection exists, but gets to the CFSEARCH line and throws a java.lang.NullPointerException.

I also noticed that any time I try to run a Repair or Optimize from the Lucee admin it shows a java.lang.NullPointerException in red.

Environment

Windows 2012, IIS, Tomcat 8
The error occurs in 5.2.7.62 but it won't let me pick that on this form (says it does not exist).

Attachments

3
  • 08 Jun 2018, 01:39 pm
  • 08 Jun 2018, 01:38 pm
  • 06 Jun 2018, 12:03 am

Activity

Show:

Michael Sprague 3 April 2019 at 12:55
Edited

For those of you that cannot wait longer for a search fix, here is a temporary solution that helped us with.

1. Get it working by re-creating the collection and confirming that search.xml has content.
2. Make a copy of search.xml in the same folder. Call it search.working.xml.
3. Place the following code at the bottom of any file with a cfindex tag.

<cfscript> searchDir = expandPath("{lucee-web}/search"); src = expandPath("#searchDir#/search.working.xml"); dst = expandPath("#searchDir#/search.xml"); fileCopy(src, dst); </cfscript>

Note that any time you add a new collection, you will need to repeat step 2.

This patch will basically replace the 0K file with a copy of the uncorrupted file each time. It survives restarts and prevents the error. It is holding us over until the real fix is in a production version.

Phil Lepanto 2 April 2019 at 17:49

We're running Lucee (5.3.1.102) and Lucene
2.4.1.32 - We get nullPointerException error when trying to create the index, but can run a cfcollection action="list" and see the index created. We get errors trying to run cfindex or cfsearch on that index. Seems like this is just fundamentally broken?

Michael Forell 11 December 2018 at 15:48

same problem here as describes in https://dev.lucee.org/t/cfsearch-exception/4922/2

scott conklin 5 December 2018 at 15:39

I have the exact same issue described above.
trying to recreate the collections after a server reboot cannot be done either programatically or using the web admin.
java.lang.NullPointerException

Stagi Punto Net 5 November 2018 at 19:47

Same issue here. As Michael Sprague wrote the search.xml is empty (0 byte). On every lucee restart I do not find my collections and I have to delete the search.xml file and to add again the collections. Without removing search.xml before lucee restart I get the java.lang.NullPointerException while trying to add again the missing collections

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 6 June 2018 at 00:06
Updated 19 May 2021 at 11:01

Flag notifications