New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FitNesse no longer stops when calling /?shutdown #875

Closed
hansjoachim opened this Issue Feb 15, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@hansjoachim
Contributor

hansjoachim commented Feb 15, 2016

To reproduce :

  1. Run java -jar fitnesse-standalone.jar
  2. Visittkort localhost to verify it is running.
  3. Locate the process. For gnu/Linux, run ps -ef | grep fitnesse. For Windows, open task manager ()
@hansjoachim

This comment has been minimized.

Show comment
Hide comment
@hansjoachim

hansjoachim Feb 15, 2016

Contributor

Sorry about the split.
Task manager (Ctrl +alt+Esc ) and go to the process tab.
4. Visit localhost/?shutdown.

Fitnesse itself will stop, but the process remains. This happens with 20151230 and latest snapshot, but with older releases the process stopped too. Looks like a regression.

Contributor

hansjoachim commented Feb 15, 2016

Sorry about the split.
Task manager (Ctrl +alt+Esc ) and go to the process tab.
4. Visit localhost/?shutdown.

Fitnesse itself will stop, but the process remains. This happens with 20151230 and latest snapshot, but with older releases the process stopped too. Looks like a regression.

@amolenaar amolenaar added this to the Next release milestone Feb 15, 2016

@amolenaar

This comment has been minimized.

Show comment
Hide comment
@amolenaar

amolenaar Feb 15, 2016

Collaborator

Indeed. It also happens on Mac.

Collaborator

amolenaar commented Feb 15, 2016

Indeed. It also happens on Mac.

@amolenaar

This comment has been minimized.

Show comment
Hide comment
@amolenaar

amolenaar Feb 15, 2016

Collaborator

The problem started when I changed FitNesse to use a thread pool instead of spawning threads in the wild (e9accb3).

Collaborator

amolenaar commented Feb 15, 2016

The problem started when I changed FitNesse to use a thread pool instead of spawning threads in the wild (e9accb3).

@amolenaar amolenaar closed this in 8be74c3 Feb 15, 2016

@amolenaar amolenaar changed the title from No longer stopp the process when accessing /?shutdown to FitNesse no longer stops when calling /?shutdown Mar 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment