Page 1 of 1

Server Log: Could not get next sequence for client_stats?

PostPosted: Thu Feb 16, 2017 2:00 pm
by tgs
Since a week or so I get this in the Servoy-Admin Server Log:
Code: Select all
2017-02-16 12:32   pool-2-thread-2   ERROR   com.servoy.j2db.util.Debug   Could not get next sequence for client_stats (using unsupported db-identity for client_stats?)       
2017-02-16 12:32   RMI TCP Connection(554)-192.168.15.103   ERROR   com.servoy.j2db.util.Debug   Could not get next sequence for client_stats (using unsupported db-identity for client_stats?)

How can I fix this?

Server Information:
Servoy version 7.4.9 -releaseNumber 2047
JVM Information:
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.version=1.8.0_121
Operating System Information:
os.name=Mac OS X
os.version=10.11.6
os.arch=x86_64

DB: PostgreSQL 9.6.2

Regards

Re: Server Log: Could not get next sequence for client_stats

PostPosted: Fri Feb 17, 2017 2:55 pm
by rgansevles
Thomas,

Do you have a client_stats table in your logserver?
If yes, what is the sequence type of column pk_id?

If it is db-identity, then this is a combination we do not support (hence the log message)

Rob

Re: Server Log: Could not get next sequence for client_stats

PostPosted: Fri Feb 17, 2017 4:03 pm
by tgs
Hi Rob,

I have nothing changed or set to db-identity. Have a look at the current setting:
client_stats.png
client_stats.png (38.32 KiB) Viewed 5497 times

Re: Server Log: Could not get next sequence for client_stats

PostPosted: Fri Feb 24, 2017 10:55 am
by rgansevles
That looks completely standard.
When I run a client with a standard setup it works as expected.
For some reason it can't generate a new id for the clientstats.pk_id column.

If you also see this in your dev environment, you could try dropping/recreating the client-stats table (from server editor, the log-server has a create-client-stats button).

Rob

Re: Server Log: Could not get next sequence for client_stats

PostPosted: Tue Feb 28, 2017 7:50 pm
by tgs
Hi Rob,

I have dropped/deleted the client_stats table on the customers SQL Server.
After a new import of the solution the client_stats table is recreated and I get no more error log about the unsupported db-identity.
Now all is looking good and it seems to be working as it should.

Thomas