[jboss-jira] [JBoss JIRA] Commented: (JBREM-608) Investigate delay in starting invokers

[Tom Elrod (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-608?page=comments#action_12344951 ] 
            
Tom  Elrod commented on JBREM-608:
----------------------------------

Both HEAD (JBossAS trunk) and JEE5 have the following error on startup, so never see the ejb3 start the server invoker:

2006-10-10 01:32:18,052 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS MISSING DEPLOYERS: Name

file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/bsh-deployer.xml
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/ear-deployer.xml
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/ejb-deployer.xml
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/ejb3-interceptors-aop.xml
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/http-invoker.sar/invoker.war/
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossweb-tomcat6.sar/ROOT.war/
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jmx-console.war/
file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/management/console-mgr.sar/web-console.war/
jar:file:/C:/tmp/JBossAS-trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws.sar/jbossws-context.war!/

*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

jboss.ws:service=DeployerInterceptorEJB21
 -> jboss.ejb:service=EJBDeployer{Create:** NOT FOUND **}
 -> jboss.ejb:service=EJBDeployer{Start:** NOT FOUND **}

jboss.ws:service=DeployerInterceptorEJB3
 -> jboss.ejb3:service=EJB3Deployer{Create:** NOT FOUND **}
 -> jboss.ejb3:service=EJB3Deployer{Start:** NOT FOUND **}


*** CONTEXTS IN ERROR: Name -> Error

jboss.ejb3:service=EJB3Deployer -> ** NOT FOUND **

jboss.ejb:service=EJBDeployer -> ** NOT FOUND **




> Investigate delay in starting invokers
> --------------------------------------
>
>                 Key: JBREM-608
>                 URL: http://jira.jboss.com/jira/browse/JBREM-608
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>         Environment: HEAD; winxp
>            Reporter: Anil Saldhana
>         Assigned To: Tom  Elrod
>
> When I start JBoss 5.0 from HEAD, there is a delay of few seconds in starting the socket server. This is not a significant delay though.
> ===========================
> 15:25:02,265 INFO  [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://192.168.15.100:3873/]
> ============================
> Maybe you can check why the ejb3 related InvokerLocator is taking time.
> The following start seems to be ok:
> 15:24:58,625 INFO  [SocketServerInvoker] Invoker started for locator: InvokerLoc
> ator [socket://192.168.15.100:4446/?dataType=invocation&enableTcpNoDelay=true&ma
> rshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeou
> t=600000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshall
> er]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira