Re: [jboss-as7-dev] Help need with JBoss 7 migration

Thank you for such a quick response Note that I've symlinks at multiple levels The WAR under deployments is a symlink (level-1) to an exploded content elsewhere, and under the exploded content else I've bunch of symlinks (level-2) pointing to some other content at a third location. It's able to follow the level-1 symlink which is to the exploded WAR but fails to look up a file under third location by following level-2 symlink. Is your test scenario is accounting for this use case as well? I'll start a thread on user forums as well. Appreciate your help on this Thanks Shashank -----Original Message----- From: jboss-as7-dev-bounces(a)lists.jboss.org [mailto:jboss-as7-dev-bounces@lists.jboss.org] On Behalf Of Brian Stansberry Sent: Tuesday, May 29, 2012 9:01 PM To: jboss-as7-dev(a)lists.jboss.org Subject: Re: [jboss-as7-dev] Help need with JBoss 7 migration I just tested creating a symlink in deployments to exploded content elsewhere, and it worked fine. Can you start a thread in the user forums with more details on the deployment failure? On 5/29/12 4:58 PM, Shashank Bellary wrote: > Hi Guys, > > I'm trying to migrate to JBoss 7.1.1 from 4.0.5. > > In our application we use lot of symlinks to support CMS content which > is managed externally and to support some file bases caching. Here is > how the deployment looks like > > JBoss 4.0.5: > > ----------------- > > Under "/deploy/jboss-4.0.5.GA/server/czen/deploy" we've our exploded > WAR directory release.war > > Here release.war is a symlink to '/deploy/webapp/current' which in > turn is a symlink to an actual release folder like > '/deploy/webapp/release-version-xyz' > > 'release-version-xyz' folder has the following structure > > -WEB-INF > > -JSP > > -Content > > -Cache > > -JS > > -CSS > > Here both Content and Cache folders are symlinks to > > /deploy/webapp/ > > -CMSContent > > -Cache > > respectively. > > This deployment structure worked perfectly fine on JBoss 4.0.5 and now > I'm moving this app to JBoss 7.1.1 and here is the deployment > structure > > Under "/deploy/jboss-as-7.1.1.Final/czen/deployments" I've moved our > release.war as a symlink. Rest of the structure remains the same as > mentioned above. With this setup JBoss 7 start up/ application > initialization fails because it's not able to follow the symlink and > find a file that my application is trying to read at startup. I looked > over the documentation and forums to figure out a solution for this > but no luck. > > Could you guys please help in troubleshooting this issue? Is there > some configuration parameter that needs to be set or are there other ways. > Please let me know, I've a deadline fast approaching > > Thanks& Regards > > Shashank > > > > This email is intended for the person(s) to whom it is addressed and > may contain information that is PRIVILEGED or CONFIDENTIAL. Any > unauthorized use, distribution, copying, or disclosure by any person > other than the > addressee(s) is strictly prohibited. If you have received this email > in error, please notify the sender immediately by return email and > delete the message and any attachments from your system. > > > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev