Error trying to debug in workshop

I am using 8.1 SP4 on Windows XP Pro in Development mode
When I start debugging my web service in workshop, I get an error that says: Unable to enable debugging. Verify that your webapp deployed correctly.
I did verify that the web service is deployed, and I am able to send messages to it. I am using the stopweblogic.cmd script to stop my instance.

Any ideas?

Solution 1
%userprofile%\Local Settings\Application Data\Adobe folder does not exist
Solution 2
Already tried this
Solution 3
Tried disabling antivirus

Similar Messages

Error while trying to debug on windows mobile 6.1 with j2me SDK 3.0 ea

Hi,
I tried to debug a simple application today. It works fine with the emulator but debug fails to connect to the device.
I followed the steps described in the userguide of 3.0.
host operating system: windows xp sp3
device: htc touch pro
device operatiing system: windows mobile 6.1 professional
The device is listed in the device selector of the SDK as Touch_Pro
The device is connected and active sync is running (i can explore the phone using windows explorer)
sun-java-cldc-emu.cab has been installed on the device and is running
When i try to debug the application from the SDK or netbeans 6.5(added 3.0ea as a platform) i get the following error:
Starting emulator with port number 51307
Cannot create device connection: Failed to connect to device 9!
Result: 1
I tried setting the loglevel to DEBUG in log4j config of the SDK, but thats it.
Are there any other settings i can change to get more detailed output?
Where do you report bugs/feedback for j2me SDK 3.0 ea?
regards,
dominikg
Edited by: dominikg on Dec 11, 2008 8:36 AM
-- changed topic title to 'error' instead of 'howto'
-- added more specific questions

Hi dominikg,
At first, You can try to restart the device-manager from system tray.
If it doesn't help, then try the following:
- stop the device manager
- Remove c:\Docement and Settings\<your User>\javame-sdk folder.
- Ran the device manager from <SDK>/bin directory
- try to debug again.
Did you tried to change port 51307 to another.
Early access build had some problems with device manager, I hope that final release will be better :)
BR,
Igor

Error line 68 in DBMS_DEBUG_JDWP when trying to debug from behind firewall

Hello!
I am using sqldeveloper on a windows client, connecting to an Oracle 10.1.0.4 database on AIX 5.3 behind our internal firewall. No sweat, I have an sql*net "hole" through the firewall to the database listener.
But when trying to debug a PL/SQL procedure, the debugging session cannot start but gets the following errors:
ORA-30683: failure establishing connection to debugger
ORA-12535: The requested operation could not be completed within the time out period.
The cause is readily seen in one of sqldeveloper's own windows, namely that the procedure call
CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '192.168.205.143', '1290' )
fails. Our internal firewall quite rightly doesn't allow a connection from "any port" on the database server to "any port" on my PC.
Is there any workaround for this issue, short of trying to get my security officer to open up so that "any port" on the database server can connect to "any port" on my windows client? I can change "debug preferences" in sqldeveloper to point to only one port on my windows client, but since I cannot control what port on the server the DBMS_DEBUG_JDWP.CONNECT_TCP procedure chooses when it tries to connect to my client, that is only a halfway solution as I see it.
Cheers from snow-white Denmark,
Hans Henrik Krohn

Wrong install Disc, that one is machine specific, & doubtful a reinstall will help all that much.
More RAM will likely help, but not awfully likely it'll be 50%.
To tell, ehen it gets slow, Open Activity Monitor, Show:>All Processes, sort on CPU%, see if anything using too much CPU% when this happens, click on Memory tab, do you have many Pageouts?

Signal ILL trying to debug java process with dbx

Hello,
I'm trying to debug a java process to find an error in JNI code. I get this message when dbx stops in a C breakpoint:
t@18 (l@19) signal ILL (illegal trap) in (unknown) t@18 (l@19) signal ILL (illegal trap) in (unknown) at 0xf848ed28
0xf848ed28:     tne     0x12This signal is not launched when running application without debugger, and after launching this exception and exiting dbx, the java process generates a core.
I've tried to find out unsuccessfully whether my dbx version is compatible with my Java version, but it seems this could be the problem.
This is my current configuration:
java �version:
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
opt/SUNWspro/bin/version:
Machine hardware:   sun4u
OS version:         5.8
Processor type:     sparc
Hardware:           SUNW,Sun-Blade-2500
The following components are installed on your system:
Forte C++ 6 update 2
        Sun WorkShop 6 update 2 Compilers C
        Sun WorkShop 6 update 2 Compilers C++
        Sun WorkShop 6 update 2 Tools.h++ 7.1
        Sun WorkShop 6 update 2 Standard 64-bit Class Library for C++
        Sun WorkShop 6 update 2 Memory Monitor for C++
        Sun WorkShop 6 update 2 Visual
        Sun WorkShop 6 update 2 Development Environment
        Sun WorkShop 6 update 2 TeamWare
        Sun WorkShop 6 update 2 FileMerge
        Sun WorkShop 6 update 2 DBX Debugging Tools
        Sun WorkShop 6 update 2 Performance Analyzer
        Sun WorkShop 6 update 2 LockLint
        XEmacs 20.4 Source Distribution
        Sun WorkShop 6 update 2 Documentation Set
Sun WorkShop 6 update 2 Building SoftwareAnd this is how I launch java application:
java -Djava.compiler=NONE -Xdebug -Xnoagent -Xrundbx_agent -jar jarname.jar -mainOptionsDid I miss something important? Does anyone know if it is possible debugging with this configuration?
Best Regards,
Alberto

