Skip to content
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

JBIDE-15126 server forcefully shuts down on module event instead of server event #107

Merged
merged 1 commit into from Jul 4, 2013

Conversation

robstryker
Copy link
Member

No description provided.

@@ -236,7 +236,8 @@ protected void initialize(IProgressMonitor monitor) {
serverStateVal = getServer().getServerState();
getServer().addServerListener(new IServerListener() {
public void serverChanged(ServerEvent event) {
if( event.getState() != serverStateVal ) {
boolean isServerChangeEvent = ((event.getKind() & ServerEvent.SERVER_CHANGE) != 0);
if( isServerChangeEvent && event.getState() != serverStateVal ) {
Trace.trace(Trace.STRING_FINER, "Framework has changed server state from starting to stopped. Ensuring server has stopped."); //$NON-NLS-1$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i know its unrelated to fix but shouldnt this trace be inside the next if ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...and should this be a info log ? how often would this happen ?

@maxandersen
Copy link
Member

+1 for fix since it is necessary now we have module state changes causing crashes.

@robstryker robstryker merged commit 6d5ba6d into jbosstools:jbosstools-4.1.x Jul 4, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants