Example Full command from command line:
/home/rob/apps/java/jdk1.6.0_02/bin/java -Dprogram.name=run.sh -server -Xms128m -Xmx512m
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.net.preferIPv4Stack=true
-Djava.endorsed.dirs=/home/rob/apps/jboss/jboss-4.2.0.GA/lib/endorsed -classpath
/home/rob/apps/jboss/jboss-4.2.0.GA/bin/run.jar:/home/rob/apps/java/jdk1.6.0_02/lib/tools.jar
org.jboss.Main
>The question is, what builds the full java command to launch the
server?
In the tooling? heh... as of now nothing. The closest we come to building a full command
is making sure IPv4Stack is preferred where it needs to be. I'll make a JIRA to make
sure I add an API for complete script mimicking.
he jmx access to the DeploymentScanner does not exist as that bean is
gone, and it would not work across server restarts since the change would not be persisted
by default.
Our main use case here is to be able to stop the server from scanning, then we update our
exploded deployed application incrementally without the server recognizing only half the
changes, and then let the server resume scanning. If there'll be another way to do it
in JBoss 5, that'd be great, but the primary goal is that the server doesn't try
to reload an updating application while it's still being changed by us.
Also, a way, either through JMX or some other method, to determine when the application
has been completely loaded by the server, so that our tools can automatically open the web
page for it. RIght now we open the web page right after we deploy, but often times the
server hasn't reloaded the app yet and the user gets an unchanged page or an error
page.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121414#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...