Re: Could not connect to MariaDB

[Maxim Solodovnik]

Thanks for reporting back and investigation
This make a lot of sense

On Thu, 4 Apr 2019 at 15:46, René Scholz
 wrote:
>
> Hello Maxim,
>
> thank you for the indoctrination about the using of graphics in emails. I 
> will do better next time.
>
> My Solution:
>
> The Parameter "serverTimezone" must in the first line of the Driver-command 
> (where is separated by "&").
> It doesn't matter where you put it.
> When I put it into the comma-separated-part it's not functionally.
>
>
> Here's my line in the mysql-persistence.xml:
>
> value="DriverClassName=com.mysql.cj.jdbc.Driver
> , 
> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&serverTimezone=Europe/Berlin&createDatabaseIfNotExist=true&characterEncoding=utf-8
>  
> &connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true
> , maxTotal=100
> , maxIdle=100
> , minIdle=0
> , maxWaitMillis=1
> , TestOnBorrow=true
> , poolPreparedStatements=true
> , Username=
> , Password=" />
>
>
> Best regards,
>
> René
>
>
>
>
> Am 03.04.2019 um 14:28 schrieb Maxim Solodovnik:
>
> 2 points:
> 1) no need to share screen-shot to share _text_ :)
> 2) when I wrote "Could you please check if persistense.xml have all necessary 
> parameters" I mean:
>a) open file in your favorite editor
>b) check it's content
>
> If changes made by installer are "disappear", check:
> 1) if you have only one copy of OM on your VM
> 2) if you don't have some script rewriting persistense.xml
>
> Additionally after successful installation there should be DB tables, and 
> these tables shouldn't be empty
>
> BTW are you using MariaDB or MySql?
>
> On Wed, 3 Apr 2019 at 18:51, R. Scholz  
> wrote:
>>
>> No way.
>> At the installation-process it stuck.
>>
>>
>>
>> Am 03.04.2019 um 11:55 schrieb Maxim Solodovnik:
>>
>> Hello René,
>>
>> after successful installation your mysql_persistense.xml file should be 
>> copied to persistense.xml
>> Could you please check if persistense.xml have all necessary parameters?
>> 1) correct DB host/port/name
>> 2) correct DB credentials
>> 3) this additional time-zone parameter
>>
>> On Wed, 3 Apr 2019 at 16:28, R. Scholz  
>> wrote:
>>>
>>> Hm, since a few minutes the " The server time zone value 'CEST' "-error is 
>>> back.
>>>
>>> I had change that after boot there is no GUI.
>>> sudo systemctl set-default multi-user.target
>>> and make a reboot.
>>>
>>> After that I get the installation-screen and on the scond screen with the 
>>> Database-choice I get the error.
>>>
>>> A little bit frustrating.
>>>
>>> Best regards,
>>>
>>> René
>>>
>>>
>>> Am 03.04.2019 um 11:06 schrieb Maxim Solodovnik:
>>>
>>> Thanks for reporting back!
>>> great it works as expected :)
>>>
>>> On Wed, 3 Apr 2019 at 13:22, R. Scholz  
>>> wrote:

 Hello Maxim,

 the result of "timedatectl":
   Local time: Mi 2019-04-03 08:06:21 CEST
   Universal time: Mi 2019-04-03 06:06:21 UTC
 RTC time: Mi 2019-04-03 06:06:21
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
 systemd-timesyncd.service active: no
  RTC in local TZ: no

 Now I put the parameter you wrote helpful in your last email and it seems 
 to be functionally.

 Here is the fully parameter I actually use, if someone need it.

 >>> value="DriverClassName=com.mysql.cj.jdbc.Driver
 , 
 Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_ge
 , maxTotal=100
 , maxIdle=100
 , minIdle=0
 , maxWaitMillis=1
 , TestOnBorrow=true
 , poolPreparedStatements=true
 , serverTimezone=Europe/Berlin
 , Username=
 , Password=" />

 I am a little bit amazed about one thing: To test the new OM5 I made a lot 
 of times a new virtual machine with the same Ubuntu 18.04-Installation. I 
 mean that the
 the first times the OM-MySQL-Connection runs without problems. No 
 modification necessary. Anytime the error Maxim describe occurs, and I 
 dont know why.
 Sure, I made something different, but I have no idea what it can be.

 OK, for the moment I am very happy, get a gulp from my fresh/hot coffee 
 and look forward to test the newest modification Maxim implemented 
 yesterday in a speed where I am very surprised.
 Maxim: Very good work!

 Best regards,

 René


 Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:

 Just have tried to change TZ on my te

