Author Topic: Friday, 1/19/2018 Mission Abort  (Read 268 times)

Offline AKA_Relent

  • Training Officer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1670
  • AKA_Wardogs
    • View Profile
Friday, 1/19/2018 Mission Abort
« on: January 21, 2018, 04:09:48 pm »

I looked at the log for IL2/46 created from Friday's mission, where the IL2 server died after about 2.5 hours.  I saw the following exception about 120+ times in the log before it croaked:

[3:39:23 AM]   1604>[3:39:34 AM]   java.lang.NullPointerException
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at com.maddox.il2.engine.Interpolators.tick(
[3:39:34 AM]      at com.maddox.il2.engine.Actor.interpolateTick(
[3:39:34 AM]      at com.maddox.il2.engine.InterpolateAdapter.msgTimeOut(
[3:39:34 AM]      at com.maddox.rts.MsgTimeOut.invokeListener(
[3:39:34 AM]      at com.maddox.rts.Message._send(
[3:39:34 AM]      at com.maddox.rts.Message.sendToObject(
[3:39:34 AM]      at com.maddox.rts.Message.sendTo(
[3:39:34 AM]      at com.maddox.rts.Message.trySend(
[3:39:34 AM]      at com.maddox.rts.Time.loopMessages(
[3:39:34 AM]      at com.maddox.rts.RTSConf.loopMsgs(
[3:39:34 AM]      at
[3:39:34 AM]      at
[3:39:34 AM]      at

From the various messages, it seems the crash occurred while AI aircraft were engaged.  Looking at the bolded message above, I'm wondering if this issue occurred when AI fighters were engaging other AI fighters.  If this is the case, it's probably not something that happens very often (i.e. a red fighter sweep engages a blue fighter sweep, or sweep vs escort, etc.).  It may have just been a fluke that a large number of AI fighters from each side were in a crazy dogfight and it overwhelmed the software LOL :).  Maybe something missed in QA way back in IL2/46 development.

Hopefully this won't happen again/very often.

S! Rel