I have a servoy solution created on the PC. (Version R2 2.2-build 328 Java version 1.4.2_06-b03 (Windows 2000))
I export it out and import it to a Mac (Version R2 2.2-build 328 Java version 1.4.2-38 (Mac OSX))
I get one of two different responses:
If I do a regular import, it will sit and spin forever. No final outcome.
If I do a import as, it sits and spins for a little while and then stops as if it is done, but the solution never pops up on the list.
Is this a bug or am I doing something wrong?
Any ideas?
Have you had any operational problems with the OSX Servoy install or is this the only issue that you have had with it ?
Is there anything in the log file which may point to what has happened ?
Harry
This is the first I have tried it on a Mac. Previously I have done all of my builds on PC. Where on the mac can I find the log?
Try Applications/Servoy/sybase_db/sybase_log.txt.
You can also look in Applications/Utilities/Console - this logs a lot of useful info.
HTH
Graham Greensall
Worxinfo Ltd
elyod_72:
Is this a bug or am I doing something wrong?
It could be an issue, could you sent the solution file? or sample solution for which happens the same?
I finally got it working this morning. evadentally it does load, but for whatever reason it takes almost 10 minutes to load. I think it may be the computer. I will try it on a different mac and see if it has the same effect.
elyod_72:
I have a servoy solution created on the PC. (Version R2 2.2-build 328 Java version 1.4.2_06-b03 (Windows 2000))
I export it out and import it to a Mac (Version R2 2.2-build 328 Java version 1.4.2-38 (Mac OSX))
I get one of two different responses:
If I do a regular import, it will sit and spin forever. No final outcome.
…
I have a similar problem…
Have exported out of a Sybase repository in 2.2 on Win XP and I’m trying to import into a Postgresql 8.0 repository still on the same PC running Win XP. But I’m doing it remotely 
from my Mac OS 10.4.2 running 2.2…
Some smaller solutions import fine.
Looks like there the solution imports fine after a long delay. The solution giving me trouble accesses 30,000 records in mySQL on a remote server…
If you send me the solution file I can have a look if I can find any obvious problems. Note however that depending on your network connection, sending 30000 rows over the network can take a long time. Have you tried importing to a local repository, running on the same server as the Servoy Developer used for the import? Does this take just as long?
sebster:
If you send me the solution file I can have a look if I can find any obvious problems. Note however that depending on your network connection, sending 30000 rows over the network can take a long time. Have you tried importing to a local repository, running on the same server as the Servoy Developer used for the import? Does this take just as long?
Local import takes a while too.
Note that I’m not importing any data, just the solution. The mysql server contains live production data.
The main problem is that you don’t get any feedback as to what is happening.
I would need to send you
- exported solution
- servoy.properties
and allow your IP access to
- my client’s mysql server
- my client’s postgresql server…
Maybe the best thing is to wait until I come across this again, hopefully when using my internal test servers…
You can use -DSTACKTRACE=true to get more information when running Servoy. I think the mysql backend is being slow, so another option is to rebuild your indexes or enable the slow query log (or both). This should help us get a better insight into where the problem is actually occurring.
See: http://dev.mysql.com/doc/mysql/en/slow-query-log.html
Just imported 3 modules on with exactly the same setup and they all imported quickly.