Re: Could not connect to MariaDB

[René Scholz]

Hello Maxim,

thank you for the indoctrination about the using of graphics in emails. 
I will do better next time.


My Solution:

The Parameter "serverTimezone" must in the first line of the 
Driver-command (where is separated by "&").

It doesn't matter where you put it.
When I put it into the comma-separated-part it's not functionally.


Here's my line in the mysql-persistence.xml:

value="DriverClassName=com.mysql.cj.jdbc.Driver
    , 
Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&*serverTimezone=Europe/Berlin&*createDatabaseIfNotExist=true&characterEncoding=utf-8 
&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true

, maxTotal=100
, maxIdle=100
, minIdle=0
, maxWaitMillis=1
, TestOnBorrow=true
, poolPreparedStatements=true
, Username=
, Password=" />


Best regards,

René




Am 03.04.2019 um 14:28 schrieb Maxim Solodovnik:

2 points:
1) no need to share screen-shot to share _text_ :)
2) when I wrote "Could you please check if persistense.xml have all 
necessary parameters" I mean:

   a) open file in your favorite editor
   b) check it's content

If changes made by installer are "disappear", check:
1) if you have only one copy of OM on your VM
2) if you don't have some script rewriting persistense.xml

Additionally after successful installation there should be DB tables, 
and these tables shouldn't be empty


BTW are you using MariaDB or MySql?

On Wed, 3 Apr 2019 at 18:51, R. Scholz 
> wrote:


No way.
At the installation-process it stuck.



Am 03.04.2019 um 11:55 schrieb Maxim Solodovnik:

Hello René,

after successful installation your mysql_persistense.xml file
should be copied to persistense.xml
Could you please check if persistense.xml have all necessary
parameters?
1) correct DB host/port/name
2) correct DB credentials
3) this additional time-zone parameter

On Wed, 3 Apr 2019 at 16:28, R. Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hm, since a few minutes the " The server time zone value
'CEST' "-error is back.

I had change that after boot there is no GUI.
sudo systemctl set-default multi-user.target
and make a reboot.

After that I get the installation-screen and on the scond
screen with the Database-choice I get the error.

A little bit frustrating.

Best regards,

René


Am 03.04.2019 um 11:06 schrieb Maxim Solodovnik:

Thanks for reporting back!
great it works as expected :)

On Wed, 3 Apr 2019 at 13:22, R. Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello Maxim,

the result of "timedatectl":
  Local time: Mi 2019-04-03 08:06:21
CEST
  Universal time: Mi 2019-04-03 06:06:21 UTC
    RTC time: Mi 2019-04-03 06:06:21
   Time zone: Europe/Berlin (CEST,
+0200)
   System clock synchronized: no
systemd-timesyncd.service active: no
 RTC in local TZ: no

Now I put the parameter you wrote helpful in your last
email and it seems to be functionally.

Here is the fully parameter I actually use, if someone
need it.



I am a little bit amazed about one thing: To test the
new OM5 I made a lot of times a new virtual machine with
the same Ubuntu 18.04-Installation. I mean that the
the first times the OM-MySQL-Connection runs without
problems. No modification necessary. Anytime the error
Maxim describe occurs, and I dont know why.
Sure, I made something different, but I have no idea
what it can be.

OK, for the moment I am very happy, get a gulp from my
fresh/hot coffee and look forward to test the newest
modification Maxim implemented yesterday in a speed
where I am very surprised.
Maxim: Very good work!

Best regards,

René


Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:

Just have tried to change TZ on my test Ubuntu server
to be CEST and:

*sudo timedatectl set-timezone CEST*
Failed to set time zone: Invalid time zone 'CEST'

