Aplication Information Tunning ( TOMCAT) ?

Post any questions regarding Installing or Upgrading Ebase, including problems starting up the Ebase Xi Server or Designer

Moderators: Jon, Steve, Ian, Dave

armin_kessler
Ebase User
Posts: 27
Joined: Sun Jan 08, 2012 2:39 am

Aplication Information Tunning ( TOMCAT) ?

#1

Postby armin_kessler » Wed Nov 06, 2013 5:42 pm

Hello All.

I recently install Ebase Xi 4.5.0 on a windows Server 2008 R2 standard
64 bits with 10 GB RAM. I installed the Ebase Xi licence for 30 users and
all is OK, but the page do not work with more than 8 users. I check the
logs but don't understand.

Should I adjust parameters on the application Server TOMCAT , depending
on the concurrent users number ?

Thanks in advance ... Armin
0 x
Armin Kessler

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#2

Postby Jon » Thu Nov 07, 2013 10:27 am

Armin,

What error do you get?
Check the license info in the designer: Help > License. What is the number of Maximum runtime users?

Regards
Jon
0 x

armin_kessler
Ebase User
Posts: 27
Joined: Sun Jan 08, 2012 2:39 am

#3

Postby armin_kessler » Thu Nov 07, 2013 12:48 pm

Hello Jon:

Thank you for your response.

Maximum runtime users: 30

The user do not receive an error, simple when he type the user
name and password, the page seems to stay in a loop and do not
renpond. When this occurs I check on the Ebase Xi Designer / Help /
View connected Users :

1- Number of concurrent runtime users( for licensing purposes) : 8
2- Maximum number of concurrent runtime users reached: 8
3- Number of times runtime user connection rejected: 0

The values of 1 and 2 its variable : 10/10 , 8/12 ...

Thanks in advance ... Armin[/url]
0 x
Armin Kessler

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#4

Postby Jon » Thu Nov 07, 2013 2:13 pm

It doesn't look like it's got anything to do with licensing or the number of users. It looks like your app is hanging for some reason. Maybe check on the server for errors. If nothing is visible, you could add some logging to your scripts and try and find where it's getting stuck. Possible reasons are:

o Running out of database connections (applies if you are getting connections and not closing them)
o Database locks
o Running out of memory
0 x


Who is online

Users browsing this forum: No registered users and 11 guests