[adamhawkins0]

Is there a way to change the default jboss directory ‘deploy’ when using the deployment tool as i want to deploy to the farm directory so that the deployment will be deployed to all nodes in the cluster.

[Riyad Kalla]

Not currently, this is will be one of the improvements made to the deployment tool in the 2.8 release. I do not currently have an ETA for 2.8, but it shouldn’t be too far off.

[dstevenson]

I am using 3.8.1 and I still cannot figure out how to deploy to the JBoss farm directory instead of the deploy directory. Has this been addressed yet.

[Riyad Kalla]

No, custom deployments took a back seat to some other high priority functionality. I will bring it up again and see if we have an ETA for it. I appologize.

[Riyad Kalla]

Official word:

Should show up after 3.8.2. Perhaps in 3.8.3+, definately by 3.9.

[amalamud]

How can I configure MyEclipse to start JBoss ‘run -c all’. I can’t find a way to pass a ‘-c’ option correctly. I am using version 4.1M1. Is it possible? Thanks.

[Greg]

You can accomplish this by going to Windows -> Preferences -> MyEclipse -> AppServers -> Jboss(3|4) and then set the “Optional Program Arguments” to the following value:

-c all

[amalamud]

Setting “Optional Program Arguments” to “-c all” did not work. It assumes that -c is the server’s name. Here is the trace:

jboss: unused non-option argument: all
09:46:40,246 INFO [Server] Starting JBoss (MX MicroKernel)…
09:46:40,307 INFO [Server] Release ID: JBoss [Zion] 4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)
09:46:40,317 INFO [Server] Home Dir: C:\jroot\jboss-4.0.3SP1
09:46:40,327 INFO [Server] Home URL: file:/C:/jroot/jboss-4.0.3SP1/
09:46:40,327 INFO [Server] Patch URL: null
09:46:40,327 INFO [Server] Server Name: -c
09:46:40,327 INFO [Server] Server Home Dir: C:\jroot\jboss-4.0.3SP1\server\-c
09:46:40,327 INFO [Server] Server Home URL: file:/C:/jroot/jboss-4.0.3SP1/server/-c/
09:46:40,327 INFO [Server] Server Temp Dir: C:\jroot\jboss-4.0.3SP1\server\-c\tmp
09:46:40,327 INFO [Server] Root Deployment Filename: jboss-service.xml
09:46:41,969 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc.
09:46:41,969 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc.
09:46:41,969 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
09:46:43,021 INFO [Server] Core system initialized
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: url file:/C:/jroot/jboss-4.0.3SP1/server/-c/conf/jboss-service.xml could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:191)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:752)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
at org.jboss.Main.boot(Main.java:187)
at org.jboss.Main$1.run(Main.java:438)
at java.lang.Thread.run(Thread.java:595)

[Greg]

I configured my jboss4 appserver connector in the MyEclipse preferences like shown in the following screenshot. After this I was able to start the jboss4 server with no problems.

If you don’t see the same results with similiar settings then there must be some other configuration or environment problem.

[Author]

Posts