These are chat archives for atomix/atomix

29th
Apr 2016
Roman Pearah
@neverfox
Apr 29 2016 02:58

So I was trying to run the standalone server jar and I got this:

~ java -jar atomix-standalone-server-1.0.0-rc4-shaded.jar localhost:5000 -bootstrap
Exception in thread "main" java.lang.NullPointerException
    at java.io.FileInputStream.<init>(FileInputStream.java:130)
    at java.io.FileInputStream.<init>(FileInputStream.java:93)
    at io.atomix.catalyst.util.PropertiesReader.loadProperties(PropertiesReader.java:62)
    at io.atomix.catalyst.util.PropertiesReader.load(PropertiesReader.java:44)
    at io.atomix.standalone.server.StandaloneServer.main(StandaloneServer.java:64)

Looking at the code, it seems to require that you use the -config flag, but the docs imply that you can run it without a file and get the default configuration.

Roman Pearah
@neverfox
Apr 29 2016 04:01

I did go ahead and feed it the example.properties file but that gives me this:

Exception in thread "main" java.lang.IllegalArgumentException: compactionThreads must be positive
    at io.atomix.catalyst.util.Assert.arg(Assert.java:15)
    at io.atomix.catalyst.util.Assert.arg(Assert.java:22)
    at io.atomix.copycat.server.storage.Storage$Builder.withCompactionThreads(Storage.java:463)
    at io.atomix.manager.ResourceServer.builder(ResourceServer.java:145)
    at io.atomix.manager.ResourceServer.builder(ResourceServer.java:122)
    at io.atomix.standalone.server.StandaloneServer.main(StandaloneServer.java:65)

which is odd since the file clearly contains storage.compaction.threads=2

Roman Pearah
@neverfox
Apr 29 2016 04:32
Arg, nvm about the last error. wget had garbled the properties file.
but..now that I have the property file corrected, it get this error:
Exception in thread "main" io.atomix.catalyst.serializer.RegistrationException: no default serializer found for type: class io.atomix.copycat.protocol.CommandRequest
    at io.atomix.catalyst.serializer.SerializerRegistry.register(SerializerRegistry.java:122)
    at io.atomix.copycat.protocol.ClientRequestTypeResolver.resolve(ClientRequestTypeResolver.java:44)
    at io.atomix.catalyst.serializer.SerializerRegistry.resolve(SerializerRegistry.java:78)
    at io.atomix.catalyst.serializer.SerializerRegistry.resolve(SerializerRegistry.java:62)
    at io.atomix.catalyst.serializer.Serializer.resolve(Serializer.java:301)
    at io.atomix.copycat.server.CopycatServer$Builder.build(CopycatServer.java:1040)
    at io.atomix.manager.ResourceServer$Builder.build(ResourceServer.java:624)
    at io.atomix.standalone.server.StandaloneServer.main(StandaloneServer.java:67)
Jordan Halterman
@kuujo
Apr 29 2016 07:34
Hey sorry I've been head down in work projects...
Jordan Halterman
@kuujo
Apr 29 2016 07:39
Hmm... TBH I don't think the standalone server has really been tested since the cluster configuration was changed. I think exception this is an artifact of how the standalone server builds the Serializer. Because you can define serializers in the server configuration, it creates a Serializer but that serializer isn't properly configured. Essentially, it's not configured with the CatalystSerializableSerializer. This can probably be fixed by adding that serializer to the properties file, but there will probably be other side effects, including all the primitive and collection serializers not being registered either. This really needs to be fixed in Catalyst I thinks
Easy fix
Roman Pearah
@neverfox
Apr 29 2016 14:06
Hey thanks
Jordan Halterman
@kuujo
Apr 29 2016 18:29
Hacking out a bunch of
Bah... Hacking out a bunch of bug fixes this weekend. Will release probably on Sunday
Roman Pearah
@neverfox
Apr 29 2016 18:33
:clap: