Why my question thread is locked?
I found that my question thread is locked, why?
Hi Guys,
Here are two questions about ABAP.
(1)
UML provides various diagram types. Mark the valid UML diagrams
(More than one answer is correct)
1 Aggregation
2 Composition
3 Class
4 Component
5 Behavior
I think the correct answers are (1) (2) (3). But the standard answers are (3)(4)(5).
Why?
(2)
Mark the valid logical nodes.
(More than one answer is correct)
1 Node
2 Table
3 Structure
4 Complex Data Object
5 File
The standard answers are (2) (3) (4). Can anybody explain it in details?
Thanks.
Edited by: Michael on Jan 29, 2008 3:36 PM
Hi Micheal,
The answer for the first question is:
1)
Firstly Aggregation & Composition are types of relationships and they are part of an UML Diagram used to connect the various classes/parts of that specific diagram.
They are not the actual diagrams
The remainig three options
Class,
Component &
Behavioural are the UML Diagrams, which contain the various classes,components, packages etc.
Hence the options 3,4,5 are correct.
The UML Diagrams are categorized as
Structural and Behavioural Diagrams.
Under Structural Diagrams
Class Diagram
Object Diagram
Component Diagram
Deployment Diagram
Under Behavioral Diagrams
Use Case Diagram
Sequence Diagram
Collaboration Diagram
Statechart Diagram
Activity Diagram
If you are still not clear then please go through the below link which clearly shows the various relations existing and about the UML Diagrams.
[http://www.dotnetcoders.com/web/learning/uml/diagrams/classdiagram.aspx]
Reward if useful,
Sravani.
Similar Messages
-
Why did the thread get locked or deleted?
Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Occasionally you may see a thread get locked or deleted, or the possibility of a user having been banned. This tip is a viewpoint of an end user of how the Terms of Use apply to deletions, locks, or bans. Moderators may at their discretion choose these actions as the Terms of Use allow them to, even when none of these points below matter.
When you signed up on this board, a Terms of Use page was agreed to in order for you to enter. That Terms of Use page is also on the link "Help & Terms of Use" on the right hand side. Posts themselves may get deleted that weren't the source of the thread being locked or deleted. So if you didn't disobey the Terms of use, someone else might have.
Do not take either as a sign of censorship, a sign of personal chastisement, or anything negative per say. This is after all a community open to the public.
When one of the terms of use is violated, it is either because it does not offer constructive points of view for fixing a technical issue from end user to end user, or it is overly digressive from doing such actions. Terms of use suggest to avoid:
1. Prognosticating.
2. Guessing Apple's policy.
3. Offer advice on something which may be against copyright laws.
4. Offer advice on something which would violate a license agreement.
5. Posting in a thread with "me toos". Try to solve the problem at hand. It makes it very hard for those of us trying to help the original poster when additional people chime in, saying they too have the same problem, or have a problem almost identical. Those trying to help
the original poster, may not know if the solution applies to all the people having the problem, or just some. It ends up requiring people coming to help to directly address a person to avoid confusing who should follow various advice.
A Post New Topic is available at all Forum levels, but at the Category level of Discussions. For more on this discussion, see the tip here:
http://discussions.apple.com/ann.jspa?annID=650
6. Other things which may be illegal in the State of California or in the United States of America
should not be suggested or inferred by what you post.
7. Rants or complaints about people and companies.
They are unhelpful, and really don't solve technical issues.
Approach complaints with tact when posting in a public forum that is moderated such as this one.
It is one thing to say, I hate this feature being missing, is there any way to get this feature added, or are there any ways of getting it from another source?
It is another thing to blame Apple for a feature that is missing, and drop the ball at that waiting for a response. These type of posts are more likely to be frowned upon.
Complaining of a service not rendered is also often frowned upon. There are points of contact later in this tip to address such service issues. This is a forum for addressing technical inquiries about how things work or if things can be made to work on your system.
8. Polls asking for a feature to be added/removed are generally frowned upon, as well as polls about various apparent defects and their propensity. You are only addressing less than 1% of the Apple using population here.
Such polls would not be very scientific even if they are carried out for long periods of time. Long threads may appear to act as polls, and may violate terms of use. If you see such a thread and wonder why it hasn't been locked or deleted, you are welcome to ask that in Discussions Feedback, or click on "Report This Post" at the bottom right corner if available.
As the Terms of Use state, in the end essentially it is up to the moderator to decide if a thread is worthy being deleted or locked. Don't take it personally if it is. Also Level 2 through Level 5 users, while we can ask the moderators look at a thread, we are not Apple Employees. You may also ask a moderator look at a thread or an individual on the Discussion Feedback forum or by clicking Report this post at the bottom right hand corner of a specific post.
If the purpose of your thread is to provide feedback to Apple for a product, see these pages:
http://www.apple.com/contact/
http://www.apple.com/feedback/
http://www.apple.com/contact/feedback.html
If you have isolated a bug with a procedure worthy of a software developer, sign up for a free developer account on http://developer.apple.com/ and report the bug here:
http://bugreporter.apple.com/
As this is a user to user forum answers may not come right away. Have patience, and usually someone eventually can come up with an answer. Some forums may not fit the subject line of your topic, and you are welcome to ask if you are unsure where to post a topic.
This is the 2nd version of this tip. It was submitted on September 28, 2010 by a brody.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Occasionally you may see a thread get locked or deleted, or the possibility of a user having been banned. This tip is a viewpoint of an end user of how the Terms of Use apply to deletions, locks, or bans. Moderators may at their discretion choose these actions as the Terms of Use allow them to, even when none of these points below matter.
When you signed up on this board, a Terms of Use page was agreed to in order for you to enter. That Terms of Use page is also on the link "Help & Terms of Use" on the right hand side. Posts themselves may get deleted that weren't the source of the thread being locked or deleted. So if you didn't disobey the Terms of use, someone else might have.
Do not take either as a sign of censorship, a sign of personal chastisement, or anything negative per say. This is after all a community open to the public.
When one of the terms of use is violated, it is either because it does not offer constructive points of view for fixing a technical issue from end user to end user, or it is overly digressive from doing such actions. Terms of use suggest to avoid:
1. Prognosticating.
2. Guessing Apple's policy.
3. Offer advice on something which may be against copyright laws.
4. Offer advice on something which would violate a license agreement.
5. Posting in a thread with "me toos". Try to solve the problem at hand. It makes it very hard for those of us trying to help the original poster when additional people chime in, saying they too have the same problem, or have a problem almost identical. Those trying to help
the original poster, may not know if the solution applies to all the people having the problem, or just some. It ends up requiring people coming to help to directly address a person to avoid confusing who should follow various advice.
A Post New Topic is available at all Forum levels, but at the Category level of Discussions. For more on this discussion, see the tip here:
http://discussions.apple.com/ann.jspa?annID=650
6. Other things which may be illegal in the State of California or in the United States of America
should not be suggested or inferred by what you post.
7. Rants or complaints about people and companies.
They are unhelpful, and really don't solve technical issues.
Approach complaints with tact when posting in a public forum that is moderated such as this one.
It is one thing to say, I hate this feature being missing, is there any way to get this feature added, or are there any ways of getting it from another source?
It is another thing to blame Apple for a feature that is missing, and drop the ball at that waiting for a response. These type of posts are more likely to be frowned upon.
Complaining of a service not rendered is also often frowned upon. There are points of contact later in this tip to address such service issues. This is a forum for addressing technical inquiries about how things work or if things can be made to work on your system.
8. Polls asking for a feature to be added/removed are generally frowned upon, as well as polls about various apparent defects and their propensity. You are only addressing less than 1% of the Apple using population here.
Such polls would not be very scientific even if they are carried out for long periods of time. Long threads may appear to act as polls, and may violate terms of use. If you see such a thread and wonder why it hasn't been locked or deleted, you are welcome to ask that in Discussions Feedback, or click on "Report This Post" at the bottom right corner if available.
As the Terms of Use state, in the end essentially it is up to the moderator to decide if a thread is worthy being deleted or locked. Don't take it personally if it is. Also Level 2 through Level 5 users, while we can ask the moderators look at a thread, we are not Apple Employees. You may also ask a moderator look at a thread or an individual on the Discussion Feedback forum or by clicking Report this post at the bottom right hand corner of a specific post.
If the purpose of your thread is to provide feedback to Apple for a product, see these pages:
http://www.apple.com/contact/
http://www.apple.com/feedback/
http://www.apple.com/contact/feedback.html
If you have isolated a bug with a procedure worthy of a software developer, sign up for a free developer account on http://developer.apple.com/ and report the bug here:
http://bugreporter.apple.com/
As this is a user to user forum answers may not come right away. Have patience, and usually someone eventually can come up with an answer. Some forums may not fit the subject line of your topic, and you are welcome to ask if you are unsure where to post a topic.
This is the 2nd version of this tip. It was submitted on September 28, 2010 by a brody.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information. -
I know I'm new here but can someone tell me why my thread got locked regarding the problems I have been having with upgrading my high speed internet? It says it's being "resolved in a private support area." But no one has contacted me to provide support. *sigh* Why can't I just get a straight answer?
Quantrill wrote:
In other words....
Don't count on anything being resolved.
Now I wouldn't say that... it's something new they're trying out so I'd see if it helps. Just trying to make this board a bit more like other technical support boards where old posts from people are not getting necro'd or new posts being flooded with unrelated issues for what is usually a single line incident.
As far as replying to http://forums.verizon.com/t5/High-Speed-Internet-DSL-and-Dial/Upgrade-High-Speed-Internet/td-p/42398... goes...
1: DSL speeds can be provisioned often times on the spot. Verizon has automated systems which allow people with the right access to pick a speed, the PVC and DSLAM and any related equipment will provision for the speed and your line will re-synchronize once the DSLAM has the new configuration pushed. The issue with why Verizon takes forever to change the speed in many areas, such as mine where it takes a week is due to the billing system most likely. Until Billing updates their records network doesn't update the profile you're on, that way you are not seen as getting "Free speed boosts."
2: Bandwidth on demand often comes with business connections, notably Fiber as the speed can be kicked up or down on demand and billing adjusted on the fly. Verizon Business has such a system up and they can do such a thing without killing the connection first (ADSL2+ has methods as well, same with FiOS!).
3: Service changes should never result in a disconnect. If a disconnect occurs it needs to be resolved promptly as no one should be pulling your line from a DSL-enabled card or unprovisioning your line. Now if your line will not come up because they set the speed much too high and bursts of noise are knocking the DSLAM and modem offline before they fully synch, that could be another thing but the two pieces of equipment should train at lower speeds, not retry a bad speed if noise clears.
========
The first to bring me 1Gbps Fiber for $30/m wins! -
HELP!!! Why do my thread dump have so many locked monitor
In recent weeks, My customer's weblogic server become more busy.Each time I downloaded
the thread dump when CPU is busy than 90%,I found a lot of lock in the thread
dump! Especially the class named "weblogic.kernel.ExecuteThread" . It's the kernel
class of weblogic, Why were most of them locked?
Full thread dump:
"process forker" daemon prio=1 tid=0x95b4c8e0 nid=0x3084 waiting on monitor [0x977ff000..0x977ff890]
at java.lang.Object.wait(Native Method)
- waiting on <53d26420> (a java.lang.Object)
at java.lang.UNIXProcessForker.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"process reaper" daemon prio=1 tid=0x95376758 nid=0x3083 runnable [0x96eff000..0x96eff890]
at java.lang.UNIXProcessReaper.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x825bf18 nid=0x25a1 waiting
on monitor [0x95dff000..0x95dff890]
at java.lang.Object.wait(Native Method)
- waiting on <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" prio=1 tid=0x94d00630 nid=0x25a0 runnable [0x95fff000..0x95fff890]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
- locked <538fa238> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=1 tid=0x8c0dd1d0 nid=0x259c waiting on monitor
[0x94521000..0x94521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9650> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9650> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"NBExecuteThread-0" daemon prio=1 tid=0x8c0dc7d0 nid=0x259b waiting on monitor
[0x94321000..0x94321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9060> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9060> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
//"ExecuteThread-49" daemon prio=1 tid=0x8c034660 nid=0x259a runnable [0x94121000..0x94121890]
at java.net.PlainDatagramSocketImpl.peek(Native Method)
- locked <537acf60> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:349)
- locked <486f9980> (a java.net.DatagramPacket)
- locked <537acf40> (a java.net.MulticastSocket)
at weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:86)
at weblogic.cluster.TMSocket.execute(TMSocket.java:249)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-48" daemon prio=1 tid=0x8c0c3d18 nid=0x2599 waiting for monitor
entry [0x93f21000..0x93f21890]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-47" daemon prio=1 tid=0x8c0c32d0 nid=0x2598 runnable [0x93d21000..0x93d21890]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- locked <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-46" daemon prio=1 tid=0x8c0bf410 nid=0x2597 waiting for monitor
entry [0x93b21000..0x93b21890]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-45" daemon prio=1 tid=0x8c0be9c8 nid=0x2596 waiting on monitor
[0x93921000..0x93921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6df8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6df8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-44" daemon prio=1 tid=0x8c0bdab0 nid=0x2595 waiting on monitor
[0x93721000..0x93721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6828> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6828> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-43" daemon prio=1 tid=0x8c0bd068 nid=0x2594 waiting on monitor
[0x93521000..0x93521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6258> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6258> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-42" daemon prio=1 tid=0x8c0c0ce0 nid=0x2593 waiting on monitor
[0x93321000..0x93321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a5c88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a5c88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-41" daemon prio=1 tid=0x8c0c0298 nid=0x2592 waiting on monitor
[0x93121000..0x93121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a56b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a56b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-40" daemon prio=1 tid=0x8c0a21e0 nid=0x2591 waiting on monitor
[0x92f21000..0x92f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a50e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a50e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-39" daemon prio=1 tid=0x8c0d4520 nid=0x2590 waiting on monitor
[0x92d21000..0x92d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4b18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4b18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-38" daemon prio=1 tid=0x8c0d43d0 nid=0x258f waiting on monitor
[0x92b21000..0x92b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4548> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4548> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-37" daemon prio=1 tid=0x8c0d3988 nid=0x258e waiting on monitor
[0x92921000..0x92921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a3f78> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a3f78> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-36" daemon prio=1 tid=0x8c0ded20 nid=0x258d waiting on monitor
[0x92721000..0x92721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a39a8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a39a8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-35" daemon prio=1 tid=0x8c0de2d8 nid=0x258c waiting on monitor
[0x92521000..0x92521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a33d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a33d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-34" daemon prio=1 tid=0x8c0cd528 nid=0x258b waiting on monitor
[0x92321000..0x92321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2e08> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2e08> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-33" daemon prio=1 tid=0x8c0ccae0 nid=0x258a waiting on monitor
[0x92121000..0x92121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2838> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2838> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-32" daemon prio=1 tid=0x8c075360 nid=0x2589 waiting on monitor
[0x91f21000..0x91f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2268> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2268> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-31" daemon prio=1 tid=0x8c0837d0 nid=0x2588 waiting on monitor
[0x91d21000..0x91d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a1c98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a1c98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-30" daemon prio=1 tid=0x8c0a5628 nid=0x2587 waiting on monitor
[0x91b21000..0x91b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a16c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a16c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-29" daemon prio=1 tid=0x8c07aaf8 nid=0x2586 waiting on monitor
[0x91921000..0x91921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a10f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a10f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-28" daemon prio=1 tid=0x8c0c23d0 nid=0x2585 waiting on monitor
[0x91721000..0x91721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0b28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0b28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-27" daemon prio=1 tid=0x8c0c1988 nid=0x2584 waiting on monitor
[0x91521000..0x91521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0558> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0558> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-26" daemon prio=1 tid=0x8c07ca00 nid=0x2583 waiting on monitor
[0x91321000..0x91321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ff88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ff88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-25" daemon prio=1 tid=0x8c079e70 nid=0x2582 waiting on monitor
[0x91121000..0x91121890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f9b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f9b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-24" daemon prio=1 tid=0x8c078038 nid=0x2581 waiting on monitor
[0x90f21000..0x90f21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f3e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f3e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-23" daemon prio=1 tid=0x8c0a3298 nid=0x2580 waiting on monitor
[0x90d21000..0x90d21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ee18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ee18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-22" daemon prio=1 tid=0x8c0e30d8 nid=0x257f waiting on monitor
[0x90b21000..0x90b21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e848> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e848> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-21" daemon prio=1 tid=0x8c0c5948 nid=0x257e waiting on monitor
[0x90921000..0x90921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e278> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e278> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-20" daemon prio=1 tid=0x8c0d0470 nid=0x257d waiting on monitor
[0x90721000..0x90721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379dca8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379dca8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-19" daemon prio=1 tid=0x8c080798 nid=0x257c waiting on monitor
[0x90521000..0x90521890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d6d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d6d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-18" daemon prio=1 tid=0x8c080648 nid=0x257b waiting on monitor
[0x90321000..0x90321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d108> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d108> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-17" daemon prio=1 tid=0x8c032380 nid=0x257a runnable [0x90121000..0x90121890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-16" daemon prio=1 tid=0x8c0df9a8 nid=0x2579 waiting on monitor
[0x8ff21000..0x8ff21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379c568> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379c568> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-15" daemon prio=1 tid=0x8c0a6288 nid=0x2578 waiting on monitor
[0x8fd21000..0x8fd21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379bf98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379bf98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-14" daemon prio=1 tid=0x8c0dbd60 nid=0x2577 waiting on monitor
[0x8fb21000..0x8fb21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b9c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b9c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-13" daemon prio=1 tid=0x8c0c8498 nid=0x2576 waiting on monitor
[0x8f921000..0x8f921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b3f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b3f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-12" daemon prio=1 tid=0x8c0a6a28 nid=0x2575 waiting on monitor
[0x8f721000..0x8f721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ae28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ae28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-11" daemon prio=1 tid=0x8c07d348 nid=0x2574 runnable [0x8f521000..0x8f521890]
at java.lang.System.arraycopy(Native Method)
at java.lang.String.getChars(String.java:557)
at java.lang.String.concat(String.java:1554)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:251)
at com.ebao.carcase.servlet.claim.ClaimServlet.doGet(ClaimServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-10" daemon prio=1 tid=0x8c0369b0 nid=0x2571 waiting on monitor
[0x8f321000..0x8f321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379a288> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379a288> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-9" daemon prio=1 tid=0x8c079898 nid=0x256f waiting on monitor [0x8f121000..0x8f121890]
at java.lang.Object.wait(Native Method)
- waiting on <53799cb8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799cb8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-8" daemon prio=1 tid=0x8c035260 nid=0x256e waiting on monitor [0x8ef21000..0x8ef21890]
at java.lang.Object.wait(Native Method)
- waiting on <537996e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537996e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-7" daemon prio=1 tid=0x8c034510 nid=0x256d waiting on monitor [0x8ed21000..0x8ed21890]
at java.lang.Object.wait(Native Method)
- waiting on <53799118> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799118> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-6" daemon prio=1 tid=0x8c081130 nid=0x256c waiting on monitor [0x8eb21000..0x8eb21890]
at java.lang.Object.wait(Native Method)
- waiting on <53798b48> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798b48> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-5" daemon prio=1 tid=0x8c0c7108 nid=0x256b waiting on monitor [0x8e921000..0x8e921890]
at java.lang.Object.wait(Native Method)
- waiting on <53798578> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798578> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-4" daemon prio=1 tid=0x8c0a4388 nid=0x256a waiting on monitor [0x8e721000..0x8e721890]
at java.lang.Object.wait(Native Method)
- waiting on <53797fa8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797fa8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-3" daemon prio=1 tid=0x8c0367b8 nid=0x2569 waiting on monitor [0x8e521000..0x8e521890]
at java.lang.Object.wait(Native Method)
- waiting on <537979d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537979d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-2" daemon prio=1 tid=0x8c036290 nid=0x2568 waiting on monitor [0x8e321000..0x8e321890]
at java.lang.Object.wait(Native Method)
- waiting on <53797408> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797408> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-1" daemon prio=1 tid=0x8c0a4ee0 nid=0x2567 waiting on monitor [0x8e121000..0x8e121890]
at java.lang.Object.wait(Native Method)
- waiting on <53796e38> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53796e38> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-0" daemon prio=1 tid=0x8c0a4550 nid=0x2566 runnable [0x8df21000..0x8df21890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
at com.ebao.carcase.servlet.end.EndCaseServlet.service(EndCaseServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"TimeEventGenerator" daemon prio=1 tid=0x8c076008 nid=0x2565 waiting on monitor
[0x8dd21000..0x8dd21890]
at java.lang.Object.wait(Native Method)
- waiting on <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x8c0b34a0 nid=0x2563 waiting on monitor
[0x8db21000..0x8db21890]
at java.lang.Object.wait(Native Method)
- waiting on <53793040> (a weblogic.security.SpinnerThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:104)
- locked <53793040> (a weblogic.security.SpinnerThread)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
"Signal Dispatcher" daemon prio=1 tid=0x8c0077e8 nid=0x2561 waiting on monitor
[0..0]
"Finalizer" daemon prio=1 tid=0x8c000540 nid=0x255e waiting on monitor [0x8c2ff000..0x8c2ff890]
at java.lang.Object.wait(Native Method)
- waiting on <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
- locked <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80851f0 nid=0x255d waiting on monitor
[0x8bf8c000..0x8bf8c890]
at java.lang.Object.wait(Native Method)
- waiting on <53720208> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:415)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
- locked <53720208> (a java.lang.ref.Reference$Lock)
"main" prio=1 tid=0x804ead0 nid=0x2543 waiting on monitor [0xbfffc000..0xbfffd00c]
at java.lang.Object.wait(Native Method)
- waiting on <53743c20> (a weblogic.t3.srvr.T3Srvr)
at java.lang.Object.wait(Object.java:415)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1958)
- locked <53743c20> (a weblogic.t3.srvr.T3Srvr)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:148)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
"VM Thread" prio=1 tid=0x8082110 nid=0x255c runnable
"VM Periodic Task Thread" prio=1 tid=0x8c0064f8 nid=0x255f waiting on monitor
"Suspend Checker Thread" prio=1 tid=0x8c006e30 nid=0x2560 runnableThese are execute threads waiting for requests to come in.
BTW, you probably want to look into using StringBuffer instead of
strings concatenation in com.ebao.carcase.bean.query.Query.generatorXML.
"min.lu" <[email protected]> wrote in message
news:[email protected]...
>
In recent weeks, My customer's weblogic server become more busy.Each timeI downloaded
the thread dump when CPU is busy than 90%,I found a lot of lock in thethread
dump! Especially the class named "weblogic.kernel.ExecuteThread" . It'sthe kernel
class of weblogic, Why were most of them locked?
Full thread dump:
"process forker" daemon prio=1 tid=0x95b4c8e0 nid=0x3084 waiting onmonitor [0x977ff000..0x977ff890]
at java.lang.Object.wait(Native Method)
- waiting on <53d26420> (a java.lang.Object)
at java.lang.UNIXProcessForker.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"process reaper" daemon prio=1 tid=0x95376758 nid=0x3083 runnable[0x96eff000..0x96eff890]
at java.lang.UNIXProcessReaper.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x825bf18 nid=0x25a1waiting
on monitor [0x95dff000..0x95dff890]
at java.lang.Object.wait(Native Method)
- waiting on <53a3bd10> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53a3bd10> (a weblogic.time.common.internal.TimeTable)
atweblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:141)
at java.lang.Thread.run(Thread.java:479)
"ListenThread" prio=1 tid=0x94d00630 nid=0x25a0 runnable[0x95fff000..0x95fff890]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
- locked <538fa238> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
atweblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
"NBExecuteThread-1" daemon prio=1 tid=0x8c0dd1d0 nid=0x259c waiting onmonitor
[0x94521000..0x94521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9650> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9650> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"NBExecuteThread-0" daemon prio=1 tid=0x8c0dc7d0 nid=0x259b waiting onmonitor
[0x94321000..0x94321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a9060> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a9060> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
//"ExecuteThread-49" daemon prio=1 tid=0x8c034660 nid=0x259a runnable[0x94121000..0x94121890]
at java.net.PlainDatagramSocketImpl.peek(Native Method)
- locked <537acf60> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:349)
- locked <486f9980> (a java.net.DatagramPacket)
- locked <537acf40> (a java.net.MulticastSocket)
at weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:86)
at weblogic.cluster.TMSocket.execute(TMSocket.java:249)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-48" daemon prio=1 tid=0x8c0c3d18 nid=0x2599 waiting formonitor
entry [0x93f21000..0x93f21890]
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-47" daemon prio=1 tid=0x8c0c32d0 nid=0x2598 runnable[0x93d21000..0x93d21890]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- locked <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-46" daemon prio=1 tid=0x8c0bf410 nid=0x2597 waiting formonitor
entry [0x93b21000..0x93b21890]
atweblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
- waiting to lock <538fa5c8> (a java.lang.Object)
atweblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-45" daemon prio=1 tid=0x8c0be9c8 nid=0x2596 waiting onmonitor
[0x93921000..0x93921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6df8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6df8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-44" daemon prio=1 tid=0x8c0bdab0 nid=0x2595 waiting onmonitor
[0x93721000..0x93721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6828> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6828> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-43" daemon prio=1 tid=0x8c0bd068 nid=0x2594 waiting onmonitor
[0x93521000..0x93521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a6258> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a6258> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-42" daemon prio=1 tid=0x8c0c0ce0 nid=0x2593 waiting onmonitor
[0x93321000..0x93321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a5c88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a5c88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-41" daemon prio=1 tid=0x8c0c0298 nid=0x2592 waiting onmonitor
[0x93121000..0x93121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a56b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a56b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-40" daemon prio=1 tid=0x8c0a21e0 nid=0x2591 waiting onmonitor
[0x92f21000..0x92f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a50e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a50e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-39" daemon prio=1 tid=0x8c0d4520 nid=0x2590 waiting onmonitor
[0x92d21000..0x92d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4b18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4b18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-38" daemon prio=1 tid=0x8c0d43d0 nid=0x258f waiting onmonitor
[0x92b21000..0x92b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a4548> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a4548> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-37" daemon prio=1 tid=0x8c0d3988 nid=0x258e waiting onmonitor
[0x92921000..0x92921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a3f78> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a3f78> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-36" daemon prio=1 tid=0x8c0ded20 nid=0x258d waiting onmonitor
[0x92721000..0x92721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a39a8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a39a8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-35" daemon prio=1 tid=0x8c0de2d8 nid=0x258c waiting onmonitor
[0x92521000..0x92521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a33d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a33d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-34" daemon prio=1 tid=0x8c0cd528 nid=0x258b waiting onmonitor
[0x92321000..0x92321890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2e08> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2e08> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-33" daemon prio=1 tid=0x8c0ccae0 nid=0x258a waiting onmonitor
[0x92121000..0x92121890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2838> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2838> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-32" daemon prio=1 tid=0x8c075360 nid=0x2589 waiting onmonitor
[0x91f21000..0x91f21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a2268> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a2268> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-31" daemon prio=1 tid=0x8c0837d0 nid=0x2588 waiting onmonitor
[0x91d21000..0x91d21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a1c98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a1c98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-30" daemon prio=1 tid=0x8c0a5628 nid=0x2587 waiting onmonitor
[0x91b21000..0x91b21890]
at java.lang.Object.wait(Native Method)
- waiting on <537a16c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a16c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-29" daemon prio=1 tid=0x8c07aaf8 nid=0x2586 waiting onmonitor
[0x91921000..0x91921890]
at java.lang.Object.wait(Native Method)
- waiting on <537a10f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a10f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-28" daemon prio=1 tid=0x8c0c23d0 nid=0x2585 waiting onmonitor
[0x91721000..0x91721890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0b28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0b28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-27" daemon prio=1 tid=0x8c0c1988 nid=0x2584 waiting onmonitor
[0x91521000..0x91521890]
at java.lang.Object.wait(Native Method)
- waiting on <537a0558> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537a0558> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-26" daemon prio=1 tid=0x8c07ca00 nid=0x2583 waiting onmonitor
[0x91321000..0x91321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ff88> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ff88> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-25" daemon prio=1 tid=0x8c079e70 nid=0x2582 waiting onmonitor
[0x91121000..0x91121890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f9b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f9b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-24" daemon prio=1 tid=0x8c078038 nid=0x2581 waiting onmonitor
[0x90f21000..0x90f21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379f3e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379f3e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-23" daemon prio=1 tid=0x8c0a3298 nid=0x2580 waiting onmonitor
[0x90d21000..0x90d21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ee18> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ee18> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-22" daemon prio=1 tid=0x8c0e30d8 nid=0x257f waiting onmonitor
[0x90b21000..0x90b21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e848> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e848> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-21" daemon prio=1 tid=0x8c0c5948 nid=0x257e waiting onmonitor
[0x90921000..0x90921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379e278> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379e278> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-20" daemon prio=1 tid=0x8c0d0470 nid=0x257d waiting onmonitor
[0x90721000..0x90721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379dca8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379dca8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-19" daemon prio=1 tid=0x8c080798 nid=0x257c waiting onmonitor
[0x90521000..0x90521890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d6d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d6d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-18" daemon prio=1 tid=0x8c080648 nid=0x257b waiting onmonitor
[0x90321000..0x90321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379d108> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379d108> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-17" daemon prio=1 tid=0x8c032380 nid=0x257a runnable[0x90121000..0x90121890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-16" daemon prio=1 tid=0x8c0df9a8 nid=0x2579 waiting onmonitor
[0x8ff21000..0x8ff21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379c568> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379c568> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-15" daemon prio=1 tid=0x8c0a6288 nid=0x2578 waiting onmonitor
[0x8fd21000..0x8fd21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379bf98> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379bf98> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-14" daemon prio=1 tid=0x8c0dbd60 nid=0x2577 waiting onmonitor
[0x8fb21000..0x8fb21890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b9c8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b9c8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-13" daemon prio=1 tid=0x8c0c8498 nid=0x2576 waiting onmonitor
[0x8f921000..0x8f921890]
at java.lang.Object.wait(Native Method)
- waiting on <5379b3f8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379b3f8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-12" daemon prio=1 tid=0x8c0a6a28 nid=0x2575 waiting onmonitor
[0x8f721000..0x8f721890]
at java.lang.Object.wait(Native Method)
- waiting on <5379ae28> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379ae28> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-11" daemon prio=1 tid=0x8c07d348 nid=0x2574 runnable[0x8f521000..0x8f521890]
at java.lang.System.arraycopy(Native Method)
at java.lang.String.getChars(String.java:557)
at java.lang.String.concat(String.java:1554)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.claim.ClaimServlet.doPost(ClaimServlet.java:251)
at com.ebao.carcase.servlet.claim.ClaimServlet.doGet(ClaimServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"ExecuteThread-10" daemon prio=1 tid=0x8c0369b0 nid=0x2571 waiting onmonitor
[0x8f321000..0x8f321890]
at java.lang.Object.wait(Native Method)
- waiting on <5379a288> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <5379a288> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-9" daemon prio=1 tid=0x8c079898 nid=0x256f waiting onmonitor [0x8f121000..0x8f121890]
at java.lang.Object.wait(Native Method)
- waiting on <53799cb8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799cb8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-8" daemon prio=1 tid=0x8c035260 nid=0x256e waiting onmonitor [0x8ef21000..0x8ef21890]
at java.lang.Object.wait(Native Method)
- waiting on <537996e8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537996e8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-7" daemon prio=1 tid=0x8c034510 nid=0x256d waiting onmonitor [0x8ed21000..0x8ed21890]
at java.lang.Object.wait(Native Method)
- waiting on <53799118> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53799118> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-6" daemon prio=1 tid=0x8c081130 nid=0x256c waiting onmonitor [0x8eb21000..0x8eb21890]
at java.lang.Object.wait(Native Method)
- waiting on <53798b48> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798b48> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-5" daemon prio=1 tid=0x8c0c7108 nid=0x256b waiting onmonitor [0x8e921000..0x8e921890]
at java.lang.Object.wait(Native Method)
- waiting on <53798578> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53798578> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-4" daemon prio=1 tid=0x8c0a4388 nid=0x256a waiting onmonitor [0x8e721000..0x8e721890]
at java.lang.Object.wait(Native Method)
- waiting on <53797fa8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797fa8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-3" daemon prio=1 tid=0x8c0367b8 nid=0x2569 waiting onmonitor [0x8e521000..0x8e521890]
at java.lang.Object.wait(Native Method)
- waiting on <537979d8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <537979d8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-2" daemon prio=1 tid=0x8c036290 nid=0x2568 waiting onmonitor [0x8e321000..0x8e321890]
at java.lang.Object.wait(Native Method)
- waiting on <53797408> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53797408> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-1" daemon prio=1 tid=0x8c0a4ee0 nid=0x2567 waiting onmonitor [0x8e121000..0x8e121890]
at java.lang.Object.wait(Native Method)
- waiting on <53796e38> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:100)
- locked <53796e38> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:127)
"ExecuteThread-0" daemon prio=1 tid=0x8c0a4550 nid=0x2566 runnable[0x8df21000..0x8df21890]
at java.lang.String.concat(String.java:1553)
at com.ebao.carcase.bean.query.Query.generatorXML(Query.java:239)
at com.ebao.carcase.bean.query.Query.generatorXMLByList(Query.java:158)
at com.ebao.carcase.servlet.common.CommonBean.query(CommonBean.java:652)
atcom.ebao.carcase.servlet.end.EndCaseServlet.service(EndCaseServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
at weblogic.servlet.ServletServlet.service(ServletServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:945)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:909)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:269)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
"TimeEventGenerator" daemon prio=1 tid=0x8c076008 nid=0x2565 waiting onmonitor
[0x8dd21000..0x8dd21890]
at java.lang.Object.wait(Native Method)
- waiting on <53795330> (a weblogic.time.common.internal.TimeTable)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
- locked <53795330> (a weblogic.time.common.internal.TimeTable)
atweblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:141)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x8c0b34a0 nid=0x2563 waiting onmonitor
[0x8db21000..0x8db21890]
at java.lang.Object.wait(Native Method)
- waiting on <53793040> (a weblogic.security.SpinnerThread)
at java.lang.Object.wait(Object.java:415)
atweblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
4)
- locked <53793040> (a weblogic.security.SpinnerThread)
at weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:121)
"Signal Dispatcher" daemon prio=1 tid=0x8c0077e8 nid=0x2561 waiting onmonitor
[0..0]
"Finalizer" daemon prio=1 tid=0x8c000540 nid=0x255e waiting on monitor[0x8c2ff000..0x8c2ff890]
at java.lang.Object.wait(Native Method)
- waiting on <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
- locked <537202f8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80851f0 nid=0x255d waiting onmonitor
[0x8bf8c000..0x8bf8c890]
at java.lang.Object.wait(Native Method)
- waiting on <53720208> (a java.l -
Wrong answer to question ... but thread is locked.
Hey guys,
i was looking for a solution for the problem described in this thread:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/d6a6b014-c09c-4436-9f18-0f151bae85b5/caculated-column-formula-for-workdays-between-two-dates-excluding-weekends-datediff?forum=sharepointcustomizationlegacy
I was looking over the formula that was marked as answer and (in case im not wrong) checked it. In my view this answer isnt correct. Proof:
Just one scenario to show it: Assume starting day is thursday and end is a sunday 2 weeks later for example. Because Sunday is later than Friday the IF-condition is false and the ELSE-statement is done. Here only 2 weekends are taken out of the total difference
though there are 3 in this time span. (because the FLOOR rounds down which brings wrong results).
Well maybe it takes some time to figure out not working on this, but my MAIN issue here is that this thread is LOCKED and i cant even discuss or respond and the guys are probably using a wrong formula.
Any help / suggestions?
Regards
PatrickHi Patrick,
Considering that the thread you've linked to is from 2009, I'm not totally surprised that it's locked. The OP appears to still be an active user here on the forums, but everyone else from that thread hasn't been active for at least a few months (or years).
You can always start a new thread and provide a link back to that thread as background for anyone reading your thread.
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing) -
Why wait() is there in Object class why not in Thread class
why wait() is there in Object class why not in Thread class .
while we use wait() in the case of thread environment?
If there is any situation where we use it without using threads please mention with example. or link to that example..839091 wrote:
The question still remain un-answered as the answers provided are not clear. Can anybody explain why wait(), notify() methods are available in Object class and not thread?What part of the answers given did you not understand?
Have you even tried writing any code that uses wait/notify and thought about how you'd write the same code if they existed only on Thread rather than on Object?
Have you studied the basics of Java's multithreading?
Do you know what a lock is?
Do you know what the synchronized keyword does?
Do you understand the relationship between synchronized and wait/notify?
If you can answer yes to these questions, then the reason that wait/notify exist on Object should be obvious. So, which of the above are "no"? -
Why are the threads start and terminate randomly?
Hi there,
I got the program below. I am wondering why are the threads start and terminate randomly? Everytime, I run the program, it produces different results.
I know that these four threads have got same normal priority (should be 5), and under windows there is something called timeslice. Then these four threads rotate using this timeslice. How do we know what exactly the timeslice is in seconds? If the timeslice is fix, then why the results are ramdom?
Thanks in advance!
* To change this template, choose Tools | Templates
* and open the template in the editor.
package mythreadone;
* @author Administrator
public class MyThreadOne implements Runnable {
String tName;
Thread t;
MyThreadOne(String threadName) {
tName = threadName;
t = new Thread(this, tName);
t.start();
public void run() {
try {
System.out.println("Thread: " + tName);
Thread.sleep(2000);
} catch (InterruptedException e) {
System.out.println("Exception: Thread "
+ tName + " interrupted");
System.out.println("Terminating thread: " + tName);
public static void main(String args[]) {
// Why are the threads start and terminate randomly?
new MyThreadOne("1");
new MyThreadOne("2");
new MyThreadOne("3");
new MyThreadOne("4");
try {
Thread.sleep(10000);
// Thread.sleep(2000);
} catch (InterruptedException e) {
System.out.println(
"Exception: Thread main interrupted.");
System.out.println(
"Terminating thread: main thread.");
1. Firstly, I set in the main function:
Thread.sleep(10000);
and I run the program it gives:
Thread: 1
Thread: 4
Thread: 2
Thread: 3
Terminating thread: 1
Terminating thread: 3
Terminating thread: 4
Terminating thread: 2
Terminating thread: main thread.
BUILD SUCCESSFUL (total time: 10 seconds)
Run it again, it gives:
Thread: 2
Thread: 4
Thread: 3
Thread: 1
Terminating thread: 2
Terminating thread: 1
Terminating thread: 3
Terminating thread: 4
Terminating thread: main thread.
BUILD SUCCESSFUL (total time: 10 seconds)
And my question was why it outputs like this? It suppose to be:
Thread: 1
Thread: 2
Thread: 3
Thread: 4
Terminating thread: 1
Terminating thread: 2
Terminating thread: 3
Terminating thread: 4
Terminating thread: main thread.
BUILD SUCCESSFUL (total time: 10 seconds)
Why these four threads start and finish randomly each time I run the program? I use Windows, suppose there is a timeslice (i.e. 1 second), these threads have the same priority. Then the threads should start and finish in turn one by one. Am I right?
2. My second question is:
When I change the codes in the 'main' function into:
Thread.sleep(10000); -> Thread.sleep(2000);
it gives me the results like:
Thread: 1
Thread: 4
Thread: 3
Thread: 2
Terminating thread: main thread.
Terminating thread: 1
Terminating thread: 4
Terminating thread: 3
Terminating thread: 2
BUILD SUCCESSFUL (total time: 2 seconds)
Run it again:
Thread: 1
Thread: 2
Thread: 3
Thread: 4
Terminating thread: 3
Terminating thread: main thread.
Terminating thread: 4
Terminating thread: 2
Terminating thread: 1
BUILD SUCCESSFUL (total time: 2 seconds)
I tried several times. The main thread always terminates before or after the first child thread finished.
My question is why it doesn't output something like:
Thread: 1
Thread: 2
Thread: 3
Thread: 4
Terminating thread: 3
Terminating thread: 4
Terminating thread: 2
Terminating thread: main thread.
Terminating thread: 1
BUILD SUCCESSFUL (total time: 2 seconds)
or
Thread: 1
Thread: 2
Thread: 3
Thread: 4
Terminating thread: 3
Terminating thread: 4
Terminating thread: 2
Terminating thread: 1
Terminating thread: main thread.
BUILD SUCCESSFUL (total time: 2 seconds)user13476736 wrote:
Yes, my machine has multi-core. Then you mean that if I got a one core machine the result should always be:
Thread: 1
Thread: 2
Thread: 3
Thread: 4
Terminating thread: 1
Terminating thread: 2
Terminating thread: 3
Terminating thread: 4
Terminating thread: main thread.
BUILD SUCCESSFUL (total time: 10 seconds)
???No.
>
How to explain my second quesiton then? Why the main thread always terminates before some of the child threads end? Thanks a lot. -
"Common" questions thread/board/whatever
I have been seeing so many repeat questions lately that really are very common. How to update control values programmatically and how to pass data between parallel loops to name the two I see most.
I have a suggestion that we create a common questions thread that is put together with links to common forum questions. This can be a sticky, or maybe force it to come up at the beginning of every search no matter the key words put in. I'm obviously open to other suggestions and I'm posting this because there would need to be other things resolved (can all members post to the thread or just NI staff so we avoid follow up questions? Which links to common question responses would be added to the thread? How do we determine the BEST answers? etc.) However, I think it would be a nice place to point users to, rather than to have to go dig up an old thread and point the users to it ourselves, when it's really what they should have looked for in the first place. We could just post a link to the "common questions thread"
This would save ben from posting his AE nugget link (which he probably has memorized) every day, or people repeatedly posting "try a producer-consumer queued state machine - see NI template that is included with LabVIEW"...and the list goes on.
Any comments on how to implement this, or why it's just a bad idea in general?
Message Edited by for(imstuck) on 06-03-2010 10:15 AM
CLA, LabVIEW Versions 2010-2013JackDunaway wrote:
Ben wrote:
The serahes can be improved by US !
Tags are included in the serach. If someone asks about a "niad pulse converter" without mentioning it by name, the search engine could have trouble. But if we know about the thread where a conversation took place, we can add tags to that thread with words that appeared in their original Q. The next time some asks, the tags will show in their search.
TAGS have the potential of codifying YOUR expertise in such a way that a novice can stand on your foundation.
Ben
Ben, good plug for tagging - there's one problem though. You're by far the most diligent tagger, but most of your tags are hyphenated or underscored on the compound words. For instance, if I search for "Converting array to cluster", I'm guessing the search engine would not return the result that you have tagged "ConvertingArray-to-Cluster". Or am I wrong here - does the search engine throw out the hyphens and underscores?
A Quick search from my Forum_Tips tag yielded this and I quote"
Ben wrote
The search
engine is smart enough to ignore
underscores. So by constructing tags using an underscore between key
words let you create a connection between them.
All tags
(a text string delimited by spaces before and after) are counted and a
connection made when they are included for the same post.
So
by
constructing hierachial names and grouping them in a sinlge post you
create structure that if repeated, will create your own outline.
I have to Say, I'm liking tags more and more ! !
Message Edited by Jeff Bohrer on 06-08-2010 05:10 PM
Jeff -
Hi
Can anyone help with this please.
I bought my iphone 4s outright, brand new, 2 years ago from the Apple Store, not as part of a contract. I've been on a Sim only contract from "3" network from the outset. I now want to change my network provider, but I was informed my phone was locked. I went into the O2 Store to look for a sim only and the lady asked if my iphone was locked. I didn't know so she checked it by putting one of their sims in it and she told me it was indeed, locked.
So I go back to the 3 store and they tell me to ring 3 cust. services to get it unlocked. However, a friend of mine informs me that the phone should not be locked at all and it is Apple's responsibility to unlock it.
Help, I'm very confused.
Thank you.Thanks Tim.
I had no idea at the time that I had to specifically ask for an unlocked phone. I'd not owned any smart phones prior to this.
It begs the question: Why on Earth would anyone sell a "Locked" phone, or indeed, why would anybody buy a locked phone. I should have been told at the time surely, why would I want to limit my choices?
Oh well, looks like a call to 3 then.
Cheers. -
Why my icloud has been locked !!! and i cant reset because my icloud is my reset email!!!
why my icloud has been locked !!! and i cant reset because
my icloud is my reset email!!!Use the Security Questions option: If you forgot your Apple ID password - Apple Support
OR
Contact Apple: Apple ID: Contacting Apple for help with Apple ID account security - Apple Support -
Hi,
I was just wondering if someone could tell me why this innocuous thread was censored.
As you can see, the question concerned a malfunctioning Help Viewer that, based on the description of the problem, I thought needed to be reset. I directed the user to the X Lab's page on troubleshooting the Help Viewer, and I also excerpted from that page the steps necessary to reset the Help Viewer (a small subset of a very lengthy page).
The portion that was excised was the excerpt.
The excerpt wasn't particularly long, only seven itemized steps plus some additional explanatory language. I included it, rather than just referring the OP to the linked Web page, because the OP seemed to me to be a new user -- he/she had registered only yesterday and had a total of two posts so far -- and the X Lab Web page on troubleshooting the Help Viewer is quite extensive, much lengthier than other such troubleshooting pages, and I was concerned that the OP might easily get lost if given only the link.
If I violated any Discussions rule by including the excerpt, I'm unaware of it and would like to know so that I don't unintentionally violate it again.
Thanks for your time.
-- JDee518/2964
Hi Donald, ~JB~, JDee and all,
"Or is that allowed on the boards as long as you declare you are quoting an apple document?"
We do that all the time, no problem. Just clearly indicate that the excerpt is from KB article #xxxxx, you use it to help pointing the info you're giving in your reply.
Anyway that's what you naturally do, to strenghten your point, don't you?
This is just a matter of using other's knowledge in a proper, civil way, giving credits to the author.
Come on, it's worked perfectly until now, between normal, honest, sensible people,
are you sure this too has to become an issue and a political debate???
--> EXAMPLE: (about the eMac PSU)
How do you write "configured for 100-120V AC or 200-240V AC depending on country of use" without quoting, please?
By adding spaces between letters?
Oh God I'm so fed up with those disclaimers (especially those that are used as advertisements but not obviously enough so they still comply with the TOU), please, Apple Discussions are just nice, friendly, technical discussions forums!!
No lawyer needed (yet?) to post a reply, and no KGB either!
Thanks!!
Regards.
Axl
About the so famous "BlankMacHelpthisisacommonproblemjustdeletethisfolderandthesefiles"
question:
Why don't you write your own version like many did already?
You could for example add some spaces to the above...
Disclaimer:
"Although I doubt it very much, I may receive some form of compensation, not financial but as a small yellow or as a big green star, from my recommendation or link." -
How can I create a new Question thread?
How to create a new "Question Thread" regarding the account payment ?
Hello MotionBoy,
There are two ways to go about creating a new thread to run a step. The first is to create a new sequence, into which you put the LabVIEW step you want to run and any other steps that may go along with it. Then use a sequence call step to call this newly created sequence. Set the Execution Options of the Sequence call step to 'Use New Thread.' This will allow you to run a set of steps in a new thread, not just a VI. The second method, which is only available for a LabVIEW VI, is to use the “Run VI Asynchronously” step. This can be accessed if you right-click within your sequence and select Insert Step » LabVIEW Utility » Run VI Asynchronously. This step will allow you to call a VI and have it automatically open in a new thread. You can further customize this step by opening the configuration menu in the Step Settings.
To address the current behavior of your steps I would like to know if the modules in steps 1 & 2 pass data between them or it would be desirable for them to do so? If so you are going to need a more complex synchronization structure such as TestStand/LabVIEW queues. There is a simple example you may want to look at in the TestStand examples, under the Synchronization folder that demonstrates how to use queues. Otherwise the above solution should be all you need.
John B.
Applications Engineer
National Instruments -
STS: Why data can't be locked when status is sent to approval.
Hi All,
I'd like to ask about STS, I have a problem on it. I'm working in IP.
Why data can't be locked though the status is already in "send to approval" ?
I've setup data slice under the corresponding cube based on exit class: CL_UPS_LOCK_DATASLICE.
Is it because I've yet to assign R_STS_PT authorization to the planner ? So when I'm opening the data using planner user id, data is still not locked yet.
Could you kindly help me to resolve this problem please ?
Thanks a lot all,
Have a good day,
Best regards,
Daniel N.Hi Daniel,
Thanks for the response, much appreciated, a bit of good fortune that I ran into someone in April 2010 who is having the same problem as me on the obscure STS!
I have some queries about your response;
1) You say to create planning a function within a sequence to copy the status., did you mean to copy the version?
2) So the basic principle is, when a user submits data for approval, they use the STS monitor's 'Approval' button, this then triggers the planning sequence to copy data which they just planned to a certain version, this version is hard coded into the data slice, is this correct?
3) What happens then when the higher level manager approves the data, is this then unlocked by copying to another version?
If you could please break it down for me.
Appreciate your time & help.
Regards
SS
Hi Sulman,
You can create function and planning sequence to copy the status.
Then you create dataslice based on particular status to block data from data entry.
You can embed the planning sequence to STS using t-code: BPS_TC.
Thanks a lot .
Best regards,
Daniel N. -
I forgot my security questions, now Im locked out of my account. How can I log in. I just wanted to change my password
You need to ask Apple to reset your security questions; ways of contacting them include clicking here and picking a method for your country, and filling out and submitting this form.
(96789) -
hi i dont remamber my security questions and the lock my apple ID what should i do pleas help me.
Contact Apple for assistance with your security questions > Contacting Apple for support and service as the link suggests that you posted from.
This is a user to user forum. No one here can help reset your security questions, only Apple.
Maybe you are looking for
-
HP 1200 not printing pdfs/uses default fonts in Word docs
Happy Birthday USA! Last week I loaded 10.4.10 to Mac mini and eversince I have not been able to print pdfs from Adobe Reader or print desired fonts from Word. (I have overcome default to US letter problem in Word) I have loaded latest drivers from H
-
Can't see external firewire drive (DOS Fat 32) over network
When I connect to another computer via airport (old/slow airport) I can't see a firewire 400 drive that is connect to the computer. The drive is mounted and working properly on the networked computer. The only caveat I can think of is that it has bee
-
UCCE: Forceful Release an Agent Call from ICM Script, Can I?
Hi, let me explain the requirement first. Customer wants to make their IVR free of cost but they want to start billing only when the call is landed to skill group/agent. So far I can think to make it possible by triggering their billing server by ODB
-
Is installation on 2.16 GHz Intel Core Duo (MacBook Pro)really not possible and why?
I would like to buy OS X Lion and install it on my MacBook Pro with 2.16 GHz Intel Core Duo, but this processor is not in the list of the specifications (Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7 or Xeon processor). Is it reall
-
Adding third address line to infotype-6
I want to add a custom field say. third address line to infotype-6. I want this field to be displayed just below the address line 2 in infotype-6 and not under additional fields. Is there any way to add this field. If I do this using transaction PM01