CMDBuild Forum

2.5.0 : Soap webservice : memory leak

Old Versions
#1

Hi,

as other user in this forum,  we encounter a memory leak problem when using the soap webservice..

This leak seems to be related to the session cache :  we do not have any problem when we lower the sessiontimeout configuration variable from its default (3600) to a much lower value (60 seconds for example). Alas this timeout is rather low from a user using the GUI.

It seems (according to bitbucket) that soap will be deprecated in 3.0, nevertheless soap webservices are important *now* for CMDB integration.

Do you plan to examine this problem in 2.5.1 ? Or, as a workaround ,would it be possible to use another instance of the cmdbuild webapp (not in cluster mode) with one instance dedicated to user gui (sessiontimeout 3600s) , another instance dedicated to web service (sessiontimeout 60s)?

 

Regards.

J.-M.

#2

Unfortunately, the solution to this problem is planned in version 3.0, not in version 2.5.1.
But it
is not true that the SOAP webservice will be deprecated in CMDBuild
3.0, only we will replace JSON-RPC with REST in the communication between
client and server on the standard GUI.
Regarding the use of two CMDBuild nodes it is only possible if you enable the cluster configuration.
CMDBuild Team

#3

Thanks for your answer,

 

Previously Tecnoteca wrote:
Unfortunately, the solution to this problem is planned in version 3.0, not in version 2.5.1.
But it is not true that the SOAP webservice will be deprecated in CMDBuild 3.0, only we will replace JSON-RPC with REST in the communication between client and server on the standard GUI.
Regarding the use of two CMDBuild nodes it is only possible if you enable the cluster configuration.
CMDBuild Team

 

So soap will not be deprecated (sorry for my mistake) and will not no more eat memory in 3.0 :)

 

Another three questions :

1-Is there any other workaround for this leaking memory problem ? it impacts heavily the exernal integration capabilities of cmdbui:d :(.

 

2-Maybe  the soap webservice is not intended to use for bulk synchronization of the database, if not please could you make a blear statement about that in one of the manuals ?

 

3-Is there already have any work (commit id) seeable in bitbucket (git or previous hg) ?

 

Thanks for your work and Regards;

J.-M.

#4

Here’s the answers.
1) I’m sorry we do not have a workaround to suggest (in addition to using the cluster);
2) The soap webservice can be used also for bulk synchronization of databases tables, for
example our connector between OCS Inventory and CMDBuild synchronizes every night the
MySQL tables of computers, disks, network data, ecc (updated from the automatic discovery agent) with the  PostgreSQL tables of computers, network interfaces and software;
3) the
change will be done on a structural level and is not yet available on
GIT, but a first part of the solution is already available on GIT and in
particular the storage of sessions in the database.
CMDBuild Team

#5

Previously Tecnoteca wrote:

Here's the answers.
1) I'm sorry we do not have a workaround to suggest (in addition to using the cluster);
2) The soap webservice can be used also for bulk synchronization of databases tables, for example our connector between OCS Inventory and CMDBuild synchronizes every night the MySQL tables of computers, disks, network data, ecc (updated from the automatic discovery agent) with the  PostgreSQL tables of computers, network interfaces and software;
3) the change will be done on a structural level and is not yet available on GIT, but a first part of the solution is already available on GIT and in particular the storage of sessions in the database.
CMDBuild Team

OK, structural changes are difficult to plan for sub-minor releases :)

We will see if the cluster way is feasible ...

 

Thanks

J.-M.