[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Yann Le Moigne commented on JBIDE-10224: ---------------------------------------- Same here, workaround : in server view, double click jboss,in startup poller, set webport. Not perfect, but it work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10224: ------------------------------------- Juergen: you need to set your poller to Web Poller as a workaround. This is being investigated -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] jaikiran pai commented on JBIDE-10224: -------------------------------------- My guess is that whatever mechanism JBoss Tools is using right now, is ending up using a older version of JBoss Remoting3 and JBoss SASL libraries. The server side in 7.1.0 Beta1 is using remoting3 3.2.0.CR3 and sasl 1.0.0.Beta6. I've seen users running into this issue if the client had a different (lower) versions of this library. Ofcourse it's a different matter whether the backward compatibility was intentionally changed or if it's an oversight/bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10224: ---------------------------------------- Issue Type: Bug (was: Feature Request) Priority: Blocker (was: Major) Workaround described at http://community.jboss.org/en/tools/blog/2011/11/24/jboss-as-71-beta1-wit... And after talking with Darran L. and Emanuel M. this was an unintended sideeffect of supporting the "local-authentication" feature for AS7. We'll be looking at how we can avoid that for future AS releases. Stay tuned. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10224: ------------------------------------------ well, it seems like "bundles with services have to be activated by default, no lazy initialization" is legacy. http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc... http://www.osgi.org/Design/LazyStart {quote} 10. Lazy activation bundles MUST be able to participate in the service layer before the first class is loaded from the bundle. This requires that the BundleContext for a lazy activation bundle be available to component systems (e.g. Declarative Services, Spring-OSGi, etc.) before the bundle enters the ACTIVE state. {quote} I had problems with service in the usage plugin when the bundle was lazy. that was last year. I then therefore switched it to be active. I have the impression that we pretty much hit an equinox bug here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10224 at 11/25/11 11:36 AM: --------------------------------------------------------------------- well, it seems like "bundles with services have to be activated by default, no lazy initialization" is legacy. http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc... http://www.osgi.org/Design/LazyStart {quote} 10. Lazy activation bundles MUST be able to participate in the service layer before the first class is loaded from the bundle. This requires that the BundleContext for a lazy activation bundle be available to component systems (e.g. Declarative Services, Spring-OSGi, etc.) before the bundle enters the ACTIVE state. {quote} I had problems with the branding service in the usage plugin when the bundle was lazy. that was last year. I therefore switched it to be active. I have the impression that we pretty much hit an equinox bug here. was (Author: adietish): well, it seems like "bundles with services have to be activated by default, no lazy initialization" is legacy. http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc... http://www.osgi.org/Design/LazyStart {quote} 10. Lazy activation bundles MUST be able to participate in the service layer before the first class is loaded from the bundle. This requires that the BundleContext for a lazy activation bundle be available to component systems (e.g. Declarative Services, Spring-OSGi, etc.) before the bundle enters the ACTIVE state. {quote} I had problems with the branding service in the usage plugin when the bundle was lazy. that was last year. I then therefore switched it to be active. I have the impression that we pretty much hit an equinox bug here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10224 at 11/25/11 11:40 AM: --------------------------------------------------------------------- removed erroneous comments was (Author: adietish): I did test the hack pretty intensely and it pretty much solved the problems we were experiencing - at least for me. I did then dig further and found out that the bundles were activated lazily which is not valid for bundles that have services. Bundles with services have to be activated by default. I therefore removed the bundle activators and unchecked "Activate plug-in if one of its classes is loaded". Now things work fine for me even when the hack is commented. I committed my changes to TRUNK. @Rob: Please verify that things work fine for you, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10224. -------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Juergen Zimmermann commented on JBIDE-10224: -------------------------------------------- Confirmed. Let's try the next build ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10224. --------------------------------- Resolution: Done There were substantial issues with the fix. They've been resolved now :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-10224: --------------------------------------- Stopping of remote server doesn't work even for AS7.0.2. I suppose it's not done yet. Andre, is there a JIRA for that? I couldn't find one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-10224: --------------------------------------- To clarify why I'm still waiting for a build - the as component job was failing in Hudson for the last few days, but Rob says it should be ok now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10224: --------------------------------------------- resolving since it is working for us - if qe finds issue reopen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-10224. ----------------------------------------- Resolution: Done Thanks Juergen, resolving this issue leaving the other issue open for that specific issue for M5. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] u j commented on JBIDE-10224: ----------------------------- Hm, I just installed 3.3.0.M5 and switched back to the standard runtime configuration (startup poller = JBoss 7 Manager Service, server port management automatically detected) and the old error on start up (Remote connection failed) is back. I understood that M5 fixes this?! Do you still need to change the configuration? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10224: --------------------------------------------- we've tested M5 with AS7.0.2, AS 7.1.0.b1b and AS 7.1.0.CR1 without seeing any problems. Please open separate/new bug with details and be 100% sure you are actually using latest M5 *and* one of the above AS 7.1's, i.e. AS 7.1.0.b1 won't work - AS 7.1.0.b1b will. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira