Hello! I have a log warning with exception and without callstack. How can I track where error came from or maybe fix?
WARN SFSWorker:Sys:3 controllers.v290.SystemReqController java.lang.NullPointerException
Log warning without call stack
-
Kkkosatkin
- Posts: 14
- Joined: 09 Sep 2025, 13:10
Re: Log warning without call stack
Hi,
this is usually caused by the JIT compiler when optimizing code that is invoked very often.
There's a specific setting to get the stack traces back:
Hope it helps
this is usually caused by the JIT compiler when optimizing code that is invoked very often.
There's a specific setting to get the stack traces back:
You can add it to your configuration, via the AdminTool > Server Settings > JVM Settings, then saving and restarting SFS2X.-XX:-OmitStackTraceInFastThrow
Hope it helps
-
Kkkosatkin
- Posts: 14
- Joined: 09 Sep 2025, 13:10
Re: Log warning without call stack
Thanks, thats really helped with viewing call stack. Further research using decompiler showed that error can be on a server side, addBuddy function, on error handling block.Lapo wrote: 20 Nov 2025, 10:46 Hi,
this is usually caused by the JIT compiler when optimizing code that is invoked very often.
There's a specific setting to get the stack traces back:You can add it to your configuration, via the AdminTool > Server Settings > JVM Settings, then saving and restarting SFS2X.-XX:-OmitStackTraceInFastThrow
Hope it helps
"throw new SFSBuddyListException("Cannot add Buddy to " + ownerName + " BuddyList. The BuddyList was not loaded first.");" - there is no "errorData" parameter here
Re: Log warning without call stack
Yes, because there is no server notification sent back to client about this error.Kkkosatkin wrote: 21 Nov 2025, 16:04 "throw new SFSBuddyListException("Cannot add Buddy to " + ownerName + " BuddyList. The BuddyList was not loaded first.");" - there is no "errorData" parameter here
You should catch the issue when you're testing and fix the client by initializing the BuddyList in the LOGIN event, and before allowing users to add buddies to their list.
Cheers
-
Kkkosatkin
- Posts: 14
- Joined: 09 Sep 2025, 13:10
Re: Log warning without call stack
Hello again. I mean, there is an error on server-side code. There is no argument to the error at class constructor, at throwing error exception.
throw new SFSBuddyListException("Cannot add Buddy to " + ownerName + " BuddyList. The BuddyList was not loaded first.") - require "errorData" parameter here. Parent class SFSException constructor set "errorData = null", but the "notifyRequestError" function try to get this value. This error causes "java.lang.NullPointerException" on a log viwer when trying to send error notification. On the client-side, we continue to investigate where the error with desync of buddyList.Inited occured.
throw new SFSBuddyListException("Cannot add Buddy to " + ownerName + " BuddyList. The BuddyList was not loaded first.") - require "errorData" parameter here. Parent class SFSException constructor set "errorData = null", but the "notifyRequestError" function try to get this value. This error causes "java.lang.NullPointerException" on a log viwer when trying to send error notification. On the client-side, we continue to investigate where the error with desync of buddyList.Inited occured.
Re: Log warning without call stack
Can you provide a step by step description of how to reproduce this?
The details we need are listed here: https://forums.smartfoxserver.com/viewtopic.php?t=16497
Thanks
The details we need are listed here: https://forums.smartfoxserver.com/viewtopic.php?t=16497
Thanks
-
Kkkosatkin
- Posts: 14
- Joined: 09 Sep 2025, 13:10
Re: Log warning without call stack
We haven't fully figured out how this case happens on the client, but we are seeing an error on the server side. On the screenshots 1-2 you can see that when error is thrown (SFSBuddyListException), "errorData" parameter is not used in the constructor, but then this parameter is used (3-rd screenshot)






Re: Log warning without call stack
Yeah... we don't need the decompiled code
We know it already. I was asking for a reproducible case.
Thanks anyways.
Thanks anyways.
Re: Log warning without call stack
If you find a way to reproduce the problem please let us know.
Cheers
Cheers