The CreatorCon Call for Content is officially open! Get started here.

loadRow failure java.lang.NullPointerException after Upgrade to London

seberly
Giga Expert

After upgrading to London from Jakarta we noticed our instance performance was degraded.  We can replicate reliably by navigating to Catalog Item Variables.  Other transactions are hit or miss.  For example, I can log in with ease, but my colleague waited around 20 seconds to login.

Loading the Catalog Item Variable takes around 3-4 times longer than the normal duration of a server response (based on what we're seeing in our instances that have not been upgraded to London).  Upon searching the logs, the one consistent message that seems to be a symptom is "*** ERROR *** loadRow failure java.lang.NullPointerException".  This error appears around 1,000 times within the period of 5 seconds for any given transaction where we run into the long loading problem.  In total today, this error appears in the log about 21,000 times (we've been working for just over 2 hours).

Any ideas what's going on here?

Thanks in advance!
Scott

25 REPLIES 25

Hello,

 

Did you get a reply from Hi?
I stumbled upon the same error message today in our dev instance.
Upgraded to London last week.

With regards
Anton

Hi Scott,

 

I have the same log errors with two separate installs for a customer.

One is on London patch 1, the other on London patch 2. Both systems were upgraded from Istanbul patch 11b.

 

Any update from HI?

John Ping
Mega Guru

Hi Seberly,

 

Did you find a cause for this issue? I'm seeing something similar, and I didn't see anything concerning in my update logs.

seberly
Giga Expert

All,

The HI support team is still working through the issue.  They have made some traction, but I've not received a word from them on the official state.

Scott

ABouland
Kilo Guru

Just updated to London and seeing similar errors in our logs re:

loadRow failure: java.lang.NullPointerException:

In addition to seeing this when accessing a variable record from Catalog Item, am also seeing same error if a user accesses a report.
Have reported to HI, am awaiting a response.