Rogue AP: Question
I need a bit of info with the below topics.
Q1. What is a Rogue AP?
Q2. WLC 4400 is detecting a number of rogue access points from neighboring buildings. How should the WLC 4400 deal with these rogue access points?
Q3. Can the WLC 4400 block these accees points from broadcasting their SSID's into our air space?
Regards,
Colm
For the Clases, you have the ability to define what criteria must be met for a roge to be called friendly or malicious. Under the Security tab > Wireless Protection Policy, Rogue Policies, Rogue Rules.
Class Type:
unclassified <--- AP detected but not matching any policy
friendly <--- AP matches the criteria of a friendly AP
malicious <--- AP matches the criteria of a malicious AP
Update Status:
Contain <--Contain the AP, uses our own AP to spoof the AP to get the clients to join "us" instead of "them" , once again, you need to be real careful with this, as if you are containing your neighbors, there can be reprocussions
Alert <-- Just a message saying there is a rogue
Similar Messages
-
have set up the rogue app process to kill what is not listed in the exception list, everything seem to be working except for a few apps that are getting terminated even though they are listed in the exception list. rundll32.exe is the main problem although there have been one or two others. Also have one app that is not in the exception list that does not get killed (starcraft.exe). the program is launched by a different exe but loads starcraft.exe as the process. is there something else I need to look at?
this is the registry:
[HKEY_CURRENT_USER\Software\NetWare\NAL\1.0\process management]
"default action"=dword:00000001
"report ignored"=dword:00000000
"report terminated"=dword:00000001
[HKEY_CURRENT_USER\Software\NetWare\NAL\1.0\process management\exception list]
"rundll32.exe"=dword:00000000
zen ver 6.5, workstions are xp sp2
Reply With Quoteblowder,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/ -
I have 2 controllers 2106 both with the same mobility group, I have 3 APs in one controller and 3 APs on the other. I have just one rogue detector. Do I need a rogue detector on both or just in one controller?
Rogue detection is not bound by any regulations and no legal adherence is required for its operation. However, rogue containment usually introduces legal issues that can put the infrastructure provider in an uncomfortable position if left to operate automatically. Cisco is extremely sensitive to such issues and provides these solutions. Each controller is configured with a RF Group name.Once a Lightweight AP registers with a controller, it embeds an authentication Information Element (IE) that is specific to the RF Group configured on the controller in all its beacons/probe response frames. When the Lightweight AP hears beacons/ probe response frames from an AP either without this IE or with wrong IE, then the Lightweight AP reports that AP as a rogue, records its BSSID in a rogue table, and sends the table to the controller. There are two methods, namely Rogue Location Discovery Protocol (RLDP) and passive operation. These two are described in detail in the link below.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_white_paper09186a0080722d8c.shtml
As you can see from above all APs listen for rogues based on the above criteria but this is costly in resource overhead and is better solved by placing certain APs in rogue detection mode. This will become even more invaluable with the advent of the IDS/IPS solution. -
Hi All,
I have a question regarding rogue detection configuration on WLC.
we know that rogue detection can be enabled on a per AP basis under the advanced tab of each AP, starting from code 6.0, and it also supports rogue detection in RF groups when we configure protection type as "AP Authentication" under WLC security tab, which will make APs to authentication frames based on the RF group name, if name is different, then the AP is considered as a rogue.
so the question is if we only enable rogue detection on the AP level, however leave the AP authentication selected as "none", how does the AP detect rogues? does that mean if any signal detected is not from the APs connected to the WLC, then this will be considered as a rogue?
also in the configuration guide, under the section "enable rogue access point detection in RF groups", it says rogue detection will need the AP to be configured as either local or monitor mode, when we also have AP authentication enabled. however if an AP is under h-reap mode, we still able to enable/disable rogue detection under the advanced tab, so how does H-REAP mode APs detect rogues? is that the same method as when AP authentication selected as "none"
thanks in advance for your help.I've done some tests as well:
I have multiple WLCs on same mobility and same RF groups. AP Auth type set to "none" on all o ft hem. I took one WLC (I'll call it thereafter "My WLC") and changed its RF group name. I also cahnged its AP auth policy to "AP Authentication". All WLCs have same SSIDs configured. I added one extra test SSID on "MY WLC".
The results are:
- The WLC with different RF group name did not mention other APs as rogues. Other APs did not mention my WLC APs as rogues as well.
- There is very high number of AP impersonation detected by "My WLC". other WLCs did not detect ap impersonation. This indicates that other APs on other WLCs try to contain "My WLC" APs. However, "My WLC" does not seem to try impersonating other APs. (it worths to notice that number of APs on "My WLC" is much less than APs on other WLCs).
- When using "AP authentication", there is a new IE appears in the SSID beacons.
The highlighted in blue is that information that could not be interpretted (as seen in highlighted yellow above). This information differs based no the SSID. Different SSID name shows different information. This IE seems to carry the information about the RF group name. If this does not appear when using "none" as AP auth policy then WLCs can not distinguish different RF group names if ap auth set to "none". (because I could not find any RF group info anywhere in the beacon packet. If you know it is exist somewhere else please let us know. So far I assume it is included in this vendor specific IE).
- When I changed the AP auth to "none" the number of AP impersonation reported started to decrease gradually. I'll keep monitoring to see what it will be after couple of hours.
- Config guide is very useful. However, sometimes it is extremley stupid. Why?
well, because if you go to the part that talks about configuring MFP (http://tiny.cc/un6thw), and if you go to Step 5, you will find that the optoin metnioned in step 5 is not available in the AP. It tells you that to enable or disable MFP validation for specific AP you can do this from under Advanced tab. However, this option is not available under Advanced tab. I had a big discussion with TAC about this very long time ago. prompted to doc guys about it but so far nothign changed.
HTH
Amjad -
Rogue cpu hog while running WebLogic
Hello,
My application is a servlet/EJB/Oracle application running on
WebLogic.
During stress test, I am seeing a java thread that is taking up 50% of
available cpu on a dual cpu machine. The thread remains at 100% even
after the load is over.
Here are some data and observations:
0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
cpu. My application consists of a few servlets talking to some 20
stateless session beans which uses CMP 2.0 entity beans to talk to
Oracle 9.0.1. We are using the oci jdbc driver.
1. After the load was over, I used ps and saw that the thread was
still running. I tracked its parent to the weblogic root process.
2. I ran top and saw the thread taking up 50% of available cpu
(sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and 40%
of cpu2, etc).
3. I did a full thread dump, all but one thread are weblogic's or the
jvm's internal threads. My application did have one thread remaining,
but it is a periodic cleanup thread that wakes up every 30 secs and I
believe it is benign. I am not able to quickly point out which thread
is the rogue thread.
4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
into the load (but this number varies from load to load, there was one
that kicked in after an hour). After that point, I saw the number of
runnable process remained at least one, and the idle cpu never goes
above 50 (remember it is a dual cpu machine). After I stopped the
load, the number of runnable process stayed at 1 and the idle cpu
stayed at 50.
5. This thread does not always kicked in, sometimes I would be able to
complete a 24-hour load and did not see the evidence of the thread.
6. The presence of the thread caused a 30% performance degradation.
So here is the question, what is this thread and how can I stop it
from kicking in?
I have attached a full thread dump and the outputs of top and vmstat.
I have also searched previous posts and apparently this has been seen
before by other users of weblogic, but in those threads of discussions
I never saw a resolution.
Thanks in advance,
Chishun Kwong
=================
Full thread dump:
"Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
[0xa7153000..0xa7153870]
at java.lang.Thread.sleep(Native Method)
at com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
"ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
[0xa694f000..0xa694f870]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
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:256)
"ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
[0xa674f000..0xa674f870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
[0xa5dec000..0xa5dec870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
at java.lang.Object.wait(Native Method)
at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
monitor [0xa2cff000..0xa2cff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:114)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
[0xa0bff000..0xa0bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
[0xa09ff000..0xa09ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
[0xa07ff000..0xa07ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
[0xa05ff000..0xa05ff870]
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:427)
at java.util.TimerThread.run(Timer.java:380)
"ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
waiting on monitor [0x9f9ff000..0x9f9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:306)
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:192)
"ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
[0x9f7ff000..0x9f7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
[0x9f5ff000..0x9f5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
[0x9f3ff000..0x9f3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
[0x9f1ff000..0x9f1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
[0x9edff000..0x9edff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
[0x9ebff000..0x9ebff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
[0x9e9ff000..0x9e9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
[0x9e7ff000..0x9e7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
[0x9e5ff000..0x9e5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
[0x9e3ff000..0x9e3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
[0x9e1ff000..0x9e1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
[0x9dfff000..0x9dfff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting on
monitor [0x9ddff000..0x9ddff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
on monitor [0x9d5ff000..0x9d5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:60)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
[0x9c1ff000..0x9c1ff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1660)
at java.lang.Thread.run(Thread.java:479)
"Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
monitor [0..0]
"Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
[0x983ae000..0x983ae870]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
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=0x80b6618 nid=0x9fa waiting on
monitor [0x981ae000..0x981ae870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
"main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
[0xbfffb000..0xbfffb8b4]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
at weblogic.Server.main(Server.java:32)
"VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
"VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
monitor
"Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
==============
Output of top:
11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
90844K buff
Swap: 2097112K av, 0K used, 2097112K free
1178236K cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
COMMAND
2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
2 root 9 0 0 0 0 SW 0.0 0.0 0:00
keventd
===========================================================
Output of vmstat (when I believe the rogue thread started):
procs memory swap io system
cpu
r b w swpd free buff cache si so bi bo in cs
us sy id
0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
17 1 82
0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
6 0 93
0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
1 1 98
4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
25 3 72
1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
33 4 63
0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
25 4 72
0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
8 1 91
4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
64 10 26
4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
57 7 36
1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
55 5 40
1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
63 3 34
1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
71 1 28
1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
68 3 29
2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
66 2 33"laxman" <[email protected]> wrote in message
news:[email protected]...
|
| I have had the exact same problem! It took us a long time to find the
resolution.
| I had a BEA engineer and a SUN engineer on site and finally we discovered
it
| to be a problem with the SUN JVM JDK1.3.1
|
| The BEA contact who resolved this for us is Richard Wallace.
|
| -- Laxman
|
|
| Rob Woollen <[email protected]> wrote:
| >Interesting. I think we'll need even more information to know for sure
| >
| >what's going on here. WLS (almost) never creates threads after it
| >starts. However, it does fork a process to compile JSPs. I'm
| >suspicious this could be a spinning javac process. If you cat
| >/proc/<pid>/cmdline then we should be able to tell whether it's a server
| >
| >thread or a javac process.
| >
| >Does your app start any threads or processes? The thread dump you
| >showed appeared to be idle.
| >
| >-- Rob
| >
| >Chishun Kwong wrote:
| >> Hello,
| >>
| >> My application is a servlet/EJB/Oracle application running on
| >> WebLogic.
| >> During stress test, I am seeing a java thread that is taking up 50%
| >of
| >> available cpu on a dual cpu machine. The thread remains at 100% even
| >> after the load is over.
| >> Here are some data and observations:
| >>
| >> 0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
| >> cpu. My application consists of a few servlets talking to some 20
| >> stateless session beans which uses CMP 2.0 entity beans to talk to
| >> Oracle 9.0.1. We are using the oci jdbc driver.
| >>
| >> 1. After the load was over, I used ps and saw that the thread was
| >> still running. I tracked its parent to the weblogic root process.
| >>
| >> 2. I ran top and saw the thread taking up 50% of available cpu
| >> (sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and
| >40%
| >> of cpu2, etc).
| >>
| >> 3. I did a full thread dump, all but one thread are weblogic's or the
| >> jvm's internal threads. My application did have one thread remaining,
| >> but it is a periodic cleanup thread that wakes up every 30 secs and
| >I
| >> believe it is benign. I am not able to quickly point out which thread
| >> is the rogue thread.
| >>
| >> 4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
| >> into the load (but this number varies from load to load, there was
| >one
| >> that kicked in after an hour). After that point, I saw the number of
| >> runnable process remained at least one, and the idle cpu never goes
| >> above 50 (remember it is a dual cpu machine). After I stopped the
| >> load, the number of runnable process stayed at 1 and the idle cpu
| >> stayed at 50.
| >>
| >> 5. This thread does not always kicked in, sometimes I would be able
| >to
| >> complete a 24-hour load and did not see the evidence of the thread.
| >>
| >> 6. The presence of the thread caused a 30% performance degradation.
| >>
| >> So here is the question, what is this thread and how can I stop it
| >> from kicking in?
| >>
| >> I have attached a full thread dump and the outputs of top and vmstat.
| >> I have also searched previous posts and apparently this has been seen
| >> before by other users of weblogic, but in those threads of discussions
| >> I never saw a resolution.
| >>
| >> Thanks in advance,
| >> Chishun Kwong
| >>
| >> =================
| >>
| >> Full thread dump:
| >>
| >> "Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
| >> [0xa7153000..0xa7153870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
| >>
| >> "ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
| >> [0xa694f000..0xa694f870]
| >> at java.net.PlainSocketImpl.socketAccept(Native Method)
| >> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
| >> 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:256)
| >>
| >> "ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
| >> [0xa674f000..0xa674f870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
| >> [0xa5dec000..0xa5dec870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
| >> tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
| >> monitor [0xa2cff000..0xa2cff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:11
4)
| >>
| >> "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
| >> [0xa0bff000..0xa0bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
| >> [0xa09ff000..0xa09ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
| >> [0xa07ff000..0xa07ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
| >> [0xa05ff000..0xa05ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.util.TimerThread.mainLoop(Timer.java:427)
| >> at java.util.TimerThread.run(Timer.java:380)
| >>
| >> "ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
| >> nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
| >> nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
| >> waiting on monitor [0x9f9ff000..0x9f9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(Transac
tionProcessor.java:306)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionPro
cessor.java:192)
| >>
| >> "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
| >> [0x9f7ff000..0x9f7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
| >> [0x9f5ff000..0x9f5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
| >> [0x9f3ff000..0x9f3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
| >> [0x9f1ff000..0x9f1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
| >> [0x9edff000..0x9edff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
| >> [0x9ebff000..0x9ebff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
| >> [0x9e9ff000..0x9e9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
| >> [0x9e7ff000..0x9e7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
| >> [0x9e5ff000..0x9e5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
| >> [0x9e3ff000..0x9e3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
| >> [0x9e1ff000..0x9e1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
| >> [0x9dfff000..0x9dfff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting
| >on
| >> monitor [0x9ddff000..0x9ddff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
| >> nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
| >> on monitor [0x9d5ff000..0x9d5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:6
0)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
| >> nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
| >> nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
| >> at weblogic.socket.PosixSocketMuxer.poll(Native Method)
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
| >> nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
| >> nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
| >> nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
| >> nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
| >> nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
| >> [0x9c1ff000..0x9c1ff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1660)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
| >> monitor [0..0]
| >>
| >> "Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
| >> [0x983ae000..0x983ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
| >> 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=0x80b6618 nid=0x9fa waiting on
| >> monitor [0x981ae000..0x981ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
| >>
| >> "main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
| >> [0xbfffb000..0xbfffb8b4]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
| >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
| >> at weblogic.Server.main(Server.java:32)
| >>
| >> "VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
| >>
| >> "VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
| >> monitor
| >> "Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
| >>
| >> ==============
| >>
| >> Output of top:
| >>
| >> 11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
| >> 185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
| >> CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
| >> CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
| >> Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
| >
| >> 90844K buff
| >> Swap: 2097112K av, 0K used, 2097112K free
| >> 1178236K cached
| >>
| >> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
| >> COMMAND
| >> 2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
| >> 30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
| >> 1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
| >> 2 root 9 0 0 0 0 SW 0.0 0.0 0:00
| >> keventd
| >>
| >> ===========================================================
| >>
| >> Output of vmstat (when I believe the rogue thread started):
| >>
| >> procs memory swap io system
| >
| >> cpu
| >> r b w swpd free buff cache si so bi bo in cs
| >
| >> us sy id
| >> 0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
| >
| >> 17 1 82
| >> 0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
| >
| >> 6 0 93
| >> 0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
| >
| >> 1 1 98
| >> 4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
| >
| >> 25 3 72
| >> 1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
| >
| >> 33 4 63
| >> 0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
| >
| >> 25 4 72
| >> 0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
| >
| >> 8 1 91
| >> 4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
| >
| >> 64 10 26
| >> 4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
| >
| >> 57 7 36
| >> 1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
| >
| >> 55 5 40
| >> 1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
| >
| >> 63 3 34
| >> 1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
| >
| >> 71 1 28
| >> 1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
| >
| >> 68 3 29
| >> 2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
| >
| >> 66 2 33
| >
|
|
Is this specific to a version of the 1.3.1 JVM? (1.3.1_x)?
k -
802.1x for user authentication setup questions
Hi,
I am fairly new to the 802.1x realm, I have read several documents on how the setup is accomplished and I was hoping someone could validate the setup I have in mind to make sure I am on the right page. Any comments or assistance would be greatly appreciated, I do not have the infrastructure to test everything before hand.
I have a remote site with a switch and router. I want to authenticate users using their AD credentials. At the datacenter I will have ACS 5.2, a Windows 2008 enterprise server for AD service and CS service. I do not have the option to install an additional client on the PC like anyconnect, I need to use Windows OS supplicant without installing physcial certificates on the machine.
- Within the CS service I will generate a certificate that will be imported by ACS.
- I will activate ACS to integrate with AD
- I do not want to insall certificates on the client machines so I will use PEAP w/ MSCHAPv2
- The authenticating clients will be XP w/ SP3, I am hoping that a group policy can be created to enabed the wired service to start automatically and I will also need to add my CS/CA server as a trusted authority unless I purhcase a verisign certificate to be used. Correct? or will this need to be done when the desktop image is installed on the pc?
Additional Questions:
- With the setup I described above using MSCHAPv2 when the user boots the computer in the morning, hits ctrl+alt+delete and provides their AD credentials will this act as a single sign on? first authenticating them through 802.1x so the port is authorized and then authenticating them to the AD server? or will there be some type of pop up window that will appear before the ctrl+alt+delete window? making the user provide credentials twice (annoying)
- Once the user is autheticated can I push an ACL down to the switch to enforce a set policy? or does this happen on the router?
- Most of the documents I have read are related to L2 802.1x is there a L3 option that includes the router that I should be looking at to provide more features?
- can anyone speak to their experience with the Windows OS supplicants? is the functionality flaky/clunky or if the backend is setup properly it works seamlessly?
Sorry for the long winded post but I am kind of shooting in the dark without having the equipment to test with. Any help is appreciated!
ThanksThanks too you both for the responses.
I have a few followup questions which I have added inline.
Q:
- With the setup I described above using MSCHAPv2 when the user boots the computer in the morning, hits ctrl+alt+delete and provides their AD credentials will this act as a single sign on? first authenticating them through 802.1x so the port is authorized and then authenticating them to the AD server? or will there be some type of pop up window that will appear before the ctrl+alt+delete window? making the user provide credentials twice (annoying)
A: If you select "Use windows credentials" it won't prompt you for credentials. so All automatic.
However note that it will only login AFTER you entered the credentials on the logon page. So you won't have network connectivity for the initial logon, so no login scripts this way.
With your comments I am rethinking my approach, I am considering that if the company security policy will allow it I will do machine authentication only instead of user auth. Obviously this is not as secure since a rogue user could change the local admin password and have access to the network. But interms of simplicity and ease of use machine authentication provides a transparent authentication mechanism that should suffice. I would just have to sell the solution to security.
There a few things I need to understand before persuing this.
- will the machine be 802.1x authenticated and on the network before the ctrl+alt+delete? so when user logs in the machine has passed 802.1x already and has received ip from dhcp? this is my hope.
- is peap/mschap still the supported protocol so no physical cert is required per machine? no EAP-TLS
- is the machine profile on the AD server used for 802.1x verification/authentication? meaning ACS will pass off to AD to verify the machine is part of the domain? or do you have to create machine profiles in ACS?
- I have read a few articles out there about issues with machine auth with clients using XP, perhaps this was related to previous serivce packs before SP3? there was mention of registery changes required etc.
- is there a different supplicant offered by cisco that is more robust that would provide more stability or is the cisco supplicant cost money per user license or other etc.
Again your feedback is invaluable as I do not have the physical equipment to test with. Unfortunatly I have to propose a solution before actually testing something which I am not particularly fond of.
Regards,
Eric -
Interview questions for oracle dba
Hi I am trying to find teh interview questions for oracle dba .
What will be your answer to the following questions. Can somebody shed some light...
. What is the day to day duties of oracle dba?
· Did you use online or off-line backups?
· What version of Oracle were you running?
· Haw many databases and what sizes?
· If you have to advise a backup strategy for a new application, how would you approach it and what questions will you ask?
· If a customer calls you about a hanging database session, what will you do to resolve it?
· Compare Oracle to any other database that you know. Why would you prefer to work on one and not on the other?
Thx
KK. What is the day to day duties of oracle dba?
I have got a checklist, designed for my daily, weekly, fortnightly and monthly tasks. For example, in the daily checklist tasks, I check for the alert log file, competion and correction of my exports and operating system backups. DB space situation, Antivirus status, standby database status, space on disks, any rogue queries etc.
· Did you use online or off-line backups?
Both.
· What version of Oracle were you running?
8i(not any more), 9i, 10g
· Haw many databases and what sizes?
8 databases, ranging from 1 TB to 10 GB. I have segregated them into OLTP production, testing, cm, and development and a Datawarehouse.
· If you have to advise a backup strategy for a new application, how would you approach it and what questions will you ask?
How much they could afford to lose data or they want zero data loss and also I will get their requirements about down time and up time of database.
· If a customer calls you about a hanging database session, what will you do to resolve it?
First I will identify it, then see to it what exactly it is doing, capture that situation and then either try to release the locks(if its a blocking or blocked session), or kill the session, if its hanging on a runaway query.
· Compare Oracle to any other database that you know. Why would you prefer to work on one and not on the other?
Oracle passes the ACID rule with distinction as compared to the other databases. Moreover, the multiversion read consistency, recovery, flexibility and challenges of Oracle are matchless.
Cheers
fahdoracle.blogspot.com -
Hi all
I work in a company where we rented offices and we offer internet service for all (VOiP and internet). The place where I work has 2 buildings and each building has 2 Cisco WLC 4400. We have about 100 Acces point in total (connected to the WLC) to give free and public internet service . The problem we have is that companies connect their LAN AP and makes the free wireless network go very slow. If we enter to the WLC appear around 300 Rogue Aps per building, it's a lot!. We think that the problem of slowness is this. Is there any possibility that our APs not see the APs of the other companies? How can we fix the internet speed of our APs?
thank you very muchThe signal strength of the Rogue APs doesn't affect any of your issues.
What you and your management should think about is the age of your APs. 1020 is long, long End-of-Support. The firmware you are using is ... ancient.
1020 supports 802.11b. So this means you're maximum 11 Mbps. And when everyone says 11 Mbps, this is expressed in HALF duplex or one-way traffic only. In reality, you'll be lucky to get 5 Mbps.
Now, let's say you've got one person with a brand-spanking-new iPhone 6 ... One guy alone with a smartphone can really, really slow down your wireless.
If the model of your AP is that old and the firmware of your WLC is equally as old, then I shudder to think about the age of your LAN/WAN infrastructure. This also means any opportunist salesperson can potentially sell you EVERYTHING:
1. LAN & WAN: Maybe it's time to upgrade your current LAN switches because high-speed 802.11n and 802.11ac wave1, wave 2 will require 1 Gbps. 802.11ac wave 1 and wave 2 would benefit if you have 10 Gbps uplink to core network.
2. Security: IDS/IPS and Firewall. If you've got guest wifi, you'll need to incorporate these.
3. Network Monitoring: If you've got executives who like to look at performance numbers, colors, graphs, etc. then CPI is your tool to manage your LAN/WAN and wireless as well as generate mind-numbing reports for bean counters to salivate upon.
4. Wireless: You need to upgrade your APs. You will also need to upgrade your WLC. No question about it.
5. IP Telephony: If your LAN supports PoE/PoE+ then IP telephony is your best bet. You can even link IP telephony with wireless as Cisco has two models of wireless handsets: 792X and 9971.
6. Video Conferencing: Do your executives like to do video conferencing? You can also "link" this with IP Telephony as Cisco has a few desk phones which can also do video conferencing.
7. Instant Messenger: Cisco is pouring a lot of resources into the improvement of Jabber.
8. Digital Media Streaming: Does your company consider putting some kind of network-based Digital Media Streaming in your office? -
I tested the capability of containing rogue AP over the air in a lab environment. It works great, but I have the following questions/concerns:
1. How could I detect if others/hackers do this to our wireless network?
2. Will the WLCs be able to detect this kind of stuff?
3. Any links or documents on this topic would be greatly appreciated.
Thanks
BinhBe very careful when you are using AP Containment. In some countries, if you contain the wrong AP/WLAN, you and/or your organization can be liable.
The WLC/WCS can conduct AP Containment very well. I know because I've used this on Rogues AP found WITHIN the premises. -
Rogue AP Countermeasure in WLC
WLC detects rogue AP in their environtment, WLC also have some action to do with those rogue AP, by changing Update Status in Rogue AP Detail to Contain. It will make the AP that detect rogue AP launch the management frame (deauthentication frame) to that rogue AP. So whatever and whoever client trying to connect to the rogue AP, they will kicked out or deauthenticated.
So that's in theory.
In a real, i set up an AP using Nokia tethering features. Obviously the WLC will detect it as rogue AP, and i initiate deauth attack to AP that i just been setup using WLC. In theory all device that trying to associate to this AP will deauthenticated or it will not be connected. But in my lab, i am trying to connect my other device to my nokia AP. And voila my other device is connected.
So my question ,
What makes my other device is not deauthenticated ?
ThanksDid you use Monitor mode AP?
Also If client and AP are using 802.11w then containment will not work as in that case the management frames are protected.
To dig further you can try the setup where you have one monitor mode Ap to launch deauth attach. One sniffer mode Ap to see whats going on in Air. and a hotspot which you already have for containing. -
We see several Rogue APs in our network which are, according to WCS, not 'On Network'. However, most of them do turn out to be 'On Network': their MAC address appears as connected&active in a switch port. I wonder if this is because the 'On Network' status is never re-examined after first detection? Any suggestions?
A couple of questions
1) What LWAPs are you using
2) Have you enabled Rogue Location Discovery protocol
3) Have you configured dedicated Rogue detector LWAPs
4) Have you got legacy Autonomous APs on your network -
Cisco Prime Infrastructure 1.2 - web browser freezes when managing rogue APs alarms
Hello all,
has anybody faced a freezing problem when you click in Cisco Prime Infrastructure 1.2 down on alarm bar and then to Rogue AP alarms and then try to add an annotitation or change a rogue alarm to Friendly?
I tried it on different PC, different browsers (Firefox 14.0.1. Chrome ...) and the problem is still there.
Has anybody an idea?
Thanks.
Regards
KarelI just tried it from my lab VM and had no problems. I use Chrome and the browser does sometimes not refresh for a while but that is just when I start to click around.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered" -
Best practices for configure Rogue Detector AP and trunk port?
I'm using a 2504 controller. I dont have WCS.
My questions are about the best way to configure a Rogue Detector AP.
In my lab environment I setup the WLC with 2 APs. One AP was in local mode, and I put the other in Rogue Detector mode.
The Rogue Detector AP was connected to a trunk port on my switch. But the AP needed to get its IP address from the DHCP server running on the WLC. So I set the native vlan of the trunk port to be the vlan on which the WLC management interface resides. If the trunk port was not configured with a native vlan, the AP couldn't get an address through DHCP, nor could the AP communicate with the WLC. This makes sense because untagged traffic on the trunk port will be delivered to the native vlan. So I take it that the AP doesn't know how to tag frames.
Everything looked like it was working ok.
So I connected an autonomous AP (to be used as the rogue), and associated a wireless client to it. Sure enough it showed up on the WLC as a rogue AP, but it didn't say that it was connected on the wire. From the rogue client I was able to successfully ping the management interface of the WLC.
But the WLC never actually reported the rogue AP as being connected to the wired network.
So my questions are:
1. What is the correct configuration for the trunk port? Should it not be configured with a native vlan? If not, then I'm assuming the rogue detector AP will have to have a static IP address defined, and it would have to be told which vlan it's supposed to use to communicate with the WLC.
2. Assuming there is a rogue client associated with the rogue AP, how long should it reasonably take before it is determined that the rogue AP is connected to the wired network? I know this depends on if the rogue client is actually generating traffic, but in my lab environment I had the rogue client pinging the management interface of the WLC and still wasn't being picked up as an on-the-wire rogue.
Thanks for any input!!#what's the autonomous AP's(as Rogue AP) Wired and Wireless MAC address?
it has to be +1 or -1 difference. If Wired MAC is x.x.x.x.x.05 and the wireless mac should be x.x.x.x.x.04 or 06. It is not going to detect if the difference is more than + 1 or - 1.
#Does the switch sees the Rogue AP's wired MAC on its MAC table.
Rogue Detector listens to ARPs to get all the Wired MAC info and forwards to WLC, It compares with Wireless MAC, if there is a +1 or -1 difference then it will be flagged as Rogue on wire. And the client that connected to it is also marked as found on wire.
Regards to Trunking, Only Native vlan matters per trunk link, just configure the right vlan as native and we're done.
It is not mandatory to keep the Rogue detector on Management vlan of wlc. It can also be on L3 vlan also as long as it can join the WLC to forward the learnt wired MACs.
So if we don't have +1, -1 difference on Rogues then you've to use RLDP which will work with your existing setup to find Rogue on wire. there's a performance hit when we use this feature on local mode APs.
Note: For AP join - AP can't understand Trunk, meaning if AP connected to Trunk it'll only talk to its native vlan irrespective of AP mode, however rogue detector listens to the Trunk port to learn MACs via ARPs from different VLANs and forwards to WLC using native vlan. -
Rogue detection with Prime 2.1
Hi@all,
i know many questions in the last days, but i must say, the last WCS works better as the compination Prime 2.1 and 5760 ;).
My problem, we have a huge campus and at peaks ~ 1500 rogue-aps.
In my new configuration (2x 5760 and Prime 2.1), the wlc see the rogue-aps but in the security dashboard at the prime no rogue are listet.
The 5760 are in the same mobility/rf-group, the polling interval at the Prime are 15 minutes.
Maybe some one has a similar problem and could help.
regards
RenéHi
Do you see the rogue AP on 5760 itself ? "show wireless wps rogue ap summary" output shows you the identified rogue APs. If you can't see anything there, then you may not enable Rogue AP detection on your controller. See whether in your 5760 configuration, the first line below is configured (which will enable rogue detection). Second line is to increase the threshold to minimize false detection. Refer 5760 RRM config guide for more details.
wireless wps ap-authentication
wireless wps ap-authentication threshold 50
This document describe some of the best practices of 5760 configuration including rogue detection as well.
Cisco 5760 IOS Wireless LAN Controller Configuration Best Practices
HTH
Rasika
**** Pls rate all useful responses **** -
Hi All,
I have a couple of question in regards to rogues and rf grouping.
Does the controller count the rougues access points when calculating channels assignments in the network?
The current setup has each floor in a separate RF group, does the APs in a RF group consider another AP from a different RF group a foreign Access Point? also when it is beneficial to have each floor in a separate RF group?
Thank you allHi,
A WLC on a mobility group may see APs joining other WLCs on same mobility group as rogue devices IF they are in different RF groups.
This depends on the AP authentication configuration. (security -> Wireless Protection Policies -> AP Authentication).
If the value is set to "None" then different RF groups do not matter. If the value is set to "AP Authentication" then if two APs are in two RF groups the WLC will probably raise the rogue flag.
The above was true before different RF groups on same WLC were possible.
I don't honestly know the behavior when two different RF groups are configured on the same WLC. (You may try changing the AP Authentication config and feed us back ).
HTH
Amjad
Rating useful replies is more useful than saying "Thank you"
Maybe you are looking for
-
How do I transfer video from my camcorder to my iMac?
I have a Sony HandyCam (DCR-DVD92 NTSC, 800x Digital zoom, 20x Optical zoom). How can I transfer the video to my iMac? Is the "Video Capture" from Elgato the best way, or is there something easier?
-
My wife likes to work out and she wants to key in on songs with the right BPM. I am assuming this is not included in the song files. How would one find this out? Thanks!
-
Which is the best user-friendly IDE for swing program development
Which is the best user-friendly IDE for swing program development
-
Summing of currency and quantity fields individually
hi experts From Table BSIS fields are BELNR, BUDAT, DMBTR, MENGE required output is quantity and currencey fields should be sum at line item level.write a program ? regds Venky
-
Why can't I find a representative of iTunes to help me with an iTunes problem?
Why can't I find an iTunes employee to help me with an iTunes problem?