Galera,
Tenho um ambiente configurado usando JBoss Seam 2.1.1.GA, JBoss As 4.2.3.GA e jdk5. Porém o cliente exige a mudança para o JBoss Seam 2.2.0.GA, JBoss As 5.0.0.GA e jdk6…Tenho apanhado para ‘migrar’ o ambiente já tem quase umas duas semanas e o projeto já começa no meio do mês. Alguém sabe o que acontece? O jboss 5.0.0.GA começa a startar e para exatamente como mostrado abaixo e aí fica eternamente como se estivesse em um loop.
Alguém pode me dá uma luz por gentileza?!
[/quote]
16:36:23,367 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@eb73a6
16:36:23,380 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@eb73a6
16:36:23,470 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@eb73a6
16:36:23,477 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@eb73a6
16:36:23,864 INFO [JBossASKernel] Created KernelDeployment for: jboss-seam.jar
16:36:23,870 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
16:36:23,870 INFO [JBossASKernel] with dependencies:
16:36:23,870 INFO [JBossASKernel] and demands:
16:36:23,871 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
16:36:23,871 INFO [JBossASKernel] and supplies:
16:36:23,871 INFO [JBossASKernel] jndi:piloto/TimerServiceDispatcher/local
16:36:23,871 INFO [JBossASKernel] Class:org.jboss.seam.async.LocalTimerServiceDispatcher
16:36:23,871 INFO [JBossASKernel] jndi:piloto/TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher
16:36:23,871 INFO [JBossASKernel] jndi:piloto/TimerServiceDispatcher/remote
16:36:23,871 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3) to KernelDeployment of: jboss-seam.jar
16:36:23,872 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=EjbSynchronizations,service=EJB3
16:36:23,872 INFO [JBossASKernel] with dependencies:
16:36:23,872 INFO [JBossASKernel] and demands:
16:36:23,872 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
16:36:23,872 INFO [JBossASKernel] and supplies:
16:36:23,872 INFO [JBossASKernel] jndi:piloto/EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations
16:36:23,872 INFO [JBossASKernel] jndi:piloto/EjbSynchronizations/remote
16:36:23,872 INFO [JBossASKernel] Class:org.jboss.seam.transaction.LocalEjbSynchronizations
16:36:23,872 INFO [JBossASKernel] jndi:piloto/EjbSynchronizations/local
16:36:23,872 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=EjbSynchronizations,service=EJB3) to KernelDeployment of: jboss-seam.jar
16:36:24,090 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
16:36:24,104 INFO [EJBContainer] STARTED EJB: org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
16:36:24,178 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
piloto/TimerServiceDispatcher/local - EJB3.x Default Local Business Interface
piloto/TimerServiceDispatcher/local-org.jboss.seam.async.LocalTimerServiceDispatcher - EJB3.x Local Business Interface
16:36:24,272 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=piloto.ear,jar=jboss-seam.jar,name=EjbSynchronizations,service=EJB3
16:36:24,273 INFO [EJBContainer] STARTED EJB: org.jboss.seam.transaction.EjbSynchronizations ejbName: EjbSynchronizations
16:36:24,292 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
piloto/EjbSynchronizations/local - EJB3.x Default Local Business Interface
piloto/EjbSynchronizations/local-org.jboss.seam.transaction.LocalEjbSynchronizations - EJB3.x Local Business Interface
16:36:24,376 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=piloto.ear/piloto-common.jar#default
[quote]