What is the result of `timedatectl` command on your system?


On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello René,

Re: Could not connect to MariaDB

[Maxim Solodovnik]

Hello René,

after successful installation your mysql_persistense.xml file should be
copied to persistense.xml
Could you please check if persistense.xml have all necessary parameters?
1) correct DB host/port/name
2) correct DB credentials
3) this additional time-zone parameter

On Wed, 3 Apr 2019 at 16:28, R. Scholz 
wrote:

> Hm, since a few minutes the " The server time zone value 'CEST' "-error is
> back.
>
> I had change that after boot there is no GUI.
> sudo systemctl set-default multi-user.target
> and make a reboot.
>
> After that I get the installation-screen and on the scond screen with the
> Database-choice I get the error.
>
> A little bit frustrating.
>
> Best regards,
>
> René
>
>
> Am 03.04.2019 um 11:06 schrieb Maxim Solodovnik:
>
> Thanks for reporting back!
> great it works as expected :)
>
> On Wed, 3 Apr 2019 at 13:22, R. Scholz 
> wrote:
>
>> Hello Maxim,
>>
>> the result of "timedatectl":
>>   Local time: Mi 2019-04-03 08:06:21 CEST
>>   Universal time: Mi 2019-04-03 06:06:21 UTC
>> RTC time: Mi 2019-04-03 06:06:21
>>Time zone: Europe/Berlin (CEST, +0200)
>>System clock synchronized: no
>> systemd-timesyncd.service active: no
>>  RTC in local TZ: no
>>
>> Now I put the parameter you wrote helpful in your last email and it seems
>> to be functionally.
>>
>> Here is the fully parameter I actually use, if someone need it.
>>
>> > value="DriverClassName=com.mysql.cj.jdbc.Driver
>> ,
>> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_ge
>> , maxTotal=100
>> , maxIdle=100
>> , minIdle=0
>> , maxWaitMillis=1
>> , TestOnBorrow=true
>> , poolPreparedStatements=true
>> , serverTimezone=Europe/Berlin
>> , Username=
>> , Password=" />
>>
>> I am a little bit amazed about one thing: To test the new OM5 I made a
>> lot of times a new virtual machine with the same Ubuntu 18.04-Installation.
>> I mean that the
>> the first times the OM-MySQL-Connection runs without problems. No
>> modification necessary. Anytime the error Maxim describe occurs, and I dont
>> know why.
>> Sure, I made something different, but I have no idea what it can be.
>>
>> OK, for the moment I am very happy, get a gulp from my fresh/hot coffee
>> and look forward to test the newest modification Maxim implemented
>> yesterday in a speed where I am very surprised.
>> Maxim: Very good work!
>>
>> Best regards,
>>
>> René
>>
>>
>> Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:
>>
>> Just have tried to change TZ on my test Ubuntu server to be CEST and:
>>
>> *sudo timedatectl set-timezone CEST*
>> Failed to set time zone: Invalid time zone 'CEST'
>>
>> What is the result of `timedatectl` command on your system?
>>
>>
>> On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik 
>> wrote:
>>
>>> Hello René,
>>>
>>> I'll try to set up VM to test following steps (so here it is untested)
>>> 1) open
>>> ${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
>>> 2) find >> 3) add ", serverTimezone=Europe/Berlin" to the comma separated values
>>>
>>> run command line or web installer
>>>
>>> On Wed, 3 Apr 2019 at 02:16, R. Scholz
>>>  wrote:
>>> >
>>> > Hello,
>>> >
>>> > I dont know where I have to write what TimeZone-Variable.
>>> > I think it is the
>>> "/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
>>> >
>>> > But where I have to write what to eliminate the "The server time zone
>>> value 'CEST' is unrecognized or..."-error?
>>> >
>>> > Best regards,
>>> >
>>> > René
>>> >
>>> >
>>> >
>>> >
>>> > Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
>>> >
>>> > Hello All,
>>> >
>>> > recently I got error report from Alvaro regarding DB connection issue
>>> while MariaDB us used
>>> > After some "email ping-pong" I got logs, relevant part of logs can be
>>> found here [1]
>>> >
>>> > The first, huge stack trace provides only general information: "Could
>>> not create connection to database server. Attempted reconnect 3 times.
>>> Giving up."
>>> > Nothing to work with
>>> >
>>> > BUT the second one states: "The server time zone value 'CEST' is
>>> unrecognized or represents more than one time zone. You must configure
>>> either the server or JDBC driver (via the serverTimezone configuration
>>> property) to use a more specifc time zone value if you want to utilize time
>>> zone support."
>>> >
>>> > This one provides the root cause of the problem and possible solutions:
>>> > 1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
>>> > 2) edit persistense.xml file and add `serverTimezone` configuration
>>> property with TZ of MariaDb server
>>> >
>>> > Hope it can help
>>> >
>>> > [1]
>>> > java.sql.SQLNonTransientConnectionException: Could not create
>>> connection to databa

