What is the longest that an import into Servoy should take?

Classic Servoy
1

We were trying to import a new build into our servoy server this morning, and it appeared to be hung on import with no error messages. We let it run a couple of times with the longest being about 15 minutes. It has never taken this long before. Maybe 5 minutes. Is this because of all the new information from people connecting to our now live system? Or is it something that we have done in development that is causing the import problem?

Thanks for your help.

2

Well, that’s an overload of information to evaluate ;)

It can be virtually everything:

  1. just a bad day
  2. import over the network with bad performance
  3. different file structure
  4. larger file
  5. cpu time shared with other task
    etc, etc…

In other words, what database do you use. What is different between previous and current files. What is different between the previous and current Servoy setup. etc.

3

IT2Be:
Well, that’s an overload of information to evaluate ;)

It can be virtually everything:

  1. just a bad day

I think you’re right there.

  1. import over the network with bad performance

We thought this was a possibility, so we copied the update to the server running the service, and tried the update from there using developer. Same issue. (Doesn’t opening developer on the production server start back up the server so clients can try to connect, defeating the purpose of shutting down the service while importing a new build?)

  1. different file structure

Same file structure.

  1. larger file

Will check this.

  1. cpu time shared with other task

It’s a dedicated server.

In other words, what database do you use. What is different between previous and current files. What is different between the previous and current Servoy setup. etc.

Nothing has changed except that users have been using the system for a day now.

We’re going to give it another shot at lunch today…

P.S. Thanks for the reply.

4

How does the server log look like? Are there any errors?

5

We also had some reports about admin-pages that did’nt respond anymore, while we were updating solutions.

Sebster (Sebastiaan) and I looked into the problem, and saw that Servoy had a so called ‘death-lock’. In our case this could happen, when, you are using Sybase, updating your solution, and while your system is updating, the solution is openend a lot at the same time by users.

I think it will be fixed in the new 3.0 and 2.2.6

6

Dead locks occured occasionally in our place, too. Servoy uses a transaction when importing a solution. Depending on your DB this can lead to a lock. YOu can usually see if you are locked using some DB tool.

7

We’re having serious issues importing solutions (modules) into our production environment.

When we use the admin web, we can import one module, but when trying to import the next one, the server hangs and stop responding. We need to restart the service and import the module again.

Maybe it’s somehting related with a database lock, but I don’t think so, since when importing modules from servoy developer everything goes smooth…

We’re using Servoy 3.5.7 on Java 1.6. Our database is SQL Server 2005