-
1. Re: How to disable deferred deployment ?
nickarls Apr 19, 2013 2:21 AM (in response to nmay)I glanced at the pull request for the feature at https://github.com/jbossas/jboss-as/pull/3225/files but I didn't see any global configuration switch.
-
2. Re: How to disable deferred deployment ?
jaikiran Apr 19, 2013 3:11 AM (in response to nmay)What kind of a deployment is that? OSGi?
-
3. Re: How to disable deferred deployment ?
nmay Apr 19, 2013 5:59 AM (in response to jaikiran)It's a normal ear deployment.
During deployment I would like to start some jobs, but with deferred deployment it is not possible.
I remember that in "OLD" JBoss it was the property "jboss.as.deployment.ondemand" but in the new EAP I do not know how to start deployment at the server start.
It start always with deffered deployment.
-
4. Re: How to disable deferred deployment ?
jaikiran Apr 19, 2013 6:24 AM (in response to nmay)AFAIK, the deferred deployment phase is an internal implementation detail and shouldn't affect applications. Can you explain a bit more about what you are trying to do and what's not working?
-
5. Re: How to disable deferred deployment ?
nmay Apr 19, 2013 6:41 AM (in response to jaikiran)I trying to port old sar archive from jboss 4.x which is packet within my ear archive and the service should start immidiatly at deployment time.
For example I made an mbean configuration in the jboss-service.xml:
<mbean code="com.my.server.infrastructure.diskmonitor.DiskMonitor" name="my:service=DISK-MONITOR">
<attribute name="critical">true</attribute>
<attribute name="systemDiskMin">1073741824</attribute>
<attribute name="dataDiskMin">1073741824</attribute>
<attribute name="logDiskMin">8589934592</attribute>
<attribute name="logDiskCritical">1073741824</attribute>
</mbean>
I would like that disk monitor service starts and send the signals immediately after the server start, and after it deployed...
If this service start fails the deploymen should fail as well ...
It is working well with jboss 7.1.1 community edition , but in EAP with deferred deployment it is not possible.
I really do not know how to achieve the same behavior with EAP..
Ce message a été modifié par: nmay
Ce message a été modifié par: nmay
-
6. Re: How to disable deferred deployment ?
jaikiran Apr 19, 2013 6:42 AM (in response to nmay)Please attach the entire server log file. Also post the application packaging structure which is the output from:
jar -tf yourear.ear
-
7. Re: How to disable deferred deployment ?
nmay Apr 19, 2013 7:29 AM (in response to jaikiran)Hi , I attached the structure of ear file and server output.
-
server_out.txt.zip 8.1 KB
-
structure.txt.zip 1.2 KB
-
-
8. Re: How to disable deferred deployment ?
ctomc Apr 19, 2013 8:24 AM (in response to nmay)Hi,
given that you dont use OSGI, i would susggest you disable it.
you can do that by commenting out / removing osgi subsystem from your standalone.xml (or any other configuration you are using)
This should remove defer warnings.
--
tomaz
-
9. Re: How to disable deferred deployment ?
jaikiran Apr 19, 2013 8:31 AM (in response to ctomc)1 of 1 people found this helpfulUnless, nmay is using a custom standalone*.xml, the OSGi subsystem is disabled in the standalone-full.xml that we ship.
-
10. Re: How to disable deferred deployment ?
nmay Apr 19, 2013 8:49 AM (in response to jaikiran)Hi,
yes I modified a bit standalone-full.xml , I attached it.
But is there is possibility in configurations to enable immidiatly deployment ? I didn't found it.
Actually I copy it from my jboss 7.1.1 installation. Hmm ... maybe this is the problem... I will try to start with original configuration..
-
standalone-full.xml 23.3 KB
-
-
11. Re: How to disable deferred deployment ?
ctomc Apr 19, 2013 8:46 AM (in response to jaikiran)1 of 1 people found this helpfulIt might be upgrade from older version.
OSGI subsystem is being activated, at least that is what log file says
--
tomaz
-
12. Re: How to disable deferred deployment ?
nmay Apr 19, 2013 9:00 AM (in response to nmay)Sorry , guys ... It was my problem ..
I change to originally delivered standalone-full configuration and it starts to deploy immediately ...
Thank you for the hint !