Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-11110

UnsupportedOperationException: null when stopping grid

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.7
    • 2.10
    • None
    • None
    • Fixed NPE on stopping grid node with enabled collision SPI.
    • Release Notes Required

    Description

      After upgrading to 2.7 we've started getting these errors when stopping grids:

      java.lang.UnsupportedOperationException: null
      	at org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.Ignition.stop(Ignition.java:225) ~[ignite-core-2.7.0.jar:2.7.0]
      	at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568) ~[ignite-core-2.7.0.jar:2.7.0]
      

      At first glance it looks likely that it was introduced with commit d04d764 (the GridJobProcessor still calls clear() on maps).

      Attachments

        Issue Links

          Activity

            People

              antkr Anton Kurbanov
              jens.borgland Jens Borgland
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m