i was just trying to start the baratine distribution:
downloading baratine-0.11.3.zip
unzip
bin\baratine start
results in
null
java.lang.NullPointerException
at com.caucho.v5.web.cli.CommandStart.doCommandImpl(CommandStart.java:66)
at com.caucho.v5.web.cli.CommandStart.doCommandImpl(CommandStart.java:41)
at com.caucho.v5.cli.args.CommandBase.doCommand(CommandBase.java:304)
at com.caucho.v5.cli.args.ArgsBase.doCommand(ArgsBase.java:159)
at com.caucho.v5.cli.args.ArgsBase.doMain(ArgsBase.java:181)
at com.caucho.v5.cli.baratine.BaratineCommandLine.main(BaratineCommandLine.java:46)
tested on Windows7 and centos 7.4 both using
java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
Is the release broken ? Do i have to start baratine in a different way ?
(I did manage to start my Services using "Web.go()" within eclipse ... but i want to do a cluster deployment with different pods running on multiple servers)
so i need to wrap the startup in a public void main(String[] args) method and configure things programatically ?
./bin/baratine start (+ deploy a packaged bar/jar file) is not possible at the moment (even for non-clustered deployments = no pods deploymens)?
When can i expect that the pod functionality and sharding via urls on multiple server will be available again ?
Best regards
Thomas
On Friday, June 10, 2016 at 8:57:54 AM UTC+2, Nam Nguyen wrote:
> Hi Thomas,
>
> We are reworking the clustering and it doesn't work at the moment. We
> are currently focusing on the single server case for the upcoming 1.0
> release.
>
> -- Nam
>