Application Server CPU at 100%

We are running Oracle Forms and Reports 9.0.4 using OC4J on a Solaris 9 server. Environment responds quickly, except when an end user requests the generation of a large PDF report (with several hundred to over a thousand pages). Although query results are returned quickly by the database server, CPU on application server tops out at 100% for an hour or more while these large reports are being generated. During this hour or more, no other reports can be generated by other end users. Can the application server be configured to allow CPU and other resources to be shared during generation of large PDF reports? If so, how?

>
... -Dlogfile=/vol04/applmgr/DEV/inst/apps/DEV_devas/logs/appl/conc/log/FNDOPP216337.txt ...
>
This looks to be the XML/BI Publisher process. Can you post relevant sections from this file ?
Pl post EBS related questions in the EBS forums - http://forums.oracle.com/forums/category.jspa?categoryID=3
HTH
Srini

Similar Messages

Sun Java Application Server 9.0 and 9.1 - High CPU PROCENTAGE 100%

Hi,
I have problem with sun java application Server running after few days during watching a logs from web admin suddenly the application server takes 100% cpu and keeps this procentage - I have to manually close the server process.
The server running on Windows Server 2003.
Anyone have any idea to sovle the problem?

Hi Kedar,
Thanks for the reply. Yes, I finally figured it out.
The custom MBeans seem to work well for the most part though I don't know for sure if I'm using them in the way they were really intended.
Basically, I want to run 'services' on my application server for the lifetime of the server. I want these 'services' to maintain things like runtime caching of information over time that is not persisted in a DB but needs to be kept around in active memory to be used at a later time, but only while the application server is up and running.
Another thing I would like to do is have them receive JMS notifications directly, but I seem to be having trouble when subscribing as a consumer within my custom MBean. The topic thread on that is here:
http://forum.java.sun.com/thread.jspa?threadID=5153124&tstart=0

Timer Job job-application-server-admin-service spiking CPU after every minute

Hi all,
I have an issue in my SP2010 Farm that all the servers spiking CPU to 100% after a minute or so. I have drilled down and found that the following timer jon is the culprit.
Timer Job job-application-server-admin-service. If I change the service running to 2 minutes (default is 1 Min) then the spikes comes after every 2 minutes.
Please suggest what I can do about this?

Was it working fine previously. If yes, what changes happened which caused this issue
1. Check the ULS + Eventviewer logs at the time when this issue happens.
2. Collect perflog files and execute PAL on that this will give you the complete analysis of processes and performance at that time.
Check below:
http://social.technet.microsoft.com/Forums/office/en-US/07207109-0450-47cf-b6ee-467a58eaa887/trust-relationship-between-the-primary-domain-and-trusted-domain-failed?forum=sharepointgenerallegacy
http://webcache.googleusercontent.com/search?q=cache:nJYnqC6ug8cJ:sharepointfraggel.blogspot.com/+&cd=3&hl=en&ct=clnk&gl=in
Fix the problem
Manually clear the file system cache on the local servers (fe's) on which the timer service is running (http://support.microsoft.com/kb/939308)
Stop the SharePoint Timer Service in Administrative Tool/Services.
Go to the cache folder. For Windows Server 2008: Drive:\ProgramData\Microsoft\SharePoint\Config
Find the folder that contains the file Cache.ini
Delete all the XML configuration files in the folder so that you can verify that the folder is replaced by new XML files when the cache is rebuilt.
Open the Cache.ini file, delete all content in the file and type 1, save and exit.
Start the SharePoint Timer service
If this helped you resolve your issue, please mark it Answered

Evenlog viewing causes CPU usage 100% on Windows server 2008 SP2

We have Windows server 2008 SP2 with strange behaviour. When I scroll down events in eventlog viewer CPU usage hits 100% and eventlog viewer freeze. CPU usage is split between 2 processes SVCHOST.EXE (lmhosts, eventlog and Dhcp services) and MMC.EXE.
1)I tried to replace eventlog files with new ones. That didn’t helped
2)After server clean boot problem still exist.
3)When CPU hits 100% usage process explorer shows that from SVCHOST.EXE process CPU is used by service EventLog.
Any ideas how to fix this?

