[jbosstools-issues] [JBoss JIRA] (JBIDE-10224) JBossAS 7.1 cannot be launched

[Andre Dietisheim (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645661#comment-12645661 ] 

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.isv/whatsNew/platform_isv_whatsnew.html

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.
                
> JBossAS 7.1 cannot be launched
> ------------------------------
>
>                 Key: JBIDE-10224
>                 URL: https://issues.jboss.org/browse/JBIDE-10224
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M4
>            Reporter: Juergen Zimmermann
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: jbossas_7.1
>             Fix For: 3.3.0.M5
>
>
> I just installed JBossAS 7.1.Beta1. However, the server start is hanging in an endless loop (see below). Maybe it's due to the new security mechanism in standalone/configuration/mgmt-users.properties.
> Console output:
> 13:55:42,836 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Beta1 "Tesla" started in 2862ms - Started 143 of 206 services (60 services are passive or on-demand)
> 13:55:45,116 ERROR [org.jboss.remoting.remote] (Remoting "iwi-w-ziju01-c:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 001bd732 to /127.0.0.1:53864
> // from now on: endless loop of the preceeding line

--
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