Re: Could not connect to MariaDB

[R. Scholz]

Hm, since a few minutes the " The server time zone value 'CEST' "-error 
is back.


I had change that after boot there is no GUI.
sudo systemctl set-default multi-user.target
and make a reboot.

After that I get the installation-screen and on the scond screen with 
the Database-choice I get the error.


A little bit frustrating.

Best regards,

René


Am 03.04.2019 um 11:06 schrieb Maxim Solodovnik:

Thanks for reporting back!
great it works as expected :)

On Wed, 3 Apr 2019 at 13:22, R. Scholz 
> wrote:


Hello Maxim,

the result of "timedatectl":
  Local time: Mi 2019-04-03 08:06:21 CEST
  Universal time: Mi 2019-04-03 06:06:21 UTC
    RTC time: Mi 2019-04-03 06:06:21
   Time zone: Europe/Berlin (CEST, +0200)
   System clock synchronized: no
systemd-timesyncd.service active: no
 RTC in local TZ: no

Now I put the parameter you wrote helpful in your last email and
it seems to be functionally.

Here is the fully parameter I actually use, if someone need it.



I am a little bit amazed about one thing: To test the new OM5 I
made a lot of times a new virtual machine with the same Ubuntu
18.04-Installation. I mean that the
the first times the OM-MySQL-Connection runs without problems. No
modification necessary. Anytime the error Maxim describe occurs,
and I dont know why.
Sure, I made something different, but I have no idea what it can be.

OK, for the moment I am very happy, get a gulp from my fresh/hot
coffee and look forward to test the newest modification Maxim
implemented yesterday in a speed where I am very surprised.
Maxim: Very good work!

Best regards,

René


Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:

Just have tried to change TZ on my test Ubuntu server to be CEST and:

*sudo timedatectl set-timezone CEST*
Failed to set time zone: Invalid time zone 'CEST'

What is the result of `timedatectl` command on your system?


On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello René,

I'll try to set up VM to test following steps (so here it is
untested)
1) open

${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
2) find mailto:rene.sch...@abakus-edv-systems.de>> wrote:
>
> Hello,
>
> I dont know where I have to write what TimeZone-Variable.
> I think it is the

"/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
>
> But where I have to write what to eliminate the "The server
time zone value 'CEST' is unrecognized or..."-error?
>
> Best regards,
>
> René
>
>
>
>
> Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
>
> Hello All,
>
> recently I got error report from Alvaro regarding DB
connection issue while MariaDB us used
> After some "email ping-pong" I got logs, relevant part of
logs can be found here [1]
>
> The first, huge stack trace provides only general
information: "Could not create connection to database server.
Attempted reconnect 3 times. Giving up."
> Nothing to work with
>
> BUT the second one states: "The server time zone value
'CEST' is unrecognized or represents more than one time zone.
You must configure either the server or JDBC driver (via the
serverTimezone configuration property) to use a more specifc
time zone value if you want to utilize time zone support."
>
> This one provides the root cause of the problem and
possible solutions:
> 1) change server TZ to be more specific i.e. Europe/Berlin
(not CEST)
> 2) edit persistense.xml file and add `serverTimezone`
configuration property with TZ of MariaDb server
>
> Hope it can help
>
> [1]
> java.sql.SQLNonTransientConnectionException: Could not
create connection to database server. Attempted reconnect 3
times. Giving up.
> at

com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
> at

com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> at

com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
> at

com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
> at

com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
> at

com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
> at
com.mysql.cj.jdbc.

Re: Could not connect to MariaDB

[Maxim Solodovnik]

Thanks for reporting back!
great it works as expected :)

On Wed, 3 Apr 2019 at 13:22, R. Scholz 
wrote:

> Hello Maxim,
>
> the result of "timedatectl":
>   Local time: Mi 2019-04-03 08:06:21 CEST
>   Universal time: Mi 2019-04-03 06:06:21 UTC
> RTC time: Mi 2019-04-03 06:06:21
>Time zone: Europe/Berlin (CEST, +0200)
>System clock synchronized: no
> systemd-timesyncd.service active: no
>  RTC in local TZ: no
>
> Now I put the parameter you wrote helpful in your last email and it seems
> to be functionally.
>
> Here is the fully parameter I actually use, if someone need it.
>
>  value="DriverClassName=com.mysql.cj.jdbc.Driver
> ,
> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_ge
> , maxTotal=100
> , maxIdle=100
> , minIdle=0
> , maxWaitMillis=1
> , TestOnBorrow=true
> , poolPreparedStatements=true
> , serverTimezone=Europe/Berlin
> , Username=
> , Password=" />
>
> I am a little bit amazed about one thing: To test the new OM5 I made a lot
> of times a new virtual machine with the same Ubuntu 18.04-Installation. I
> mean that the
> the first times the OM-MySQL-Connection runs without problems. No
> modification necessary. Anytime the error Maxim describe occurs, and I dont
> know why.
> Sure, I made something different, but I have no idea what it can be.
>
> OK, for the moment I am very happy, get a gulp from my fresh/hot coffee
> and look forward to test the newest modification Maxim implemented
> yesterday in a speed where I am very surprised.
> Maxim: Very good work!
>
> Best regards,
>
> René
>
>
> Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:
>
> Just have tried to change TZ on my test Ubuntu server to be CEST and:
>
> *sudo timedatectl set-timezone CEST*
> Failed to set time zone: Invalid time zone 'CEST'
>
> What is the result of `timedatectl` command on your system?
>
>
> On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik 
> wrote:
>
>> Hello René,
>>
>> I'll try to set up VM to test following steps (so here it is untested)
>> 1) open
>> ${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
>> 2) find > 3) add ", serverTimezone=Europe/Berlin" to the comma separated values
>>
>> run command line or web installer
>>
>> On Wed, 3 Apr 2019 at 02:16, R. Scholz
>>  wrote:
>> >
>> > Hello,
>> >
>> > I dont know where I have to write what TimeZone-Variable.
>> > I think it is the
>> "/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
>> >
>> > But where I have to write what to eliminate the "The server time zone
>> value 'CEST' is unrecognized or..."-error?
>> >
>> > Best regards,
>> >
>> > René
>> >
>> >
>> >
>> >
>> > Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
>> >
>> > Hello All,
>> >
>> > recently I got error report from Alvaro regarding DB connection issue
>> while MariaDB us used
>> > After some "email ping-pong" I got logs, relevant part of logs can be
>> found here [1]
>> >
>> > The first, huge stack trace provides only general information: "Could
>> not create connection to database server. Attempted reconnect 3 times.
>> Giving up."
>> > Nothing to work with
>> >
>> > BUT the second one states: "The server time zone value 'CEST' is
>> unrecognized or represents more than one time zone. You must configure
>> either the server or JDBC driver (via the serverTimezone configuration
>> property) to use a more specifc time zone value if you want to utilize time
>> zone support."
>> >
>> > This one provides the root cause of the problem and possible solutions:
>> > 1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
>> > 2) edit persistense.xml file and add `serverTimezone` configuration
>> property with TZ of MariaDb server
>> >
>> > Hope it can help
>> >
>> > [1]
>> > java.sql.SQLNonTransientConnectionException: Could not create
>> connection to database server. Attempted reconnect 3 times. Giving up.
>> > at
>> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
>> > at
>> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
>> > at
>> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
>> > at
>> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
>> > at
>> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
>> > at
>> com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
>> > at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
>> > at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
>> > at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
>> > at
>> com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)
>> > 

