2 Replies Latest reply on Dec 11, 2009 4:57 PM by chris fortescue

    jboss 5.1 /seam 2.2.0 continuous redeployment

    chris fortescue Newbie

      Long time user, first time poster.

      I thought I had made it through the JBoss AS 4.2.2->5.1 upgrade gauntlet when I encountered the boot-rolling of my application on server startup.

      Under AS 4.2.2, I had upgraded my app to seam 2.2.0 \hibernate 3.3.2 et al some time ago and had no problems so this upgrade involves AS itself. I think I can rule out seam 2.2 & hibernate 3.3.2 since I've been using them for a while.

      I read http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898 and all the related posts but they all seem to either die off or go into incredible minutae pre-dating 5.1. No one seems to have a definitive resolution to possible causes though there are lots of posts.

      FWIW, I am using JBossTools 2.0.2 in eclipse 3.4 2, exploding the ear into ${jboss.home}/all (I use CORBA). Also, I originally created the project file with seam-gen from seam 2.0.

      In light of previous posts related to this issue, I add these facts:
      - There are no *.jsdia or other files that aren't supposed to be in the exploded all/deploy directory.
      - I have *shutdown* eclipse and run strictly from the command line.


      The are no [ERROR] lines emitted but I see the following lines [WARN] in the log:

      16:00:18,787 INFO [ServerImpl] Starting JBoss (Microcontainer)...
      16:00:18,787 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
      --snip--
      16:00:21,349 INFO [ServerInfo] Java version: 1.6.0_02,Sun Microsystems Inc.
      16:00:21,349 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_02-b06)
      16:00:21,365 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_02-b06,Sun Microsystems Inc.
      16:00:21,365 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      --snip--
      
      16:01:11,881 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
      
      16:01:12,053 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
      
      16:01:12,099 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
      
      --snip--
      
      16:02:20,099 INFO [WSDLFilePublisher] WSDL published to: file:/C:/cygwin/home/chris/src/jboss-5.1.0.GA/server/all/data/wsdl/campaign.ear/campaign.jar/CampaignService3854.wsdl
      16:02:20,162 INFO [TomcatDeployment] deploy, ctxPath=/campaign-campaign
      16:02:20,193 WARNING [config] Unable to process deployment descriptor for context '/campaign-campaign'
      
      --snip--
      16:01:31,896 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=campaign.ear,jar=campaign.jar,name=CampaignMgmt,service=EJB3) to KernelDeployment of: campaign.jar
      16:01:31,943 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f5bef
      16:01:31,959 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f5bef
      16:01:31,974 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f5bef
      16:01:31,974 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f5bef
      
      --snip--
      
      16:27:05,334 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      16:27:05,365 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
      16:27:05,381 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 1m:32s:641ms
      
      16:27:15,224 INFO [TomcatDeployment] undeploy, ctxPath=/campaign
      16:27:15,318 INFO [TomcatDeployment] undeploy, ctxPath=/campaign-campaign
      
      
      



      I am using seam-remote hence the WSDL. Is the wsdl message an error and not a warning? Is the the 'AOP Weirdness' message that gets emitted a possible culprit?

      I would appreciate any light that may be shed upon this.

      Thanks,
      Chris