[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17895: ------------------------------------- The most recent was an issue that no JIRA was opened for. It was only filed on upstream eclipse. JMX connections were not appearing inside the JMX view for started servers. The reason is that the provider of JMX connections was not alerted that the server was started. There were issues int eh past where XPaths were not added for newly created servers. I'm sure you remember this, as well as saying "This isn't the first time this has happened" Cannot locate jira. There were issues where filesets were not being added to newly created servers. I'm sure you remember this, as well as saying "This isn't the first time this has happened" Cannot find the jira. JBIDE-13444 - deployment scanners were not being added. We opted to move launching of the add-scanner code into the behavior rather than through listeners because I could not figure out why my listeners were not active. Module state for servers was not being updated after a publish because no event was fired. No jira was filed, I changed my implementation before committing, so that my behavior launches a job instead of depending on a listener. All of these bugs were intermitent, only happening sometimes. Most were not easily replicatable or only in some environments. They contributed to a general idea that ASTools wasn't working. The ones *I* could replicate, I didn't file a jira for, because I found them before committing and it affected my design decisions. Several jiras were also closed as unreplicatable a few years ago before we became more stringent on keeping them open. Basically, I'd say this bug was behind a lot of the missed and broken behavior, and I never discovered the cause. I'm sorry if I can't link to more jiras. -- This message was sent by Atlassian JIRA (v6.2.6#6264)