Re: Could not connect to MariaDB

[R. Scholz]

Hello Maxim,

the result of "timedatectl":
  Local time: Mi 2019-04-03 08:06:21 CEST
  Universal time: Mi 2019-04-03 06:06:21 UTC
    RTC time: Mi 2019-04-03 06:06:21
   Time zone: Europe/Berlin (CEST, +0200)
   System clock synchronized: no
systemd-timesyncd.service active: no
 RTC in local TZ: no

Now I put the parameter you wrote helpful in your last email and it 
seems to be functionally.


Here is the fully parameter I actually use, if someone need it.


        , maxTotal=100
        , maxIdle=100
        , minIdle=0
        , maxWaitMillis=1
        , TestOnBorrow=true
        , poolPreparedStatements=true
        , serverTimezone=Europe/Berlin
        , Username=
        , Password=" />

I am a little bit amazed about one thing: To test the new OM5 I made a 
lot of times a new virtual machine with the same Ubuntu 
18.04-Installation. I mean that the
the first times the OM-MySQL-Connection runs without problems. No 
modification necessary. Anytime the error Maxim describe occurs, and I 
dont know why.

Sure, I made something different, but I have no idea what it can be.

OK, for the moment I am very happy, get a gulp from my fresh/hot coffee 
and look forward to test the newest modification Maxim implemented 
yesterday in a speed where I am very surprised.

Maxim: Very good work!

Best regards,

René


Am 03.04.2019 um 05:25 schrieb Maxim Solodovnik:

Just have tried to change TZ on my test Ubuntu server to be CEST and:

*sudo timedatectl set-timezone CEST*
Failed to set time zone: Invalid time zone 'CEST'

What is the result of `timedatectl` command on your system?


On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik > wrote:


Hello René,

I'll try to set up VM to test following steps (so here it is untested)
1) open

${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
2) find mailto:rene.sch...@abakus-edv-systems.de>> wrote:
>
> Hello,
>
> I dont know where I have to write what TimeZone-Variable.
> I think it is the

"/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
>
> But where I have to write what to eliminate the "The server time
zone value 'CEST' is unrecognized or..."-error?
>
> Best regards,
>
> René
>
>
>
>
> Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
>
> Hello All,
>
> recently I got error report from Alvaro regarding DB connection
issue while MariaDB us used
> After some "email ping-pong" I got logs, relevant part of logs
can be found here [1]
>
> The first, huge stack trace provides only general information:
"Could not create connection to database server. Attempted
reconnect 3 times. Giving up."
> Nothing to work with
>
> BUT the second one states: "The server time zone value 'CEST' is
unrecognized or represents more than one time zone. You must
configure either the server or JDBC driver (via the serverTimezone
configuration property) to use a more specifc time zone value if
you want to utilize time zone support."
>
> This one provides the root cause of the problem and possible
solutions:
> 1) change server TZ to be more specific i.e. Europe/Berlin (not
CEST)
> 2) edit persistense.xml file and add `serverTimezone`
configuration property with TZ of MariaDb server
>
> Hope it can help
>
> [1]
> java.sql.SQLNonTransientConnectionException: Could not create
connection to database server. Attempted reconnect 3 times. Giving up.
> at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
> at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
> at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
> at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
> at
com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
> at
com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
> at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
> at
com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
> at

com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at

org.apache.openmeetings.web.pages.install.InstallWizard$DbStep$1.onValidateModelObjects(InstallWizard.java:266)
> at

