Unable to deploy EAR using TWIDDLE

[rpatel1]

Hi,

I am using the below Twiddle command to deploy ear file.

ko-sled10:/opt/JBoss/jboss-5.1.0.GA/bin # ./twiddle.sh -s ko-sled10 invoke "jboss.system:service=MainDeployer" deploy "file:///home/rpatel/riskwrite-5.6.17-pNOV001446.ear"

'null'

But after running the command, it prints NULL on the screen. In the server logfile, it prints:

2010-03-03 12:58:09,578 INFO  [org.jboss.deployment.MainDeployer] (RMI TCP Connection(528)-192.168.216.39) deploy, url=file:/home/rpatel/riskwrite-5.6.17-pNOV001446.ear

It does not do anything after that.

Please provide solution as we need to manage/automate deployment using twiddle script. I could not find any good documentation on twiddle too.

Thanks in advance....

regards

Raj

[peterj]

Your twiddle command looks correct. What happens if you deploy the EAR manullay (that is, copy it to the deploy directory)?

[rpatel1]

Hi,

Thanks for your reply.

When we manually deploy the ear using HD or thru admin console (thru add new resource), it works fine except it doesnot explode the .war file inside .ear file. Also in HD mode, I dont know how to deploy the .ear file in exploded mode.

It seems all mystery which gets resolved in this forum. Documentation is not good enough to suss the issue.

regards

Raj

[peterj]

It is an EAR archive file, and not a directory, correct?

And the JBoss AS can access the file given that URL? Based on yoru twiuddle command, JBoss AS is running on a server name ko-sled10. The file you gave it, /home/rpatel/riskwrite-5.6.17-pNOV001446.ear, is on that server?

[rpatel1]

Absolutely yes.

regards

Raj

[rpatel1]

Hi,

Please provide me some help in this regard..

regards

Raj

[peterj]

Sorry, but I have though of everything that I could ask to try to find the root cause. At this point it looks like someone has to debug what is going on when the EAR is deployed in this way, and I don't have the time to try this. Maybe someone else will have some thoughts?

[jaikiran]

[e-mail] wrote:

Hi,

I am using the below Twiddle command to deploy ear file.

ko-sled10:/opt/JBoss/jboss-5.1.0.GA/bin # ./twiddle.sh -s ko-sled10 invoke "jboss.system:service=MainDeployer" deploy "file:///home/rpatel/riskwrite-5.6.17-pNOV001446.ear"

'null'

But after running the command, it prints NULL on the screen. In the server logfile, it prints:

2010-03-03 12:58:09,578 INFO  [org.jboss.deployment.MainDeployer] (RMI TCP Connection(528)-192.168.216.39) deploy, url=file:/home/rpatel/riskwrite-5.6.17-pNOV001446.ear

It does not do anything after that.

I just gave a quick try against my AS 5.1.0. Works fine. I too receive that "null" message on the twiddle prompt. But the deployment of the .ear takes place fine on the server side. Are you worried about that "null" message or are you worried that you don't see any logs on the server side? Absence of log does not always mean that the deployment failed. It might be just a logging configuration issue. Have you tried accessing your application after the twiddle command completes? Also have you tried deploying your application manually outside of the twiddle command? Do you see any difference?

[rpatel1]

Hi,

Yesterday evening, I tried twiddle again and it gave me loadonstartup error, which proved that deployment using twiddle does work and after fixing the loadon startup error as per your last advice it went on but gave some error, which are application specific errors. We need to fix that and then I think it will work.

However I wasnt able to figure out to do exploded deployment using twiddle.

regards

Raj

[peterj]

You cannot do exploded development through twiddle. The deployer mbean allows only archive files to be passed to the deploy operation.