Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-18287

Seam project fails to deploy after IDE restart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 4.2.0.CR2
    • 4.2.0.CR1
    • seam2, server
    • None
    • Hide

      0. Start with a fresh workspace
      1. Add EAP 5.2 using runtime detection
      2. Create a new seam web project bound to the EAP 5.2 runtime, use all defaults
      3. Start the server - the seam project will be deployed successfully - no errors in server console
      4. Stop the server, restart IDE
      5. Start the server again - there will be errors in the server console

      Workaround:
      6. Undeploy the seam project
      7. Deploy the project again - this time it will work.
      or
      6.Server>Clean publishes again the missing -ds.xml file, and problem does not occur anymore (until starting with a new project)

      Show
      0. Start with a fresh workspace 1. Add EAP 5.2 using runtime detection 2. Create a new seam web project bound to the EAP 5.2 runtime, use all defaults 3. Start the server - the seam project will be deployed successfully - no errors in server console 4. Stop the server, restart IDE 5. Start the server again - there will be errors in the server console Workaround: 6. Undeploy the seam project 7. Deploy the project again - this time it will work. or 6.Server>Clean publishes again the missing -ds.xml file, and problem does not occur anymore (until starting with a new project)

    Description

      When you create a seam web project and deploy to EAP 5.2, then stop the server, restart JBDS and start the server again, the project fails to deploy properly:

      10:55:27,380 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/seamproj'
10:55:27,900 INFO  [ServletContextListener] Welcome to Seam 2.2.6.EAP5
10:55:28,862 WARN  [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
10:55:28,961 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey@6d4879f2[domain=default, server=default, name=default]
10:55:28,962 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "persistence.unit:unitName=seamproj.war#seamproj" is missing the following dependencies:
    Dependency "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **")

DEPLOYMENTS IN ERROR:
  Deployment "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **

10:55:28,968 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
10:55:28,982 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
10:55:28,988 INFO  [ServerImpl] JBoss (Microcontainer) [5.2.0 (build: SVNTag=JBPAPP_5_2_0 date=201211232041)] Started in 15s:311ms

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-14001 First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-14001 First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: