Turns out that I had to "clone" it rather than "re-open" - is that what you meant or do I just not have the authority to re-open?
John Hawkins Director: Solutions Architecture On Thu, Jul 2, 2015 at 2:20 PM, Isuru Perera <isu...@wso2.com> wrote: > Hi John, > > It's okay to re-open the JIRA as you can reproduce the issue. > > On Thu, Jul 2, 2015 at 6:16 PM, John Hawkins <jo...@wso2.com> wrote: > >> Hi Folks, >> >> I get the same problem as someone else did last year - >> https://wso2.org/jira/browse/TOOLS-2597 >> >> That defect is marked closed and un-reproducable - I can reproduce it >> everytime I restart the ESB server in eclipse server view :-) >> >> I'm guessing that what is going on is that whatever is monitoring for the >> server to close is not working quite correctly and is restarting the server >> too soon and therefore hitting the port clash. (I've had this sort of thing >> before when ports are held open even though you think they are closed. I >> don't know if this is the exact error but very similar - very annoying and >> OS dependent !). >> >> What's the best way to re-open this bug? I'm happy to help in reproducing >> it if you folks can't in order to get you more information or try out fixes >> ? >> >> many thanks, >> John. >> >> John Hawkins >> Director: Solutions Architecture >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Isuru Perera > Associate Technical Lead | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about> >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
