java.lang.IllegalArgumentException

Field buildData must have a getter & setter, or getAt & setAt, or busyLock & unlock.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web12106

  • Field buildData must have a getter & setter, or getAt & setAt, or busyLock & unlock.
  • via GitHub by peter-lawrey
    , 8 months ago
    Field entry must have a getter and setter.
  • via GitHub by Cotton-Ben
    , 8 months ago
    Field entry must have a getter and setter.
  • Stack trace

    • java.lang.IllegalArgumentException: Field buildData must have a getter & setter, or getAt & setAt, or busyLock & unlock. at net.openhft.lang.model.DataValueModelImpl.<init>(DataValueModelImpl.java:220) at net.openhft.lang.model.DataValueModels.acquireModel(DataValueModels.java:46) at net.openhft.lang.model.DataValueGenerator.firstPrimitiveFieldType(DataValueGenerator.java:96) at net.openhft.chronicle.map.ChronicleMapBuilder.valueAlignment(ChronicleMapBuilder.java:636) at net.openhft.chronicle.map.ChronicleMapBuilder.entrySizeInfo(ChronicleMapBuilder.java:474) at net.openhft.chronicle.map.ChronicleMapBuilder.averageChunksPerEntry(ChronicleMapBuilder.java:574) at net.openhft.chronicle.map.ChronicleMapBuilder.trySegments(ChronicleMapBuilder.java:816) at net.openhft.chronicle.map.ChronicleMapBuilder.actualSegments(ChronicleMapBuilder.java:801) at net.openhft.chronicle.map.ChronicleMapBuilder.segmentHeaderSize(ChronicleMapBuilder.java:824) at net.openhft.chronicle.map.VanillaChronicleMap.<init>(VanillaChronicleMap.java:176) at net.openhft.chronicle.map.ChronicleMapBuilder.newMap(ChronicleMapBuilder.java:1389) at net.openhft.chronicle.map.ChronicleMapBuilder.createWithFile(ChronicleMapBuilder.java:1316) at net.openhft.chronicle.map.ChronicleMapBuilder.createPersistedTo(ChronicleMapBuilder.java:1250)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.