org.apache.wicket.markup.html.form.Form.internalOnValidateModelObjects(Form.java:1870)
> at org.apache.wicket.markup.html.form.Form.process(Form.

Re: Could not connect to MariaDB

[Maxim Solodovnik]

Just have tried to change TZ on my test Ubuntu server to be CEST and:

*sudo timedatectl set-timezone CEST*
Failed to set time zone: Invalid time zone 'CEST'

What is the result of `timedatectl` command on your system?


On Wed, 3 Apr 2019 at 07:35, Maxim Solodovnik  wrote:

> Hello René,
>
> I'll try to set up VM to test following steps (so here it is untested)
> 1) open
> ${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
> 2) find  3) add ", serverTimezone=Europe/Berlin" to the comma separated values
>
> run command line or web installer
>
> On Wed, 3 Apr 2019 at 02:16, R. Scholz
>  wrote:
> >
> > Hello,
> >
> > I dont know where I have to write what TimeZone-Variable.
> > I think it is the
> "/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
> >
> > But where I have to write what to eliminate the "The server time zone
> value 'CEST' is unrecognized or..."-error?
> >
> > Best regards,
> >
> > René
> >
> >
> >
> >
> > Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
> >
> > Hello All,
> >
> > recently I got error report from Alvaro regarding DB connection issue
> while MariaDB us used
> > After some "email ping-pong" I got logs, relevant part of logs can be
> found here [1]
> >
> > The first, huge stack trace provides only general information: "Could
> not create connection to database server. Attempted reconnect 3 times.
> Giving up."
> > Nothing to work with
> >
> > BUT the second one states: "The server time zone value 'CEST' is
> unrecognized or represents more than one time zone. You must configure
> either the server or JDBC driver (via the serverTimezone configuration
> property) to use a more specifc time zone value if you want to utilize time
> zone support."
> >
> > This one provides the root cause of the problem and possible solutions:
> > 1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
> > 2) edit persistense.xml file and add `serverTimezone` configuration
> property with TZ of MariaDb server
> >
> > Hope it can help
> >
> > [1]
> > java.sql.SQLNonTransientConnectionException: Could not create connection
> to database server. Attempted reconnect 3 times. Giving up.
> > at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
> > at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> > at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
> > at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
> > at
> com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
> > at
> com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
> > at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
> > at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
> > at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
> > at
> com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)
> > at java.sql.DriverManager.getConnection(DriverManager.java:664)
> > at java.sql.DriverManager.getConnection(DriverManager.java:247)
> > at
> org.apache.openmeetings.web.pages.install.InstallWizard$DbStep$1.onValidateModelObjects(InstallWizard.java:266)
> > at
> org.apache.wicket.markup.html.form.Form.internalOnValidateModelObjects(Form.java:1870)
> > at org.apache.wicket.markup.html.form.Form.process(Form.java:956)
> > at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:788)
> > at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:176)
> > at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:127)
> > at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:598)
> > at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
> > at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)
> > at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)
> > at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
> > at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:914)
> > at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> > at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:282)
> > at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> > at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> > at org.apache.wicket.protocol.ws
> .AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
> > at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206)
> > at
> org.apache.wicket.protocol.http.Wicket

Re: Could not connect to MariaDB

[Maxim Solodovnik]

Hello René,

I'll try to set up VM to test following steps (so here it is untested)
1) open 
${OM_HOME}/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
2) find  wrote:
>
> Hello,
>
> I dont know where I have to write what TimeZone-Variable.
> I think it is the 
> "/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".
>
> But where I have to write what to eliminate the "The server time zone value 
> 'CEST' is unrecognized or..."-error?
>
> Best regards,
>
> René
>
>
>
>
> Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:
>
> Hello All,
>
> recently I got error report from Alvaro regarding DB connection issue while 
> MariaDB us used
> After some "email ping-pong" I got logs, relevant part of logs can be found 
> here [1]
>
> The first, huge stack trace provides only general information: "Could not 
> create connection to database server. Attempted reconnect 3 times. Giving up."
> Nothing to work with
>
> BUT the second one states: "The server time zone value 'CEST' is unrecognized 
> or represents more than one time zone. You must configure either the server 
> or JDBC driver (via the serverTimezone configuration property) to use a more 
> specifc time zone value if you want to utilize time zone support."
>
> This one provides the root cause of the problem and possible solutions:
> 1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
> 2) edit persistense.xml file and add `serverTimezone` configuration property 
> with TZ of MariaDb server
>
> Hope it can help
>
> [1]
> java.sql.SQLNonTransientConnectionException: Could not create connection to 
> database server. Attempted reconnect 3 times. Giving up.
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
> at 
> com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
> at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
> at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
> at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
> at 
> com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at 
> org.apache.openmeetings.web.pages.install.InstallWizard$DbStep$1.onValidateModelObjects(InstallWizard.java:266)
> at 
> org.apache.wicket.markup.html.form.Form.internalOnValidateModelObjects(Form.java:1870)
> at org.apache.wicket.markup.html.form.Form.process(Form.java:956)
> at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:788)
> at 
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:176)
> at 
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:127)
> at 
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:598)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)
> at 
> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
> at 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:914)
> at 
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:282)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> at 
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206)
> at 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:607)
> at 
> org.apache.catalina.core.Standar

