BAPI_INSPLOT_SETUSAGEDECISION dumping, why?
Hi All,
I'm using BAPI_INSPLOT_SETUSAGEDECISION to update usage decisions on a number of inspection lots. Here is my code..
loop at gt_batches.
clear gv_ud_data.
gv_number = gv_ud_data = gt_batches-prueflos.
gv_ud_data-ud_plant = gt_batches-werk.
gv_ud_data-ud_code = p_vcode.
gv_ud_data-ud_code_group = p_vcodeg.
gv_ud_data-ud_selected_set = p_vaus.
call function 'BAPI_INSPLOT_SETUSAGEDECISION'
exporting
number = gv_number
ud_data = gv_ud_data
importing
return = gv_return.
The first call in the bapi is to FM 'QEVC_PROCESS_AUTO_UD' and this is where it's dumping. It's not even caught by the exceptions are anything.
Has anyone had a similar experience before and if so what did you do to reslove it? Am I missing a something.
If anyone could help, I'd be most grateful,
Thanks,
Liz.
Hi Martin,
Firstly thanks for the response. I don't get any error mesages, it simply stops executing and reverts back to the input screen. I've been degugging in se37 and it simply stops and throws back to se37 screen.
I will double check my input parameters but I'm fairly sure they're correct.
Regards,
Liz.
Similar Messages
-
[root@northstar udump]# more ora_orcl_4186.trc
Dump file /u04/udump/ora_orcl_4186.trc
Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production
ORACLE_HOME = /u01/app/oracle/product/8.0.5
System name: Linux
Node name: xxxxxxxxxxxxxxxxxxxxxxxxxx
Release: 2.0.35
Version: #1 Tue Jul 14 23:56:39 EDT 1998
Machine: i686
Instance name: ORCL
Redo thread mounted by this instance: 1
Oracle process number: 0
Unix process pid: 4186, image: oracleORCL
Exception signal: 11, code = 2b
ORA-07445: exception encountered: core dump [11] [43] [] [] [] []
----- Call Stack Trace -----
calling call entry argument
values in hex
location type point (? means
dubious value)
ssexhd()+221 CALL ksedst()+0 0 ? 400 ?
BFFFF314 CALLs ssexhd()+0
4000590A CALL 400055F0
ntacaddr2bnd()+393 CALLr 00000000 8CD8FA0 ?
4E2F6E6F ? 100 ?
0 ?
nsgetclientaddress CALL ntacaddr2bnd()+0 BFFFFCDC ? 68
? BFFFF5B0 ?
8CC1AFC ?
8CDF724 ?
kzsinn()+459 CALL nsgetclientaddress
opiino()+1222 CALL kzsinn()+0 8AA6FA8 ?
BFFFFCEC ?
BFFFF7AC ?
8CBFD78 ? 1 ?
opiodr()+1254 CALLr 00000000 FFFFFFFF ?
FFFFFFFF ?
FFFFFFFF ?
opidrv()+893 CALL opiodr()+0
sou2o()+25 CALL opidrv()+0
main()+240 CALL sou2o()+0
_start()+53 CALL main()+0 0 ? BFFFFEF1 ?
BFFFFF1B ?
----- Argument/Register Address Dump -----
Argument/Register addr=8cd8fa0. Dump of memory from 8CD8F60 to
8CD90A0
8CD8F60 3130752F 7070612F 61726F2F 2F656C63 646F7270 2F746375
2E302E38 656E2F35
8CD8F80 726F7774 72742F6B 2F656361 5F727673 36383134 6372742E
00000000 00000061
8CD8FA0 08CD8F08 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF
8CD8FC0 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF
8CD8FE0 FFFFFFFF 00000000 00000000 00000000 00000000 00000000
08CD0C58 00000131
8CD9000 5754454E 004B524F 00000000 00000000 00000007 00544C4E
00000000 00000003
8CD9020 00000025 08CD7BE8 00000000 00000000 00000000 00000000
00000000 00000000
8CD9040 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
Repeat 2 times
Argument/Register addr=bffffcdc. Dump of memory from BFFFFC9C to
BFFFFDDC
BFFFFC80
BFFFFCDC
BFFFFCA0 00000000 BFFFFE30 0804B449 BFFFFCEC 0000003C 00000004
BFFFFCDC 4000A358
BFFFFCC0 00000002 0804B2E0 08CB1208 00000000 00000007 00000004
4003919C BFFFFEE6
BFFFFCE0 FFFFFFFF 00000000 00000001 00000000 40034158 4000A128
0AB94A30 40035000
BFFFFD00 4003919C BFFFFD54 00000000 00000000 BFFFFD44 4000A128
4000AF50 00000002
BFFFFD20 400CBE7C BFFFFE54 BFFFFEF1 00000007 40037E3C 400CC3FC
40047D34 40037E3C
BFFFFD40 400CC030 4003919C 4003F34C 4003F36C BFFFFD9C 40004280
4003052B 4003F36C
BFFFFD60 4000A358 40034000 00000007 00000004 40040372 BFFFFDC0
40004280 400305DA
BFFFFD80 40040372 08049864 BFFFFDD4 40004280 4003F4A9 08049864
4000A358 4000A988
BFFFFDA0 00000007 00000004 40037FDC 40034158 0000001A 4003F34C
40037E3C 00000006
BFFFFDC0 40034158 4000A128 02ADAE54 40035000 40037FDC BFFFFE24
00000000
Argument/Register addr=bffff5b0. Dump of memory from BFFFF570 to
BFFFF6B0
BFFFF560 00000000 00000000
00000000 00000010
BFFFF580 08CC342C 08CC3454 00000001 BFFFF5D8 08687038 08CC3454
08B54418 0000000E
BFFFF5A0 00000000 08CC3408 08CC1AFC 00000100 00000100 00000000
00000000 00000000
BFFFF5C0 00000000 00000000 00800010 00000001 00000000 00000010
BFFFF628 085CA2A9
BFFFF5E0 08CBFD10 08CC342C 00000800 08CBFC2C 08CBFD78 BFFFF684
08CC56C8 00000005
BFFFF600 BFFFF61C 08685CBF 08CC56C8 08B5D3AD 0000001D 08CD5688
00000000 BFFFF638
BFFFF620 08584472 00000000 00000000 00000000 00000000 08B5D3AD
BFFFF884 BFFFF884
BFFFF640 082F33A3 08CC1A50 08CD9908 08CE2988 000000B3 00000000
08AA6FA8 08AA6FA8
BFFFF660 BFFFFCEC BFFFF7AC 08CBFD78 00000001 000000B3 08CE2988
08CC1D94 00000000
BFFFF680 00000000 00000000 00000000 C3FFF7A7 BFFFF73C 31303030
BFFFF73C 4006EF33
BFFFF6A0 BFFFF6E4 08CB48BC BFFFF770 BFFFF6E4
Argument/Register addr=8cc1afc. Dump of memory from 8CC1ABC to
8CC1BFC
8CC1AA0
00000000
8CC1AC0 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
Repeat 8 times
8CC1BE0 00000000 00000000 00000000 00000000 00000000 00000000
00000000
Argument/Register addr=8cdf724. Dump of memory from 8CDF6E4 to
8CDF824
8CDF6E0 00000010 00000000 00000000 00000000 00000000
00000000 00000000
8CDF700 00000000 00000000 00000000 00000000 00000000 08CE0E38
00000000 00000000
8CDF720 00000000 00000000 00000000 00000000 08CDF23C 75000000
78B91B00 00000000
8CDF740 00000000 00000000 00000000 00000641 00000000 08CE0164
08CDF098 00000000
8CDF760 00000000 0000009B 00000000 00000000 08CDFD90 08CD0C58
00000000 00000000
8CDF780 08CDF79C 00000000 00000000 00000000 00000000 00000000
00000000 00000000
8CDF7A0 00000000 00000000 00000000 00000000 00000000 00000002
00000000 08CD99F0
8CDF7C0 00000000 00000000 08CDB8E0 0000FFFF 000052C1 43800000
0000001D 00000017
8CDF7E0 08CD9AD8 08CA655F 00000000 00000000 00000002 00003231
00000000 00000000
8CDF800 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
8CDF820 00000000
Argument/Register addr=8aa6fa8. Dump of memory from 8AA6F68 to
8AA70A8
8AA6F60 00000038 08AA7654 082F8194 08AA6B88
00000039 08AA7647
8AA6F80 082F81AC 08AA6B88 0000003A 08AA7641 082FADC0 00000000
0000003B 08AA7638
8AA6FA0 082F98DC 00000000 0000003C 08AA7753 082F2ED8 00000000
00000000 00000000
8AA6FC0 00000000 00000000 0000003E 08AA762D 082F3E28 00000000
00000000 00000000
8AA6FE0 00000000 00000000 00000000 00000000 00000000 00000000
00000041 08AA7621
8AA7000 084DBED0 00000000 00000042 08AA7612 084DBB9C 00000000
00000043 08AA7602
8AA7020 082D793C 00000000 00000044 08AA75F1 082F3A30 00000000
00000045 08AA75E5
8AA7040 082F5990 00000000 00000046 08AA75DA 08300738 08AA6BA0
00000047 08AA75D1
8AA7060 0853128C 00000000 00000048 08AA7761 082F5DDC 08AA6BD0
00000000 00000000
8AA7080 00000000 00000000 0000004A 08AA75C8 082EB1B0 00000000
00000000 00000000
8AA70A0 00000000 00000000
Argument/Register addr=bffff7ac. Dump of memory from BFFFF76C to
BFFFF8AC
BFFFF760 00000002 0000001F 08CB5A70
BFFFF7FC 00000007
BFFFF780 080487C4 08CCAA14 20B6B684 08CC33C0 00000000 00000000
BF000000 00000000
BFFFF7A0 00000000 00000000 400306F0 00000000 BFFFF9A0 10000000
BFFFF7AC 08CBFD78
BFFFF7C0 BFFFFCEC BFFFF884 BFFFF640 082F30DB 00000000 BFFFFCEC
00000008 00000004
BFFFF7E0 00000008 00000007 0000000B 0000001F 00000018 00000019
00000006 00000000
BFFFF800 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
BFFFF820 00000000 00000000 00000000 00000000 00000000 3130752F
400400DD BFFFF888
BFFFF840 40004280 40040ECD 400400DD 4000A358 40034000 00000000
00000004 08CD98C8
BFFFF860 08CD9908 08CE2988 00000000 00000000 00000000 00000000
00000000 00000000
BFFFF880 00000000 BFFFFA64 0804DC68 0000003C 00000004 BFFFFCDC
BFFFFB50 08CBFD78
BFFFF8A0 BFFFFCEC FFFFFFFF FFFFFFFF
Argument/Register addr=8cbfd78. Dump of memory from 8CBFD38 to
8CBFE78
8CBFD20
00000000 00000000
8CBFD40 00000000 00000000 00000000 00000000 08A6E380 00001000
00000000 00000000
8CBFD60 00000000 0000000C 00000010 00000000 00000000 00000000
BFFFF9A0 00000000
8CBFD80 00000000 00000002 00001D15 08CC0204 00000002 0000000E
00000000 00000000
8CBFDA0 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
Repeat 5 times
8CBFE60 00000000 00000000 00000000 00000000 00000000 00000000
Argument/Register addr=bffffef1. Dump of memory from BFFFFEB1 to
BFFFFFF1
BFFFFEA0 0000000C 000001F5
0000000D 000001F5
BFFFFEC0 0000000E 000001F5 00000000 00000000 00000000 00000000
6F000000 6C636172
BFFFFEE0 43524F65 4C28004C 4C41434F 294F4E3D 41524F00 5F454C43
454D4F48 30752F3D
BFFFFF00 70612F31 726F2F70 656C6361 6F72702F 74637564 302E382F
5000352E 3D485441
BFFFFF20 3130752F 7070612F 61726F2F 2F656C63 646F7270 2F746375
2E302E38 69622F35
BFFFFF40 4F002F6E 4C434152 49535F45 524F3D44 4C004C43 494C5F44
52415242 41505F59
BFFFFF60 2F3D4854 2F313075 2F707061 6361726F 702F656C 75646F72
382F7463 352E302E
BFFFFF80 62696C2F 30752F3A 70612F31 726F2F70 656C6361 6F72702F
74637564 302E382F
BFFFFFA0 6A2F352E 2F636264 0062696C 454D4F48 6F682F3D 6F2F656D
6C636172 4F003865
BFFFFFC0 4E5F4152 5F325445 43534544 2C33313D 2F003631 2F313075
2F707061 6361726F
BFFFFFE0 702F656C 75646F72 382F7463 352E302E 6E69622F
----- End of Call Stack Trace -----
===================================================
PROCESS STATE
Process global information:
process: 0, call: 0, xact: 0, curses: 0, usrses: 0
No process is allocated.
END OF PROCESS STATE
******************** Cursor Dump ************************
No curdef array
ssexhd: crashing the process...
Shadow_Core_Dump = FULL
nullYou can download Sheng Liang's book ("Java Native Interface: Programmer's Guide and Specification", Addison-Wesley Pub Co, ISBN 0201325772 ), from:
ftp://ftp.javasoft.com/docs/specs/jni.pdf
Read pg. 78 (section 6.2.2: Handling Exceptions). He says that you probably will have to call ExceptionClear. -
LOOP AT imseg_mkpf_e.
itab_mbew_b-matnr = imseg_mkpf_e-matnr.
MOVE '99999999' TO itab_mbew_b-min_qty.
itab_mbew_b-max_qty = '0'.
COLLECT itab_mbew_b.
ENDLOOP.
"an internal table defined to small"
declare
DATA : BEGIN OF imseg_mkpf OCCURS 0,
werks like mseg-werks,
lgort like mseg-lgort,
matnr like mseg-matnr,
lbkum like mseg-lbkum,
mblnr like mseg-mblnr,
shkzg like mseg-SHKZG,
menge like mseg-menge,
s_stock like mardh-labst,
e_stock like mardh-labst,
min_qty like mseg-lbkum,
max_qty like mseg-lbkum,
END OF imseg_mkpf.
DATA : itab_mbew_b LIKE imseg_mkpf OCCURS 0 WITH HEADER LINE.Hi Rani,
This is working fine for me. Check this.
REPORT abc.
DATA : BEGIN OF imseg_mkpf OCCURS 0,
werks LIKE mseg-werks,
lgort LIKE mseg-lgort,
matnr LIKE mseg-matnr,
lbkum LIKE mseg-lbkum,
mblnr LIKE mseg-mblnr,
shkzg LIKE mseg-shkzg,
menge LIKE mseg-menge,
s_stock LIKE mardh-labst,
e_stock LIKE mardh-labst,
min_qty LIKE mseg-lbkum,
max_qty LIKE mseg-lbkum,
END OF imseg_mkpf.
DATA : itab_mbew_b LIKE imseg_mkpf OCCURS 0 WITH HEADER LINE.
SELECT
werks
lgort
matnr
lbkum
mblnr
shkzg
menge
FROM mseg INTO TABLE imseg_mkpf UP TO 500 ROWS.
LOOP AT imseg_mkpf.
itab_mbew_b-matnr = imseg_mkpf-matnr.
MOVE '99999999' TO itab_mbew_b-min_qty.
itab_mbew_b-max_qty = '0'.
COLLECT itab_mbew_b.
ENDLOOP.
BREAK-POINT.
Can you elaborate the dump problem.
Regards,
AS -
After copied class from standard class program getting dump.?
HI
Expert
I copied to a zclass from standard class (CL_SPROJECT_SOLAR_BASE_REPORT).. if calling program through zclass program getting dump, if calliing program through above standard class then it works fine...
error is
The function module interface allows you to specify only fields of particular type under i_so_report. The field "ME" specified different here......
Note:- Totaly i copied from standard class and activated it also.. even i did not changed any code inside method .but facing this dump why..
How to achieve this...pls help me out
Thanks
SusantaI did wt ever was there given solution but still not resolved pls help me ..thanks
showing error
Call Method XXXXX
DATA: lo_grid TYPE REF TO CL_SPROJECT_SOLAR_BASE_REPORT.
lo_grid = me.
CALL FUNCTION 'SPROJECT_EVAL_SET_SELSCREEN'
EXPORTING
i_o_data_container = a_o_data_container
i_v_reptype = global_reptype
i_o_sa_report = lo_grid
i_v_category = category
i_o_data_cont_lnk_docu = a_o_data_cont_lnk_docu "MP 21.07.05
syntax error - The type of "ME" cannot be converted to the type of "LO_GRID". ..why..? did i coded incoreclty or tell me where to define that data type... -
SELECT Query performance tunning
Hi All,
our objective is to read value from three DSO table, for that we have written three select query .
In this we have used three internal talbes.
We have written in END routine.
A model select statement for reading the Values in DSO and move statement i have given .
for 1,75000 records it is taking about 8 hours for DTP to run .
Usually they are meaning that it will take just 20 minutes.
Can anbody help on this please ??????????????????????????????
SELECT logsys
doc_num
doc_item
comp_code
/bic/gpusiteid
/bic/gpumtgrid
/bic/gpuspntyp
/bic/gpuspndid
/bic/gpuprocmt
/bic/gpubufunc
co_area
order_quan
po_unit
entry_date
/bic/gpuitmddt
/bic/gpuovpoc
currency
/bic/gpudel_in
BT8695*
costcenter
/bic/gpuordnum
/bic/gpupostxt
BT8695*
FROM (c_poadm_det)
INTO TABLE t_podetails
FOR ALL ENTRIES IN result_package
WHERE logsys EQ result_package-logsys
AND doc_num EQ result_package-doc_num
AND doc_item EQ result_package-doc_item.
LOOP AT result_package
ASSIGNING <result_fields>.
UNASSIGN <fs_podetails>.
READ TABLE t_podetails
ASSIGNING <fs_podetails>
WITH KEY logsys = <result_fields>-logsys
doc_num = <result_fields>-doc_num
doc_item = <result_fields>-doc_item.
IF sy-subrc EQ 0.
MOVE <fs_podetails>-/bic/gpusiteid TO <result_fields>-/bic/gpusiteid.
MOVE <fs_podetails>-/bic/gpumtgrid TO <result_fields>-/bic/gpumtgrid.
MOVE <fs_podetails>-/bic/gpuspntyp TO <result_fields>-/bic/gpuspntyp.
IF <result_fields>-order_quan NE ' '.
MOVE c_true TO <result_fields>-/bic/gpucount.
ENDIF.
ENDIF.Hi,
In the Read statement just use BINARY SEARCH it will improve the performance. Before putting BINARY SEARCH first the
internal table should be sort like wht field you giving the condition in read statement.
sort t_podetails by logsys doc_num doc_item."add this line
LOOP AT result_package
ASSIGNING <result_fields>.
UNASSIGN <fs_podetails>."why your giving the unassigned here it will give the dump. why because the field symbol is not assigned after the read symbol only they going to assign.
READ TABLE t_podetails
ASSIGNING <fs_podetails>
WITH KEY logsys = <result_fields>-logsys
doc_num = <result_fields>-doc_num
doc_item = <result_fields>-doc_item. " use BINARY SEARCH here
IF sy-subrc EQ 0.
MOVE <fs_podetails>-/bic/gpusiteid TO <result_fields>-/bic/gpusiteid.
MOVE <fs_podetails>-/bic/gpumtgrid TO <result_fields>-/bic/gpumtgrid.
MOVE <fs_podetails>-/bic/gpuspntyp TO <result_fields>-/bic/gpuspntyp.
IF <result_fields>-order_quan NE ' '.
MOVE c_true TO <result_fields>-/bic/gpucount.
ENDIF.
ENDIF.
Regards,
Dhina.. -
OCCI call PL/SQL Procedure with 2 IN/OUT Parameters..BUS ERROR!!
Hi~ All,
I am new user for using OCCI. Util now, I encountered a problem with OCCI when I call a procedure with 2 IN/OUT parameters. Then,I got an error(core dump), Why?
CREATE OR REPLACE PROCEDURE demo_proc (v1 in integer, v2 in out varchar2, v3 in out varchar2);
==== OCCI Code ========
stmt = conn->createStatement
("BEGIN demo_proc(:v1, :v2, :v3); END;");
cout << "Executing the block :" << stmt->getSQL() << endl;
stmt->setInt (1, 10);
stmt->setString (2, "Test1");
stmt->setString (3, "First");
int updateCount = stmt->executeUpdate ();
cout << "Update Count:" << updateCount << endl;
cout << "Printing the INOUT & OUT parameters:" << endl;
string c1 = stmt->getString (2);
cout << c1 << endl;
string c2 = stmt->getString (3);
==== RUN RESULT ====
Bus error(coredump)
But, If i just only got one of string from v1 or v2,I could get correct result!! Why? Does some one know how to avoid this two IN/OUT parameters issue?Hi~ Amoghavarsha,
Thanks for your response! I solved the problem by myself. I found the root cause, it seems very strange in
initializing environment variable.
=== FAILED ===
Environment *env;
=== SUCCESS ===
Environment *env = NULL; <---Why??
cout << "occidml - createEnvironment" << endl;
env = Environment::createEnvironment (Environment::OBJECT);
Eventually, I fixed this issue in Win2K and HP-UX 11.
Best Regards, -
I want to setup a datapump job to run automatically every night. This works fine but fails on the second run because the dump file alreay exists. With exp it would automatically overwrite the existing file buth with DP it appears the existing file needs to be manually deleted first. Is there another way (eg the "reuse" parameter in datafile create). I want to run this from within the database so I don't have access to OS commands.
Thanksif you should use the UTL_FILE.FREMOVE package, how can I then also use it with datefileformats?
the export datapump is maybe a nice tool, but the biggest mistake ever of Oracle in this, was not to allow the same filename for the dump, why is it allowed to overwrite the logfile. This is stupid move of Oracle. Everything of the datapump is ok for me, except you can't overwrite the dumpfile.
Now I'm having problem with it, with exp I used to run it every day and it was overwritten, with this, I had made a script that runs everyday with a date in the filename (file_name_date.dmp). But off course, those files need to be removed a regulary time. How can I do that with the package UTL_FILE.FREMOVE ?
(removing file without changing date-name is no problem...)
thanks -
Sun ONE 6.1 Performance Issues - Sleeping / Hanging
We have been running the Sun family of web servers for many years now, and ran Netscape Enterprise Server 3.6 for a long time.
Several months ago we upgraded to Sun ONE Web Server 6.0 and then 6.1. We have not had any issues until the past few weeks.
Specifically, the web server appears to 'go to sleep' or 'hang' for many seconds - sometimes up to 45 seconds - before processing any requests.
The server will accept the connection immediately but will not return a page. If left alone, the problem will go away, only to return again. A stop and start will also cure the problem.
Some background: 6 web servers run on this same server (Sun E250 2x400 MHz, 1280 MB RAM) - these servers are all relatively lightly loaded. Copper gigabit connection for network.
Primary data is static, with very few cgi-bin scripts and no applets or server-side Java.
All 6 servers have DNS lookups enabled with caching. The server also has a local DNS caching server running (BIND 9) which is used to help performance.
One of the 'public' web servers (external people can access it) is the one showing these performance issues. I've enabled statistics, and it seems during these 'sleepy' periods I see the following in /.perf (which it finally returns): (I am fetching /.perf every minute and timing how long it takes to fetch it, then saving it in a separate file):
webservd pid: 9507
Sun ONE Web Server 6.1 B08/22/2003 12:37 (SunOS DOMESTIC)
Server started Thu Mar 11 00:31:37 2004
Process 9507 started Thu Mar 11 00:31:37 2004
ConnectionQueue:
Current/Peak/Limit Queue Length 98/98/4096
Total Connections Queued 17873
Average Queueing Delay 0.11 milliseconds
ListenSocket group1:
Address http://146.137.96.68:80
Acceptor Threads 1
Default Virtual Server https-www.anl.gov
KeepAliveInfo:
KeepAliveCount 0/256
KeepAliveHits 1414
KeepAliveFlushes 0
KeepAliveRefusals 0
KeepAliveTimeouts 709
KeepAliveTimeout 30 seconds
SessionCreationInfo:
Active Sessions 105
Total Sessions Created 158/256
CacheInfo:
enabled yes
CacheEntries 1024/1024
Hit Ratio 58558/76530 ( 76.52%)
Maximum Age 30
Native pools:
NativePool:
Idle/Peak/Limit 1/1/128
Work Queue Length/Peak/Limit 0/0/0
DNSCacheInfo:
enabled yes
CacheEntries 406/2048
HitRatio 16547/18476 ( 89.56%)
Async DNS disabled
Performance Counters:
Average Total Percent
Total number of requests: 16961
Request processing time: 0.5940 10074.6680
default-bucket (Default bucket)
Number of Requests: 16961 (100.00%)
Number of Invocations: 268684 (100.00%)
Latency: 0.0013 21.2806 ( 0.21%)
Function Processing Time: 0.5927 10053.3877 ( 99.79%)
Total Response Time: 0.5940 10074.6680 (100.00%)
Sessions:
Process Status Function
9507 response flex-log
response flex-log
response shtml_send
response shtml_send
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response shtml_send
response shtml_send
response shtml_send
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log
response shtml_send
response shtml_send
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response send-file
response shtml_send
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response shtml_send
response flex-log
response flex-log
response shtml_send
response shtml_send
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response shtml_send
response shtml_send
response flex-log
response shtml_send
response flex-log
response shtml_send
response shtml_send
response flex-log
response shtml_send
response flex-log
response flex-log
response shtml_send
response flex-log
response send-cgi
response send-cgi
response shtml_send
response flex-log
response flex-log
response shtml_send
response shtml_send
response shtml_send
response shtml_send
response shtml_send
response shtml-hacktype
response flex-log
response send-cgi
response send-cgi
response send-file
response send-cgi
response flex-log
response shtml_send
response shtml_send
response shtml_send
response flex-log
response shtml_send
response send-file
response flex-log
response send-cgi
response shtml_send
response flex-log
response shtml_send
response send-cgi
response shtml_send
response shtml_send
response flex-log
response flex-log
response send-cgi
response shtml_send
response send-cgi
response flex-log
response shtml_send
response send-file
response send-cgi
response shtml_send
response shtml_send
response flex-log
response service-dump
Why do I have all of these processes queued on the server?
Is DNS causing this? I know Sun ONE 6.x does NOT have asynchronous DNS implemented (although it is an option, it has no effect). Did Netscape Enterprise Server 3.6 has ASync DNS implemented?
We would like to avoid turning off DNS resolution for a number of reasons. However, what really bothers us is that this web server's performance suddenly became a problem while the other 5 servers see FANTASTIC performance and never go to sleep (although some of them are NOT accessible from the general Internet).
Has anyone else seen this?
As a side note, all of these web servers are using a NSAPI plugin that I wrote years ago. It's purpose is access control and automatic forwarding to different pages. It also uses DNS hostnames, but thinking it might be a problem with this web server, I've disabled DNS on the plug-in. It has not helped. Again, this plug-in has worked great for years and is quite straightforward and simple.
Something tells me there is more going on here - thoughts or ideas?
We're getting immensely frustrated here.
In desperation we've made some magnus.conf changes but to no real effect (partially listed below):
DNS on
RqThrottle 256
StackSize 131072
CGIWaitPid on
AsyncDNS off
KeepAliveThreads 2
MaxKeepAliveConnections 256
UseNativePoll 1
RcvBufSize 8192
# default=100
KeepAliveQueryMeanTime 25
# default=100
KeepAliveQueryMaxSleepTime 25
# CGI
MinCgiStubs 10
MaxCgiStubs 50
CGIStubIdleTimeout 45
CGIExpirationTimeout 90
Thanks for any pointers,
--DaveNote that at the moment it seems to be responding normally, but we still have a lot of threads hanging around - very strange...
9507 response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log
processing flex-log
response shtml_send
response flex-log
response shtml_send
response shtml_send
response shtml_send
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response shtml_send
response flex-log
response shtml_send
response flex-log
response shtml_send
response flex-log
response send-file
response shtml_send
response flex-log
response shtml_send
response send-file
response service-dump
response shtml_send
response shtml_send
response shtml_send
response flex-log
response send-file
response flex-log
response flex-log
response shtml_send
response shtml_send
response flex-log
response flex-log
response shtml_send
response shtml_send
response shtml_send
response flex-log
response shtml_send
response shtml_send
response shtml_send
response shtml_send
response flex-log
response flex-log
response shtml_send
response shtml_send
response shtml_send
response send-file
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log
response flex-log
response flex-log
response shtml_send
response flex-log
response shtml_send
response shtml_send
response shtml_send
response flex-log
response flex-log
response shtml_send
response flex-log
response flex-log
response flex-log -
Weblogic 8.14: Stuck Threads during JMS - IO native write operations
G'day!
Hope somebody can advise a solution on the following...
Recently message loads have started to increase on our weblogic 8.14 cluster (3 servers) and we started to see an almost daily occurrence of Stuck Thread issues. From thread dumps we could see these were caused by jrockit/net/SocketNativeIO.write processes. We concluded we had reached the max performance limit for the file based JMS stores and so we moved these to database based JMS stores. This certainly seemed to improve matters - but we have recently seen the issue return. Which is puzzling, as technically we thought all messages would be persisted to the database, and any file IO on the application server would be eliminated. Our database resides on a separate dedicated oracle server. We tracked a recent cause to a large message (200K) which caused the Struck Thread - resulting in a build up of pending messages. After bouncing the server the message processed ok. Any thoughts on how to overcome these issues - greatly appreciated. Here's some detail on the stuck thread from the thread dump: (+Why does weblogic use IO when the JMS store is on a database?+). All messages are persistant.
"ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" prio=5 id=0xc00 pid=27544 active, daemon
at jrockit/net/SocketNativeIO.write(Native Method)@0xf3aeae10
at jrockit/net/SocketNativeIO.write(Unknown Source)@0xf3aeae9c
at jrockit/io/NativeIO.write(Unknown Source)@0xf3ae62c6
at java/net/AbstractSocketImpl$2.write(Unknown Source)@0xf3aeada4
at jrockit/io/NativeIOOutputStream.write(Unknown Source)@0xf3ae61ec
at jrockit/io/NativeIOOutputStream.write(Unknown Source)@0xf3ae618d
at java/io/DataOutputStream.write(Unknown Source)@0xf4e3ec25
^-- Holding lock: java/io/DataOutputStream@0x4309fc80[thin lock]
at com/ibm/mq/MQInternalCommunications.send(MQInternalCommunications.java:1022)@0xed34364a
^-- Holding lock: com/ibm/mq/MQInternalCommunications@0x4309f7e0[thin lock]
at com/ibm/mq/MQSESSIONClient.lowLevelComms(MQSESSIONClient.java:2832)@0xed342fbd
^-- Holding lock: java/lang/Integer@0x4309f8a0[thin lock]
at com/ibm/mq/MQSESSIONClient.MQPUT(MQSESSIONClient.java:3844)@0xed34271b
at com/ibm/mq/MQQueue.putMsg2(MQQueue.java:1486)@0xed342262
^-- Holding lock: com/ibm/mq/MQSPIQueue@0x4312ce80[thin lock]
at com/ibm/mq/jms/MQMessageProducer.sendInternal(MQMessageProducer.java:1569)@0xed33d1ab
at com/ibm/mq/jms/MQMessageProducer.send(MQMessageProducer.java:1012)@0xed860a49
at com/ibm/mq/jms/MQMessageProducer.send(MQMessageProducer.java:1046)@0xed8605f4
at weblogic/jms/adapter/JMSBaseConnection.sendInternal(JMSBaseConnection.java:667)@0xef7df0bf
^-- Holding lock: weblogic/jms/adapter/JMSBaseConnection@0x43093748[thin lock]
at weblogic/jms/adapter/JMSBaseConnection.access$200(JMSBaseConnection.java:80)@0xef7dee28
at weblogic/jms/adapter/JMSBaseConnection$6.run(JMSBaseConnection.java:647)@0xef7dee1d
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)@0xf2fcbb88
at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:147)@0xf2fcbb0a
at weblogic/jms/adapter/JMSBaseConnection.send(JMSBaseConnection.java:644)@0xef7decf3
at weblogic/jms/adapter/JMSConnectionHandle.send(JMSConnectionHandle.java:144)@0xef7dec7c
at jrockit/reflect/NativeMethodInvoker.invoke0(Native Method)@0xf4f10d10
at jrockit/reflect/NativeMethodInvoker.invoke(Unknown Source)@0xf4f10e98
at jrockit/reflect/VirtualNativeMethodInvoker.invoke(Unknown Source)@0xf4e86d70
at java/lang/reflect/Method.invoke(Unknown Source)@0xf4f104c3
at weblogic/connector/common/internal/ConnectionWrapper.invoke(ConnectionWrapper.java:149)@0xed96a498
at $Proxy14.send(Unknown Source)@0xef7dec04
at weblogic/jms/bridge/internal/MessagingBridge.onMessageInternal(MessagingBridge.java:1258)@0xed857b25
at weblogic/jms/bridge/internal/MessagingBridge.onMessage(MessagingBridge.java:1181)@0xed857864
at weblogic/jms/adapter/JMSBaseConnection$27.run(JMSBaseConnection.java:1943)@0xef7de623
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)@0xf2fcbb88
at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:147)@0xf2fcbb0a
at weblogic/jms/adapter/JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)@0xef7de586
at weblogic/jms/client/JMSSession.onMessage(JMSSession.java:2678)@0xeee7e30c
at weblogic/jms/client/JMSSession.execute(JMSSession.java:2598)@0xeee7d25d
at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:219)@0xf4e14070
at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:178)@0xf4e1fddb
at java/lang/Thread.startThreadFromVM(Unknown Source)@0xf4f3c9f3
Thanks
C.I'm not sure what operating system you're running, but I only have experience of WLS8.1 on Windows.
We did extensive load testing of JMS before we went live, and found JDBC file stores to be rubbish in comparison to file store. When a message is persisted, it has to be written to the database, then when it is consumed, it must be deleted from the table. This simply killed our system when we load tested it.
One thing we did do though, was use a second JMS server and second file store for one particularly heavy queue, where we did have IO issues. This was with a JMS distributed destination. We also use a synchronous write policy of cache-flush on the file store and we also have configured a paging store to page messages so the app server does not run out of memory.
200K isn't by any means a huge message though, and shouldn't be any problem at all, we have 1mb messages quite regularly.
I notice from the stack trace, that you have MQ series aswell. I'm not experienced with MQ, so can't give any information, but what I would try is the following.
Using a JMS server with JMS File storage, develop a small java client to write as many messages to the queue and effectively stress the JMS subsystem just to establish if the filestore is the problem. This should be done without a connection to MQ and also use large messages. if you don't get any issues and WebLogic JMS with file store looks ok, then attach a consumer to the queue, which should also be a simple java client. Then you have production and consumption going on, which will result in writes and read's/deletes from the jms file store.
Once you've stress tested JMS and you are satisfied that its ok or not, then add the MQseries connection and see how that affects things.
You may well have already done all this, so please feel free to ignore me! I did a load of this kind of stuff before we went live to try and bash JMS to bits, but I didn't manage it! The only thing we did was add a second file store and second JMS server.
I just looked back in my support cases, and found we'd had a similar issue - disk fragmentation seemed to be one of the factors here too. The JMS file store was heavily fragmented. That's windows for you though!!!
Hope that helps.
Pete -
HELP!!! Why do my thread dump have so many locked monitor
In recent weeks, My customer's weblogic server become more busy.Each time I downloaded
the thread dump when CPU is busy than 90%,I found a lot of lock in the thread
dump! Especially the class named "weblogic.kernel.ExecuteThread" . It's the kernel
class of weblogic, Why were most of them locked?
Full thread dump:
"process forker" daemon prio=1 tid=0x95b4c8e0 nid=0x3084 waiting on monitor [0x977ff000..0x977ff890]
at java.lang.Object.wait(Native Method)
- waiting on <53d26420> (a java.lang.Object)
at java.lang.UNIXProcessForker.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"process reaper" daemon prio=1 tid=0x95376758 nid=0x3083 runnable [0x96eff000..0x96eff890]
at java.lang.UNIXProcessReaper.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x825bf18 nid=0x25a1 waiting
on monitor [0x95dff000..0x95dff890]
at java.lang.Object.wait(Native Method)
- waiting on <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" prio=1 tid=0x94d00630 nid=0x25a0 runnable [0x95fff000..0x95fff890]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
- locked <538fa238> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=1 tid=0x8c0dd1d0 nid=0x259c waiting on monitor
[0x94521000..0x94521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9650> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9650> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"NBExecuteThread-0" daemon prio=1 tid=0x8c0dc7d0 nid=0x259b waiting on monitor
[0x94321000..0x94321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9060> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9060> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
//"ExecuteThread-49" daemon prio=1 tid=0x8c034660 nid=0x259a runnable [0x94121000..0x94121890]
at java.net.PlainDatagramSocketImpl.peek(Native Method)
- locked <537acf60> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:349)
- locked <486f9980> (a java.net.DatagramPacket)
- locked <537acf40> (a java.net.MulticastSocket)
at weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:86)
at weblogic.cluster.TMSocket.execute(TMSocket.java:249)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-48" daemon prio=1 tid=0x8c0c3d18 nid=0x2599 waiting for monitor
entry [0x93f21000..0x93f21890]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-47" daemon prio=1 tid=0x8c0c32d0 nid=0x2598 runnable [0x93d21000..0x93d21890]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- locked <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-46" daemon prio=1 tid=0x8c0bf410 nid=0x2597 waiting for monitor
entry [0x93b21000..0x93b21890]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-45" daemon prio=1 tid=0x8c0be9c8 nid=0x2596 waiting on monitor
[0x93921000..0x93921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6df8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6df8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-44" daemon prio=1 tid=0x8c0bdab0 nid=0x2595 waiting on monitor
[0x93721000..0x93721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6828> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6828> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-43" daemon prio=1 tid=0x8c0bd068 nid=0x2594 waiting on monitor
[0x93521000..0x93521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6258> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6258> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-42" daemon prio=1 tid=0x8c0c0ce0 nid=0x2593 waiting on monitor
[0x93321000..0x93321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a5c88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a5c88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-41" daemon prio=1 tid=0x8c0c0298 nid=0x2592 waiting on monitor
[0x93121000..0x93121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a56b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a56b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-40" daemon prio=1 tid=0x8c0a21e0 nid=0x2591 waiting on monitor
[0x92f21000..0x92f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a50e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a50e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-39" daemon prio=1 tid=0x8c0d4520 nid=0x2590 waiting on monitor
[0x92d21000..0x92d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4b18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4b18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-38" daemon prio=1 tid=0x8c0d43d0 nid=0x258f waiting on monitor
[0x92b21000..0x92b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4548> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4548> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-37" daemon prio=1 tid=0x8c0d3988 nid=0x258e waiting on monitor
[0x92921000..0x92921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a3f78> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a3f78> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-36" daemon prio=1 tid=0x8c0ded20 nid=0x258d waiting on monitor
[0x92721000..0x92721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a39a8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a39a8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-35" daemon prio=1 tid=0x8c0de2d8 nid=0x258c waiting on monitor
[0x92521000..0x92521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a33d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a33d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-34" daemon prio=1 tid=0x8c0cd528 nid=0x258b waiting on monitor
[0x92321000..0x92321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2e08> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2e08> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-33" daemon prio=1 tid=0x8c0ccae0 nid=0x258a waiting on monitor
[0x92121000..0x92121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2838> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2838> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-32" daemon prio=1 tid=0x8c075360 nid=0x2589 waiting on monitor
[0x91f21000..0x91f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2268> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2268> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-31" daemon prio=1 tid=0x8c0837d0 nid=0x2588 waiting on monitor
[0x91d21000..0x91d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a1c98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a1c98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-30" daemon prio=1 tid=0x8c0a5628 nid=0x2587 waiting on monitor
[0x91b21000..0x91b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a16c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a16c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-29" daemon prio=1 tid=0x8c07aaf8 nid=0x2586 waiting on monitor
[0x91921000..0x91921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a10f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a10f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-28" daemon prio=1 tid=0x8c0c23d0 nid=0x2585 waiting on monitor
[0x91721000..0x91721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0b28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0b28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-27" daemon prio=1 tid=0x8c0c1988 nid=0x2584 waiting on monitor
[0x91521000..0x91521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0558> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0558> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-26" daemon prio=1 tid=0x8c07ca00 nid=0x2583 waiting on monitor
[0x91321000..0x91321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ff88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ff88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-25" daemon prio=1 tid=0x8c079e70 nid=0x2582 waiting on monitor
[0x91121000..0x91121890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f9b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f9b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-24" daemon prio=1 tid=0x8c078038 nid=0x2581 waiting on monitor
[0x90f21000..0x90f21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f3e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f3e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-23" daemon prio=1 tid=0x8c0a3298 nid=0x2580 waiting on monitor
[0x90d21000..0x90d21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ee18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ee18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-22" daemon prio=1 tid=0x8c0e30d8 nid=0x257f waiting on monitor
[0x90b21000..0x90b21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e848> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e848> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-21" daemon prio=1 tid=0x8c0c5948 nid=0x257e waiting on monitor
[0x90921000..0x90921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e278> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e278> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-20" daemon prio=1 tid=0x8c0d0470 nid=0x257d waiting on monitor
[0x90721000..0x90721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379dca8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379dca8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-19" daemon prio=1 tid=0x8c080798 nid=0x257c waiting on monitor
[0x90521000..0x90521890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d6d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d6d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-18" daemon prio=1 tid=0x8c080648 nid=0x257b waiting on monitor
[0x90321000..0x90321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d108> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d108> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-17" daemon prio=1 tid=0x8c032380 nid=0x257a runnable [0x90121000..0x90121890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-16" daemon prio=1 tid=0x8c0df9a8 nid=0x2579 waiting on monitor
[0x8ff21000..0x8ff21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379c568> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379c568> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-15" daemon prio=1 tid=0x8c0a6288 nid=0x2578 waiting on monitor
[0x8fd21000..0x8fd21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379bf98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379bf98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-14" daemon prio=1 tid=0x8c0dbd60 nid=0x2577 waiting on monitor
[0x8fb21000..0x8fb21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b9c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b9c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-13" daemon prio=1 tid=0x8c0c8498 nid=0x2576 waiting on monitor
[0x8f921000..0x8f921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b3f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b3f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-12" daemon prio=1 tid=0x8c0a6a28 nid=0x2575 waiting on monitor
[0x8f721000..0x8f721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ae28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ae28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-11" daemon prio=1 tid=0x8c07d348 nid=0x2574 runnable [0x8f521000..0x8f521890]
at java.lang.System.arraycopy(Native Method)
at java.lang.String.getChars(String.java:557)
at java.lang.String.concat(String.java:1554)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:251)
at com.ebao.carcase.servlet.claim.ClaimServlet.doGet(ClaimServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-10" daemon prio=1 tid=0x8c0369b0 nid=0x2571 waiting on monitor
[0x8f321000..0x8f321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379a288> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379a288> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-9" daemon prio=1 tid=0x8c079898 nid=0x256f waiting on monitor [0x8f121000..0x8f121890]
at java.lang.Object.wait(Native Method)
- waiting on <53799cb8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799cb8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-8" daemon prio=1 tid=0x8c035260 nid=0x256e waiting on monitor [0x8ef21000..0x8ef21890]
at java.lang.Object.wait(Native Method)
- waiting on <537996e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537996e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-7" daemon prio=1 tid=0x8c034510 nid=0x256d waiting on monitor [0x8ed21000..0x8ed21890]
at java.lang.Object.wait(Native Method)
- waiting on <53799118> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799118> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-6" daemon prio=1 tid=0x8c081130 nid=0x256c waiting on monitor [0x8eb21000..0x8eb21890]
at java.lang.Object.wait(Native Method)
- waiting on <53798b48> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798b48> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-5" daemon prio=1 tid=0x8c0c7108 nid=0x256b waiting on monitor [0x8e921000..0x8e921890]
at java.lang.Object.wait(Native Method)
- waiting on <53798578> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798578> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-4" daemon prio=1 tid=0x8c0a4388 nid=0x256a waiting on monitor [0x8e721000..0x8e721890]
at java.lang.Object.wait(Native Method)
- waiting on <53797fa8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797fa8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-3" daemon prio=1 tid=0x8c0367b8 nid=0x2569 waiting on monitor [0x8e521000..0x8e521890]
at java.lang.Object.wait(Native Method)
- waiting on <537979d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537979d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-2" daemon prio=1 tid=0x8c036290 nid=0x2568 waiting on monitor [0x8e321000..0x8e321890]
at java.lang.Object.wait(Native Method)
- waiting on <53797408> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797408> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-1" daemon prio=1 tid=0x8c0a4ee0 nid=0x2567 waiting on monitor [0x8e121000..0x8e121890]
at java.lang.Object.wait(Native Method)
- waiting on <53796e38> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53796e38> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-0" daemon prio=1 tid=0x8c0a4550 nid=0x2566 runnable [0x8df21000..0x8df21890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.end.EndCaseServlet.service(EndCaseServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"TimeEventGenerator" daemon prio=1 tid=0x8c076008 nid=0x2565 waiting on monitor
[0x8dd21000..0x8dd21890]
at java.lang.Object.wait(Native Method)
- waiting on <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x8c0b34a0 nid=0x2563 waiting on monitor
[0x8db21000..0x8db21890]
at java.lang.Object.wait(Native Method)
- waiting on <53793040> (a weblogic.security.SpinnerThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:104)
- locked <53793040> (a weblogic.security.SpinnerThread)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
"Signal Dispatcher" daemon prio=1 tid=0x8c0077e8 nid=0x2561 waiting on monitor
[0..0]
"Finalizer" daemon prio=1 tid=0x8c000540 nid=0x255e waiting on monitor [0x8c2ff000..0x8c2ff890]
at java.lang.Object.wait(Native Method)
- waiting on <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
- locked <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80851f0 nid=0x255d waiting on monitor
[0x8bf8c000..0x8bf8c890]
at java.lang.Object.wait(Native Method)
- waiting on <53720208> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:415)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
- locked <53720208> (a java.lang.ref.Reference$Lock)
"main" prio=1 tid=0x804ead0 nid=0x2543 waiting on monitor [0xbfffc000..0xbfffd00c]
at java.lang.Object.wait(Native Method)
- waiting on <53743c20> (a weblogic.t3.srvr.T3Srvr)
at java.lang.Object.wait(Object.java:415)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1958)
- locked <53743c20> (a weblogic.t3.srvr.T3Srvr)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:148)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
"VM Thread" prio=1 tid=0x8082110 nid=0x255c runnable
"VM Periodic Task Thread" prio=1 tid=0x8c0064f8 nid=0x255f waiting on monitor
"Suspend Checker Thread" prio=1 tid=0x8c006e30 nid=0x2560 runnableThese are execute threads waiting for requests to come in.
BTW, you probably want to look into using StringBuffer instead of
strings concatenation in com.ebao.carcase.bean.query.Query.generatorXML.
"min.lu" <[email protected]> wrote in message
news:[email protected]...
>
In recent weeks, My customer's weblogic server become more busy.Each timeI downloaded
the thread dump when CPU is busy than 90%,I found a lot of lock in thethread
dump! Especially the class named "weblogic.kernel.ExecuteThread" . It'sthe kernel
class of weblogic, Why were most of them locked?
Full thread dump:
"process forker" daemon prio=1 tid=0x95b4c8e0 nid=0x3084 waiting onmonitor [0x977ff000..0x977ff890]
at java.lang.Object.wait(Native Method)
- waiting on <53d26420> (a java.lang.Object)
at java.lang.UNIXProcessForker.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"process reaper" daemon prio=1 tid=0x95376758 nid=0x3083 runnable[0x96eff000..0x96eff890]
at java.lang.UNIXProcessReaper.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x825bf18 nid=0x25a1waiting
on monitor [0x95dff000..0x95dff890]
at java.lang.Object.wait(Native Method)
- waiting on <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53a3bd10> (a weblogic.time.common.internal.TimeTable)
atweblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:141)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" prio=1 tid=0x94d00630 nid=0x25a0 runnable[0x95fff000..0x95fff890]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
- locked <538fa238> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
atweblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=1 tid=0x8c0dd1d0 nid=0x259c waiting onmonitor
[0x94521000..0x94521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9650> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9650> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"NBExecuteThread-0" daemon prio=1 tid=0x8c0dc7d0 nid=0x259b waiting onmonitor
[0x94321000..0x94321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9060> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9060> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
//"ExecuteThread-49" daemon prio=1 tid=0x8c034660 nid=0x259a runnable[0x94121000..0x94121890]
at java.net.PlainDatagramSocketImpl.peek(Native Method)
- locked <537acf60> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:349)
- locked <486f9980> (a java.net.DatagramPacket)
- locked <537acf40> (a java.net.MulticastSocket)
at weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:86)
at weblogic.cluster.TMSocket.execute(TMSocket.java:249)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-48" daemon prio=1 tid=0x8c0c3d18 nid=0x2599 waiting formonitor
entry [0x93f21000..0x93f21890]
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-47" daemon prio=1 tid=0x8c0c32d0 nid=0x2598 runnable[0x93d21000..0x93d21890]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- locked <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-46" daemon prio=1 tid=0x8c0bf410 nid=0x2597 waiting formonitor
entry [0x93b21000..0x93b21890]
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-45" daemon prio=1 tid=0x8c0be9c8 nid=0x2596 waiting onmonitor
[0x93921000..0x93921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6df8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6df8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-44" daemon prio=1 tid=0x8c0bdab0 nid=0x2595 waiting onmonitor
[0x93721000..0x93721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6828> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6828> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-43" daemon prio=1 tid=0x8c0bd068 nid=0x2594 waiting onmonitor
[0x93521000..0x93521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6258> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6258> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-42" daemon prio=1 tid=0x8c0c0ce0 nid=0x2593 waiting onmonitor
[0x93321000..0x93321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a5c88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a5c88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-41" daemon prio=1 tid=0x8c0c0298 nid=0x2592 waiting onmonitor
[0x93121000..0x93121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a56b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a56b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-40" daemon prio=1 tid=0x8c0a21e0 nid=0x2591 waiting onmonitor
[0x92f21000..0x92f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a50e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a50e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-39" daemon prio=1 tid=0x8c0d4520 nid=0x2590 waiting onmonitor
[0x92d21000..0x92d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4b18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4b18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-38" daemon prio=1 tid=0x8c0d43d0 nid=0x258f waiting onmonitor
[0x92b21000..0x92b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4548> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4548> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-37" daemon prio=1 tid=0x8c0d3988 nid=0x258e waiting onmonitor
[0x92921000..0x92921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a3f78> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a3f78> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-36" daemon prio=1 tid=0x8c0ded20 nid=0x258d waiting onmonitor
[0x92721000..0x92721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a39a8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a39a8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-35" daemon prio=1 tid=0x8c0de2d8 nid=0x258c waiting onmonitor
[0x92521000..0x92521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a33d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a33d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-34" daemon prio=1 tid=0x8c0cd528 nid=0x258b waiting onmonitor
[0x92321000..0x92321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2e08> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2e08> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-33" daemon prio=1 tid=0x8c0ccae0 nid=0x258a waiting onmonitor
[0x92121000..0x92121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2838> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2838> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-32" daemon prio=1 tid=0x8c075360 nid=0x2589 waiting onmonitor
[0x91f21000..0x91f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2268> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2268> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-31" daemon prio=1 tid=0x8c0837d0 nid=0x2588 waiting onmonitor
[0x91d21000..0x91d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a1c98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a1c98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-30" daemon prio=1 tid=0x8c0a5628 nid=0x2587 waiting onmonitor
[0x91b21000..0x91b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a16c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a16c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-29" daemon prio=1 tid=0x8c07aaf8 nid=0x2586 waiting onmonitor
[0x91921000..0x91921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a10f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a10f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-28" daemon prio=1 tid=0x8c0c23d0 nid=0x2585 waiting onmonitor
[0x91721000..0x91721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0b28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0b28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-27" daemon prio=1 tid=0x8c0c1988 nid=0x2584 waiting onmonitor
[0x91521000..0x91521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0558> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0558> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-26" daemon prio=1 tid=0x8c07ca00 nid=0x2583 waiting onmonitor
[0x91321000..0x91321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ff88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ff88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-25" daemon prio=1 tid=0x8c079e70 nid=0x2582 waiting onmonitor
[0x91121000..0x91121890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f9b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f9b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-24" daemon prio=1 tid=0x8c078038 nid=0x2581 waiting onmonitor
[0x90f21000..0x90f21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f3e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f3e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-23" daemon prio=1 tid=0x8c0a3298 nid=0x2580 waiting onmonitor
[0x90d21000..0x90d21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ee18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ee18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-22" daemon prio=1 tid=0x8c0e30d8 nid=0x257f waiting onmonitor
[0x90b21000..0x90b21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e848> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e848> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-21" daemon prio=1 tid=0x8c0c5948 nid=0x257e waiting onmonitor
[0x90921000..0x90921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e278> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e278> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-20" daemon prio=1 tid=0x8c0d0470 nid=0x257d waiting onmonitor
[0x90721000..0x90721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379dca8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379dca8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-19" daemon prio=1 tid=0x8c080798 nid=0x257c waiting onmonitor
[0x90521000..0x90521890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d6d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d6d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-18" daemon prio=1 tid=0x8c080648 nid=0x257b waiting onmonitor
[0x90321000..0x90321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d108> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d108> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-17" daemon prio=1 tid=0x8c032380 nid=0x257a runnable[0x90121000..0x90121890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-16" daemon prio=1 tid=0x8c0df9a8 nid=0x2579 waiting onmonitor
[0x8ff21000..0x8ff21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379c568> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379c568> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-15" daemon prio=1 tid=0x8c0a6288 nid=0x2578 waiting onmonitor
[0x8fd21000..0x8fd21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379bf98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379bf98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-14" daemon prio=1 tid=0x8c0dbd60 nid=0x2577 waiting onmonitor
[0x8fb21000..0x8fb21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b9c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b9c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-13" daemon prio=1 tid=0x8c0c8498 nid=0x2576 waiting onmonitor
[0x8f921000..0x8f921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b3f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b3f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-12" daemon prio=1 tid=0x8c0a6a28 nid=0x2575 waiting onmonitor
[0x8f721000..0x8f721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ae28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ae28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-11" daemon prio=1 tid=0x8c07d348 nid=0x2574 runnable[0x8f521000..0x8f521890]
at java.lang.System.arraycopy(Native Method)
at java.lang.String.getChars(String.java:557)
at java.lang.String.concat(String.java:1554)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:251)
at com.ebao.carcase.servlet.claim.ClaimServlet.doGet(ClaimServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-10" daemon prio=1 tid=0x8c0369b0 nid=0x2571 waiting onmonitor
[0x8f321000..0x8f321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379a288> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379a288> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-9" daemon prio=1 tid=0x8c079898 nid=0x256f waiting onmonitor [0x8f121000..0x8f121890]
at java.lang.Object.wait(Native Method)
- waiting on <53799cb8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799cb8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-8" daemon prio=1 tid=0x8c035260 nid=0x256e waiting onmonitor [0x8ef21000..0x8ef21890]
at java.lang.Object.wait(Native Method)
- waiting on <537996e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537996e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-7" daemon prio=1 tid=0x8c034510 nid=0x256d waiting onmonitor [0x8ed21000..0x8ed21890]
at java.lang.Object.wait(Native Method)
- waiting on <53799118> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799118> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-6" daemon prio=1 tid=0x8c081130 nid=0x256c waiting onmonitor [0x8eb21000..0x8eb21890]
at java.lang.Object.wait(Native Method)
- waiting on <53798b48> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798b48> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-5" daemon prio=1 tid=0x8c0c7108 nid=0x256b waiting onmonitor [0x8e921000..0x8e921890]
at java.lang.Object.wait(Native Method)
- waiting on <53798578> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798578> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-4" daemon prio=1 tid=0x8c0a4388 nid=0x256a waiting onmonitor [0x8e721000..0x8e721890]
at java.lang.Object.wait(Native Method)
- waiting on <53797fa8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797fa8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-3" daemon prio=1 tid=0x8c0367b8 nid=0x2569 waiting onmonitor [0x8e521000..0x8e521890]
at java.lang.Object.wait(Native Method)
- waiting on <537979d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537979d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-2" daemon prio=1 tid=0x8c036290 nid=0x2568 waiting onmonitor [0x8e321000..0x8e321890]
at java.lang.Object.wait(Native Method)
- waiting on <53797408> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797408> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-1" daemon prio=1 tid=0x8c0a4ee0 nid=0x2567 waiting onmonitor [0x8e121000..0x8e121890]
at java.lang.Object.wait(Native Method)
- waiting on <53796e38> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53796e38> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-0" daemon prio=1 tid=0x8c0a4550 nid=0x2566 runnable[0x8df21000..0x8df21890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.end.EndCaseServlet.service(EndCaseServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"TimeEventGenerator" daemon prio=1 tid=0x8c076008 nid=0x2565 waiting onmonitor
[0x8dd21000..0x8dd21890]
at java.lang.Object.wait(Native Method)
- waiting on <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53795330> (a weblogic.time.common.internal.TimeTable)
atweblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:141)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x8c0b34a0 nid=0x2563 waiting onmonitor
[0x8db21000..0x8db21890]
at java.lang.Object.wait(Native Method)
- waiting on <53793040> (a weblogic.security.SpinnerThread)
at java.lang.Object.wait(Object.java:415)
atweblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
4)
- locked <53793040> (a weblogic.security.SpinnerThread)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
"Signal Dispatcher" daemon prio=1 tid=0x8c0077e8 nid=0x2561 waiting onmonitor
[0..0]
"Finalizer" daemon prio=1 tid=0x8c000540 nid=0x255e waiting on monitor[0x8c2ff000..0x8c2ff890]
at java.lang.Object.wait(Native Method)
- waiting on <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
- locked <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80851f0 nid=0x255d waiting onmonitor
[0x8bf8c000..0x8bf8c890]
at java.lang.Object.wait(Native Method)
- waiting on <53720208> (a java.l -
Why my core dump file is "???? " in main process in solaris 10
why my core dump file is "???? ?" in main process in solaris 10?
and called funtion is ok , can see the name and address!
this problem is only occurent in solaris 10, not in solaris 8
for exampel, pstacking core file is :
?????(0x0034x,......)----------this function in main process
ACE_Rector::svc()(0xff3e........)this is called functionIf i recall correctly its because the binary called a function (in a library for instance) which pstack can not resolve.
.7/M. -
Why do we call an ABAP Runtime error a "Short Dump"
Hi All,
I was just working on one of the ABAP runtime errors with my technical counterpart and a question came to my mind "Why do we call an ABAP Runtime error a "Short Dump"?".
I tried asking a few friends of mine working in the technical space in SAP and they were not able to answer.
So, some one of you experts help me getting answer to this question.
Thanks in Advance.
Nitin.ABAP Runtime error is a generalized term .......... meaning the error occured while runtime.
wheare as short dump.
Short - means brief.
dump - error information from the memory
Short dumps (also called ABAP memory dumps). Short dumps occur when an ABAP program fails.
Short dumps provide basic information about which program failed and what the error was.
hope this helps. -
JVM falls down often. Why? (I have thread dump)
Good day!
Sometimes (about each two days) our production server falls down. But we can't understand why.
There is no one record in logs and stdout.
When server has falled down two days ago, I make full stack dump (kill -3). This is the link to stackdump:
http://users.g.com.ua/~vitaly_b/work/stackdump2.zip
I have writed tool that analyzes stackdump.
I've seen that there is 5 locks that are in waiting state from more than one another threads. This locks are in waiting state for some minutes.
One of this lock (0x00002b58afb89630) is never locked in stack dump, but 85 threads waits for it. How can it be???
Another 5 locks are locked with threads, that makes primitive operations for very long time. For example this thread now in java.util.HashMap.newKeyIterator, but 89 other threads are waiting for lock <0x00002b58afb85b1> for few minutes:
"http-8080-Processor1533" daemon prio=1 tid=0x00002aaab2566160 nid=0x6acb runnable
[0x000000004c410000..0x000000004c412c20]
at java.util.HashMap.newKeyIterator(HashMap.java:889)
at java.util.HashMap$KeySet.iterator(HashMap.java:921)
at java.util.HashSet.iterator(HashSet.java:154)
at net.sf.ehcache.event.RegisteredEventListeners.notifyElementExpiry(RegisteredEventListeners.java:116)
at net.sf.ehcache.Cache.remove(Cache.java:1017)
at net.sf.ehcache.Cache.searchInMemoryStore(Cache.java:829)
at net.sf.ehcache.Cache.get(Cache.java:654)
- locked <0x00002b58afb85b18> (a net.sf.ehcache.Cache)
at org.hibernate.cache.EhCache.get(EhCache.java:75)
at org.hibernate.cache.StandardQueryCache.get(StandardQueryCache.java:96)
at org.hibernate.loader.Loader.getResultFromQueryCache(Loader.java:2086)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)Other locks are waits in same state.
Stack dump analysis with my tool:
waiting to lock <xxx>::
<0x00002b58afb8bd18>: 1 times.
<0x00002b58afb9aa50>: 1 times.
<0x00002b58afb9c138>: 2 times.
<0x00002b58afb8b690>: 1 times.
<0x00002b597ae1ecf8>: 1 times.
<0x00002b58afb85b18>: 89 times.
<0x00002b58afb88548>: 1 times.
<0x00002b58afb96110>: 1 times.
<0x00002b58afb89630>: 85 times.
<0x00002b58afb8e5a0>: 1 times.
<0x00002b58afb98090>: 1 times.
<0x00002b58afbacd28>: 1 times.
<0x00002b58afb99380>: 1 times.
<0x00002b58afb9a0f8>: 1 times.
<0x00002b58afb90d48>: 1 times.
<0x00002b58a34127a8>: 4 times.
<0x00002b58b09c5138>: 29 times.
<0x00002b58afb91d18>: 1 times.
waiting on <xxx>::
<0x00002b58afbb0370>: 1 times.
<0x00002b58adae0ff8>: 1 times.
<0x00002b58adae0f48>: 1 times.
<0x00002b58adae0d38>: 1 times.
<0x00002b58afbb0518>: 1 times.
<0x00002b58adae0de8>: 1 times.
<0x00002b58af9a7ba0>: 1 times.
<0x00002b58adae0e98>: 1 times.
<0x00002b58afbaf898>: 1 times.
<0x00002b58b0930400>: 1 times.
<0x00002b58afbaff00>: 1 times.My system configuration:
jdk 1.5.0.11
tomcat 5.5.20
SuSe Linux 10.1
How can I solve this problem? Help me please!
Thanks!Good day!
Sometimes (about each two days) our production server falls down. But we can't understand why.
There is no one record in logs and stdout.
When server has falled down two days ago, I make full stack dump (kill -3). This is the link to stackdump:
http://users.g.com.ua/~vitaly_b/work/stackdump2.zip
I have writed tool that analyzes stackdump.
I've seen that there is 5 locks that are in waiting state from more than one another threads. This locks are in waiting state for some minutes.
One of this lock (0x00002b58afb89630) is never locked in stack dump, but 85 threads waits for it. How can it be???
Another 5 locks are locked with threads, that makes primitive operations for very long time. For example this thread now in java.util.HashMap.newKeyIterator, but 89 other threads are waiting for lock <0x00002b58afb85b1> for few minutes:
"http-8080-Processor1533" daemon prio=1 tid=0x00002aaab2566160 nid=0x6acb runnable
[0x000000004c410000..0x000000004c412c20]
at java.util.HashMap.newKeyIterator(HashMap.java:889)
at java.util.HashMap$KeySet.iterator(HashMap.java:921)
at java.util.HashSet.iterator(HashSet.java:154)
at net.sf.ehcache.event.RegisteredEventListeners.notifyElementExpiry(RegisteredEventListeners.java:116)
at net.sf.ehcache.Cache.remove(Cache.java:1017)
at net.sf.ehcache.Cache.searchInMemoryStore(Cache.java:829)
at net.sf.ehcache.Cache.get(Cache.java:654)
- locked <0x00002b58afb85b18> (a net.sf.ehcache.Cache)
at org.hibernate.cache.EhCache.get(EhCache.java:75)
at org.hibernate.cache.StandardQueryCache.get(StandardQueryCache.java:96)
at org.hibernate.loader.Loader.getResultFromQueryCache(Loader.java:2086)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)Other locks are waits in same state.
Stack dump analysis with my tool:
waiting to lock <xxx>::
<0x00002b58afb8bd18>: 1 times.
<0x00002b58afb9aa50>: 1 times.
<0x00002b58afb9c138>: 2 times.
<0x00002b58afb8b690>: 1 times.
<0x00002b597ae1ecf8>: 1 times.
<0x00002b58afb85b18>: 89 times.
<0x00002b58afb88548>: 1 times.
<0x00002b58afb96110>: 1 times.
<0x00002b58afb89630>: 85 times.
<0x00002b58afb8e5a0>: 1 times.
<0x00002b58afb98090>: 1 times.
<0x00002b58afbacd28>: 1 times.
<0x00002b58afb99380>: 1 times.
<0x00002b58afb9a0f8>: 1 times.
<0x00002b58afb90d48>: 1 times.
<0x00002b58a34127a8>: 4 times.
<0x00002b58b09c5138>: 29 times.
<0x00002b58afb91d18>: 1 times.
waiting on <xxx>::
<0x00002b58afbb0370>: 1 times.
<0x00002b58adae0ff8>: 1 times.
<0x00002b58adae0f48>: 1 times.
<0x00002b58adae0d38>: 1 times.
<0x00002b58afbb0518>: 1 times.
<0x00002b58adae0de8>: 1 times.
<0x00002b58af9a7ba0>: 1 times.
<0x00002b58adae0e98>: 1 times.
<0x00002b58afbaf898>: 1 times.
<0x00002b58b0930400>: 1 times.
<0x00002b58afbaff00>: 1 times.My system configuration:
jdk 1.5.0.11
tomcat 5.5.20
SuSe Linux 10.1
How can I solve this problem? Help me please!
Thanks! -
Why there is no dump(8) util in Lion?
Hi All!
Is there some way to make backup data from external HD? Previously i used dump(8) util for that but as i revealed, dump(8) no more there! Why Apple excluded some useful utils from Lion?DUMP(8) BSD System Manager's Manual DUMP(8)
NAME
dump, rdump -- filesystem backup
ALERT
UFS SUPPORT IS IN THE PROCESS OF BEING DEPRECATED.
This copy of dump is supplied only for completeness and is expected to have deficiencies.
It will likely disappear in the future. -
I want to know why display core dump when arch starts!
I want to know why display core dump when arch starts!
2008. 06 iso!
u can see display coredump in starting......GAH, you silly people!
Now I'm going to have to go off and write a program that selects a random string from a file to show on startup!
(I'll probably fill the file with all the Arch snapshot names)
EDIT: I should mention that you're silly because you managed to get me following a random compulsion.
EDIT AGAIN: Done! I now get a random snapshot name in that spot whenever my system boots. I can post the script if anyone wants it, it's three lines.
EDIT ONE LAST TIME: Oh wait, three lines and a extra file full of snapshot names.
Last edited by arew264 (2008-07-19 02:35:05)
Maybe you are looking for
-
I want to connect my IMAC to TV with HDMI cable. I did it before going to Dispaly and Arrangments and then mirror. Now when I go to display I dont have to option of arrangements. Olny {Display and Color} pops up. Any ideas what happend to arrengement
-
Reconcilation problem in sub-contracting scenario
Hai, In sub-contracting process after receiving GR, i have gone for challana reconcilation, where i am getting one error "challana material number is different from material document. please help me out
-
Spatial - SDO_AGGR_UNION question.
I have extracted geo spatial informaton from a document and created sdo_geometry objects of different types in my database. I have polygons, points, lines, ellipsis, and multipoint types of gtypes. I am trying to aggregate them using SDO_AGGR_UNION.
-
Sun One Search Engine Integration with the Fatwire Content Server
Hello everyone, I am presently using Fatwire(Divine) Content Server. I have uploaded certain documents using Fatwire flex attributes(metadata). I want to use portal search engine for implementing Full Text Search of uploaded documents. how can i map
-
Database Template File missing
Hi everyone, I'm trying to set up a installation of OCS over multiple computers. The Infrastructre installation works fine withouth any error and all services are up and running. Now I'd like to install and set up the storage database. While running