I got some more information:
- the problem is now also confirmed under Sun Java 1.5.0_05, we hoped it would be a bug in the Java Runtime.
- When we try to create a new connection we get a: Status_code = 403 error.
- When we choose a existing connection, it works to connect, but the update failes with: Error_existingConnection_Update
- When we try to commit we get: Error_Commit
The so6.properties file has this content (password and user crossed out):
#do not edit
#Mon Nov 14 20:44:56 MEZ 2005
so6.user.login=************
so6.binary.ext=pdf ps eps zip class gif jpg mp3 mpg pngn
so6.clienti.name=org.libresource.so6.core.client.ClientIServletImpl
so6.queue.id=/projects/courses/05HT/DAB702/projects/team3/repository
so6.wsc.name=Markus, Project Manager
so6.user.password=**********
so6.service.url=http://cs.msi.vxu.se:9000/ls-so6/so6
so6.path=/home/markus/workspace/TTT
so6.corruption.state=11
so6.connection.path=/home/markus/workspace/TTT/.so6/1
so6.last.ticket.before.corruption=0
I got some screen shots from the error messages. Is there a way I can upload them?
Any help would be appreciated. Thank you.
I don't see were the problem come from, and unfortunatly we didn't get this error before... Thats a pity...So as I understand, when you use the Web clients it works, but since you use the Eclipse one, you always corrupt your workspace... No, not exactly, the workspace gets in both cases corrupted, but in the web client, we can restore/fit it one time, update/commit, and then fix it again