Run EEM applet on login
I am new to EEM and was wondering if it was possible to get an applet to run for a specific user when that user logins to the device? If so, which event would I be looking for?
Thanks in advance.
Joseph...thank you very much for the help. I have another question however. I am trying to piece together a very simple script that will show the running config if a particular user logs into the device. So I have this so far:
event manager applet login
event syslog pattern "Login Success \[user: testuser]"
action 1.0 cli command "enable"
action 2.0 cli command "sh run"
Once I login as "testuser" it would appear that the applet runs but not in the current session....as in testuser does not see the results. I have tried to add the following
action 3.0 puts "$_cli_result"
But again no difference. Is there a way to pipe the information to the cli session of testuser?
Thanks again!
Similar Messages
-
Problem running Java applets since Java update 2 (1.6.0_20)
Hi,
Since I upgraded to Java update 2, Java applets started having problems. The most noticeable ones are:
Non-modal windows appear behing the browser Window (tested Safari 4, 5, Chrome 5).
Double buffering not working as usual (slower, white boxes appear when dragging a window, etc.)
Slower rendering in general
The same applications run perfectly using Java Web Start. And they used to work very well also in Java update 1.
The application can be tested here (press ok if a login prompt appears):
Java applet: http://jmap3.k2geospatial.com/montreal_applet/
Java Web Start: http://jmap3.k2geospatial.com/montreal_jws/dockingClient.jnlp
Our applications running in applets use the new plug-in 2 with JNLP files.
Notice the Java startup splash (the animated sun-like logo) is not moving as smoothly as usual. It is very jerky now.
Are these problems known by anyone?
How can I downgrade Java to previous version?
sorry I cross-posted this in Unix forum also. I think it is better here.
Thank you,
Jean-Robert
K2 GeospatialSince the last Java update on mac, all my OpenGL applets stop working and now just shows a white screen on Chrome, Firefox and Opera. They was working well on all browsers (Safari/WebKit,Chrome,Firefox,Opera) just before the update.
The trouble maker seem to be the java plugin 2 and the new offscreen rendering pipeline, as reported by jrhaddad with the disucssion linked to the different Java/OpenGL community forums.
This is a huge regression for me, and I think for all hobbies/ independent developers and all companies who are doing some Java/OpenGL develoment. All our work just stop working since this update.
If would really want to know from Apple if they are working on this problem and/or how this can be solved.
Should this be fixed by Apple with a new java update, or should the various browsers must upgrade their applet support plugins according to the new java plugin 2 changes ?
Best Regards,
Jérôme -
EEM applet that triggers on high CPU utilization
Hi Folks,
I am trying to create an eem applet which triggers on high cpu utilization (detected by erm). The applet should then tftp the output from "show proc cpu sorted" to a tftp server.
I am trying to configure this on a 1841 running 124-24.T3 code
This is my config:
resource policy
policy HighGlobalCPU global
system
cpu total
critical rising 5 falling 2 interval 10
cpu process
critical rising 5 falling 2 interval 10
! I'm not sure whether it is correct to monitor 'cpu total' or 'cpu process'. The rising thresholds are deliberately low to maker testing easier
event manager applet ReportHighCPU
event resource policy "HighGlobalCPU"
action 1.0 cli command "show process cpu sorted 5sec | redirect tftp://192.168.1.1/highCPU$_resource_time_sent.txt"
action 2.0 syslog priority debugging msg "high cpu event detected, output tftp sent"
The problem is that I can't seem to trigger the applet. I have generated enough traffic to push the cpu utilization to over 30% (according to 'show proc cpu'), but the applet does not appear to trigger (no syslog messages appear, and my syslog server does not receive anything).
If anyone can tell me what I've done wrong here I would be very grateful!
Thanks,
DarraghI am just replying off the top of my head but I believe you
need to also add to your conf the line
user global HighGlobalCPU -
I am using the following applet to modify entries in two ACLs from a mobile device. Please see applet below with output from a test run:
3 applet user none Off Sun Mar 28 22:42:59 2010 rite1
policyname {rite1} sync {yes}
maxrun 60.000
action 1.0 puts "Set HostA:"
action 1.1 gets hosta
action 1.2 puts "Set HostB:"
action 1.3 gets hostb
action 1.4 cli command "enable"
action 1.5 cli command "config t"
action 1.6 cli command "ip access-list extended rite1_incoming"
action 1.7 cli command "no 10"
action 1.8 cli command "no 20"
action 1.9 cli command "10 permit ip host $hosta host $hostb"
action 2.0 cli command "20 permit ip host $hostb host $hosta"
action 2.1 cli command "ip access-list extended rite1_outgoing"
action 2.2 cli command "no 10"
action 2.3 cli command "no 20"
action 2.4 cli command "10 permit ip host $hosta host $hostb"
action 2.5 cli command "20 permit ip host $hostb host $hosta"
action 2.6 cli command "end"
action 2.7 cli command "show ip access-list | s rite1"
action 2.8 puts "$_cli_result"
action 2.9 puts ""
action 3.1 puts "-------------------------------------"
action 3.2 puts ""
action 3.3 puts "Use following packet_capture commands:"
action 3.4 puts " ritesh - show packet_capture"
action 3.5 puts " ritecl - clear packet_capture"
action 3.6 puts " ritestr - start packet_capture"
action 3.7 puts " ritestp - stop packet_capture"
action 3.8 puts ""
action 3.9 puts "-------------------------------------"
alias exec rite1 event manager run rite1
Router#rite1
Set HostA:
172.20.1.1
Set HostB:
20.1.1.1
Extended IP access list rite1_incoming
10 permit ip host 172.20.1.1 host 20.1.1.1
20 permit ip host 20.1.1.1 host 172.20.1.1
Extended IP access list rite1_outgoing
10 permit ip host 172.20.1.1 host 20.1.1.1
20 permit ip host 20.1.1.1 host 172.20.1.1
Use following packet_capture commands:
ritesh - show packet_capture
ritecl - clear packet_capture
ritestr - start packet_capture
ritestp - stop packet_capture
I use this for packet capturing with RITE on remote sites that do not warrant consistent samples. We get alerted when a specific top-talker is showing unusual high volumes of traffic and our techs are able to run the following script on the fly from mobile devices. The high-volume converstaion gets captured and we have another script that exports those onboard captures to centralized servers. The whole operation runs pretty great. The problem is that for some reason it eats a TON of process usage.
117852: Mar 28 23:03:54.197 DST: %SYS-1-CPURISINGTHRESHOLD: Threshold: Total CPU Utilization(Total/Intr): 72%/1%, Top 3 processes(Pid/Util): 199/71%, 49/0%, 81/0%
117865: Mar 28 23:04:09.128 DST: %SYS-1-CPUFALLINGTHRESHOLD: Threshold: Total CPU Utilization(Total/Intr) 1%/0%.
I"m assuming that process # 199 is dynamically created for this specific applet when it runs, as it does not seem to run on the routers at other times:
Router#show process cpu
....output omitted....
198 0 3 0 0.00% 0.00% 0.00% 0 EEM ED RPC
201 14371 99291 144 0.00% 0.00% 0.00% 0 DHCPD Receive
....output omitted....
For some reason, while the router is interacting with the user, waiting for input from the "action x.x get" commands, the processer is through the roof. Any ideas on how I could run this similar operation without taking up so much process overhead? I want to say that I could probably limit the resource usage of those specific processes maybe with ERM, but I'm currently not very familiar with ERM. Thanks for everyone's help.Joe,
Thanks so much for converting our applet into a tcl script. It works great everywhere that we have deployed it. We did run into one issue deploying on a 3745 Router with 12.4(15)T9. When the policy was triggered, we received the following error:
error reading "stdin": Unknown error 134217728
while executing
"gets stdin"
invoked from within
"$slave eval $Contents"
(procedure "eval_script" line 7)
invoked from within
"eval_script slave $scriptname"
invoked from within
"if {$security_level == 1} { #untrusted script
interp create -safe slave
interp share {} stdin slave
interp share {} stdout slave
(file "tmpsys:/lib/tcl/base.tcl" line 50)
Tcl policy execute failed: error reading "stdin": Unknown error 134217728
Tcl policy execute failed: error reading "stdin": Unknown error 134217728
I also pulled the specific script that it's referencing the error from:
# base.tcl - Safe base script forinvoking safe-tcl on FM policies.
# August 2002, Jason Pfeifer
# Copyright (c) 2002, 2004-2006 bycisco Systems, Inc.
# All rights reserved.
# Current security levels:
# 0 - trusted script, safe mode not enabled
# 1 - untrusted script, safe modeenabled
#################### Procedures ##################
proc TraceVariable { fromInterp fromVartoInterp toVar } {
set value [ interp eval $fromInterpset ::$fromVar]
interp eval $toInterp [list set::$toVar $value]
proc eval_script { slave scriptname } {
# Open script and evaluate it in slave
set F [open $scriptname]
set Contents [read $F]
close $F
$slave eval $Contents
#################### End of Procedures ##################
# main
# Process argv input:
set scriptname [lindex $argv 0]
set security_level [lindex $argv 1]
if {$security_level != 0 && $security_level != 1} {
set security_level 1
#Set Security level specific parameters
set errorInfo ""
set FM_TCLLIBDIR [info library]
if {$security_level == 1} { #untrusted script
interp create -safe slave
interp share {} stdin slave
interp share {} stdout slave
interp share {} stderr slave
lappend global_vars auto_path
lappend global_vars auto_oldpath
lappend global_vars tcl_library
foreach entry [info vars] {
if [array exists $entry] {
continue
if {[lsearch -exact$global_vars $entry] >= 0} {
continue;
TraceVariable {} $entry slave$entry
# uncomment to debug safe.tcl
#::safe::setLogCmd puts stderr
::safe::interpInit slave
# Hidden commands that are exposed to slave to ease restrictions.
interp alias slave exit {} exit
interp expose slave fconfigure
interp expose slave socket
eval_script slave $scriptname
close stdin
close stdout
close stderr
::safe::interpDelete slave
} else { #trusted script
interp create slave
interp share {} stdin slave
interp share {} stdout slave
interp share {} stderr slave
foreach entry [info vars] {
if [array exists $entry] {
continue
TraceVariable {} $entry slave$entry
if {[catch {::interp eval slave\
{source [file join$FM_TCLLIBDIR init.tcl]}} msg]} {
error "can't sourceinit.tcl into slave ($msg)"
eval_script slave $scriptname
interp delete slave
What ended up happening is the script stayed stuck in pending(no 'scheduler' commands in this early version of eem) and we eventually had to reboot the router(we waited until a regularly scheduled maintenance window, so it worked out fine). Since receiving this error, we haven't tried to run this particular script on this particular router. All other devices that we have deployed this on, including other 3745's running 12.4(15)T, have worked great. If anyone has some idea as to exactly what happened and what adjustments we need to perform to correct the problem, we would greatly appreciate it.
Thanks again for everyone's help. -
EEM Applet - Interface bandwidth utilization
We are planning to get syslog or snmp alert for bandwidth utilization of Uplinks by EEM applet, can any bdy help me on that?
We managed to get alert for input traffic but we are not able to get alert for total bandwidth utilization ( input + output ).This is possible with an EEM applet. I have done it on G1 ISRs with 15.1. The applet is here:
http://ephemeralportal.blogspot.jp/2014/01/eem-applet-teach-your-router-to-monitor_24.html
I usually run 12.4 on 3745s in GNS3 and they do not have the action set to do variable manipulation, so I am guessing that this is a newer feature, although I could not find what minimum version you would need on a quick search. -
Hi,
I have a scenario where i would like to execute a EEM applet for running an ip sla event when othe ip sla event is up. Just to summarize an IP sla event success should trigger anothe IP sla event. I have tried the two options below but was not able to find any debug logs.
ip sla 10
icmp-jitter x.x.x.x source-ip x.x.x.x num-packets 10
frequency 30
ip sla schedule 10 life forever start-time now
ip sla 20
icmp-jitter x.x.x.x source-ip x.x.x.x num-packets 10
frequency 30
event manager applet SLA
event timer cron cron-entry "5 * * * *"
event ipsla operation-id 10 reaction-type timeout
action 10 if $_ipsla_condition eq "Occurred"
action 15 cli command "enable"
action 20 cli command "configure term"
action 25 cli command "no ip sla schedule 20 life forever start-time now"
action 30 else
action 35 cli command "enable"
action 40 cli command "configure term"
action 45 cli command "ip sla schedule 20 life forever start-time now"
action 50 end
OR
ip sla 10
icmp-jitter x.x.x.x source-ip x.x.x.x num-packets 10
frequency 30
ip sla schedule 10 life forever start-time now
ip sla 20
icmp-jitter y.y.y.y source-ip y.y.y.y num-packets 10
frequency 30
track 1 ip lsa reachability
event manager applet SLA-1
event timer cron cron-entry "5 * * * *"
event track 1 state up
action 10 cli command "enable"
action 20 cli command "conf t"
action 30 cli command "ip sla schedule 20 life forever start-time now"
action 40 cli command "end"
event manager applet SLA-2
event timer cron cron-entry "5 * * * *"
event track 1 state down
action 10 cli command "enable"
action 20 cli command '' conf t"
action 30 cli command "no ip sla schedule 20 life forever start-time now"
action 40 cli command "end"
Regards,
Sathvik K VHi Joseph,
I would like to run the script pasted below during buisness hours(9am to 6pm). When two if conditions are used is it the first condition is checked and if that passes it will check the second condition.
event manager applet APP-1
event track 1 state up
action 001 cli command "enable"
action 002 cli command "show clock"
action 003 regexp "([0-9]+):[0-9]:[0-9]" $_cli_result match hour
action 004 if $hour ge 9
action 005 cli command "conf t"
action 006 cli command "ip sla 2"
action 007 cli command "icmp-echo x.x.x.x source-ip x.x.x.x"
action 008 cli command "frequency 30"
action 009 cli command "ip sla schedule 2 life forever start-time now"
action 010 end
action 011 if $hour le 18
action 012 cli command "ip sla 2"
action 013 cli command "icmp-echo x.x.x.x source-ip x.x.x.x"
action 014 cli command "frequency 30"
action 015 cli command "ip sla schedule 2 life forever start-time now"
action 016 end
event manager applet APP-2
event track 1 state down
action 10 cli command "enable"
action 20 cli command "conf t"
action 30 cli command "no ip sla 2"
action 40 cli command "end"
Regards,
Sathvik -
Need help in executing EEM applet only once
Do we have any sample script for EEM applet counter ? We want applet to execute once after reload after matching a string . We tried couple of solutions like “ server suspend “( customer does not like server suspend) and event counter ( this does not allow syslog string matching ). Please let me know if there are any options.
At the router reload, match the string , bring down the interface and run this applet only once . I have been trying multiple messages in Bootup log for this for bringing the interface down.
The issue we are facing is that most of the bootup log messages can be triggered when the router is up as well which will result in triggering of the applet which is what we want to avoid.
event manager applet Interface_down
event syslog pattern "SPA removed from subslot 0/0"
trigger delay 10
action 1.0 cli command "enable"
action 1.5 cli command "config t"
action 2.0 cli command "interface gi0/0/0"
action 2.5 cli command "shutdown"
action 3.0 cli command "end"
event manager applet Interface_up
event syslog pattern "Bulk Sync succeeded"
trigger delay 100
action 1.0 cli command "enable"
action 1.5 cli command "config t"
action 2.0 cli command "interface gi0/0/0"
action 2.5 cli command "no shutdown"
action 3.0 cli command "end"
endThis is a bit dirty but you can create an applet to run at startup that creates the event detection applet. Then at the end of the detection applet, have it remove itself from the running config. This means that the applet running at startup will always create the event detection applet but the event detection applet will only ever run once for that router boot period as it deletes itself after first run.
The problem is that when you want to have one applet create another applet, you have issues with the inverted commas being correctly configured for the second applet which will cause it to run once, but fail after that. The way you can get around this is to write the applet to a text file on the flash and then copy the contents of the text file to the running config at boot. This preserves the structure of the applet being created and ensures that it will function correctly.
The following example builds the event detection applet at system restart (BUILDAPPLET) by copying the file "eventapplet.txt" to running config. The event detection applet (EVENTDETECT) detects a syslog pattern, in this case exiting global config, and runs the applet sending a puts command and outputting HELLO. The event detection applet then removes itself from the running config.
!# configure the router
conf t
!# turn off file prompting to let the BUILDAPPLET run when copying
file prompt quiet
!# create the applet that runs at system restart and copies the flash applet to the running config
event manager applet BUILDAPPLET
event syslog pattern "%SYS-5-RESTART"
action 10 cli command "en"
action 11 cli command "copy flash:eventapplet.txt running-config"
!# exit
end
!######## Create the flash file containing your run once applet ########
! enter the tclsh so we can write our applet to a file - put your event detection applet in here between the {} that you want to run once
tclsh
puts [open "flash:eventapplet.txt" w+] {
event manager applet EVENTDETECT
event syslog pattern "%SYS-5-CONFIG_I"
action 1.0 puts "HELLO"
action 2.0 cli command "en"
action 3.0 cli command "conf t"
action 4.0 cli command "no event manager applet EVENTDETECT" -
As i am going to configure EEM applet for TFTP backup on my cisco production device, I want to know weather there are any drawbacks of EEM applet like resources consumtion etc.
Hi Joseph,
I am going to use below applet for Automatic TFTP backup.
action 1 cli command "enable"
action 2 cli command "configure terminal"
action 3 cli command "file prompt quiet"
action 4 cli command "end"
action 5 cli command "copy running-config tftp://tftp-server/router-confg"
action 6 cli command "configure terminal"
action 7 cli command "no file prompt quiet"
action 8 cli command "end"
Do I need to take any precautions during this applet configuration ? -
How to run an applet(in a html file) in the server?
I am using the jpedal Viewer inmy code, I embedded the applet code
in a html file , it is running fine, but when I try to run the same Viewer applet in the Server it is throwing an error
"java.lang.NoClassDefFoundError: org/jpedal/objects/acroforms/DefaultAcroRenderer
at org.jpedal.PdfDecoder.startup(Unknown Source)
at org.jpedal.PdfDecoder.<init>(Unknown Source)
at pdfViewer.PdfApplet.init(PdfApplet.java:199)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)"
What is the problem ?
Please suggest solution for it?
Its urgentI am trying to run the Applet in Tomcat server,
Could you post the code where you invoke the Applet? It sounds like you're saying you're trying to run the Applet as part of your server-side code. The other interpretation is that you are simply accessing the Applet through the browser that happens to be on the machine being used as the server.
Like I say, post the code that shows how you're trying to use the Applet "on the server". -
Crashes when running Java Applets and trying to open Security System Preferences
Browser crashes when trying to run Java Applets, I've tried 4 different browsers. This is the crash report.
Process: java [90472]
Path: /usr/bin/java
Identifier: com.apple.javajdk16.cmd
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: Google Chrome Helper EH [90460]
Date/Time: 2012-02-17 15:04:44.693 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 9110 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 43908 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: DFA20D26-FD7E-4507-AAA9-EBF29199EC56
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 31 Java: Thread-11
Application Specific Information:
Java information:
Exception type: Bus Error (0xa) at pc=00000000
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.4-b02-402 mixed mode macosx-amd64)
Current thread (102a13000): JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
Stack: [124283000,124383000]
Java Threads: ( => current thread )
126525000 JavaThread "Thread-26" daemon [_thread_blocked, id=878407680, stack(1344b7000,1345b7000)]
126524000 JavaThread "Thread-25" daemon [_thread_in_native, id=877346816, stack(1343b4000,1344b4000)]
102f20800 JavaThread "Thread-21" daemon [_thread_blocked, id=636690432, stack(125e32000,125f32000)]
102b96000 JavaThread "Thread-20" daemon [_thread_in_native, id=550666240, stack(120ca8000,120d28000)]
102b95000 JavaThread "Thread-19" daemon [_thread_blocked, id=632483840, stack(125a2f000,125b2f000)]
1261e6000 JavaThread "Java Sound Event Dispatcher" daemon [_thread_blocked, id=591368192, stack(1232f9000,1233f9000)]
10191b800 JavaThread "Thread-15" daemon [_thread_blocked, id=611905536, stack(12468f000,12478f000)]
1029c7800 JavaThread "Thread-14" daemon [_thread_blocked, id=610844672, stack(12458c000,12468c000)]
102b11000 JavaThread "Thread-13" daemon [_thread_blocked, id=609783808, stack(124489000,124589000)]
101929000 JavaThread "Thread-12" daemon [_thread_blocked, id=608722944, stack(124386000,124486000)]
=>102a13000 JavaThread "Thread-11" daemon [_thread_in_Java, id=607662080, stack(124283000,124383000)]
1029d2000 JavaThread "Poller SunPKCS11-Darwin" daemon [_thread_blocked, id=541855744, stack(1203c1000,1204c1000)]
101a43800 JavaThread "thread applet-Rs2Applet.class-1" [_thread_blocked, id=534294528, stack(11fc8b000,11fd8b000)]
102a07800 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=527765504, stack(11f651000,11f751000)]
102878000 JavaThread "JVM[id=0]-Heartbeat" daemon [_thread_blocked, id=490639360, stack(11d2e9000,11d3e9000)]
101943000 JavaThread "AWT-EventQueue-2" [_thread_blocked, id=494882816, stack(11d6f5000,11d7f5000)]
102933000 JavaThread "Applet 1 LiveConnect Worker Thread" [_thread_blocked, id=466014208, stack(11bb6d000,11bc6d000)]
101933800 JavaThread "Browser Side Object Cleanup Thread" [_thread_blocked, id=191471616, stack(10b59a000,10b69a000)]
101944000 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=493821952, stack(11d5f2000,11d6f2000)]
1029ae800 JavaThread "CacheCleanUpThread" daemon [_thread_blocked, id=492761088, stack(11d4ef000,11d5ef000)]
102a04800 JavaThread "CacheMemoryCleanUpThread" daemon [_thread_blocked, id=491700224, stack(11d3ec000,11d4ec000)]
102b2e000 JavaThread "SysExecutionTheadCreator" daemon [_thread_blocked, id=489578496, stack(11d1e6000,11d2e6000)]
1018e6800 JavaThread "Java Plug-In Pipe Worker Thread (Client-Side)" daemon [_thread_in_native, id=464945152, stack(11ba68000,11bb68000)]
101a46800 JavaThread "AWT-Shutdown" [_thread_blocked, id=463884288, stack(11b965000,11ba65000)]
101934800 JavaThread "AWT-AppKit" daemon [_thread_in_native, id=1896107200, stack(7fff5f400000,7fff5fc00000)]
101933000 JavaThread "Timer-0" [_thread_blocked, id=190410752, stack(10b497000,10b597000)]
1018cd000 JavaThread "traceMsgQueueThread" daemon [_thread_blocked, id=188145664, stack(10b26e000,10b36e000)]
102853000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=172019712, stack(10a30d000,10a40d000)]
102852800 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=170958848, stack(10a20a000,10a30a000)]
102851800 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=169897984, stack(10a107000,10a207000)]
102851000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=168837120, stack(10a004000,10a104000)]
102850000 JavaThread "Surrogate Locker Thread (Concurrent GC)" daemon [_thread_blocked, id=167776256, stack(109f01000,10a001000)]
102842800 JavaThread "Finalizer" daemon [_thread_blocked, id=162287616, stack(1099c5000,109ac5000)]
102841800 JavaThread "Reference Handler" daemon [_thread_blocked, id=161226752, stack(1098c2000,1099c2000)]
101801000 JavaThread "main" [_thread_blocked, id=5246976, stack(100401000,100501000)]
Other Threads:
10283d000 VMThread [stack: 1097bf000,1098bf000] [id=160165888]
10285d000 WatcherThread [stack: 10a410000,10a510000] [id=173080576]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
par new generation total 19136K, used 9943K [7eae00000, 7ec2c0000, 7ece00000)
eden space 17024K, 46% used [7eae00000, 7eb5a5ec8, 7ebea0000)
from space 2112K, 100% used [7ec0b0000, 7ec2c0000, 7ec2c0000)
to space 2112K, 0% used [7ebea0000, 7ebea0000, 7ec0b0000)
concurrent mark-sweep generation total 144152K, used 110056K [7ece00000, 7f5ac6000, 7fae00000)
concurrent-mark-sweep perm gen total 62268K, used 37524K [7fae00000, 7feacf000, 800000000)
Code Cache [103801000, 104192000, 106801000)
total_blobs=2217 nmethods=1445 adapters=734 free_code_cache=40529280 largest_free_block=47360
Virtual Machine Arguments:
JVM Args: -D__jvm_launched=1329508711033330 -Xbootclasspath/a:/System/Library/Frameworks/JavaVM.framework/Resources/Deploy. bundle/Contents/Resources/Java/deploy.jar:/System/Library/Frameworks/JavaVM.fram ework/Resources/Deploy.bundle/Contents/Resources/Java/javaws.jar:/System/Library /Frameworks/JavaVM.framework/Resources/Deploy.bundle/Contents/Resources/Java/plu gin.jar -Djava.applet.host=world8.runescape.com -Dapple.awt.UIElement=true -Dsun.awt.warmup=true -Xmx256m -Xss1m -Xincgc -XX:+UseConcMarkSweepGC -Dsun.java2d.noddraw=true
Java Command: sun.plugin2.main.client.PluginMain write_pipe_name=/var/folders/Aa/Aa4dzX7xHJmbzy55DpvyiE+++TI/-Tmp-/.java.deploy. 90460.994108354874315847
Launcher Type: SUN_STANDARD
Physical Memory: Page Size = 4k, Total = 3840M, Free = 774M
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff864f2902 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff864f1d8f CFRunLoopRunSpecific + 575
4 com.apple.HIToolbox 0x00007fff857827ee RunCurrentEventLoopInMode + 333
5 com.apple.HIToolbox 0x00007fff857825f3 ReceiveNextEventCommon + 310
6 com.apple.HIToolbox 0x00007fff857824ac BlockUntilNextEventMatchingListInMode + 59
7 com.apple.AppKit 0x00007fff85ae6eb2 _DPSNextEvent + 708
8 com.apple.AppKit 0x00007fff85ae6801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
9 libawt.jnilib 0x000000010b6f1f0d -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 124
10 com.apple.AppKit 0x00007fff85aac68f -[NSApplication run] + 395
11 libawt.jnilib 0x000000010b69e19c +[AWTStarter startAWT:] + 1495
12 libawt.jnilib 0x000000010b69db16 -[CPerformer perform] + 93
13 com.apple.Foundation 0x00007fff8357745f __NSThreadPerformPerform + 219
14 com.apple.CoreFoundation 0x00007fff864f43d1 __CFRunLoopDoSources0 + 1361
15 com.apple.CoreFoundation 0x00007fff864f25c9 __CFRunLoopRun + 873
16 com.apple.CoreFoundation 0x00007fff864f1d8f CFRunLoopRunSpecific + 575
17 java 0x000000010000483f 0x100000000 + 18495
18 java 0x0000000100004296 0x100000000 + 17046
19 java 0x0000000100001a94 0x100000000 + 6804
Thread 1:
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x000000010380685a 0 + 4353714266
13 ??? 0x000000010380685a 0 + 4353714266
14 ??? 0x0000000103801438 0 + 4353692728
15 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
16 libclient64.dylib 0x00000001010a4f16 JVM_Lseek + 192613
17 libclient64.dylib 0x00000001010c8e0e JVM_FindLoadedClass + 3186
18 libclient64.dylib 0x00000001010c8cb6 JVM_FindLoadedClass + 2842
19 java 0x0000000100002cef 0x100000000 + 11503
20 java 0x000000010000323c 0x100000000 + 12860
21 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
22 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 2: Java: Exception Handler Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libSystem.B.dylib 0x00007fff8864aa17 mach_msg_server + 468
3 libclient64.dylib 0x000000010100e7cb jio_snprintf + 41425
4 libclient64.dylib 0x000000010100e683 jio_snprintf + 41097
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 3: Java: Gang worker#0 (Parallel GC Threads)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101025fa4 jio_vsnprintf + 312
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 4: Java: Gang worker#1 (Parallel GC Threads)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101025fa4 jio_vsnprintf + 312
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 5: Java: Concurrent Mark-Sweep GC Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x0000000101302097 JVM_Timeout + 883428
8 libclient64.dylib 0x000000010122803c JVM_Yield + 40397
9 libclient64.dylib 0x000000010122783d JVM_Yield + 38350
10 libclient64.dylib 0x00000001012277af JVM_Yield + 38208
11 libclient64.dylib 0x000000010122764e JVM_Yield + 37855
12 libclient64.dylib 0x00000001012273eb JVM_Yield + 37244
13 libclient64.dylib 0x000000010121edca JVM_Yield + 2907
14 libclient64.dylib 0x000000010102c3dc jio_vsnprintf + 25968
15 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
16 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
17 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 6: Java: VM Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x000000010102c54a jio_vsnprintf + 26334
4 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
5 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
6 libclient64.dylib 0x00000001010a3f8f JVM_Lseek + 188638
7 libclient64.dylib 0x00000001010a3cdf JVM_Lseek + 187950
8 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
9 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
10 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 7: Java: Reference Handler
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x00000001039622d4 0 + 4355138260
10 ??? 0x0000000103801438 0 + 4353692728
11 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
12 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
13 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
14 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
15 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
16 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
17 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
18 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
19 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 8: Java: Finalizer
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 9: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff885e6c0a kevent + 10
1 libSystem.B.dylib 0x00007fff885e8add _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff885e87b4 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff885e82de _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff885e7c08 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff885e7aa5 start_wqthread + 13
Thread 10: Java: Surrogate Locker Thread (Concurrent GC)
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c2261 JVM_IsPrimitiveClass + 6521
8 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
9 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
10 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
11 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
12 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 11: Java: Signal Dispatcher
0 libSystem.B.dylib 0x00007fff885cddb6 semaphore_wait_trap + 10
1 libclient64.dylib 0x00000001010c2aa3 JVM_IsPrimitiveClass + 8635
2 libclient64.dylib 0x00000001010c252a JVM_IsPrimitiveClass + 7234
3 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
4 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 12: Java: C2 CompilerThread0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c9319 JVM_Write + 346
8 libclient64.dylib 0x00000001010c3913 JVM_IsPrimitiveClass + 12331
9 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
10 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
11 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
12 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
13 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 13: Java: C2 CompilerThread1
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d10a jio_snprintf + 35600
7 libclient64.dylib 0x00000001010c9319 JVM_Write + 346
8 libclient64.dylib 0x00000001010c3913 JVM_IsPrimitiveClass + 12331
9 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
10 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
11 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
12 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
13 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 14: Java: Low Memory Detector
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x000000010100d722 jio_snprintf + 37160
5 libclient64.dylib 0x000000010100d2fd jio_snprintf + 36099
6 libclient64.dylib 0x000000010100d1a3 jio_snprintf + 35753
7 libclient64.dylib 0x00000001010c5318 JVM_IsPrimitiveClass + 18992
8 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
9 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
10 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
11 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
12 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 15: Java: VM Periodic Task Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x00000001011afc26 JVM_GetClassInterfaces + 11348
4 libclient64.dylib 0x00000001010c73a7 JVM_IsPrimitiveClass + 27327
5 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
6 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 16: Java: traceMsgQueueThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 17: Java: Timer-0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x000000010380685a 0 + 4353714266
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 18: Java: AWT-Shutdown
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 19: Java: Java Plug-In Pipe Worker Thread (Client-Side)
0 libSystem.B.dylib 0x00007fff885d8466 read + 10
1 libdeploy.jnilib 0x0000000109d4d5d9 Java_com_sun_deploy_net_socket_UnixSocketImpl_unStreamSocketRead + 140
2 ??? 0x0000000103811d6e 0 + 4353760622
3 ??? 0x000000010380696e 0 + 4353714542
4 ??? 0x000000010380696e 0 + 4353714542
5 ??? 0x000000010380696e 0 + 4353714542
6 ??? 0x000000010380696e 0 + 4353714542
7 ??? 0x000000010386d2b4 0 + 4354134708
8 ??? 0xfda21644ff67b8d7 0 + 18276194723421468887
Thread 20: Java: SysExecutionTheadCreator
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103801438 0 + 4353692728
12 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
13 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
14 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
15 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
16 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
17 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
18 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
19 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
20 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 21: Java: CacheMemoryCleanUpThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 22: Java: CacheCleanUpThread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103801438 0 + 4353692728
12 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
13 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
14 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
15 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
16 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
17 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
18 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
19 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
20 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 23: Java: AWT-EventQueue-0
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x0000000103aaac60 0 + 4356484192
Thread 24: Java: Browser Side Object Cleanup Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 25: Java: Applet 1 LiveConnect Worker Thread
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103811d6e 0 + 4353760622
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x000000010380685a 0 + 4353714266
11 ??? 0x0000000103806d34 0 + 4353715508
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 26: Java: AWT-EventQueue-2
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d903 jio_snprintf + 37641
3 libclient64.dylib 0x000000010100d7c3 jio_snprintf + 37321
4 libclient64.dylib 0x00000001010b2597 JVM_MonitorWait + 4001
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x0000000103aaac60 0 + 4356484192
Thread 27: Java: JVM[id=0]-Heartbeat
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_msg + 59
2 libclient64.dylib 0x000000010100d995 jio_snprintf + 37787
3 libclient64.dylib 0x000000010102c54a jio_vsnprintf + 26334
4 libclient64.dylib 0x00000001010b25a1 JVM_MonitorWait + 4011
5 libclient64.dylib 0x00000001010b1a24 JVM_MonitorWait + 1070
6 libclient64.dylib 0x00000001010b1690 JVM_MonitorWait + 154
7 libjvmlinkage.dylib 0x0000000100093b9b JVM_MonitorWait + 59
8 ??? 0x0000000103a3d848 0 + 4356036680
9 ??? 0x000000010380685a 0 + 4353714266
10 ??? 0x00000001038069b3 0 + 4353714611
11 ??? 0x00000001038069b3 0 + 4353714611
12 ??? 0x0000000103801438 0 + 4353692728
13 libclient64.dylib 0x00000001010a5152 JVM_Lseek + 193185
14 libclient64.dylib 0x00000001010b11dc JVM_StartThread + 2565
15 libclient64.dylib 0x00000001010b10d2 JVM_StartThread + 2299
16 libclient64.dylib 0x00000001010b1072 JVM_StartThread + 2203
17 libclient64.dylib 0x00000001010b0f14 JVM_StartThread + 1853
18 libclient64.dylib 0x00000001010b0d29 JVM_StartThread + 1362
19 libclient64.dylib 0x000000010100d264 jio_snprintf + 35946
20 libSystem.B.dylib 0x00007fff88606fd6 _pthread_start + 331
21 libSystem.B.dylib 0x00007fff88606e89 thread_start + 13
Thread 28: Java: Java2D Disposer
0 libSystem.B.dylib 0x00007fff885cdd7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff885ce3ed mach_mDid you get this fixed? I have had this error everytime I try to access my bank, inventory, and ither things. Please help.
-
Why cant i run my applet on JRE 1.6 but on JRE 1.5?
Hello,
I know this is a very basic problem, but i still cannot get a justified answer for this problem. Its like i have an applet which is compiled in JDk j2sdk1.4.2_16. Now when i try to run this applet on my IE under jre 1.5.* family on all the client machines it works fine. But when i switch to jre 1.6.* family, i see the applet being displayed, but i cannot perform any operations on it i no mouse clicks work and i cannot open any file menu or my jdialog boxes.
Is it because of the incompatibilities in jre 1.6, but wont it be backward compatible to that older version applets can run on this new jre. My applet seems to be a simple applet,with only one exception that it has lot of jframes and jpanel in it.
This problem is killing me ..
Can someone point me towards where can i find what all changes are made in JRE 1.6 over JRE 1.5 so that atleast i can compare what is causing my applet freeze in JRE 1.6.
i went through the release notes but cant find anything useful there.
Please help.Sun ensures that newer versions of the JRE are backward compatible. Your applet should work under the newest JRE version. Have you tried running the applet in a different browser (e.g., Firefox) with JRE 1.6 to eliminate it being an IE issue?
-
HOw to run the Applet in dos mode
how to run the applet in Command Prompt(DOS).
I have save this in directory D/vijay/javap/A.java and my JDK is in C drive.
Plz send me reply as soon as possible.
My code is :-
import java.applet.*;
import java.awt.*;
public class A extends Applet
private int w, h;
public void init( )
w = 45;
h = 50;
public void paint(Graphics g)
g.drawRect(w, h, 20, 80);
}import java.applet.*;
import java.awt.*;
public class A extends Applet
private int w, h;
public void init( )
w = 45;
h = 50;
public void paint(Graphics g)
g.drawRect(w, h, 20, 80);
<applet class="A" height="200" width="200" code="A.class">
</applet>
*/And in command prompt
javac A.java
appletviewer A.java
Message was edited by:
passion_for_java -
How do I run an applet in full size of browser window?
When I run an applet in the browser, I have to specify the width and height for the applet. How do I tell the applet to use the full size of browser window?
Does anybody have experience on it?
Thanks!Guys,
I have found a solution already. The key is to specify percentage in width and height value. For example, width="100%" height="100%". There you go!
Jet Wu -
EEM Applet Problem With: event syslog pattern ".*" priority 2
I went to create a EEM applet that would be invoked whenever any syslog message of priority 0-2 was invoked. I figured the following event statement would work
event syslog pattern ".*" priority 2
I never really used the priority optional argument before but thought I understood from the docs that messages at or numerically lower than the specified level are matched.
Well it doesn't seem to work as documented. Seems to me that only messages at the specified level are beng matched and not messages numerically lower than the specified level.
Anyway I did what I wanted differently but wanted to post this in case this is a bug in the syslog ed.Actually, it's a problem with the documentation. The priority option only matches the specified severity. What you could do is adjust pattern to do this:
event syslog pattern "*-[012]-" -
Problems running java applet in 1.4.2
Hi,
I need some help with running an applet in the following environment:
Win 98 ver 2
jre 1.4.2
IE 6.0
My applet runs in AOL within the same environment. However, the one we wrote does not run in this at all. I get the characteristic grey patch. Additionally, even the 1.4.2 test applets do not run in my environment. I get status messages like "load:class LoadUpload_100 not found".
I need to mention that 1.2 applets run in the same environment without any issues.
Any help on this will be greatly appreciate.
Thanks,
Akoul.
[email protected]If you use Swing, you will need to convert your HTML using Sun's HTML converter.
Maybe you are looking for
-
Parameter attributes FM / Passing check box from FM ?
Hi Experts, I hv a check box in Selection screen. I wanna to pass either ' ' or 'X' values from Z FM. So, I defined the check box as RSPARAMS in FM ( and also tried with defining locally as DATA: CHECK_BOX.) I tried like, 1st case, SELNAME - check_b
-
Iphone cant recognize router, HELP!!!
I have a Wireless G Broadband router, the model number is wrt54g2. I also have iPhone 3G. I never had problems with my iPhone and I was always able to connect to wifi until today. For some reason my iphone wont recognize my router, it tells me "CANT
-
Oracle instance always in 'shutdown' phase one day after installation
I have Windows 2003 Server (SP1) and Oracle database 10g release 2 installed. On the installation day, after completing the installation everything worked just fine. One day after that and on, everytime I boot up my OS the Oracle database instance is
-
I want to upgrade to iPhoto 9.4.3 from 8.1.2 but am concerned about losing photos as posted on various discussion sites. Is it safe to simply download the latest version from the App Store? Thank you.
-
Access a received message after transformation
Hi, in my BPM, i am receiving an Idoc transfor it make a BAPI Call. this works fine. After this i want to transform the BAPI-response and the original IDoc to a new message for the next BAPI-Call. But i have no data in this original IDOC. I created a