1 2 Previous Next 17 Replies Latest reply on Sep 3, 2010 5:48 AM by rsangam

Jboss 5.1: Unable to enable hot deployment with custom deploy directory

rsangam Sep 2, 2010 4:06 AM

Hi,

We have just started support jboss 5.1 appliaction platform for our application. Since application is huge, instead of copying the application ear into deploy folder of jboss server, we are using custom deploy folder. <our-deploy-folder> And this has been configured in <jboss-home>/server/our-server/conf/bootstrap/profile.xml and <jboss-home>/server/our-server/conf/bootstrap/vfs.xml as suggested in (Jboss AS plaform :Getting Started Guide 5.0).

Hot deployment is enabled, as "hdscanner-jboss-beans.xml" is present in <jboss-home>/server/our-server/deploy folder (and has been deployed). Jboss has been restarted and our application gets deployed (from <our-deploy-folder>). However, Hot deployment doesn't seem to be working. I tried to modify a JSP (,say) in a <our-deploy-folder/app.ear/app.war/jsp/test.jsp>. Tried to add some other wars etc to this dir, still no luck

Just for Ref:

entry in profile.xml

===============

<bean name="BootstrapProfileFactory" class="org.jboss.system.server.profileservice.repository.StaticProfileFactory">
      <property name="bindingsURI">${jboss.server.home.url}conf/bindingservice.beans</property>
      <property name="bootstrapURI">${jboss.server.home.url}conf/jboss-service.xml</property>
        <property name="deployersURI">${jboss.server.home.url}deployers</property>
        <property name="applicationURIs">
            <list elementClass="java.net.URI">
                <value>${jboss.server.home.url}deploy</value>
                <value>file://D:/dev/APP_JBoss/build/app_stage/app_deploy</value>
            </list>
        </property>
        <property name="attachmentStoreRoot">${jboss.server.data.dir}/attachments</property>
        <property name="profileFactory"><inject bean="ProfileFactory" /></property>
    </bean>

entry in vfs.xml

===========

<entry>
<key>file://D:/dev/APP_JBoss/build/app_stage/app_deploy</key>
<value><inject bean="VfsNamesExceptionHandler"/></value>
</entry>

Awaiting a kind help from someone who has got similar stuff working!

Thanks,

Raghav.

1. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 4:16 AM (in response to rsangam)

Hot deployment isn't supported for external deploy folders.
Actions
2. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

rsangam Sep 2, 2010 4:31 AM (in response to jaikiran)

Thanks for prompt reply Jaikiran! If possible, can you please point to any Jboss document that mentiones this?

It would have been nice to have some workaround/tweak to avoid copying huge ear and yet enable hot deployment :-).

Regards,
Raghav.
Actions
3. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 4:38 AM (in response to rsangam)

I don't think there's a document which specifically mentions this. And from what I know, you'll have to programatically fiddle with ProfileService API to create your own profile which allows hot deployment for external deploy folders.
Actions
4. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

rsangam Sep 2, 2010 4:41 AM (in response to jaikiran)

O ok. Thanks for the pointer! I'll have a look at this API.

Regards,
Raghav.
Actions
5. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

welle Sep 2, 2010 5:14 AM (in response to jaikiran)

> Hot deployment isn't supported for external deploy folders.

This is new for me. I just tested the scenario described above with no problems. Both hot deploy of archives and runtime modifications of a JSP works for me (JBoss AS 5.1.0.GA running linux).
Actions
6. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 5:25 AM (in response to welle)

What do you configurations look like and how/what changes did you do to your deployed application?
Actions
7. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 5:34 AM (in response to welle)

Anders Welen wrote:

> Hot deployment isn't supported for external deploy folders.

This is new for me. I just tested the scenario described above with no problems. Both hot deploy of archives and runtime modifications of a JSP works for me (JBoss AS 5.1.0.GA running linux).
Okay, I just read on of the internal mail conversations I had about this, and I admit my earlier statement was wrong. Hot deploy of that external folder is infact supported. What's not supported is that unlike AS-4.x you can't have different hot deployment characteristics for different deploy folders (i.e. unlike AS-4.x, you can't disable/enable hot deployment for a selected few deploy folders through configuration). Sorry about that confusion.

Thanks Anders for correcting me
Actions
8. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

welle Sep 2, 2010 5:39 AM (in response to jaikiran)

My quick test:

Made the same setup as Raghav Sangam:

profile.xml
========
...
<list elementClass="java.net.URI">
                                <value>${jboss.server.home.url}deploy</value>
                                <value>file:///tmp/deploy</value>
</list>
...

vfs.xml
======
...
<entry>
   <key>file:///tmp/deploy</key>
   <value><inject bean="VfsNamesExceptionHandler"/></value>
</entry>
...

Tested it by moving the jmx-console.war from the standard deploy directory to "/tmp/deploy" and tested the hot deployment by touching the deployment descriptor file (WEB-INF/web.xml). Tested also and edited the index.jsp within the archive witout any problems. I also made a "test.ear" file where I packed the jmx-console.war within with no problems.
Actions
9. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 5:39 AM (in response to rsangam)

raghav Sangam wrote:

Tried to add some other wars etc to this dir, still no luck

What does the hdscanner-jboss-beans.xml in the deploy folder look like? What's the scanPeriod set to?
Actions
10. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

welle Sep 2, 2010 5:40 AM (in response to jaikiran)

Ok
Actions
11. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

welle Sep 2, 2010 5:42 AM (in response to jaikiran)

I haven't touched the hdscanner-jboss-beans.xml at all.
Actions
12. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

jaikiran Sep 2, 2010 5:51 AM (in response to welle)

Anders Welen wrote:

I haven't touched the hdscanner-jboss-beans.xml at all.
That question about hdscanner-jboss-beans.xml was for Raghav
Actions
13. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

rsangam Sep 2, 2010 6:10 AM (in response to jaikiran)

Hi Jaikiran - Here is the part of hdscanner-jboss-beans.xml (same as the one in jboss default profile) :

<bean name="HDScanner" class="org.jboss.system.server.profileservice.hotdeploy.HDScanner">
        <property name="deployer"><inject bean="ProfileServiceDeployer"/></property>
        <property name="profileService"><inject bean="ProfileService"/></property>
        <property name="scanPeriod">5000</property>
        <property name="scanThreadName">HDScanner</property>
    </bean>

Anders - thanks for your reply.Do you have exploded ear under your custom /tmp directory?. I had tried that with exploded folder which looks like this
<our-deploy-folder>/app.ear/ - which as all exploded jars and wars.

Interesting, so it means HD is supported with custom deployment folder? I'll try with some helloworld application and check if it has something to do with my application.

- Raghav.
Actions
14. Re: Jboss 5.1: Unable to enable hot deployment with custom deploy directory

welle Sep 2, 2010 6:43 AM (in response to rsangam)

Raghav: Yes I was testing using the exploded archive jmx-console.war. and also put that in an exploded XXX.ear.

aikiran pai: Aha...sorry
Actions

1 2 Previous Next

Go to original post