Hi Everybody,
we got a rather unexpected issue here. A client of ours requires us to deploy
to a jboss server (7.1) but restricts us from using anything but the cli
deployment method (deployment-scanner has been disabled entirely). The problem
is that because of it we cannot explode the war files properly and the
deployment will be added to temporary jboss directories. This in turn causes
errors with all the caching and config files, which cannot be found (the
repository itself is a postgres database and should be fine). On subsequent
deployments this is causing a load of errors and prohibits us from starting
magnolia entirely.
As a workaround, we tried to set the config parameters accordingly:
magnolia.cache.startdir=${magnolia.temp.home}/cache
magnolia.upload.tmpdir=${magnolia.temp.home}/tmp
magnolia.exchange.history=${magnolia.temp.home}/history
magnolia.repositories.home=${magnolia.temp.home}/repositories
magnolia.logs.dir=${magnolia.temp.home}/logs
But the errors remain (at least in parts). Help is much appreciated.
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=7e6ba798-b03e-462a-823e-2e1f3441c64b
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
