After the upgrade to V9, I now get this error message after each change in the configuration (save/update/test/edit). Any idea why? How I can solve this?
NullPointerException error after upgrade to V9 (m_application is null)
NullPointerException error after upgrade to V9 (m_application is null)
Niels
(V9.0 build 3241 - MariaDB - Windows)
(V9.0 build 3241 - MariaDB - Windows)
Re: NullPointerException error after upgrade to V9 (m_application is null)
Addition to the previous post:
As usual, after the upgrade I put back the BASServer.props file from the previous install (in my case V8.8 ). I compared that file to the default file that was included with the V9 install and found two changes. I then changed these lines in the BASServer.props file. See below old line and new line.
The issue with the NullPointerException seems to be resolved. Not sure whether there is any relationship.
As usual, after the upgrade I put back the BASServer.props file from the previous install (in my case V8.8 ). I compared that file to the default file that was included with the V9 install and found two changes. I then changed these lines in the BASServer.props file. See below old line and new line.
The issue with the NullPointerException seems to be resolved. Not sure whether there is any relationship.
Code: Select all
# OLD LINE: DirectoryServiceProvider=tcp\://dep\:61616
DirectoryServiceProvider=tcp://localhost:61616
# OLD LINE: JMS_BROKER_CONNECTOR=tcp\://dep\:61616
JMS_BROKER_CONNECTOR=tcp://localhost:61616
Niels
(V9.0 build 3241 - MariaDB - Windows)
(V9.0 build 3241 - MariaDB - Windows)
Re: NullPointerException error after upgrade to V9 (m_application is null)
The default is "localhost". Not sure how / why it got changed to //dep. I "DO" change mine all the time since I develop using the client server methodology. But then it is JUST the name of the server.. i.e. tcp://myserver:61616
Bruce
Bruce
Re: NullPointerException error after upgrade to V9 (m_application is null)
Things can change in these config files between versions so I usually do all changes anew in all files to avoid unexplained issues like this (and potentially also bug fixes, performance issues etc. e.g Aware might add some line, change some line here and there to change or optimize something). I learned this the hard way haha having a couple complete server meltdowns following changes I didn't "catch".nhofkes wrote: ↑Tue Feb 20, 2024 2:27 pm Addition to the previous post:
As usual, after the upgrade I put back the BASServer.props file from the previous install (in my case V8.8 ). I compared that file to the default file that was included with the V9 install and found two changes. I then changed these lines in the BASServer.props file. See below old line and new line.
The issue with the NullPointerException seems to be resolved. Not sure whether there is any relationship.
Code: Select all
# OLD LINE: DirectoryServiceProvider=tcp\://dep\:61616 DirectoryServiceProvider=tcp://localhost:61616 # OLD LINE: JMS_BROKER_CONNECTOR=tcp\://dep\:61616 JMS_BROKER_CONNECTOR=tcp://localhost:61616
Henrik (V8 Developer Ed. - Windows)
Re: NullPointerException error after upgrade to V9 (m_application is null)
Thanks Bruce and Henrik. I will change my update procedure.
Niels
(V9.0 build 3241 - MariaDB - Windows)
(V9.0 build 3241 - MariaDB - Windows)