This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 241135 - AssertionError: Instance WildFly 8.0 CR1 started again without proper stop
Summary: AssertionError: Instance WildFly 8.0 CR1 started again without proper stop
Status: RESOLVED DUPLICATE of bug 242197
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 20:01 UTC by Michel Graciano
Modified: 2014-02-26 07:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 207101

Attachments
stacktrace (2.33 KB, text/plain)
2014-01-29 20:01 UTC, Michel Graciano 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2014-01-29 20:01:35 UTC 
Build: NetBeans IDE Dev (Build 20140129-5f982f459489)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.0-b56, Java(TM) SE Runtime Environment, 1.7.0_40-b43
OS: Linux

User Comments:
hmichel: Run (F6) with Wildfly already running




Stacktrace: 
java.lang.AssertionError: Instance WildFly 8.0 CR1 started again without proper stop
   at org.netbeans.modules.javaee.wildfly.ide.WildflyOutputSupport.reset(WildflyOutputSupport.java:255)
   at org.netbeans.modules.javaee.wildfly.ide.WildflyOutputSupport.start(WildflyOutputSupport.java:173)
   at org.netbeans.modules.javaee.wildfly.ide.WildflyStartServer.isRunning(WildflyStartServer.java:293)
   at org.netbeans.modules.j2ee.deployment.impl.ServerInstance$3.run(ServerInstance.java:900)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
Comment 1 Michel Graciano 2014-01-29 20:01:36 UTC 
Created attachment 144556 [details]
stacktrace
Comment 2 ehsavoie 2014-02-26 07:33:16 UTC 

*** This bug has been marked as a duplicate of bug 242197 ***