facebook

Deploying large exploded WARs on JBoss 4.x timing issues

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #247816 Reply

    Amir Mistric
    Member

    Hi

    I believe there is a bug when deploying exploded WAR project using JBoss 4.x app server connector.
    What occurs (especially on LARGE projects) is that JBoss starts deploying <project>.war folder before MyEclipseIDE is finished copying contents into it.

    Due this mis-synchronization a project will fail to deploy on JBoss because not all classes, libraries and other resources are done copying when deployment occurs.

    WORKAROUND:
    Defaul deployment scanning interval in JBoss is 5000 mils (5 seconds)…This can be increased in conf/jboss-service.xml. This seem to help but occasionally problem still occurs.

    PROPOSED FIX:
    Have ME use tmp folder on initial deployment (with the name that JBoss ignores) and then rename it to <context>.war to avoid issues with large projects.

    #247864 Reply

    Riyad Kalla
    Member

    This is why we suggest not deploying to a running app server, but your proposed fix is a good idea, I’ll pitch it to the team. Thanks for reporting it.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Deploying large exploded WARs on JBoss 4.x timing issues

You must be logged in to post in the forum log in