Since my upgrade from 8.5 to 8.5.1 I am confronted with Java errors.
I saw some posts about the first one when opening any agent (LS or Java) but the suggestions didn’t help my case:
An internal error occurred during: “Collecting Backend Classes information”.
java.lang.NullPointerException
It sounds like disabling the virus scanner helped some people but I tried it and ran the install again in repair mode without any luck.
So I thought maybe I can ignore the error and my agents still work. Unfortunately: no.
My agent is using LS2J and when the Java library gets called a “LS2J Error: Threw java.lang.ExceptionInInitializerError”.
And here comes the next problem into play.
With previous version I could start the Java Debug Console and get more information. Unfortunately, selecting “Tools - Show Java Debug Console” does nothing.
So I thought let’s check out other settings. Recompiling the whole database, enabling the Java Debugging Preferences for Client/Agents and saving the library with “Compile Java code with debugging information” didn’t change anything.
So maybe there is someone out there who found a permanent solution for these Java errors.
I guess the next thing to test could be an external debugger but it looks like the problem is somewhere way before my library.
I spent some time in the Developer Lab at Lotusphere and we found some background about the “Collecting Backend Classes information” error. It appears to be harmless, more of a timing problem when loading the classes and apparently only for some users.
Workaround: Before opening/creating any agent go to ‘Help - Help Contents’. This initializes the type-ahead data for the agents and the error will be gone. Unfortunately, you have to do this after every Notes start. I expect this to be resolved in 8.5.2.
The other Java errors are a bit trickier. My client threw several errors in the backend already (without causing any problems before) so I was told to best de-install/re-install Notes which I did. Unfortunately, after several re-installs and eventually removing all previous Notes files from my machine (incl. names, desktop, bookmarks) I reached a situation where Notes crashed with almost every opening, right-click or other database action.
I took this as a sign to wipe my machine as I was planning a Win7 install anyway and this radical move helped me restore my machine and now even my LS2J agent runs again.
With the Java compiler it was the same thing. I was only able to start it again after the complete re-install and after enabling the ‘Client Agents/Applets’ port in the ‘Java Debugging Preferences’ (which I tried before without success).
I can only hope that not everyone has to take the same steps. And I’m not sure yet on how to propose a general upgrade to 8.5.1 in our company. But … maybe it was just my machine.
Subject: The same issue occurs in Lotus Notes Client 8.5.1 and 8.5.3 (Early Adopter
Does anyone know how to rung Java code in the front end? the agent I tried to use works well in backround, but throws the Java Initialiazer error when run from the lotus notes client front end.
Thomas, I am experiencing the same problem. I think something is not working properly on Lotus Notes 8.5.1 for the Java Engine. I’ve been through the same error messages when trying to open the agents in Lotus Notes Designer and when executing Java code through the agents.
Subject: This is happening to a lot of us. I haven’t seen any real solution yet…
The best I can do to resolve the issue for any length of time is quit Notes, delete my cache db & restart the OS.
Then, before starting any other applications:
Start Notes
Start designer
Open a LS agent
If I can do this without receiving the error, everything will be fine… for 5 minutes to 5 days.
Whether all of this is really necessary, I don’t know.
It’s such a pain in the butt to quit everything, restart & get back where you were in the first place… but I do it all anyway.
It seems the best way to get working again - interrupting my work for (hopefully) only 15 minutes. If I don’t do all this, I find that I may have to to it all over again anyway. That sucks the life out of anyone’s workday.