This content has been marked as final. Show 1 reply
Problem solved; first I was stupid, and second is I'm not sure. ;-)
As I mentioned earlier, I run JBoss with this command line:
Investigation showed me that run.bat don't pass its arguments to JVM under the hood, and even if it does, its arguments would be program arguments (JBoss' ones), not JVM's. To reach JVM, you need to set JAVA_OPTS env. variable so later run.bat can start JVM with their values. So far so good.
I thought that similar "-D" *.dir and *.url variables are mirroring their values to each other, for example jboss.server.base.dir and jboss.server.base.url, jboss.server.home.dir and jboss.server.home.url . I set jboss.server.base.dir and thought that its value will be used when running JBoss, as well as its *.url corresponding variable. boot.log's DEBUG level showed me that I was wrong. And when I set jboss.server.base.url to point to my writable directory, server has finally found jboss-service.xml and started well.