Hi Santosh
I re-installed VMware
tools and also configured VMXNET 3 - nothing changed :(
Sorry to hear that.
Windows event log service has couple of dependencies i.e. task scheduler and windows event collector service. Can try restrating those services ?
In addition to above, try following steps
Change NTFS permission of %WINDIR%\System32\WinEvt\Logs directory, add Local Service and
Network Service, give them FULL permissions.
Stop and Start event viewer service by running following command
net stop eventlog && net start eventlog
Issues like this might occur if the disk (FC or iSCSI SAN or even NAS) has some inconsistencies , this is true in case of both physical and virtual machines
You might want to try running chkdisk as well on the server in question
http://technet.microsoft.com/en-us/library/cc730714(v=ws.10).aspx
If nothing helps, try inplace upgrade of the Operating system as an last option.
How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
http://support.microsoft.com/kb/2255099
Thanks
Regards, Santosh
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Whenever you see a helpful reply, click on Vote As Helpful & click on
Mark As Answer if a post answers your question.

Solutions/Options for 100% uptime with Application Server

what are the solutions/options available for 100% uptime with Oracle DB and application server as one of the business area requires 100% uptime of the application system and DB.
Is there any cost effective options available to achieve the above stated requirement or else might to have to go for stand alone system?
Thanks in advance for help.

Hi,
I would recommend you to take a look at the Oracle Application Server Enterprise Deployment Guide and Oracle Application Server High Availability Guide. Both are avaliable at http://download-west.oracle.com/docs/cd/B14099_15/index.htm.
Regards,
Mathias

TRIALSP11 Application server Shutdown at SAP LOGON

This is my first adventure with SAP or ABAP..
1. I installed and followed the SAPNW2004sABAPTrialSP11 install instructions.
2. The installation instructions went fine from the
/people/manfred.lutz/blog/2007/03/16/new-blog-series-abap-trial-version-for-newbies
3. SAMMMC has MSG_SERVER.exe and DISP_WORK.EXE both green when I stared the SAP Logon.
4. After I start the SAP the waiting for response shows up.
5. SAP GUI comes up with a error saying application server shutdown.
6. my disp+work.exe goes to stopped state.
7. Error message says componet is 710, version 10, return code -17, counter 1.
The Log is attached. Any help is rewarded.
trc file: "dev_disp", trc level: 1, release: "700"
sysno      00
sid        NSP
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    95
intno      20050900
make:      multithreaded, ASCII, optimized
pid        2192
Fri Jun 29 21:56:47 2007
kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
length of sys_adm_ext is 360 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 2192) [dpxxdisp.c   1239]
Fri Jun 29 21:56:48 2007
     shared lib "dw_xml.dll" version 95 successfully loaded
     shared lib "dw_xtc.dll" version 95 successfully loaded
     shared lib "dw_stl.dll" version 95 successfully loaded
     shared lib "dw_gui.dll" version 95 successfully loaded
     shared lib "dw_mdm.dll" version 95 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Fri Jun 29 21:56:52 2007
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5355]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >kiranmtop_NSP_00                        <
DpShMCreate: sizeof(wp_adm)          6328     (904)
DpShMCreate: sizeof(tm_adm)          3605136     (17936)
DpShMCreate: sizeof(wp_ca_adm)          1200     (60)
DpShMCreate: sizeof(appc_ca_adm)     1200     (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)          528048     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1280)
DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 059B0040, size: 4205552)
DpShMCreate: allocated sys_adm at 059B0040
DpShMCreate: allocated wp_adm at 059B1A28
DpShMCreate: allocated tm_adm_list at 059B32E0
DpShMCreate: allocated tm_adm at 059B3310
DpShMCreate: allocated wp_ca_adm at 05D235A0
DpShMCreate: allocated appc_ca_adm at 05D23A50
DpShMCreate: allocated comm_adm at 05D23F00
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 05DA4DB0
DpShMCreate: allocated gw_adm at 05DA4DF0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 05DA4E20
DpShMCreate: allocated wall_adm at 05DA4E28
MBUF state OFF
DpCommInitTable: init table for 500 entries
Fri Jun 29 21:56:53 2007
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Memory Reset disabled as NT default
<ES> 127 blocks reserved for free list.
ES initialized.
rdisp/http_min_wait_dia_wp : 1 -> 1
Fri Jun 29 21:56:54 2007
***LOG Q0K=> DpMsAttach, mscon ( kiranmtop) [dpxxdisp.c   11663]
Fri Jun 29 21:56:55 2007
DpStartStopMsg: send start message (myname is >kiranmtop_NSP_00                        <)
DpStartStopMsg: start msg sent
Fri Jun 29 21:56:56 2007
CCMS: alert/MONI_SEGM_SIZE = 0   monitoring and alerting switched off.
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 95
Release check o.K.
Fri Jun 29 21:57:35 2007
ERROR => W0 (pid 2268) died [dpxxdisp.c   14318]
ERROR => W1 (pid 2276) died [dpxxdisp.c   14318]
ERROR => W2 (pid 2284) died [dpxxdisp.c   14318]
my types changed after wp death/restart 0x9f --> 0x9e
ERROR => W3 (pid 2292) died [dpxxdisp.c   14318]
my types changed after wp death/restart 0x9e --> 0x9c
ERROR => W4 (pid 2300) died [dpxxdisp.c   14318]
my types changed after wp death/restart 0x9c --> 0x98
ERROR => W5 (pid 2308) died [dpxxdisp.c   14318]
my types changed after wp death/restart 0x98 --> 0x90
ERROR => W6 (pid 2316) died [dpxxdisp.c   14318]
my types changed after wp death/restart 0x90 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:45 2007
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long)               Sat Jun 30 04:57:45 2007
========================
No Ty. Pid      Status Cause Start Err Sem CPU    Time Program Cl User         Action                    Table
0 DIA     2268 Ended         no      1   0             0
1 DIA     2276 Ended         no      1   0             0
2 DIA     2284 Ended         no      1   0             0
3 UPD     2292 Ended         no      1   0             0
4 ENQ     2300 Ended         no      1   0             0
5 BTC     2308 Ended         no      1   0             0
6 SPO     2316 Ended         no      1   0             0
Dispatcher Queue Statistics               Sat Jun 30 04:57:45 2007
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
2
2000
5
5
--------++++--
+
DIA
5
5
2000
5
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id          12
wake_evt_udp_now     0
wake events           total     7, udp     4 ( 57%), shm     3 ( 42%)
since last update     total     7, udp     4 ( 57%), shm     3 ( 42%)
Dump of tm_adm structure:               Sat Jun 30 04:57:45 2007
=========================
Term    uid man user    term   lastop mod wp ta   a/i (modes)
RM-T7, U8,                 , kiranmtop, 21:57:24, M0, W-1,     , 1/0
Workprocess Comm. Area Blocks               Sat Jun 30 04:57:45 2007
=============================
Slots: 20, Used: 2, Max: 1
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
1
DISPATCHER
-1
WPCAAD001
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:50 2007
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >kiranmtop_NSP_00                        < (normal)
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes
Stop gateway
killing process (2252) (SOFT_KILL)
Stop icman
killing process (2260) (SOFT_KILL)
Terminate gui connections
send SHUTDOWN to REM TM 7
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/20/7
LOCK WP ca_blk 2
return errno (-17) to T7
errormsg without overhead: take mode 0
NiBufIAlloc: malloc NiBufadm, to 0 bytes
try to send 14 to M0
NiBufSend starting
NiIWrite: hdl 5 sent data (wrt=14,pac=1,MESG_IO)
REL WP ca_blk 2
set status of T7 to TM_DISCONNECTED
NiBufISelUpdate: new MODE -- (r-) for hdl 5 in set0
SiSelNSet: set events of sock 1508 to: ---
NiBufISelRemove: remove hdl 5 from set0
SiSelNRemove: removed sock 1508
NiSelIRemove: removed hdl 5
DpDelSocketInfo: del info for socket 5 (type=3)
NiICloseHandle: shutdown and close hdl 5 / sock 1508
NiBufIClose: clear extension for hdl 5
dp_tm_adm[7].stat = DP_SLOT_FREE
DpGetSchedule: next schedule 1183179475/922000
Fri Jun 29 21:57:51 2007
DpGetSchedule: no schedule found
DpITmSlotRelease: release slot 7
DpListInsert: insert elem 7 into tmadm_free_list (at begin)
DpListInsert: 194 elems in tmadm_free_list
DpListRemove: remove elem 7 from tmadm_inuse_list
DpListRemove: 7 elems in tmadm_inuse_list
wait for end of work processes
wait for end of gateway
[DpProcDied] Process died (PID:2252 HANDLE:1592)
wait for end of icman
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:52 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:53 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:54 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:55 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:56 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:57 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:58 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:57:59 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:58:00 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:58:01 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:58:02 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2260 HANDLE:1608)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1629
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Jun 29 21:58:03 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:2260 HANDLE:1608)
DpStartStopMsg: send stop message (myname is >kiranmtop_NSP_00                        <)
NiIMyHostName: hostname = 'kiranmtop'
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=562,pac=1,MESG_IO)
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name                    -, type 4, key -
DpStartStopMsg: stop msg sent
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
NiIRead: read for hdl 2 timed out (0ms)
DpHalt: no more messages from the message server
DpHalt: send keepalive to synchronize with the message server
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=114,pac=1,MESG_IO)
MsINiWrite: sent 114 bytes
send msg (len 110+4) to name           MSG_SERVER, type 0, key -
MsSndName: MS_NOOP ok
Send 4 bytes to MSG_SERVER
NiIRead: hdl 2 received data (rcd=114,pac=1,MESG_IO)
NiBufIIn: NIBUF len=114
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 114 bytes
MSG received, len 110+4, flag 3, from MSG_SERVER          , typ 0, key -
Received 4 bytes from MSG_SERVER
Received opcode MS_NOOP from msg_server, reply MSOP_OK
MsOpReceive: ok
MsSendKeepalive : keepalive sent to message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
Fri Jun 29 21:58:04 2007
NiIPeek: peek for hdl 2 timed out (r; 1000ms)
NiIRead: read for hdl 2 timed out (1000ms)
DpHalt: no more messages from the message server
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   11976]
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiBufISelUpdate: new MODE -- (r-) for hdl 2 in set0
SiSelNSet: set events of sock 1556 to: ---
NiBufISelRemove: remove hdl 2 from set0
SiSelNRemove: removed sock 1556 (pos=2)
SiSelNRemove: removed sock 1556
NiSelIRemove: removed hdl 2
MBUF state OFF
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 2/20/7
LOCK WP ca_blk 2
make DISP owner of wp_ca_blk 2
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 15)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 2 / sock 1556
NiBufIClose: clear extension for hdl 2
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 2192) [dpxxdisp.c   10333]
Good Bye .....

