This is occurring with a reactor that was built with 2.13. After updated to A2 a lot of console spam is showing up...here is the message

[SEVERE] A TileEntity type erogenousbeef.bigreactors.common.tileentity.TileEntityReactorGlass at world,1098,70,724 has throw an exception trying to write state. It will not persist. Report this to the mod author

Here is the stack trace:
2014-01-05 13:17:10 [SEVERE] [ForgeModLoader] A TileEntity type erogenousbeef.bigreactors.common.tileentity.TileEntityReactorGlass at world,1104,69,734 has throw an exception trying to write state. It will not persist. Report this to the mod author
java.lang.NullPointerException
at erogenousbeef.core.multiblock.MultiblockTileEntityBase.func_70310_b(MultiblockTileEntityBase.java:103)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75820_a(AnvilChunkLoader.java:424)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75816_a(AnvilChunkLoader.java:215)
at net.minecraft.world.gen.ChunkProviderServer.func_73242_b(ChunkProviderServer.java:353)
at net.minecraft.world.gen.ChunkProviderServer.func_73151_a(ChunkProviderServer.java:429)
at net.minecraft.world.WorldServer.func_73044_a(WorldServer.java:1264)
at net.minecraft.server.MinecraftServer.func_71267_a(MinecraftServer.java:547)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:787)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:663)
at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16)

This repeats several times for the same reactor...then is stops for a while and comes back...the reactor worked prior to the update.

The reactor has 12 fuel rods in it cooled by liquid ender. If it makes a difference we also just recently switched the configs to use the more expensive recipes for casings and glass (this reactor was made with the cheaper recipes).

Screenshots of the exact reactor build can be shown if needed

That's very strange, I would've expected to see this in testing. What's your server environment? MCPC+? Is threaded chunkloading enabled?

Checked a second reactor (also pre-built) with 4 rods and is water cooled...same issues.

I've also noticed that these reactors are split between two chunks...perhaps your fix for the double chests did something.

I am using MCPC+ and asynchronous chunkloading is enabled. This was not an issue before now.

I can try with the async chunkoading turned off if it would help however this error seems to come and go from time to time...even if I remain stationary keeping the nearby chunks consistently loaded.

What version were you on prior to the upgrade? .13a, something earlier?
On Jan 6, 2014 1:41 AM, "jalapeno777" [email protected] wrote:

I am using MCPC+ and asynchronous chunkloading is enabled. This was not an
issue before now.

I can try with the async chunkoading turned off if it would help however
this error seems to come and go from time to time...even if I remain
stationary keeping the nearby chunks consistently loaded.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/86#issuecomment-31620866
.

Previous version was 0.2.10A

Interesting. Okay, I'll look through this. I think I see a fix. Give me a
day.

On Mon, Jan 6, 2014 at 1:44 AM, jalapeno777 [email protected]:

Previous version was 0.2.10A

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/86#issuecomment-31620947
.

Any luck with this? It's beginning to plague the server pretty severely.

I've been caught late at work the past two days. My plan is to try to roll
out a fix later tonight.
On Jan 7, 2014 4:25 PM, "jalapeno777" [email protected] wrote:

Any luck with this? It's beginning to plague the server pretty severely.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/86#issuecomment-31746417
.

Fixed by erogenousbeef-zz/BeefCore@20a6f89 in BeefCore. Will be in 0.2.14A later today.

0.2.14A is now out.