[
https://issues.apache.org/jira/browse/DIRSTUDIO-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959940#comment-13959940
]
Shai Levit commented on DIRSTUDIO-979:
--------------------------------------
So I start the server, which by the way is just a localhost server running on
standard port 10389, from Apache Studio GUI (where I created the new server).
But the same issue arrises when I create a server within the Eclipse Kepler
plugin - perspective (LDAP). and start the server from within Eclipse. Now this
does not happen at first. The first, say 5-10 instances of stopping and
starting the server seem to work fine, but then once the first crash happens,
it's starts to happen more frequently.
Now the crash closes the entire program (Eclipse or Apache Studio) and I have
to re-open. That is when the error that the port is already in use is noted and
if I decide to start the server anyway, it stops. If I choose another port, it
works, but that's not the optimal way to do things.
Deleting the server and starting a new instance sometimes solves this issue,
but not for long.
Hope all this helps. If there is a log file or crash report you want me to add
to this post, please advise.
regards
> Crash with port already in use issues
> -------------------------------------
>
> Key: DIRSTUDIO-979
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-979
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-connection
> Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
> Environment: Mac OS X 10.9.2
> Reporter: Shai Levit
> Labels: crash, locking, newbie, performance
> Fix For: 2.0.0-M8 (2.0.0.v20130628)
>
>
> Apache studio seems to crash often both in the stand-alone version and the
> Eclipse Kepler plugin. The issue once it crashes is that I cannot reconnect
> using the port. It states that the port is already in use. This prevents the
> server from starting. Oddly, the connection will still work, but the server
> will not start and hence other issues start to arise. To sometimes solve this
> issue, and this does not always works, is to go to the servers folder and
> delete the .dirservice.lock
> But this solution does not bode well, since the crashes still continue and
> eventually this option fails as well. I end up deleting the entire download
> and starting fresh.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