Hi Russell,
I am also facing the same problem as Kiran.
I have attached dev_w0 file, with this msg.
can you please tell me where the problem lies?
=============================================================
trc file: "dev_w0", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
B
B Sun Jul 01 18:13:56 2007
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\TEK\SYS\exe\run\dboraslib.dll' ...
B Library 'C:\usr\sap\TEK\SYS\exe\run\dboraslib.dll' loaded
B Version of 'C:\usr\sap\TEK\SYS\exe\run\dboraslib.dll' is "620.02", patchlevel (0.112)
B New connection 0 created
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    251
M intno      20020600
M pid        3464
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3464) [dpxxdisp.c   1016]
I MtxInit: -2 0 0
X
X Sun Jul 01 18:13:58 2007
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation std
M <EsNT> Memory Reset enabled as NT default
X ES initialized.
M
M Sun Jul 01 18:14:07 2007
M calling db_connect ...
C Got ORACLE_HOME=C:\oracle\ora81 from environment
C
C Sun Jul 01 18:14:12 2007
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C Logon as OPS$-user to get SAPTEK's password
C Connecting as /@TEK on connection 0 ...
C Attaching to DB Server TEK (con_hdl=0,svchp=06AA97F8,svrhp=06AA9604)
C
C Sun Jul 01 18:14:13 2007
C *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
[dboci.c      3566]
C *** ERROR => CONNECT failed with sql error '12541'
[dboci.c      9536]
C Try to connect with default password
C Connecting as SAPTEK/<pwd>@TEK on connection 0 ...
C Attaching to DB Server TEK (con_hdl=0,svchp=06AA97F8,svrhp=06AA9410)
C
C Sun Jul 01 18:14:14 2007
C *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
[dboci.c      3566]
C *** ERROR => CONNECT failed with sql error '12541'
[dboci.c      9536]
B ***LOG BY2=> sql error 12541 performing CON [dbsh#2 @ 962] [dbsh    0962 ]
B ***LOG BY0=> ORA-12541: TNS:no listener [dbsh#2 @ 962] [dbsh    0962 ]
B ***LOG BY2=> sql error 12541 performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-12541: TNS:no listener [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1098]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   8277]
M
M Info for wp 0
M
M    stat = 4
M    reqtype = 1
M    act_reqtype = -1
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = -1
M    rq_source = 255
M    last_tid = 0
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server sapsrv_TEK_00 on host sapsrv (wp 0)
M * ERROR       tskh_init: db_connect
M *
M * TIME        Sun Jul 01 18:14:14 2007
M * RELEASE     620
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        8408
M * COUNTER     1
M *
M *****************************************************************************
M
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   672]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 235]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3464) [dpnttool.c   345]

Application Server Platform Edition 8.1 2005Q2 fails to start - CLI156

I have installed and re-installed PE8.1 on my laptop many times (with security off). I followed Quickstart and after 60 seconds end up with CLI156. I have upgraded from XP Home Edition to XP Professional. I have been going round and round for the last 4 days. I have searched for CLI156 and have tried many options. Any pointers (if not memory references) would be appreciated.
Pertinent information is as follows:
Machine information
Vendor:TOSHIBA
Machine Name:Satellite L15
BIOS Name:Rev 1.0 XXX
BIOS Version:V1.80
Version:PSL10U-01X02FV
CPU Maker:GenuineIntel
CPU Name:Intel(R) Celeron(R) M processor 1.30GHz
CPU Base Clock:400
OS:Microsoft Windows XP Professional
OS Build:2600
OS SP:Service Pack 2
Ram:768432
Windows IP Configuration
Host Name . . . . . . . . . . . . : FE
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : INPROCOMM IPN2220 Wireless LAN Card
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Lease Obtained. . . . . . . . . . : Sunday, October 02, 2005 8:24:56 AM
Lease Expires . . . . . . . . . . : Monday, October 03, 2005 8:24:56 AM
Microsoft TCP/IP version 6
Realtek RTL8139/810x Family Fast Ethernet NIC
INPROCOMM IPN2220 Wireless LAN Card
Microsoft Tun Miniport Adapter
TOSHIBA Network Device Usermode I/O Protocol
INPROCOMM IPN2220 Wireless LAN Card
Realtek RTL8139/810x Family Fast Ethernet NIC
Point to Point Protocol Over Ethernet
INPROCOMM IPN2220 Wireless LAN Card
Realtek RTL8139/810x Family Fast Ethernet NIC
Point to Point Tunneling Protocol
Layer 2 Tunneling Protocol
Remote Access NDIS WAN Driver
WAN Miniport (ATW)
Direct Parallel
WAN Miniport (PPPOE)
WAN Miniport (PPTP)
WAN Miniport (L2TP)
RAS Async Adapter
NDIS Usermode I/O Protocol
INPROCOMM IPN2220 Wireless LAN Card
Realtek RTL8139/810x Family Fast Ethernet NIC
Message-oriented TCP/IP Protocol (SMB session)
WINS Client(TCP/IP) Protocol
Microsoft TCP/IP version 6
Realtek RTL8139/810x Family Fast Ethernet NIC
Microsoft TCP/IP version 6
INPROCOMM IPN2220 Wireless LAN Card
Microsoft TCP/IP version 6
Microsoft Tun Miniport Adapter
Internet Protocol (TCP/IP)
INPROCOMM IPN2220 Wireless LAN Card
Internet Protocol (TCP/IP)
Realtek RTL8139/810x Family Fast Ethernet NIC
Internet Protocol (TCP/IP)
WAN Miniport (IP)
Internet Protocol (TCP/IP)
INPROCOMM IPN2220 Wireless LAN Card
Realtek RTL8139/810x Family Fast Ethernet NIC
WAN Miniport (IP)
Network Device information
Realtek RTL8139/810x Family Fast Ethernet NIC
Device ID : PCI\VEN_10EC&DEV_8139&SUBSYS_FF311179&REV_10\4&16793A72&0&10F0
Status : Enable
Driver Vender : Realtek Semiconductor Corp.
Driver Version : 5.618.1015.2004
Driver Date : 10-15-2004
INPROCOMM IPN2220 Wireless LAN Card
Device ID : PCI\VEN_17FE&DEV_2220&SUBSYS_03101468&REV_00\4&16793A72&0&20F0
Status : Enable
Driver Vender : INPROCOMM
Driver Version : 3.3.11.2004
Driver Date : 11-4-2004
Diagnostics results
Ping Option : Off
ConfigFree Version
ConfigFree(TM) 4.90.57a
Database 3.00.02
Network Diagnostics
No Problem found
netstat -an before installation (cox high speed Internet security, IM, skype - off)
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1429 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1435 0.0.0.0:0 LISTENING
TCP 127.0.0.1:19989 0.0.0.0:0 LISTENING
TCP 192.168.1.101:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING 0
TCP [::]:1025 [::]:0 LISTENING 0
TCP [::]:1429 [::]:0 LISTENING 0
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1436 *:*
UDP 0.0.0.0:1640 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.101:123 *:*
UDP 192.168.1.101:137 *:*
UDP 192.168.1.101:138 *:*
UDP 192.168.1.101:1900 *:*
UDP 192.168.1.101:11206 *:*
fport before installation (cox high speed Internet security, IM, skype - off)
FPort v2.0 - TCP/IP Process to Port Mapper
Copyright 2000 by Foundstone, Inc.
http://www.foundstone.com
Pid Process Port Proto Path
1264 inetinfo -> 25 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 135 TCP
4 System -> 139 TCP
4 System -> 445 TCP
1684 LEXPPS -> 1025 TCP C:\WINDOWS\system32\LEXPPS.EXE
1264 inetinfo -> 1429 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 1435 TCP
524 CFSServ -> 19989 TCP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
524 CFSServ -> 123 UDP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
0 System -> 123 UDP
0 System -> 137 UDP
0 System -> 138 UDP
1264 inetinfo -> 445 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 500 UDP
4 System -> 1436 UDP
1684 LEXPPS -> 1640 UDP C:\WINDOWS\system32\LEXPPS.EXE
0 System -> 1900 UDP
1264 inetinfo -> 3456 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 4500 UDP
0 System -> 11206 UDP
fport after installation of App Server (cox high speed Internet security, IM, skype - off)
FPort v2.0 - TCP/IP Process to Port Mapper
Copyright 2000 by Foundstone, Inc.
http://www.foundstone.com
Pid Process Port Proto Path
1264 inetinfo -> 25 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 135 TCP
4 System -> 139 TCP
4 System -> 445 TCP
1684 LEXPPS -> 1025 TCP C:\WINDOWS\system32\LEXPPS.EXE
1264 inetinfo -> 1429 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 1435 TCP
524 CFSServ -> 19989 TCP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
524 CFSServ -> 123 UDP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
0 System -> 123 UDP
0 System -> 137 UDP
0 System -> 138 UDP
1264 inetinfo -> 445 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 500 UDP
4 System -> 1436 UDP
1684 LEXPPS -> 1640 UDP C:\WINDOWS\system32\LEXPPS.EXE
0 System -> 1900 UDP
1264 inetinfo -> 3456 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 4500 UDP
0 System -> 28459 UDP
early in initializing App Server
fport
FPort v2.0 - TCP/IP Process to Port Mapper
Copyright 2000 by Foundstone, Inc.
http://www.foundstone.com
Pid Process Port Proto Path
1264 inetinfo -> 25 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 135 TCP
4 System -> 139 TCP
4 System -> 445 TCP
1684 LEXPPS -> 1025 TCP C:\WINDOWS\system32\LEXPPS.EXE
1264 inetinfo -> 1429 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 1435 TCP
3960 appserv -> 1664 TCP C:\Sun\AppServer\lib\appserv.exe
0 System -> 1666 TCP
1664 java -> 1668 TCP C:\Sun\jdk1.5.0_02\bin\java.exe
3960 appserv -> 1669 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1670 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1671 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1672 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1673 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1674 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1675 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1676 TCP C:\Sun\AppServer\lib\appserv.exe
524 CFSServ -> 19989 TCP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
0 System -> 123 UDP
3960 appserv -> 123 UDP C:\Sun\AppServer\lib\appserv.exe
1664 java -> 137 UDP C:\Sun\jdk1.5.0_02\bin\java.exe
3960 appserv -> 138 UDP C:\Sun\AppServer\lib\appserv.exe
1264 inetinfo -> 445 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 500 UDP
4 System -> 1436 UDP
1684 LEXPPS -> 1640 UDP C:\WINDOWS\system32\LEXPPS.EXE
3960 appserv -> 1900 UDP C:\Sun\AppServer\lib\appserv.exe
1264 inetinfo -> 3456 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 4500 UDP
3960 appserv -> 34840 UDP C:\Sun\AppServer\lib\appserv.exe
netstat -an early in initialization of App Server
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1429 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1435 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1664 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1664 127.0.0.1:1668 ESTABLISHED
TCP 127.0.0.1:1666 127.0.0.1:1667 TIME_WAIT
TCP 127.0.0.1:1668 127.0.0.1:1664 ESTABLISHED
TCP 127.0.0.1:1669 127.0.0.1:1670 ESTABLISHED
TCP 127.0.0.1:1670 127.0.0.1:1669 ESTABLISHED
TCP 127.0.0.1:1671 127.0.0.1:1672 ESTABLISHED
TCP 127.0.0.1:1672 127.0.0.1:1671 ESTABLISHED
TCP 127.0.0.1:1673 127.0.0.1:1674 ESTABLISHED
TCP 127.0.0.1:1674 127.0.0.1:1673 ESTABLISHED
TCP 127.0.0.1:1675 127.0.0.1:1676 ESTABLISHED
TCP 127.0.0.1:1676 127.0.0.1:1675 ESTABLISHED
TCP 127.0.0.1:19989 0.0.0.0:0 LISTENING
TCP 192.168.1.101:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING 0
TCP [::]:1025 [::]:0 LISTENING 0
TCP [::]:1429 [::]:0 LISTENING 0
TCP [::]:1668 [::]:0 LISTENING 0
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1436 *:*
UDP 0.0.0.0:1640 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.101:123 *:*
UDP 192.168.1.101:137 *:*
UDP 192.168.1.101:138 *:*
UDP 192.168.1.101:1900 *:*
UDP 192.168.1.101:34840 *:*
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Full thread dump Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode, sharing):
"Thread-2" prio=5 tid=0x02d85588 nid=0x970 runnable [0x033cf000..0x033cf9e8]
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:177)
at com.sun.enterprise.util.FlusherThread.run(ProcessExecutor.java:625)
"RMI RenewClean-[192.168.1.101:1664,com.sun.enterprise.admin.server.core.channel
.LocalRMIClientSocketFactory@1415de6]" daemon prio=5 tid=0x02dfad98 nid=0x8ec in
Object.wait() [0x0333f000..0x0333fae8]
at java.lang.Object.wait(Native Method)
- waiting on <0x22a8b3e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x22a8b3e8> (a java.lang.ref.ReferenceQueue$Lock)
at sun.rmi.transport.DGCClient$EndpointEntry$RenewCleanThread.run(DGCCli
ent.java:500)
at java.lang.Thread.run(Thread.java:595)
"GC Daemon" daemon prio=2 tid=0x02de5e10 nid=0x27c in Object.wait() [0x032ff000.
.0x032ffb68]
at java.lang.Object.wait(Native Method)
- waiting on <0x22fe34d8> (a sun.misc.GC$LatencyLock)
at sun.misc.GC$Daemon.run(GC.java:100)
- locked <0x22fe34d8> (a sun.misc.GC$LatencyLock)
"RMI RenewClean-[192.168.1.101:1664,com.sun.enterprise.admin.server.core.channel
.LocalRMIClientSocketFactory@3ee284]" daemon prio=5 tid=0x02de5c90 nid=0x100 in
Object.wait() [0x032bf000..0x032bfbe8]
at java.lang.Object.wait(Native Method)
- waiting on <0x22fe30e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x22fe30e8> (a java.lang.ref.ReferenceQueue$Lock)
at sun.rmi.transport.DGCClient$EndpointEntry$RenewCleanThread.run(DGCCli
ent.java:500)
at java.lang.Thread.run(Thread.java:595)
"Low Memory Detector" daemon prio=5 tid=0x00a6db08 nid=0x198 runnable [0x0000000
0..0x00000000]
"CompilerThread0" daemon prio=10 tid=0x00a6c6e0 nid=0xe10 waiting on condition [
0x00000000..0x02bcf6c0]
"Signal Dispatcher" daemon prio=10 tid=0x00a6ba00 nid=0x844 waiting on condition
[0x00000000..0x00000000]
"Finalizer" daemon prio=9 tid=0x00a68dd8 nid=0xf10 in Object.wait() [0x02b4f000.
.0x02b4fa68]
at java.lang.Object.wait(Native Method)
- waiting on <0x22f6a038> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x22f6a038> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00a478b0 nid=0xf34 in Object.wait() [0x
02b0f000..0x02b0fae8]
at java.lang.Object.wait(Native Method)
- waiting on <0x22f6a0b8> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x22f6a0b8> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x000377a8 nid=0x194 runnable [0x0007f000..0x0007fc38]
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
- locked <0x22adcf20> (a java.net.SocksSocketImpl)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at com.sun.enterprise.admin.server.core.channel.LocalRMIClientSocketFact
ory.createSocket(LocalRMIClientSocketFactory.java:65)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at com.sun.enterprise.admin.server.core.channel.AdminChannelServer_Stub.
getServerStatusCode(Unknown Source)
at com.sun.enterprise.admin.server.core.channel.RMIClient.getInstanceSta
tusCode(RMIClient.java:250)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.getInstance
Status(PEInstancesManager.java:555)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.isInstanceS
tarting(PEInstancesManager.java:278)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager$1.check(PEI
nstancesManager.java:417)
at com.sun.enterprise.admin.servermgmt.pe.InstanceTimer.run(InstanceTime
r.java:32)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.waitUntilSt
arting(PEInstancesManager.java:423)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.waitUntilSt
arting(PEInstancesManager.java:407)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.startInstan
ce(PEInstancesManager.java:244)
at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.startInstan
ce(PEInstancesManager.java:87)
at com.sun.enterprise.admin.servermgmt.pe.PEDomainsManager.startDomain(P
EDomainsManager.java:178)
at com.sun.enterprise.cli.commands.StartDomainCommand.startDomain(StartD
omainCommand.java:104)
at com.sun.enterprise.cli.commands.StartDomainCommand.runCommand(StartDo
mainCommand.java:141)
at com.sun.enterprise.cli.framework.CLIMain.invokeCommand(CLIMain.java:1
35)
at com.sun.enterprise.cli.framework.CLIMain.main(CLIMain.java:46)
"VM Thread" prio=10 tid=0x00a67010 nid=0x82c runnable
"VM Periodic Task Thread" prio=10 tid=0x00a6ed18 nid=0x5a0 waiting on condition
J2EE 1.4 SDK and Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2 June 6,
2005
All in one and separate bundles
sjsas_pe-8_1_02_2005Q2-windows
netstat -an late in initializing App Server
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1429 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1435 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1664 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1664 127.0.0.1:1668 ESTABLISHED
TCP 127.0.0.1:1668 127.0.0.1:1664 ESTABLISHED
TCP 127.0.0.1:1669 127.0.0.1:1670 ESTABLISHED
TCP 127.0.0.1:1670 127.0.0.1:1669 ESTABLISHED
TCP 127.0.0.1:1671 127.0.0.1:1672 ESTABLISHED
TCP 127.0.0.1:1672 127.0.0.1:1671 ESTABLISHED
TCP 127.0.0.1:1673 127.0.0.1:1674 ESTABLISHED
TCP 127.0.0.1:1674 127.0.0.1:1673 ESTABLISHED
TCP 127.0.0.1:1675 127.0.0.1:1676 ESTABLISHED
TCP 127.0.0.1:1676 127.0.0.1:1675 ESTABLISHED
TCP 127.0.0.1:19989 0.0.0.0:0 LISTENING
TCP 192.168.1.101:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING 0
TCP [::]:1025 [::]:0 LISTENING 0
TCP [::]:1429 [::]:0 LISTENING 0
TCP [::]:1668 [::]:0 LISTENING 0
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1436 *:*
UDP 0.0.0.0:1640 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.101:123 *:*
UDP 192.168.1.101:137 *:*
UDP 192.168.1.101:138 *:*
UDP 192.168.1.101:1900 *:*
UDP 192.168.1.101:65456 *:*
netstat -an at CLI156 error
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1429 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1435 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1664 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1669 127.0.0.1:1670 ESTABLISHED
TCP 127.0.0.1:1670 127.0.0.1:1669 ESTABLISHED
TCP 127.0.0.1:1671 127.0.0.1:1672 ESTABLISHED
TCP 127.0.0.1:1672 127.0.0.1:1671 ESTABLISHED
TCP 127.0.0.1:1673 127.0.0.1:1674 ESTABLISHED
TCP 127.0.0.1:1674 127.0.0.1:1673 ESTABLISHED
TCP 127.0.0.1:1675 127.0.0.1:1676 ESTABLISHED
TCP 127.0.0.1:1676 127.0.0.1:1675 ESTABLISHED
TCP 127.0.0.1:19989 0.0.0.0:0 LISTENING
TCP 192.168.1.101:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING 0
TCP [::]:1025 [::]:0 LISTENING 0
TCP [::]:1429 [::]:0 LISTENING 0
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1436 *:*
UDP 0.0.0.0:1640 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.101:123 *:*
UDP 192.168.1.101:137 *:*
UDP 192.168.1.101:138 *:*
UDP 192.168.1.101:1900 *:*
UDP 192.168.1.101:31995 *:*
fport at CLI156 error
FPort v2.0 - TCP/IP Process to Port Mapper
Copyright 2000 by Foundstone, Inc.
http://www.foundstone.com
Pid Process Port Proto Path
1264 inetinfo -> 25 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 135 TCP
4 System -> 139 TCP
4 System -> 445 TCP
1684 LEXPPS -> 1025 TCP C:\WINDOWS\system32\LEXPPS.EXE
1264 inetinfo -> 1429 TCP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 1435 TCP
3960 appserv -> 1664 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1669 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1670 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1671 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1672 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1673 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1674 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1675 TCP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 1676 TCP C:\Sun\AppServer\lib\appserv.exe
524 CFSServ -> 19989 TCP C:\Program Files\TOSHIBA\ConfigFree\CFSServ
.exe
3960 appserv -> 123 UDP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 137 UDP C:\Sun\AppServer\lib\appserv.exe
3960 appserv -> 138 UDP C:\Sun\AppServer\lib\appserv.exe
1264 inetinfo -> 445 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
1104 -> 500 UDP
4 System -> 1436 UDP
1684 LEXPPS -> 1640 UDP C:\WINDOWS\system32\LEXPPS.EXE
3960 appserv -> 1900 UDP C:\Sun\AppServer\lib\appserv.exe
1264 inetinfo -> 3456 UDP C:\WINDOWS\system32\inetsrv\inetinfo.exe
2768 -> 4500 UDP
3960 appserv -> 21498 UDP C:\Sun\AppServer\lib\appserv.exe
contnets of server.log
[#|2005-10-02T08:31:05.873-0700|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|
_ThreadID=10;|
C:/Sun/jdk1.5.0_02\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/jdk1.5.0_02/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanSe
rverBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serve
rbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactor
yImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentB
uilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.Transf
ormerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.
bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\jdk1.5.0_02\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\
lib;C:\Sun\jdk1.5.0_02\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppS
erver\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bi
n;C:\Sun\AppServer\bin;C:\Sun\jdk1.5.0_02\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\syst
em32\WBEM;C:\Sun\AppServer\bin;xDefaultS-1-x�
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/jdk1.5.0_02/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\ac
tivation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Su
n/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\ap
pserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launche
r.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer
/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/Ap
pServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.
jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer
/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.j
ar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/l
ib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/Ap
pServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:
/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api
.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppS
erver/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
set path
Path=C:\Sun\AppServer\bin;C:\Sun\jdk1.5.0_02\bin;C:\WINDOWS\system32;C:\WINDOWS;
C:\WINDOWS\system32\WBEM;C:\Sun\AppServer\bin;xDefaultS-1-x☺^
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
set J2EE_HOME
J2EE_HOME=C:\Sun\AppServer
set JAVA_HOME
JAVA_HOME=C:\sun\jdk1.5.0_02\bin
set include
INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\
pertinent ports from domain.xml
id="http-listener-1" address="0.0.0.0" port="8080" id="http-listener-2"
address="0.0.0.0" port="8181"
id="admin-listener" address="0.0.0.0" port="4848"
id="orb-listener-1" address="0.0.0.0" port="3700"
id="SSL" address="0.0.0.0" port="3820"
id="SSL_MUTUALAUTH" address="0.0.0.0" port="3920"
<jmx-connector accept-all="false" address="0.0.0.0" auth-realm-name="admin-realm"
enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false"/>
<jms-host name="default_JMS_host" host="FE" port="7676" admin-user-name="admin"
admin-password="admin"/>
<property name="DatabaseName"
value="jdbc:pointbase:server://localhost:9092/sun-appserv-samples"/>
contents of domain.xml
<?xml version="1.0" encoding="UTF-8" ?>


<!DOCTYPE domain PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 8.0 Domain//EN"
"http://www.sun.com/software/appserver/dtds/sun-domain_1_1.dtd">
<domain application-root="${com.sun.aas.instanceRoot}/applications"
log-root="${com.sun.aas.instanceRoot}/logs">
<applications>
<web-module name="adminapp" context-root="/web1"
location="${com.sun.aas.install

When I set it to false, the the server log no longer gets to display native!#]
when it the hangs.
I finally gave up the ghost, bought a 160G drive, installed it into my desktop, installed Fedora Linux and have not had a problem. Life would be much better if I could get it running on the laptop. My gut tells me that something is wrong with either JAVA_HOME or J2EE_HOME, but I cannot see it.

Server CPU Usages - Critical

We have a BC4J application developed using jdev 3.1/ front end is JSPs.
The application is deployed using Oracle iAS 8i.
The problem is that when in a jsp, a query is executed that has to return a large number of rows, then the cpu utilization of the database(oracle.exe) rises to 100 percent. The same query when run from sql, causes a memory consumption of only 20 percent.
What can be the possible reasons for this huge increase in memory consumption when the query is fired using jdev data web beans from a jsp.
amit

Howard,
because the CSS has a script language, you can basically do whatever you want.
You could have a script running on the server to get the server cpu and save it into a file.
Via the CSS script language, you could retrieve this value and decided to use or not the server.
There is also something called DFP - dynamic feedback protocol. If your server vendor support this protocol you can use it to report server status to the CSS.
Regards,
Gilles.

Report Times Out only on Dialog Application Server

Hi -
We are on ECC 6. We have a Central Instance and a Dialog Instance (both on AIX 5.3). When the endusers run S_ALR_87009788 (program RFRRBIL1), which can not be run as a background job, on the Central Instance it runs to completion in about 10 minutes. When they run the same report, with the same variant, on the Dialog Instance it times out in the SAPLGSAC program within the Include program LGSACF01.
I've checked and rechecked parameters on both servers and they match. CPU, memory and swap match as well.
To add to this, the report runs in 2 minutes on our ECQ system.
What else should I look at?
Thanks!
Margaret

> No, we do not have dedicated high-speed network connections between the application servers and the database server.
This explains why you can execute the program on the database server directly but not on the application server.
Most likely you have a 100 MBit connection, all other traffic is also going through that interface. So the application server must read all data from the database server, transfer it over the network to the application server and from there it has to be transmitted again to the client.
It's highly advised to not use the normal network interface for communication between app server and database but a dedicated network infrastructure to keep latencies low and to allow almost the same speed.
Markus

Sun Application Server - Trouble starting default server

Hi everyone.
I am new to J2EE and am currently trying to get the Sun Appliation Server to run, but am having difficulties.
I have installed version 1.4 of J2EE SDK.
Running Windows XP SP2.
When I run the program Start Default Server, it hangs for ages on the message "Starting Domain1, please wait" and finally after about a minute or so gives me an error message stating:
"Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1."
I have been told that it is very common to get problems with the port you choose for the JMS to be the same as somehting else on your PC. I have experimented with different port numbers (all of which not in current use - as indiated by netstat -a in the cmd window).
If anyone knows anything else I could try that would be great and much appreciated.
Cheers
Phill
Below is a listing of my server.log file...
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-11-22T21:11:05.125+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-11-22T21:11:07.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-11-22T21:11:08.140+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-11-22T21:11:14.484+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-11-22T21:11:14.500+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-11-22T21:11:14.546+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-11-22T21:11:20.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-11-22T21:11:23.687+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-11-22T21:11:24.453+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-11-22T21:11:25.515+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-11-22T21:11:26.671+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-11-22T21:11:27.859+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-11-22T21:11:27.859+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-11-22T21:11:27.968+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-11-22T21:11:28.312+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-11-22T21:11:28.656+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-11-22T21:11:28.656+0000|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-11-22T21:11:28.656+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-11-22T21:11:28.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-11-22T21:11:28.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-11-22T21:11:28.796+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-11-22T21:11:33.031+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-11-22T21:11:34.796+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-22T21:11:34.828+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-22T21:11:34.984+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-22T21:11:34.984+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-22T21:11:35.015+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-22T21:11:35.015+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
[#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2004-11-22T21:12:36.578+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
     at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
     at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
     at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
     at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
     ... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
     ... 25 more
|#]
[#|2004-11-22T21:12:36.578+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2004-11-22T21:12:36.578+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2004-11-22T21:12:36.593+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2004-11-22T21:12:36.593+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 8080 java.net.ConnectException: Connection refused: connect|#]
[#|2004-11-22T21:12:36.671+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2004-11-22T21:12:36.687+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 1043 java.net.ConnectException: Connection refused: connect|#]
[#|2004-11-22T21:12:36.765+0000|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2004-11-22T21:12:36.781+0000|SEVERE|sun-appserver-pe8.0.0_01|org.apache.tomcat.util.net.PoolTcpEndpoint|_ThreadID=10;|Caught exception trying to unlock accept on 4848 java.net.ConnectException: Connection refused: connect|#]
[#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2004/11/22 21:12:36]|#]
[#|2004-11-22T21:12:36.953+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2004-11-22T21:12:36.953+0000|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7678]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-11-22T21:12:36.984+0000|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

OK, here is the contents of log.txt from the imqbroker\log directory...
Tell me if you have a hard time decifering which date of this log corresponds to the date of the first log and I will clear both files and recreate it.
Thanks very much for your help, I am sure we will crack it!
Thanks again
Phill
# 1101144571937 Do not modify this line
[22/Nov/2004:17:29:31 GMT] [B1002]: An existing property file for imqbroker was not found, no stored properties will be loaded
[22/Nov/2004:17:29:31 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:17:29:32 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:17:29:32 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:17:29:32 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:17:29:32 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:17:29:32 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:17:29:32 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
[22/Nov/2004:17:29:32 GMT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2004:17:29:32 GMT] [B1060]: Loading persistent data...
[22/Nov/2004:17:29:32 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[22/Nov/2004:17:29:33 GMT] [B1136]: Processing stored transactions
[22/Nov/2004:17:29:33 GMT] [B1013]: Auto Creation of Queues is Enabled
[22/Nov/2004:17:29:33 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[22/Nov/2004:17:29:33 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[22/Nov/2004:17:29:33 GMT] [B1039]: Broker "imqbroker@mono:7676" ready.
[22/Nov/2004:17:40:21 GMT] [B1047]: Shutting down broker...
[22/Nov/2004:17:40:21 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:17:40:21 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:17:40:21 GMT] [B1077]: Broadcast good-bye to all connections ...
[22/Nov/2004:17:40:21 GMT] [B1078]: Flushing good-bye messages ...
[22/Nov/2004:17:40:21 GMT] [B1063]: Done
[22/Nov/2004:17:40:21 GMT] [B1048]: Shutdown of broker complete.
jre
[22/Nov/2004:17:32:07 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:17:32:07 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:17:32:07 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:17:32:07 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:17:32:07 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:17:32:07 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
[22/Nov/2004:17:32:07 GMT] ERROR Could not start the Broker's portmapper service on port 7676.
This port is already in use by another application -- possibly another
instance of the Broker. Please quit that other application, or use a
different port number for this instance of the Broker.
[22/Nov/2004:17:42:31 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:17:42:31 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:17:42:31 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:17:42:31 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:17:42:31 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:17:42:31 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:17:42:31 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
[22/Nov/2004:17:42:31 GMT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2004:17:42:31 GMT] [B1060]: Loading persistent data...
[22/Nov/2004:17:42:31 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[22/Nov/2004:17:42:32 GMT] [B1136]: Processing stored transactions
[22/Nov/2004:17:42:32 GMT] [B1013]: Auto Creation of Queues is Enabled
[22/Nov/2004:17:42:32 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[22/Nov/2004:17:42:32 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[22/Nov/2004:17:42:32 GMT] [B1039]: Broker "imqbroker@mono:7676" ready.
[22/Nov/2004:19:26:20 GMT] [B1047]: Shutting down broker...
[22/Nov/2004:19:26:20 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:19:26:20 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:19:26:20 GMT] [B1077]: Broadcast good-bye to all connections ...
[22/Nov/2004:19:26:20 GMT] [B1078]: Flushing good-bye messages ...
[22/Nov/2004:19:26:20 GMT] [B1063]: Done
[22/Nov/2004:19:26:20 GMT] [B1048]: Shutdown of broker complete.
jre
[22/Nov/2004:19:12:30 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:19:12:30 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:19:12:30 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:19:12:30 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:19:12:30 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:19:12:30 GMT] Arguments: -name imqbroker -port 7676 -bgnd -silent
[22/Nov/2004:19:12:30 GMT] ERROR Could not start the Broker's portmapper service on port 7676.
This port is already in use by another application -- possibly another
instance of the Broker. Please quit that other application, or use a
different port number for this instance of the Broker.
[22/Nov/2004:19:15:43 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:19:15:43 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:19:15:43 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:19:15:43 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:19:15:43 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:19:15:43 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:19:15:43 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[22/Nov/2004:19:15:43 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2004:19:15:43 GMT] [B1060]: Loading persistent data...
[22/Nov/2004:19:15:43 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[22/Nov/2004:19:15:43 GMT] [B1136]: Processing stored transactions
[22/Nov/2004:19:15:43 GMT] [B1013]: Auto Creation of Queues is Enabled
[22/Nov/2004:19:15:44 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[22/Nov/2004:19:15:44 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[22/Nov/2004:19:15:44 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
[22/Nov/2004:19:26:21 GMT] [B1047]: Shutting down broker...
[22/Nov/2004:19:26:21 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:19:26:21 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:19:26:21 GMT] [B1077]: Broadcast good-bye to all connections ...
[22/Nov/2004:19:26:21 GMT] [B1078]: Flushing good-bye messages ...
[22/Nov/2004:19:26:21 GMT] [B1063]: Done
[22/Nov/2004:19:26:21 GMT] [B1048]: Shutdown of broker complete.
jre
[22/Nov/2004:19:20:56 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:19:20:56 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:19:20:56 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:19:20:56 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:19:20:56 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:19:20:56 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[22/Nov/2004:19:20:56 GMT] ERROR Could not start the Broker's portmapper service on port 7678.
This port is already in use by another application -- possibly another
instance of the Broker. Please quit that other application, or use a
different port number for this instance of the Broker.
[22/Nov/2004:19:21:14 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:19:21:14 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:19:21:15 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:19:21:15 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:19:21:15 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:19:21:15 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:19:21:15 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[22/Nov/2004:19:21:15 GMT] ERROR Could not start the Broker's portmapper service on port 7678.
This port is already in use by another application -- possibly another
instance of the Broker. Please quit that other application, or use a
different port number for this instance of the Broker.
[22/Nov/2004:21:11:12 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:21:11:12 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:21:11:13 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:21:11:13 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:21:11:13 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:21:11:13 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:21:11:13 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[22/Nov/2004:21:11:13 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2004:21:11:13 GMT] [B1060]: Loading persistent data...
[22/Nov/2004:21:11:13 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[22/Nov/2004:21:11:14 GMT] [B1136]: Processing stored transactions
[22/Nov/2004:21:11:14 GMT] [B1013]: Auto Creation of Queues is Enabled
[22/Nov/2004:21:11:14 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[22/Nov/2004:21:11:14 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[22/Nov/2004:21:11:14 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
[22/Nov/2004:21:24:10 GMT] [B1047]: Shutting down broker...
[22/Nov/2004:21:24:10 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:21:24:10 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:21:24:10 GMT] [B1077]: Broadcast good-bye to all connections ...
[22/Nov/2004:21:24:10 GMT] [B1078]: Flushing good-bye messages ...
[22/Nov/2004:21:24:11 GMT] [B1063]: Done
[22/Nov/2004:21:24:11 GMT] [B1048]: Shutdown of broker complete.
[22/Nov/2004:23:47:09 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[22/Nov/2004:23:47:09 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[22/Nov/2004:23:47:09 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[22/Nov/2004:23:47:09 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[22/Nov/2004:23:47:09 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[22/Nov/2004:23:47:09 GMT] Java Heap Size: max=194432k, current=16256k
[22/Nov/2004:23:47:09 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[22/Nov/2004:23:47:10 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
[22/Nov/2004:23:47:10 GMT] [B1060]: Loading persistent data...
[22/Nov/2004:23:47:10 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[22/Nov/2004:23:47:10 GMT] [B1136]: Processing stored transactions
[22/Nov/2004:23:47:10 GMT] [B1013]: Auto Creation of Queues is Enabled
[22/Nov/2004:23:47:10 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[22/Nov/2004:23:47:11 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[22/Nov/2004:23:47:11 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.
[22/Nov/2004:23:56:18 GMT] [B1047]: Shutting down broker...
[22/Nov/2004:23:56:18 GMT] [B1007]: Stopping Service admin with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:23:56:18 GMT] [B1007]: Stopping Service jms with protocol tcp(host = *, port=0, mode=dedicated)
[22/Nov/2004:23:56:18 GMT] [B1077]: Broadcast good-bye to all connections ...
[22/Nov/2004:23:56:18 GMT] [B1078]: Flushing good-bye messages ...
[22/Nov/2004:23:56:18 GMT] [B1063]: Done
[22/Nov/2004:23:56:18 GMT] [B1048]: Shutdown of broker complete.
[23/Nov/2004:00:19:36 GMT]
================================================================================
Sun Java(tm) System Message Queue
Sun Microsystems, Inc.
Version: 3.5 SP1 (Build 48-G)
Compile: Thu 01/29/2004
Copyright � 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.4.2_04 Sun Microsystems Inc. C:\Sun\AppServer\jdk\jre
[23/Nov/2004:00:19:36 GMT] License: Sun Java(tm) System Message Queue 3.5 SP1 PE License.
[23/Nov/2004:00:19:36 GMT] IMQ_HOME=C:\Sun\AppServer\imq
[23/Nov/2004:00:19:36 GMT] IMQ_VARHOME=C:\Sun\AppServer\domains\domain1\imq
[23/Nov/2004:00:19:36 GMT] Windows XP 5.1 x86 mono (1 cpu) phill
[23/Nov/2004:00:19:36 GMT] Java Heap Size: max=194432k, current=16256k
[23/Nov/2004:00:19:36 GMT] Arguments: -name imqbroker -port 7678 -bgnd -silent
[23/Nov/2004:00:19:36 GMT] [B1004]: Starting the portmapper service using tcp [ 7678, 50, * ] with min threads 1 and max threads of 1
[23/Nov/2004:00:19:36 GMT] [B1060]: Loading persistent data...
[23/Nov/2004:00:19:36 GMT] Using built-in file-based persistent store: C:\Sun\AppServer\domains\domain1\imq\instances\imqbroker\
[23/Nov/2004:00:19:37 GMT] [B1136]: Processing stored transactions
[23/Nov/2004:00:19:37 GMT] [B1013]: Auto Creation of Queues is Enabled
[23/Nov/2004:00:19:37 GMT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[23/Nov/2004:00:19:37 GMT] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[23/Nov/2004:00:19:37 GMT] [B1039]: Broker "imqbroker@mono:7678" ready.

Eclipse/Sun Java Application Server

Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     ... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     ... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     ... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
     ... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#]

Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     ... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
     at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
     at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
     at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
     ... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
     ... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
     at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
     at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
     ... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
     ... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#]

Running concurrent Application Server in same processor

Has anyone done any benchmark testing with running multiple concurrent application server?
I need to run 70 Application Servers 10g on the same processors and I need to know if there are any limitations or any best practices?
Any suggestions or recommendations will be greatly appreciated.
I have the following requirements:
Hardware:
RAM
64 GB
CPU and cores and CPU speed.
C8 Core 1.2GHz UltraSPARC T2 processor
HD capacity
2x146GB SAS
Server Name or type
SUN Enterprise T5220
5. Network:
Network Speed
5 Containers will share bandwidth of one Gigabit Ethernet NIC, giving theoretical bandwidth of 200Mb/s to each container on average
Network Card and Network Drivers
Internal Network Interfaces - Type: 10/100/1000; Quantity: 4
External Network Interfaces - Type: x8 PCI express Quad Gigabit Ethernet UTP low profile adapter; Quantity: 4
Software Stack:
OS version and OS type
Sun Solaris 10 US

Thanks for you response.
For the purpose of our discussion here is what we are looking at:
There is going to be only a single machine a T5220 Sun Server loaded with Solaris 10.
1. This single machine will hold 70 concurrent applications server 10g.
2. Each application servers will have its own dedicated Oracle database in a seperate server.
Should this architecture hold?

During consolidation cpu goes 100%

Hi,
During consolidation CPU is going 100%.
can you suggest me some performance tuning tips to improve the performance.
HFM 9.3.1.2 Build.

If you are concerned about the processor utilization AND you cannot simply upgrade your hardware AND consolidation time is not an issue for you, then the following registry changes may be for you :
Key Tree,     Key Name,     Key Type,     Min Value,     Max Value,     Default Value,     Unit of Measure,     Description
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server\Running Tasks,     MaxNumConcurrentConsolidations,     REG_SZ,     1,     8,          Consolidations,     Controls the nubmer of concurrent consolidations allowed per application server. Any consolidations executed above the value are queued as Scheduled Consolidations.
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server\Running Tasks,     NumConsolidationThreads,     REG_SZ,     1,     8,          Threads,     Controsl the multi-threading of consolidatiosn per application server. Lowering the value limits the system's utilization of system resources, resulting in slower consolidation performance.
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server\Running Tasks,     NumConsolidationsAllowed,     REG_SZ,     1,     20,     8,     Consolidations,     Controls the number of conslidations allower per application across all the application servers.
Edited by: beyerch on Feb 17, 2009 1:22 PM

Additional Application Server

Hello All!
I'd like to open a new discussion about adding a new application server to enhance the performance of my production system.
At the implementation, we had only two company codes, but nowadays we have added a new business unit in our SAP system as a new company code. This caused an increase of response time only at closing period (about the 2nd to 3rd business day for CO users) and casually at another time.
This is causing an increase of response time from 600-700ms to 2100ms at the more critical period of day, and consequently dissatisfaction from all users.
On July, we're implementing a new business unit, a new company code, then, a new CO closing procedures. I think it will increase more the response time.
What are your opinion about this case? May I really think about installing an application server to provide more CPU power, even for a short period of the month?
All opinion are very important for me! Thanks in advance for all help!
Best Regards,
André Koji Honma
Support Analyst

Hi André,
if your CPU is often 100%, you have to do something !
There is a very interesting part in WRKSYSSTS - the DB-capacity !
How high is that while the CPU is at 95%+ ?
If this is low, the appl server will help, if not, the SQL is the issue as you are in fear of ...
Why is the DB-time high, even when an appl server might help ?
The db time ALWAYS becomes high, when the CPU is at 100%, because then it just takes long to process each statement ...
But, as said above, it could even be, that the resources are eaten by SQL ...
=> we need the following figure (not on a second base, but several minutes:
WRKSYSSTS:
% CPU benutzt . . . . . :       41,3
% DB-Kapazität . . . . . :        4,8
Abgelaufene Zeit . . . . :   00:13:57
How is this on your site typically, when you do have the issues ?
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

Install Oracle Application Server on same as database server

How to Install Oracle Application Server.
Can I install on the same server as database server
Can some body provide a simple tutorial for Windows Installation.
Ss

If there is no licensing issues - then I could advice SOA Suite installation - there should be AS as well and many other features (BPEL e.g.). Personally I cann't see any need for installation manual as all the installation and configuration assistance poceeds automatically. Documentation can be found http://www.oracle.com/technology/documentation/appserver.html - usually zip contains large library of pdf, installation manual including.
Well - my problem is that I have installed partially SOA Suite (configuration assistants failed at web services) on machine without DB server, then I installed DB server and now I am trying to deinstall SOA Suite - but now for some days machine shows 100% CPU consumption and no any visible actions (no new errors as well)... What should I do? Kill the process and try to manually remove SOA? I plan after make another SOA installation after removal of this one.
Thanks in someone can help me!

Application Server CPU at 100%

Similar Messages

Maybe you are looking for