After replacing older JDS 7 jars with 7.05 jars, 100MB+ .._temp.jds file
still locks the system, but while it is locking itself; it is actually
stopping itself. This is a good thing. (better than a lock)
This is one step better than prior one since I don't need to reboot the
server pc itself. Prior the jds-service (in Windeows Services) was corrupted
(can not be stopped or started). Now with JdsServer Console, after it stops
and gives "network connection error or no JDBC server" message, I can start
it.
But still the main issue why JDS can not handle the temp file remains.
I am suprise not to hear any comment on this issue since ..._temp.jds file
is how JDS functions.
"Mehmet F. Erten" <mehmet...@mblsoft.com> wrote in message
news:440f51f1$1...@newsgroups.borland.com...