-
1. Re: Deployment EJB3 5.0 GA migration
jaikiran Feb 19, 2009 5:40 AM (in response to horstl)One other user too had reported this, a few days back. We have a JIRA for this https://jira.jboss.org/jira/browse/EJBTHREE-1724. However, i haven't been able to reproduce this because of lack of an application which shows this issue.
If it's possible, could you please attach an application which reproduces this, to that JIRA? -
2. Re: Deployment EJB3 5.0 GA migration
horstl Feb 19, 2009 8:47 AM (in response to horstl)hi jaikiran,
first thanx for response :-)
yes bug seem to be the same, problem the ear has a size about 20Mb and is my work of the last year:-) therefore i don't want to upload it anywhere...
i have a smaller test application (same style of implementation) but with this one the failure is not reproduceable, it seems only with a lot of beans the problem is coming up...
but can you tell me how the loading and registration is running of the entity beans and the sessionbeans, then i will help to resolve this problem
as i have seen there are this steps
1) checking dependencies of the beans
(JBossASKernel) Created KernelDeployment: installs SLSB with dependencies
2) register all beans without dep on persistence unit
(SessionSpecContainer) Starting bean only Facade (managerbean/remote if)
(EJBContainer) info about started
(JndiSessionRegistrarBase) registering for binding global jndi (managerbean with @remote)
3) database (what is this?: WARN [org.hibernate.ejb.Ejb3Configuration] (main) Persistence provider caller does not implement the EJB3 spec correctly.PersistenceUnitInfo.getNewTempClassLoader() is null)
(Ejb3Configuration) db handling schema/table generation etc
(SessionSpecContainer/EJBContainer) starting the EJB3 beans
4) register beans with persistence unit dep
(SessionSpecContainer) Starting bean only PeristenceContext (entitymanager)
(EJBContainer) info about started
(JndiSessionRegistrarBase) registering for binding global jndi (entitymanager with @local)
FAILURE always in this setp
but it seems that the failure is in a step afterwards and only the logging is to slow...
whats coming up next ?
br horst