- Native code has been compiled with -g option.
- It fails in my code, but only when debugging.
- Stack trace (executing "where" in dbx):
(dbx) where
current thread: t@18
[1] 0xf848ef68(0xf01537d8, 0xf443b7b0, 0x0, 0xf84181b0, 0x21e9, 0xef581050), at 0xf848ef68
[2] 0xf8458354(0xf15faea8, 0xf01537d8, 0xf0151a88, 0xf8419368, 0x21e8, 0x0), at 0xf8458354
[3] 0xf848c9a0(0xf15faea8, 0xf01537d8, 0xf0151a58, 0xf0151a38, 0xf0153830, 0x0), at 0xf848c9a0
[4] 0xf84577c8(0xf15faea8, 0xb6, 0x0, 0xf84181b0, 0xf0158f80, 0xef581118), at 0xf84577c8
[5] 0xf8405764(0xf15faea8, 0xb6, 0x0, 0xf8419320, 0xf0158f80, 0xef5811c8), at 0xf8405764
[6] 0xf8405764(0xf15faea8, 0xb6, 0x0, 0xf84195a0, 0xf0158f80, 0xef581250), at 0xf8405764
[7] 0xf8405764(0xf0151a38, 0xb8, 0x0, 0xf8419320, 0xf0125258, 0xef5812d8), at 0xf8405764
[8] 0xf8405874(0xf15fb6c8, 0xb8, 0x0, 0xf8419720, 0xf0125258, 0xef581360), at 0xf8405874
[9] 0xf8405764(0xf15fae98, 0xb6, 0x0, 0xf8419770, 0xf00f0088, 0xef5813f0), at 0xf8405764
[10] 0xf8405874(0xf15fae98, 0xb6, 0x0, 0xf8419320, 0x1465, 0xef581478), at 0xf8405874
[11] 0xf8405874(0xf16315b0, 0xb6, 0x0, 0xf8419320, 0xf00f0088, 0xef581500), at 0xf8405874
[12] 0xf8405764(0xf16315b0, 0xf45744c0, 0x0, 0xf8419320, 0xf45744c0, 0xef581588), at 0xf8405764
[13] 0xf8405c2c(0xf16315d0, 0xb7, 0x0, 0xf84198a0, 0xf00f0088, 0xef581618), at 0xf8405c2c
[14] 0xf8405764(0xf009c018, 0xf402c8b8, 0x0, 0xf84195a0, 0x8800, 0xef5816a8), at 0xf8405764
[15] 0xf8405c2c(0x2000, 0x2, 0x0, 0xf84198f0, 0xef50e0f8, 0xef581720), at 0xf8405c2c
[16] 0xf8400218(0xef581808, 0xef581a08, 0xa, 0xf402dae8, 0xf840ba20, 0xef581920), at 0xf8400218
[17] JavaCalls::call_helper(0x1, 0x65d188, 0xef581918, 0xef581818, 0x4, 0xef581a08), at 0xfdd9a808
[18] JavaCalls::call_virtual(0x7a9c, 0x65d188, 0x3570f8, 0x357104, 0x357100, 0xf00bc770), at 0xfdec319c
[19] thread_entry(0xf402fc58, 0x65d188, 0x3574e4, 0xfe424640, 0xfe424710, 0xfe424130), at 0xfdee2700
[20] JavaThread::run(0x65d188, 0x18, 0xfe40c790, 0x6c00, 0x7dd4, 0x7c00), at 0xfdede29c
[21] _start(0x65d188, 0x3b62, 0xfe3be000, 0x0, 0x4f24, 0x4c00), at 0xfe264240 - Stack trace (obtained from core generated after ILL signal):
----------------- lwp# 19 / thread# 18 --------------------
ff3791f0 __sigprocmask (ff37b7f4, 0, 0, ef581d98, ff38c000, 0) + 8
ff36dd0c _sigon   (ef581d98, ff3938a8, 6, ef58083c, ef581d98, ff39321c) + d0
ff370d4c _thrp_kill (0, 12, 6, ff38c000, 12, ff2c0458) + f8
ff24bce0 raise    (6, 0, 0, ffffffff, ff2c03c4, 8400) + 40
ff235984 abort    (ff2bc008, fe3be000, fe26a8e0, fe4133c4, 0, 331c8) + 100
fe264724 __1cCosFabort6Fi_v_ (1, 0, fe3f2614, fe3be000, 73b4, 7000) + 58
fe2f08f0 __1cHVMErrorOreport_and_die6M_v_ (0, fe419ad8, fe41339c, 1, fe268a14, fe41339c) + c84
fde76878 JVM_handle_solaris_signal (4, ef580fd8, ef580d20, 7800, 11, 65d188) + aac
ff37b118 __sighndlr (4, ef580fd8, ef580d20, fde75d94, ef581e40, ef581e30) + c
ff37811c sigacthandler (4, ef581d98, 0, 0, 0, ff38c000) + 708
--- called from signal handler with signal 4 (SIGILL) ---
f848ef68 ???????? (f15faea8, f01537d8, f0151a88, f8419368, 21e8, 0)
f848c9a0 ???????? (f15faea8, f01537d8, f0151a58, f0151a38, f0153830, 0)
f84577c8 ???????? (f15faea8, b6, 0, f84181b0, f0158f80, ef581118)
f8405764 ???????? (f15faea8, b6, 0, f8419320, f0158f80, ef5811c8)
f8405764 ???????? (f15faea8, b6, 0, f84195a0, f0158f80, ef581250)
f8405764 ???????? (f0151a38, b8, 0, f8419320, f0125258, ef5812d8)
f8405874 ???????? (f15fb6c8, b8, 0, f8419720, f0125258, ef581360)
f8405764 ???????? (f15fae98, b6, 0, f8419770, f00f0088, ef5813f0)
f8405874 ???????? (f15fae98, b6, 0, f8419320, 1465, ef581478)
f8405874 ???????? (f16315b0, b6, 0, f8419320, f00f0088, ef581500)
f8405764 ???????? (f16315b0, f45744c0, 0, f8419320, f45744c0, ef581588)
f8405c2c ???????? (f16315d0, b7, 0, f84198a0, f00f0088, ef581618)
f8405764 ???????? (f009c018, f402c8b8, 0, f84195a0, 8800, ef5816a8)
f8405c2c ???????? (2000, 2, 0, f84198f0, ef50e0f8, ef581720)
f8400218 ???????? (ef581808, ef581a08, a, f402dae8, f840ba20, ef581920)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 65d188, ef581918, ef581818, 4, ef581a08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 65d188, 3570f8, 357104, 357100, f00bc770) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 65d188, 3574e4, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (65d188, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (65d188, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (65d188, 0, 0, 0, 0, 0) + 40
----------------- lwp# 20 / thread# 19 --------------------
ff29f474 _lwp_sema_wait (ff3934c8, ff392e40, 0, 1, 0, 0) + c
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 21 --------------------------------
ff379200 private___lwp_cond_wait (fa5a3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa5a3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 22 --------------------------------
ff379200 private___lwp_cond_wait (fa4d3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa4d3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 23 --------------------------------
ff379200 private___lwp_cond_wait (fa4c3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa4c3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 24 --------------------------------
ff379200 private___lwp_cond_wait (fa493d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa493d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 25 --------------------------------
ff379200 private___lwp_cond_wait (fa483d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa483d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 26 --------------------------------
ff379200 private___lwp_cond_wait (fa473d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa473d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 1 / thread# 1 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, 18e, 37020, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (1c08, fe406e44, 37020, fe412d84, 38680, fe3be000) + 260
f840e22c ???????? (b9, ffbee73c, ffbee6b8, ffffff80, 0, 0)
f840e1d0 ???????? (0, b8, 0, 8, f402fc58, ffbee6d0)
f8405764 ???????? (f15996c8, fe4163d4, 0, f8419770, 8800, ffbee768)
f8405764 ???????? (f01778f8, fe4163d4, 0, f8419370, 8800, ffbee820)
f8405764 ???????? (2000, 2, 0, f8419320, ffb7c110, ffbee8b8)
f8400218 ???????? (ffbee9a0, ffbeeb00, a, f41c4038, f840ba20, ffbeea88)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 37020, ffbeea80, ffbee9b0, 4, ffbeeb00) + 5a0
fdedea14 jni_CallStaticVoidMethod (fe412d84, 381ec, 36750, 37020, 36748, 37cb8) + 500
000121fc main     (38648, 1e7fa2, fe40a630, 1d8, fded413c, 1) + 115c
00011088 _start   (0, 0, 0, 0, 0, 0) + 108
----------------- lwp# 2 / thread# 2 --------------------
ff29edc4 _signotifywait (ff38c000, 0, 0, 0, 0, 0) + 8
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 3 --------------------------------
ff379200 private___lwp_cond_wait (ff325d98, ff38cd6c, ff38c000, 0, 0, 4) + 8
ff29c9c0 _door_return (ff325cd8, ff36a358, 0, 0, 0, 0) + 68
----------------- lwp# 4 / thread# 4 --------------------
ff29f428 ___lwp_cond_wait (35d68, 35d50, fdb81978, 0, 0, fdb81970) + 8
ff296a7c _lwp_cond_timedwait (2958790, 44b36755, fdb81a50, 35d50, 35d68, a95a) + 98
fddc3258 __1cHMonitorEwait6Mil_i_ (35cf8, 11dce0, fff0bc00, fe3be000, 6000, 35d28) + 328
fdf6b4fc __1cIVMThreadDrun6M_v_ (fe4124d8, fe420c84, 0, fe420c70, fe420c80, 1) + 1b4
fe264240 __1cG_start6Fpv_0_ (11dce0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (11dce0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 5 --------------------------------
ff29c968 _door_return (4, ff38d658, ff38d670, 3, ff38c000, 1) + 10
ff36a358 _lwp_start (fe785d98, 0, 6000, ff325b9c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 6 / thread# 5 --------------------
ff29f428 ___lwp_cond_wait (120148, 120130, 0, ff2968f0, 0, 1) + 8
fdeb4768 __1cNObjectMonitorEwait6MxipnGThread__v_ (120370, 9408, 8c00, fe3be000, 11fdc0, 120390) + 59c
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (120372, 86d4, 0, 11fdc0, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, e7a14, 11fdc0, fe412d84, 0, 1) + 31c
f840e22c ???????? (51, fda816ec, fda81670, ffffff80, fdd2e808, 0)
f840e1d0 ???????? (f15817e0, b6, 0, c, 0, fda81688)
f8405764 ???????? (f15817e0, b6, 0, f8419354, 80000000, fda81708)
f8405764 ???????? (0, fe411508, 0, f8419770, 7bac, fda817a0)
f8400218 ???????? (fda81888, fda81a88, a, f40901d0, f840ba20, fda819a0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 11fdc0, fda81998, fda81898, 4, fda81a88) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 11fdc0, e7a00, e7a0c, e7a08, f0000760) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 11fdc0, e7dec, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (11fdc0, 0, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (11fdc0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (11fdc0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 7 / thread# 6 --------------------
ff29f428 ___lwp_cond_wait (121cc8, 121cb0, 0, ff2968f0, 0, 1) + 8
fdeb4768 __1cNObjectMonitorEwait6MxipnGThread__v_ (1203b8, 9408, 8c00, fe3be000, 121530, 1203d8) + 59c
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (1203ba, 86d4, 0, 121530, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, 121714, 121530, fe412d84, 0, 1) + 31c
f840e22c ???????? (59, fb3817ec, fb381768, ffffff80, 0, 0)
f840e1d0 ???????? (f1581760, b6, 0, c, 80000000, fb381780)
f8405764 ???????? (f1581768, b6, 0, f8419354, 8800, fb381820)
f8405874 ???????? (f1581768, b6, 0, f8419354, f402af58, fb3818a0)
f8405874 ???????? (0, fe411508, 0, f8419720, 7bac, fb381920)
f8400218 ???????? (fb381a08, fb381c08, a, f4090ab8, f840ba20, fb381b20)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 121530, fb381b18, fb381a18, 4, fb381c08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 121530, 121700, 12170c, 121708, f0000858) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 121530, 121aec, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (121530, 0, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (121530, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (121530, 0, 0, 0, 0, 0) + 40
----------------- lwp# 8 / thread# 7 --------------------
ff29f428 ___lwp_cond_wait (1b65f0, 1b65d8, fb281890, ff296918, ff29691c, fb281888) + 8
ff296a7c _lwp_cond_timedwait (2964ae0, 44b36756, fb281910, 1b65d8, 1b65f0, 153180) + 98
fe2606e0 __1cCosHSolarisFEventEpark6Mx_i_ (1b65b0, 6a60, fe4238d8, 1b65f0, fe406ef0, fb281910) + 1bc
fe25ff28 __1cNObjectMonitorIraw_wait6MxipnGThread__i_ (1b65b0, fe214b70, 7bac, 0, 1b59e8, 12a188) + 20c
fe1f4b8c __1cIJvmtiEnvORawMonitorWait6MpnPJvmtiRawMonitor_x_nKjvmtiError__ (fb2, 12a188, 0, 7d0, 4, 1b59e8) + a8
fe7d87ec process_next_event (fe40b864, 10000, fe7f24a0, fe7f4b90, fe7f25f0, fe7f25ec) + 108
fe7c7630 agent_bar (1b5aa4, fe7f2ae8, ff38c000, fe7f24c8, 0, 0) + 1c
fe7c7bc4 jvmti_debug_agent (fe7f2400, 1b5aa4, 0, 1678, 1, fe7f252c) + d4
fe211c74 __1cQJvmtiAgentThreadTcall_start_function6M_v_ (1b59e8, 7800, 8c94, fe3be000, fe4123c4, fe4163d4) + 150
fdede29c __1cKJavaThreadDrun6M_v_ (1b59e8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b59e8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b59e8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 9 / thread# 8 --------------------
ff29f474 _lwp_sema_wait (fb181e60, ff38c000, 0, fb181d98, 0, 0) + c
ff3690d8 _swtch   (fb181d98, ffffffff, ff38c000, 5, 1000, fe4170c4) + 158
ff36c860 sema_wait (fe4217e8, ff39785c, 5000, 10000, 534d, 1) + bc
fdf61dc0 __1cVcheck_pending_signals6Fi_i_ (1, fe4124d8, fe4123c0, 1b6ab8, fe3be000, a) + 254
fdf58ec8 __1cTsignal_thread_entry6FpnKJavaThread_pnGThread__v_ (7428, 1b6ab8, 1b7088, fe3be000, 4ff61c, 1b7080) + 34
fdede29c __1cKJavaThreadDrun6M_v_ (1b6ab8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b6ab8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b6ab8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 10 / thread# 9 --------------------
ff29f428 ___lwp_cond_wait (36548, 36530, fe423d60, 0, 0, ff29695c) + 8
fddc33ec __1cHMonitorEwait6Mil_i_ (364d8, 1b7998, 1b8510, fe3be000, 1b7998, 36508) + 4bc
fdf35d00 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b54c0, 1b7998, fe407360, 8c00, 364d8) + 22c
fdede29c __1cKJavaThreadDrun6M_v_ (1b7998, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b7998, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b7998, 0, 0, 0, 0, 0) + 40
----------------- lwp# 11 / thread# 10 --------------------
fdd0c200 __1cENodeSremove_dead_region6MpnIPhaseGVN_i_i_ (9132d4, fa6809f4, 1, 9132d4, 9132f4, 68ad00) + 2c
fdd3332c __1cHMemNodeMIdeal_common6MpnIPhaseGVN_i_pnENode__ (fa6809f4, fa6809f4, 1, 800, 9132d4, 9132f4) + 3c
fdd68a78 __1cJStoreNodeFIdeal6MpnIPhaseGVN_i_pnENode__ (9132d4, fa6809f4, 1, 0, fdd4be74, fe3fbb44) + c
fdcf887c __1cMPhaseIterGVNNtransform_old6MpnENode__2_ (fa6809f4, 9132d4, 89e938, fdd68a6c, 20000000, c7) + 28
fdde3b98 __1cMPhaseIterGVNIoptimize6M_v_ (fa6809f4, 14, 9132d4, 0, fa680b44, ffffffff) + ac
fde048d8 __1cOPhaseIdealLoop2t6MrnMPhaseIterGVN_pk0i_v_ (fa68087c, ffffffff, fa680fb0, 2, 0, fa680880) + c34
fde7fb28 __1cHCompileIOptimize6M_v_ (fa680fb0, 1b55b0, 0, 0, fe3be000, 1000) + 200
fde82740 __1cHCompile2t6MpnFciEnv_pnKC2Compiler_pnIciMethod_ii_v_ (fa680fb0, 0, 36ee0, 0, fe3384f8, fa680fb0) + be8
fde786f8 __1cKC2CompilerOcompile_method6MpnFciEnv_pnIciMethod_i_v_ (fa6818ac, fe324608, 9269b8, ffffffff, 36ee0, 1000001) + b0
fde793b4 __1cNCompileBrokerZinvoke_compiler_on_method6FpnLCompileTask__v_ (597690, 1b8eb4, 1b55b0, 1b88d8, fe338ea7, fa6818ac) + 4cc
fdf35f20 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b5550, 1b88d8, f4368380, 1b8eb0, 0) + 44c
fdede29c __1cKJavaThreadDrun6M_v_ (1b88d8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b88d8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b88d8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 12 / thread# 11 --------------------
ff29f428 ___lwp_cond_wait (365d8, 365c0, fe423d60, 0, 0, ff29695c) + 8
fddc33ec __1cHMonitorEwait6Mil_i_ (36568, 1b9818, 1ba390, fe3be000, 1b9818, 36598) + 4bc
fdf35d00 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b5550, 1b9818, fe407360, 1b9df0, 36568) + 22c
fdede29c __1cKJavaThreadDrun6M_v_ (1b9818, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b9818, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b9818, 0, 0, 0, 0, 0) + 40
----------------- lwp# 13 / thread# 12 --------------------
ff29f428 ___lwp_cond_wait (34858, 34840, 1, 0, 1, 1bb248) + 8
fddc309c __1cHMonitorEwait6Mil_i_ (347e8, 1bb1a0, fff0bc00, fe3be000, f4000, 34818) + 16c
fdf64b44 __1cRLowMemoryDetectorbGlow_memory_detector_thread_entry6FpnKJavaThread_pnGThread__v_ (1bb1a0, 347e8, 9000, fe411604, fe3be000, 1) + 2ec
fdede29c __1cKJavaThreadDrun6M_v_ (1bb1a0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1bb1a0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1bb1a0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 14 / thread# 13 --------------------
ff29d600 _poll    (fe4124d8, 32, 0, 0, 8400, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, 1, 0, 2, 4) + 25c
fdfa5194 __1cNWatcherThreadDrun6M_v_ (1bc4c8, 1b5460, 32, fe3be000, fe417db8, 0) + e8
fe264240 __1cG_start6Fpv_0_ (1bc4c8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1bc4c8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 15 / thread# 14 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f1, 3baea0, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (ba8, fe406e44, 3baea0, fe412d84, 3bb180, fe3be000) + 260
f840e22c ???????? (c9, eff818f4, eff81870, ffffff80, f00e5250, 0)
f840e1d0 ???????? (0, b8, 0, 8, f00e5250, eff81888)
f8405764 ???????? (2000, 2, 0, f8419754, eff0e110, eff81920)
f8400218 ???????? (eff81a08, eff81c08, a, f423b868, f840ba20, eff81b20)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 3baea0, eff81b18, eff81a18, 4, eff81c08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 3baea0, 254948, 254954, 254950, f01aaaf8) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 3baea0, 254d34, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (3baea0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (3baea0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (3baea0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 16 / thread# 15 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f0, 358da0, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (368, fe406e44, 358da0, fe412d84, 358f98, fe3be000) + 260
f840e22c ???????? (91, efe81874, efe817f0, ffffff80, f00dfeb0, 0)
f840e1d0 ???????? (0, b8, 0, 8, f00dfeb0, efe81808)
f8405764 ???????? (2000, 2, 0, f8419754, efe0e110, efe818a0)
f8400218 ???????? (efe81988, efe81b88, a, f423b868, f840ba20, efe81aa0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 358da0, efe81a98, efe81998, 4, efe81b88) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 358da0, 254d48, 254d54, 254d50, f01b4270) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 358da0, 255134, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (358da0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (358da0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (358da0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 17 / thread# 16 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f5, 3dd8a8, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (1628, fe406e44, 3dd8a8, fe412d84, 3c5f98, fe3be000) + 260
f840e22c ???????? (c1, efb015fc, efb01570, ffffff80, efb, 0)
f840e1d0 ???????? (0, b8, 0, 8, 8800, efb01588)
f8405764 ???????? (2000, 2, 0, f8419770, efa8e110, efb01620)
f8400218 ???????? (efb01708, efb01908, a, f422e650, f840ba20, efb01820)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 3dd8a8, efb01818, efb01718, 4, efb01908) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 3dd8a8, 3568f8, 356904, 356900, f007a910) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 3dd8a8, 356ce4, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (3dd8a8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (3dd8a8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (3dd8a8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 18 / thread# 17 --------------------
ff29f428 ___lwp_cond_wait (65b7a0, 65b788, ef681128, fe4123c4, ff2968f4, ef681120) + 8
ff296a7c _lwp_cond_timedwait (2ea2b88, 44b36759, ef681248, 65b788, 65b7a0, ff2969e4) + 98
fdeb4974 __1cNObjectMonitorEwait6MxipnGThread__v_ (120400, fe406ef0, fe4238d8, fe3be000, 65b550, 120420) + 7a8
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (120402, 86d4, 0, 65b550, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, 3dcdb4, 65b550, fe412d84, 0, 1) + 31c
f840e22c ???????? (91, ef6814b4, ef681430, ffffff80, ef6, 0)
f840e1d0 ???????? (f1631648, b6, 0, c, f00d7f28, ef681448)
f8405764 ???????? (f007ea58, fe4163d4, 0, f8419354, 8800, ef681508)
f8405764 ???????? (2000, 2, 0, f84195a0, ef60e110, ef6815a0)
f8400218 ???????? (ef681688, ef681888, a, f456d6b8, f840ba20, ef6817a0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 65b550, ef681798, ef681698, 4, ef681888) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 65b550, 3dcda0, 3dcdac, 3dcda8, f007ea58) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 65b550, 3dd18c, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (65b550, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (65b550, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (65b550, 0, 0, 0, 0, 0) + 40
-------------------------- thread# 3 --------------------
ff36d9b8 _reap_wait (ff390980, 1e924, 0, ff38c000, 0, 0) + 38
ff36d710 _reaper (ff38ce00, ff392708, ff390980, ff38cdd8, 1, fe400000) + 38
ff37b01c _thread_start (0, 0, 0, 0, 0, 0) + 40

RFC Connection error message while Debug the running WebDynpro app

Dear friends,
I am trying to debug WebDynpro application.
After configuring the NWDS with the J2EE server instance, I try to run the WebDynpro application, which I want to debug.
I did selecting the application and run after putting breakpoint at a button click.
But the webdynpro application uses 2 JCo destiantions, and so it gives JCOClientConnection for logical System: ... Please assure that you have configured the RFC connections and/or logical system name properly for this model! message.
If I run the same application from the portal, it doesn't give such error message.
Can anybody help me how can I run the WebDynpro application for debug purpose without getting this error message?
Thanks and regards,
Lakshmikanthaiah

Hi,
are you running the application on the same server? Or are you using the Debugmode on your local installation.
If so, you should check the JCO Destinations on you local server.
<a href="http://localhost:50000/webdynpro/dispatcher/sap.com/tcwdtools/WebDynproConsole">http://localhost:50000/webdynpro/dispatcher/sap.com/tcwdtools/WebDynproConsole</a>
Regards,
Dennis

Error trying to run "Measurement and Automation"

I recently purchased a PCI-6014 DAQ in an attempt to save time but along with many others we've exprerienced nothing but problems with it, including problems with the board itself and now with the NI-DAQ software. My most recent problem, which I've unsuccessfully tried to debug is an error message when trying to access "Measurement & Automation" as follows: "The instruction at 0X73DD8789 referenced memory at 0X04781D70. The memory could not be read. Click OK to terminate the program". Any suggestions or should I cut my loses and move on to another test approach as I'm already far behind schedule?

Hi cmm-
What type of operations are you trying to perform when you run into this error? It sounds like your NI-MAX installation may have become corrupted. I would suggest reinstalling NI-DAQmx 7.5. This driver install will install full support for your board as well as the newest version of NI-MAX to make sure that all files are up to date and uncorrupted.
You should first uninstall any versions of NI-DAQ and NI-MAX under the "National Instruments Software" section of Add/Remove Programs in the Control Panel. Have you had any luck in attempting to access the software on another machine or with other NI DAQ cards?
Please give these suggestions a try and let us know if you are still seeing problems.
Thanks-
Message Edited by Tom W. on 09-01-2005 01:36 PM
Tom W
National Instruments

Error trying to run tutorial ----log

Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-12-24T15:30:06.556-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2005-12-24T15:30:08.038-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-12-24T15:30:08.439-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-12-24T15:30:10.853-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-12-24T15:30:10.863-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-12-24T15:30:10.873-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-12-24T15:30:15.369-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-12-24T15:30:17.122-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-12-24T15:30:17.432-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-12-24T15:30:18.223-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-12-24T15:30:18.263-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2005-12-24T15:30:18.273-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2005-12-24T15:30:18.283-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2005-12-24T15:30:19.535-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-12-24T15:30:19.545-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-12-24T15:30:19.585-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compiling RMI-IIOP code ...|#]
[#|2005-12-24T15:30:32.203-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-12-24T15:30:32.223-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;| role is admin-role class class java.lang.String|#]
[#|2005-12-24T15:30:32.424-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;|
role is admin-role class class java.lang.String|#]
[#|2005-12-24T15:30:32.654-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 14070 msec, Total EJB Compiler Module Time: 12668 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 12668 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 12618 msec (99%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2005-12-24T15:30:32.654-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-12-24T15:30:32.754-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-12-24T15:30:33.435-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-12-24T15:30:33.445-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-12-24T15:30:33.455-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear.|#]
[#|2005-12-24T15:30:33.455-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2005-12-24T15:30:33.946-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-12-24T15:30:37.661-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-12-24T15:30:37.661-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-12-24T15:30:37.771-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4276 msec, Total EJB Compiler Module Time: 3715 msec, Portion spent EJB Compiling: 86%
Breakdown of EJBC Module Time: Total Time for EJBC: 3715 msec, CMP Generation: 942 msec (25%), Java Compilation: 2463 msec (66%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-12-24T15:30:37.771-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-12-24T15:30:37.781-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-12-24T15:30:38.232-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-12-24T15:30:38.232-0700|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!|#]
[#|2005-12-24T15:30:38.232-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-12-24T15:30:38.242-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-12-24T15:30:38.282-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-12-24T15:30:38.522-0700|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]|#]
[#|2005-12-24T15:30:38.723-0700|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]|#]
[#|2005-12-24T15:30:38.723-0700|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|#]
[#|2005-12-24T15:30:38.753-0700|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]|#]
[#|2005-12-24T15:30:38.773-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-12-24T15:30:38.773-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-12-24T15:30:38.883-0700|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|#]
[#|2005-12-24T15:30:43.169-0700|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[]|#]
[#|2005-12-24T15:30:45.132-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 18080|#]
[#|2005-12-24T15:30:45.172-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 18080|#]
[#|2005-12-24T15:30:45.352-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 11043|#]
[#|2005-12-24T15:30:45.352-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 11043|#]
[#|2005-12-24T15:30:45.392-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 14848|#]
[#|2005-12-24T15:30:45.402-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 14848|#]
[#|2005-12-24T15:30:45.733-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2005-12-24T15:30:45.733-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1135463445733|#]
[#|2005-12-24T15:30:45.733-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2005-12-24T15:30:45.733-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2005-12-24T15:31:15.756-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\domains\creator\autodeploy\hello-jaxrpc.war ] for autodeployment.|#]
[#|2005-12-24T15:31:16.156-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello-jaxrpc]|#]
[#|2005-12-24T15:31:16.156-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2005-12-24T15:31:16.156-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello-jaxrpc]|#]
[#|2005-12-24T15:31:16.227-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 421 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%
Breakdown of EJBC Module Time: Total Time for EJBC: 0 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-12-24T15:31:16.227-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = hello-jaxrpc|#]
[#|2005-12-24T15:31:16.247-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello-jaxrpc]|#]
[#|2005-12-24T15:31:16.317-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2005-12-24T15:31:17.378-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2005-12-24T15:31:17.629-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2005-12-24T15:31:17.689-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-12-24T15:31:17.699-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\domains\creator\autodeploy\hello-jaxrpc.war.|#]
[#|2005-12-24T15:31:17.699-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\domains\creator\autodeploy\jTravellerService.war ] for autodeployment.|#]
[#|2005-12-24T15:31:18.239-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [jTravellerService]|#]
[#|2005-12-24T15:31:18.239-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2005-12-24T15:31:18.239-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [jTravellerService]|#]
[#|2005-12-24T15:31:18.279-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 560 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%
Breakdown of EJBC Module Time: Total Time for EJBC: 0 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-12-24T15:31:18.290-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = jTravellerService|#]
[#|2005-12-24T15:31:18.300-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/jTravellerService]|#]
[#|2005-12-24T15:31:18.370-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2005-12-24T15:31:19.321-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2005-12-24T15:31:19.361-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2005-12-24T15:31:19.401-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-12-24T15:31:19.411-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\domains\creator\autodeploy\jTravellerService.war.|#]
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-01-27T20:33:15.701-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-01-27T20:33:17.764-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-01-27T20:33:18.305-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-01-27T20:33:22.621-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-01-27T20:33:22.641-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-01-27T20:33:22.661-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-01-27T20:33:27.919-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-01-27T20:33:30.142-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-01-27T20:33:30.532-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-01-27T20:33:31.454-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-01-27T20:33:32.515-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-01-27T20:33:33.637-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-01-27T20:33:33.637-0700|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!|#]
[#|2006-01-27T20:33:33.767-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-01-27T20:33:34.348-0700|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]|#]
[#|2006-01-27T20:33:34.528-0700|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]|#]
[#|2006-01-27T20:33:34.528-0700|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|#]
[#|2006-01-27T20:33:34.538-0700|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]|#]
[#|2006-01-27T20:33:34.548-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2006-01-27T20:33:34.558-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2006-01-27T20:33:34.578-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2006-01-27T20:33:34.588-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2006-01-27T20:33:34.749-0700|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|#]
[#|2006-01-27T20:33:39.746-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2006-01-27T20:33:40.417-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2006-01-27T20:33:40.497-0700|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[]|#]
[#|2006-01-27T20:33:42.610-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2006-01-27T20:33:42.700-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2006-01-27T20:33:43.882-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 18080|#]
[#|2006-01-27T20:33:43.942-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 18080|#]
[#|2006-01-27T20:33:44.132-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 11043|#]
[#|2006-01-27T20:33:44.142-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 11043|#]
[#|2006-01-27T20:33:44.222-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 14848|#]
[#|2006-01-27T20:33:44.222-0700|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 14848|#]
[#|2006-01-27T20:33:44.613-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2006-01-27T20:33:44.703-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1138419224703|#]
[#|2006-01-27T20:33:44.703-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2006-01-27T20:33:44.713-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2006-01-27T20:33:49.219-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [_webapplication1]|#]
[#|2006-01-27T20:33:49.219-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2006-01-27T20:33:49.259-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [_webapplication1]|#]
[#|2006-01-27T20:33:50.631-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 2393 msec, Total EJB Compiler Module Time: 40 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 40 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (25%),
|#]
[#|2006-01-27T20:33:50.681-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = _webapplication1|#]
[#|2006-01-27T20:33:50.812-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/_webapplication1]|#]
[#|2006-01-27T20:33:51.062-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable web/_webapplication1]|#]
[#|2006-01-27T20:33:51.192-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [_webapplication1] in virtual server [server] at [webapplication1]|#]
[#|2006-01-27T20:33:53.516-0700|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.beanutils.MethodUtils|_ThreadID=11;|Cannot use JVM pre-1.4 access bug workaround die to restrictive security manager.|#]
[#|2006-01-27T20:33:53.876-0700|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigDecimal)|#]
[#|2006-01-27T20:33:53.886-0700|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigInteger)|#]
[#|2006-01-27T20:33:55.568-0700|INFO|sun-appserver-pe8.0.0_01|com.sun.faces.config.ConfigureListener|_ThreadID=11;|Application object verification completed successfully|#]
[#|2006-01-27T20:33:55.659-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-01-28T17:15:48.473-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-01-28T17:15:50.045-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-01-28T17:15:50.556-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-01-28T17:15:54.191-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-01-28T17:15:54.221-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-01-28T17:15:54.231-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-01-28T17:15:58.778-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-01-28T17:16:00.670-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-01-28T17:16:01.111-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-01-28T17:16:02.092-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-01-28T17:16:03.074-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-01-28T17:16:03.865-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-01-28T17:16:03.865-0700|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!|#]
[#|2006-01-28T17:16:03.985-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-01-28T17:16:04.526-0700|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0200: Configuration error in web module [_webapplication1] (while initializing virtual server [server])
com.sun.enterprise.config.ConfigException: I/O error while loading deployment descriptor for: _webapplication1
cause: c:/Documents and Settings/Jim/My Documents/Creator/Projects/WebApplication1/build
 at com.sun.enterprise.instance.WebModulesManager.getDescriptor(WebModulesManager.java:327)
 at com.sun.enterprise.instance.WebModulesManager.getDescriptor(WebModulesManager.java:293)
 at com.sun.enterprise.web.VirtualServer.loadWebModuleConfig(VirtualServer.java:404)
 at com.sun.enterprise.web.VirtualServer.getWebModules(VirtualServer.java:253)
 at com.sun.enterprise.web.WebContainer.loadWebModules(WebContainer.java:560)
 at com.sun.enterprise.web.WebContainer.start(WebContainer.java:471)
 at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:506)
 at com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:54)
 at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
 at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
 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: java.io.FileNotFoundException: c:/Documents and Settings/Jim/My Documents/Creator/Projects/WebApplication1/build
 at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:43)
 at com.sun.enterprise.instance.WebModulesManager.getDescriptor(WebModulesManager.java:316)
 ... 15 more
|#]
[#|2006-01-28T17:16:04.526-0700|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]|#]
[#|2006-01-28T17:16:04.716-0700|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server

Author: jvandal Posts: 3 Registered: 1/27/06
 Jan 30, 2006 9:10 PM
Hi,
I am trying to run Sun Java Studio and entered the Tutorial "Developing a Web Application". I have tried to do this twice. steps
1. drage test field and name it
2, drag a label and name it
3. drage abutton and name it
4. Drage static text and name it
5. Double click button and enter "helloText.setText("Hello, "+name+"!");
6. try to build and run
These two error appear
<ant antfile="project-data/build-impl.xml" target="compile"/>
<javac srcdir="${source.java.root}" source="1.4" target="1.4" encoding="${source.encoding}" destdir="${output.classes.dir}" debug="on">
Any help would be appreciated
Jim
I first posted to this . I replied with the log but couldn't get the reply to work so I posted a new post.
i am sorry that I caused confusion
Re: Error trying to run tutorial
Author: RunaK Posts: 541 Registered: 7/27/04
 Jan 30, 2006 11:21 PM (reply 1 of 1)
Hi,
I could not reproduce your problem.The tutorial "Developing a Web Application" works fine for me.
Please post the server log file which is available at : <install-dir>:\Sun\Creator2\SunAppServer8\domains\creator\logs\server .log
Thanks,
RK.

Error trying to get LiveCycle ES up and running with JBoss/SQL Server

I am having an error trying to get LiveCycle ES Trial up and running with JBOSS and SQL Server. The LiveCycle ES and JBOSS engines are running on Windows Server 2003 SP #2 under VMWare Server with 2 vCPUs/1 GB vRAM. The SQL Server database is SQL 2005 x86-64 with SP #2 on a separate server. I have carefully followed all of the instructions for setting up jboss, modifying all of the appropriate XML files, downloading the SQL JDBC drivers and putting it in the %JBOSS_HOME%\server\all\lib directory, etc. I tried both the SQL JDBC 1.1 and 1.2 drivers and they both fail. The error I get is on startup of jboss using cmd /c start /low run.bat -c all (and yes I also just tried run.bat -c all) it runs along file until it gets here 2008-06-18 16:00:03,123 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=IDP_DS' to JNDI name 'java:IDP_DS' 2008-06-18 16:00:03,123 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=EDC_DS' to JNDI name 'java:EDC_DS' 2008-06-18 16:00:03,373 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 2008-06-18 16:00:03,373 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=adobe_JmsQueueXA' to JNDI name 'java:adobe_JmsQueueXA' 2008-06-18 16:00:03,389 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=adobe_JmsTopicXA' to JNDI name 'java:adobe_JmsTopicXA' 2008-06-18 16:00:03,482 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 2008-06-18 16:00:03,514 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: com.microsoft.jdbc.sqlserver.SQLServerDriver; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: com.microsoft.jdbc.sqlserver.SQLServerDriver)) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnecti on(LocalManagedConnectionFactory.java:164) [ lots more error scrolls ] this repeats multiple times I can see that it does acknowledge that I put the sqljdbc.jar file in the appropriate directory from the boot.log <snip> 15:59:44,856 DEBUG [SARDeployer] deployed classes for file:/C:/jboss/server/all/lib/sqljdbc.jar <snip> please help!

APJ We ran into many issues setting up a very similar environment. In the end we had to use a specially configured JBoss, supplied by Adobe, to make a connection with the SQL database. Since you have SQL w/ SP2 on it, you will need the 1.2 driver for sure, but you may want to talk to Adobe support about obtaining the version of JBoss they supplied us with. The Adobe Support Reference Number is: 1-52422366. Even with the alternate JBoss we had to perform the following steps to get the configuration right: 1. Install Livecycle from the installation DVD. Follow the instructions for installing LiveCycle supplied by Adobe, including all pre-installation instructions. Make sure NT service is installed with parameters, and dont run Configuration Manager. 2. Rename %LIVECYCLE_INSTALL%\jboss to %LIVECYCLE_INSTALL%\jboss_orig 3. Extract the zipped new, good instance of JBoss (supplied by Adobe) to the %LIVECYCLE_INSTALL%\ folder 4. Go to the %LiveCycle_Home%\deploy folder and make a copy of the file adobeimport_SQLServer.jar file. Rename the copy of the file to aadobeimport_SQLServer.jar. There seems to be a bug in configuration manager that looks for a file with the extra a appended to the beginning of the file name, where that file normally isnt there. Make sure that the adobeimport_SQLServer.jar file is still in this folder as well. 5. Edit the data source file (%JBOSS_HOME%\server\all\deploy\ adobe-ds.xml) to point to the correct database for the LiveCycle Server. a. Update the <connection-url>, <user-name>, and <password> tags with the correct database connection information. b. If BAM is to be used on the server (this should be done on the Production server) then delete both lines that state Remove this line, if BAM is used. 6. Go to the login configuration file (%JBOSS_HOME%\server\all\conf\login-config.xml), and edit the section labeled <application-policy name = "MSSQLDbRealm">. a. Change the Principal, UserName, and Password options to point to the correct database. These will be the same as what was changed in the adobe-ds.xml file from the step above. 7. Edit the system variables on the server. Add to the Path variable %JBOSS_HOME%\bin, and add the variable JBOSS_HOME with the path to the JBoss folder on the server. (D:\Adobe\LiveCycle8\jboss for example) 8. From windows services start the JBoss for Adobe LiveCycle ES v8.0 service. Review the JBoss server log (%JBOSS_HOME%\server\all\log\server.log) to verify that JBoss starts without throwing any exception errors (A document timeout exception is the only acceptable exception for starting the service). 9. Run the LiveCycle Configuration Manager (%LiveCycle_Home%\ConfigurationManager\bin\ConfigurationManager.bat). a. Select to Not Upgrade fromLiveCycle 7.x. b. Check all boxes on the Solution Component Selection screen. c. For the Task Selection screen check all the boxes except for the Import LiveCycle ES Samples into LiveCycle ES if on the production server. d. Run through the rest of the configuration manager interface to setup the LiveCycle server with the new application server. Follow the steps supplied by Adobe for this. 10. Once configuration manager has completed, reboot the server, and verify that JBoss starts up again without any exceptions or errors (again a document timeout exception is an acceptable exception. Look at the server log to verify this (%JBOSS_HOME%\server\all\log\server.log)).

Hyper-V encountered an error trying to access an object on computer 'localhost' .....- When try to install new Virtual machin in win8, 64 bit

am using windows 8, 64 bit system inside VMWARE in Ubuntu 14.04 . I have intel core i3 processor.
I want to install WIndows-7 inside windows 8 as a virtual machine. SO I tried to use "HYPER V MANAGER" with elevated privilege. wHEN I TRY , NEW->VM Machine->'after some steps'-> when I press Finish I get following error,
[Window Title]
New Virtual Machine Wizard
[Main Instruction]
Hyper-V encountered an error while configuring the network on Windows7_32bit.
[Content]
Hyper-V encountered an error trying to access an object on computer 'localhost' because the object was not found. The object might have been deleted, or you might not have permission to perform the task. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.
[Close]
my understand is: "we can use Hyper v, instead of Virtual box or as VMware player". I think in windows 8, hyper v server is not installed. does that is the problem? Why do we use it ?
Actually I wanna configure Kernel Debugging over Virtualized COM port. So what can I do next ? please help me...
Note: Virtual Machine Management service is running.

Hi mrCracker,
>>am using windows 8, 64 bit system inside VMWARE in Ubuntu 14.04 .
If I understand correctly , it is nested installation .
Windows Hyper-v is bare-metal hypervisor .
Please try to install win8 on real hardware then enable hyper-v to install VM .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Error trying to open source media - Compressor 1.2.1

I have a problem with a movie that have been sent to me. I seem unable to add it to a batch in Compressor or in Final Cut Pro 4.5 HD for the that matter.I'm using QuickTime 7.0.3 adn Mac OS X 10.4.3
When ever I had it to Compressor I get this error:
"Alert: Error trying to open source media file"
http://www.saruken.com/temp/Compressor-Error.jpg
And when I import it into Final Cut I get this error:
"File Error: 1 file(s) recognized, 0 access denied, 1 unknown."
http://www.saruken.com/temp/FCP-error.jpg
The settings for the offending movie are:
Format: H.264, 640x480, Millions, AAC, Stereo (L R), 22.050kHz
FPS: 29.97
Data Rate: 90 kbytes/sec
Key Frame: Every 300 Frames
The only difference between my test, which works fine, and this file is the frame rate (mine is at 25fps) and the number of audio channels (my test was in mono).
The file I was sent was encoded in Compressor, not sure which one - but I think it might be version 2.
The strange thing is it opens in QuickTime fine. I've tried exporting from QuickTime Pro as another h.264 with mono sound with no joy. I've tried saving a reference of the movie to see if that works, again no joy.
The only way I can get Compressor to accept the file is by transcoding it to another codec, like Soreson 3. Then FCP and Compressor are happy.
What I can't work out is why the h.264 file I made is fine (and any file I still make as well), and the one I was sent is not. I'm also having the same problem with an h.264 file I downloaded from Apple QuickTime Trailers, and an another I found on the web.
Updates that have been done recently incase they might have caused the problem are 10.4.3 and installing Motion 2 Trail (since removed), which wanted to update Pro Application Support (this might be the problem?).
Any help greatly apprieated
Hami

I just tried the offending movie file on my Powerbook, it has never seen Motion 2 or those Pro Application Support updates - and it gets the same error.
Very odd indeed - any ideas?
thanks in advance
Hami

Error: there is a problem connection to the GPRS service in your registered home network, error trying to make data connection. this may be casued by a voice call, a wired activesync connection or inncorrect network setting

like 2 weeks ago i called in to att to see how much is the data plan and it would end up costing $30.
so i was like screw that. well they figured that i got a new phone replacing the LG shine. so they asked
for to call this number so they can recieve data which would updated the system that i have a plam treo 750.
ever since this conflict i can't send picture messages. i get that problem. everytime i attempt to send a picture
i recieve this.
- there is a problem connection to the GPRS service in your registered home network.
- then i get a test that says error trying to make data connection. this may be casued by a voice call,
a wired activesync connection or inncorrect network setting.
please someone help me.
btw. hard reset and soft reset did not work for me.
Post relates to: Treo 750 (AT&T)

problem fix, i had to call in. customer serivce. and when i called to ask about the plan. they blocked it. so i had to unblock my internet.
Post relates to: Treo 750 (AT&T)

Error trying to backup photoshop elements 4.

Error trying to backup photoshop elements 4. Getting windows error: unable to save all data for file b0000408.jpg data lost try to save this file elsewhere;
and getting photoshop error "error encountered while writing file" and a bunch of numbers.
I have backed up to this device without problems.

Thank you for your reply.
I have tried the backup multiple times and it crashes in different places each time - it seems.
I did the select all and "ctrl W". This did nothing. Did you really mean "ctrl + W"? Remember I have version 4.0.
I was able to do a successful back up onto a drive that has none of my pictures on it. Could this be the problem? I have an external hard drive that I have been using for my backups which have been working just fine. I recently started storing my pictures in my catalog on this external hard drive. Since then, I have not been able to back up to that drive. Nor have I been able to back up to any other drive that has pictures on it.

Hyper-V encountered an error trying to access an object on computer ...

I'd like to share an issue which occurred during one of my recent configurations as well as the associated solution which worked for me.
While configuring Hyper-V Manager on a non-domain joined Windows 8.1 Enterprise client, to communicate with a non-domain joined Microsoft Hyper-V Server 2012R2, I received the following enjoyable message:
Hyper-V encountered an error trying to access an object on computer '.....' because the object was not found. The object might have been deleted. or you might not have permission to perform the task. Verify that the Virtual Machine Management service
on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.
As it turns out I forgot to change the machine name on the Hyper-V server. It's worth noting that it's also necessary to add an entry in the client machine's HOSTS file which matches the computer name of the Hyper-V server.

Hi ITMAGE,
Thanks for your sharing and support for this forum .
It should be helpful to other people who are facing this issue .
Best Regards,
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

FPN - error trying to lookup object - remote role assignment not working

Hello everyone,
We have implemented a Federated Portal Network connection in our landscape between our portals.
We use only remote role assignment functionality.
Everything was working fine, but since 2 days we encounter the following error in the Default trace.
Error trying to lookup object: alias: <role name>
It is possible to open the producer portal in the Portal Content Administration and also searching for the Producer portal roles is possible in User administration. But when we assign the remote role the tab is not displayed in the portal only the above mentioned error is shown in the default trace. Our portals run SP 12 and BI Java SP14.
Is there a solution or workaround for this issue ?
Martin

Hi,
I have the same issue as you, I cannot see role tabs in Consumer portal and I get the same error in the defaulttrace as you.
What did you do to resolve this issue?
Many thanks
Gordon

"Error" Trying to connect to.......

"Error" trying to connect to Infinitum9342
This message appears since i installed the update of airport for my Macbook C2D when trying to connect to the internet. (my litlte internet box)
I dont know how to name that thing in english, so i will just describe it, is a litle box, where i can connect ethernet cables or where i can connect wifi devices (such as my mac) rith now i just plug a ethernet cable to my macbook so i can get to the internet, but i loved using wi-fi, it just worked maravously for the past months in this mac, but now with the new update is all gone...and i dont know what to do!!!, the problem will be the next week
because i dont know if my computer will connect on other wifi connections (such as the one that is in my school, or work, or public places) and i need to use it for work and stuff.... and i cannot take a thernet cable everywhere, and i dont think there are public places to just connect a ethernet cable.
SO has anyone found a soultion for this kind of error? before the problem i used the ten digits (WAP) password of my "litle internet box" to connect but it dosnt works anymore.
Or can i just go back to the previous update of airport? or what can i do???
HELLLPPPPPPP!!!!!!!!!
Thanks a lot

well, WEP requires either a 5 or 13 character ASCII-password, or a 10 or 26 character hexadecimal password. WPA and WPA2 can take just about any password.
You could temporarily try disabling all encryption just to see if it works. Then hit the manual for your wireless router and see if you can get wpa2,wpa or wep working.
Good luck,
Martin

Error trying to debug in workshop

Similar Messages

Maybe you are looking for