wdeploy.sh hangs with FUTEX_WAIT_PRIVATE, 1, NULL

juni 25th, 2009
Yenlo
Uncategorized
Reageren uitgeschakeld

The wdeploy.sh returns a normal output, but hangs at Validating Configuration:

Buildfile: wcommon.xml

config:
Loading config.oas1013
Loading PerformanceManagement.properties

Warning: as_mode property not set. Standalone deployment assumed.

preconfig:

checkargs:
Validating configuration…

When looking at which process is causing the installer to stale. We preformed this command by hand to see what is going wrong here.
In order to get more detail on what is causing the stale we added strace for the $ANT command at the end of the wdeploy.sh script.

..
strace $ANT_HOME/bin/ant –noconfig -f wcommon.xml -Das_type=$as_type -listener org.apache.tools.ant.listener.Log4jListener -emacs -Dwdeploy.dir=$HERE -Dbo.dir=$BODIR -Depm.dir=$EPMDIR -Dolap.dir=$OLAPDIR -Dolap.bin.dir=$OLAPBINDIR -DBOBJE=$BOBJE -Dplatform=$platform -Dproperties.file=$propsfile $cmdline
..

executing this command ;

./wdeploy.sh oas1013 -DAPP=PerformanceManagement -Das_admin_password=”oc4j_admin_password” -Dlanglist=”en,nl” deploy

shows us that the process is waiting for resources which it does not get.

..
mmap2(NULL, 528384, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x8d275000 clone(child_stack=0x8d2f54b4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|
CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|
CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x8d2f5bd8, {entry_number:6, base_addr:0x8d2f5b90, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0x8d2f5bd8) = 9401 sched_setscheduler(9401, SCHED_OTHER, { 5 }) = -1 EINVAL (Invalid argument) futex(0xa2878ec, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xa2878e8, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 futex(0xa2ae550, FUTEX_WAKE_PRIVATE, 1) = 1 mmap2(NULL, 528384, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x8d1f4000 clone(child_stack=0x8d2744b4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|
CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|
CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x8d274bd8, {entry_number:6, base_addr:0x8d274b90, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}, child_tidptr=0x8d274bd8) = 9402 sched_setscheduler(9402, SCHED_OTHER, { 5 }) = -1 EINVAL (Invalid argument) futex(0xa2b2dd4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xa2b2dd0, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0xa2b2ce8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xa2b2f4c, FUTEX_WAIT_PRIVATE, 1, NULL

As it turned out a “preferred option” was not set correctly.

In order to deploy the BussinessObject files on a Oracle Application Server 10.1.3.1.0 succesfully, you need to adjust the
Max Heapsize to 1024M and -XX:MaxPermSize=256m. This can be done from within the ascontrol tool of the Oracle Application Server 10.1.3.1.0 ( http://server/em ).

wdelpoy