Re: Could not connect to MariaDB

[R. Scholz]

Hello,

I dont know where I have to write what TimeZone-Variable.
I think it is the 
"/opt/open500/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml".


But where I have to write what to eliminate the "The server time zone 
value 'CEST' is unrecognized or..."-error?


Best regards,

René




Am 02.04.2019 um 07:35 schrieb Maxim Solodovnik:

Hello All,

recently I got error report from Alvaro regarding DB connection issue 
while MariaDB us used
After some "email ping-pong" I got logs, relevant part of logs can be 
found here [1]


The first, huge stack trace provides only general information: "Could 
not create connection to database server. Attempted reconnect 3 times. 
Giving up."

Nothing to work with

BUT the second one states: "The server time zone value 'CEST' is 
unrecognized or represents more than one time zone. You must configure 
either the server or JDBC driver (via the serverTimezone configuration 
property) to use a more specifc time zone value if you want to utilize 
time zone support."


This one provides the root cause of the problem and possible solutions:
1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
2) edit persistense.xml file and add `serverTimezone` configuration 
property with TZ of MariaDb server


Hope it can help

[1]
java.sql.SQLNonTransientConnectionException: Could not create 
connection to database server. Attempted reconnect 3 times. Giving up.
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
at 
com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)

at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
at 
com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)

at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at 
org.apache.openmeetings.web.pages.install.InstallWizard$DbStep$1.onValidateModelObjects(InstallWizard.java:266)
at 
org.apache.wicket.markup.html.form.Form.internalOnValidateModelObjects(Form.java:1870)

at org.apache.wicket.markup.html.form.Form.process(Form.java:956)
at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:788)
at 
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:176)
at 
org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:127)
at 
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:598)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)
at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:914)
at 
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
at 
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:282)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
at 
org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206)
at 
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:607)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at 
org.apache.catalina.connector.CoyoteAdapter.service(Coyot

Could not connect to MariaDB

[Maxim Solodovnik]

Hello All,

recently I got error report from Alvaro regarding DB connection issue while
MariaDB us used
After some "email ping-pong" I got logs, relevant part of logs can be found
here [1]

The first, huge stack trace provides only general information: "Could not
create connection to database server. Attempted reconnect 3 times. Giving
up."
Nothing to work with

BUT the second one states: "The server time zone value 'CEST' is
unrecognized or represents more than one time zone. You must configure
either the server or JDBC driver (via the serverTimezone configuration
property) to use a more specifc time zone value if you want to utilize time
zone support."

This one provides the root cause of the problem and possible solutions:
1) change server TZ to be more specific i.e. Europe/Berlin (not CEST)
2) edit persistense.xml file and add `serverTimezone` configuration
property with TZ of MariaDb server

Hope it can help

[1]
java.sql.SQLNonTransientConnectionException: Could not create connection to
database server. Attempted reconnect 3 times. Giving up.
at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
at
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
at
com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:905)
at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:830)
at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:455)
at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
at
com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at
org.apache.openmeetings.web.pages.install.InstallWizard$DbStep$1.onValidateModelObjects(InstallWizard.java:266)
at
org.apache.wicket.markup.html.form.Form.internalOnValidateModelObjects(Form.java:1870)
at org.apache.wicket.markup.html.form.Form.process(Form.java:956)
at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:788)
at
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:176)
at
org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:127)
at
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:598)
at
org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)
at
org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)
at
org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)
at
org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:914)
at
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:282)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
at
org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:607)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:834)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(