Ah true. Inserting the default values for all (or at least the most
unintuitive/obvious) settings could be a sensible choice.
On Tue, Sep 24, 2013 at 10:01 PM, Ali Lown wrote:
> Bruno,
>
> You can use ant only for the src releases.
> (Why would someone have dev tools if using a binary release?)
Bruno,
You can use ant only for the src releases.
(Why would someone have dev tools if using a binary release?)
Perhaps putting the default values in, so that the user isn't required to
think to get a local server started?
Ali
On 24 Sep 2013 20:49, "Bruno Gonzalez (aka stenyak)"
wrote:
> Corre
Correct me if I'm wrong, but I think the intended way to set up the
configuration would be to use the relevant ant targets (with -D
parameters), rather than editing any file by hand?
On Tue, Sep 24, 2013 at 9:39 PM, Raphael Bircher wrote:
> Hi Ali
>
> Am 24.09.13 21:26, schrieb Ali Lown:
>
> R
Hi Ali
Am 24.09.13 21:26, schrieb Ali Lown:
Raphael,
This is because you haven't actual set yours settings in server.config.
Thanks for the quick answare. I assumed something like this.
As the error says websocket_max_message_size is not an integer.
The line in your server.config currently
E@" should be replaced by a sensible
numbers for your configuration.
You will need to do this for all the settings where the value is @SOMETHING@
Hope this helps.
Ali
On 24/09/2013, Raphael Bircher wrote:
> Hi at all
>
> I run in a Java Exeption on RC4. I hope this is my error
&g
Hi at all
I run in a Java Exeption on RC4. I hope this is my error
INFO: An exception was caught and reported. Message:
java.lang.NumberFormatException: For input string:
"@WEBSOCKET_MAX_MESSAGE_SIZE@"
org.apache.commons.configuration.ConversionException:
'websocket_max_messag
