Threads Critical

How could I change the two classes below so that the
two threads take turns to be in their critical sections,
and they aren't allowed to take two consecutive turns.
Thanks.
public class SharedVariables extends Object {
public int turn;
public boolean[] flag = new boolean[2];
public SharedVariables() {
flag[0] = false;
flag[1] = false;
// A thread running SectionedCode alternates between
// a critical section and the remainder.
public class SectionedCode implements Runnable {
int this_thread, other_thread;
SharedVariables s;
public SectionedCode( int tid, SharedVariables SV ) {
this_thread = tid;
other_thread = 1 - tid;
s = SV;
public void run() {
while ( true ) {
s.flag[this_thread] = true;
s.turn = other_thread;
while ( (s.flag[other_thread] == true) && (s.turn == other_thread) )
Thread.yield();
System.out.printn("Thread "+this_thread+ "incritical section");
s.flag[this_thread] = false;
System.out.println("Thread " + this_thread + " in remainder");
}

Cant it be done without synchronisation?If you created a boolean and a char variable, using the boolean to indicate whether or not the method is in use and the char indicates which thread last used the method, that would work. What you have effectively done is to implement your own version of synchronization. :->
Mark

Similar Messages

  • Swing's Single Threading Rule - recipe please?

    Hi there,
    Some dust has been kicked up with JSR-296 being worked on, and we're seeing lots SwingUtilities.invokeLater advocates piping up on their blogs.
    Being from the very 'old school', and not so often delving into intense Swing-isms, I'd like to learn the "right way" of doing things, and also to which granularity these should be applied.
    For reference, take a look at this blog: http://weblogs.java.net/blog/cayhorstmann/archive/2007/06/the_single_thre.html
    Sadly enough, the "StillBad" example is precisely how we were taught in University long ago. Some clarification is required:
    --> Which methods do we need to wrap into invokeLater blocks precisely?
    from what I can gather, it seems that any function that affects GUI state needs to be wrapped as such? It sure seems a ginormous PITA to have to wrap every last "setText" in an invokeLater Runnable.... doesn't this incur a pretty considerable object instantiation overhead?
    What's the "right way"?
    Thanks!
    Alex

    You're referring to the setVisible call in the component's constructor? The Java STR page would seem to exact that no harm is done in doing so, since nothing takes place post-realization. This doesn't stand?
    Like I say, it depends on when your constructor is called. If it's called directly from main() then the setVisible() (but not the subsequent setText()) is ok.
    My point is that doing this sort of thing in a constructur is A Bad Idea; because, (a) in a constructor you've no idea if you're being called at the start of the main() method or if you're being called way downstream by another bit of UI or whatever, and (b) it pre-empts what the caller is planning to do with the object - imagine creating a JPanel which went and found a component in the hierarchy and added itself - hey, I wasn't going to put it there - and whilst it's a reasonable argument that you're not likely to do much else with a frame other than display it, there may well be things you want to do before displaying it.
    So, if we lose the line that realizes the component, we not only get a more usable and predictable constructor (remember polymorphism: a JFrame doesn't make itself visible when it's constructed; yours shouldn't diverge dramatically from that behaviour - it looks like a duck but it doesn't quack like a duck) but we also lose the line that causes everything downstream to be thread critical.
    In a main method, I've never once put my initial UI constructing code, from the frame constructor to the pack()/setVisible() calls on the EDT via SwingUtilities.invokeXxx(). And I've never encountered a problem.
    Yup, that's what the documentation is saying: that's not going to cause issues. The confusing bit here is that the OP's written a constructor that looks like a 'typical'* main() method :)
    Like I say, seeing as there's only a very short and transient period where working off the EDT is valid, it's generally best to make it wholly unconfusing and do 100% of the Swing stuff on the EDT.
    * in tutorials at least

  • Errors and shut down CONSTANTLY

    I am having trouble with my S10 since I got it and I haven't seen anyone else with these posts. The screen turns to blue, comes up with error codes ( Stop 0x0000003, 0x85573b28, 0x85573c9c, 0x805D297c) A process or thread critical to system operation has failed.Beginning physical memory dump.
    I called customer service and initially they were quite helpful. Instituted returning the computer for repair. (reset bios, reimaged hard drive, reset factory defaults. (incidentally, the time won't stay set) I received it back and the very first time I booted it up, same thing. I called again, and as directed, let them know it was a returned repair. Not so helpful the second time around. I still get the messages (now a new one too, Stop C000021A. I understand this may be a small glitch, but some help would really be appreciated!
    I am running simple applications, no video, I don't think this should be happening and I guess I am not the only one disappointed with support from what I have seen on these forums.

    Did you try a restore to factory default?
    If so did the problem clear.
    If the S10 works correctly after the Restore to factory default but before you install any software then the problem is not with the S10
    Frank
    Kenmore, WA
    USA

  • StuckThread issues

    e had a crash of our weblogic managed server on linux box at 11:00am today (Thurs., Oct. 28). We believe this was due to various stuck threads (all becoming stuck in the main servlet http request) and socket exceptions (too many open files), but I would like your help please!
    In our output log for managed server, it noted 13 total stuck threads. At the time of crash, I noticed in the log, amongst the 13 total stuck threads, Critical messages stating:
    "<Oct 28, 2004 11:01:50 AM EDT> <Critical> <WebLogicServer> <BEA-000204> <Failed to listen on port 12175, failure count: 27, failing for 228 seconds, java.net.SocketException: Too many open files> "
    Does what I described seem to imply that there is a file descriptor leak in our application, thus causing the weblogic managed server hang/crash? That's what I believe the cause is. We set ulimit in our startup script as: ulimit -n 1024. This seems reasonable.
    Any advice on this matter would be greatly appreciated.
    Thank you,
    nj
    Below find some e error output until time of outage/crash:
    <...dispatcher has been busy for "1,243" seconds working on the request "Http Request: dispatcher", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
    (and about 12 more of these StuckThread errors between some of the below errors on file descriptors)
    <Oct 28, 2004 11:01:40 AM EDT> <Critical> <WebLogicServer> <BEA-000206> <Attempting to close and reopen the server socket on port 12175.>
    <Oct 28, 2004 11:01:50 AM EDT> <Notice> <WebLogicServer> <BEA-000203> <Reopening listen socket on port 12175.>
    <Oct 28, 2004 11:01:50 AM EDT> <Critical> <WebLogicServer> <BEA-000204> <Failed to listen on port 12175, failure count: 27, failing for 228 seconds, java.net.SocketException: Too many open files>
    <Oct 28, 2004 11:01:50 AM EDT> <Critical> <WebLogicServer> <BEA-000206> <Attempting to close and reopen the server socket on port 12175.>

    Hi,
    BEA suggested value was 8096. Please consult the OS admin on how to make this change. We had a similar issue and specifying a ulimit command in ur startup script did not have any impact as the OS(in my case it was SunOS) over writes this setting when a new process is stared.
    Try using lsof command when the server hangs.This command should tell if max descriptors have reached and use pfiles command to check if ulimit setting changed the descriptor limit as u specified
    Hope this helps
    Jagan

  • Ruby-enterprise 1.8.7-12: timeout.rb:60: [BUG] Segmentation fault

    Something in timeout.rb is making gem segfault.  There's discussion around the Internet about glibc 2.14 giving ruby a hard time, so perhaps this is relavant to the issue, being that we're on 2.15 now?
    $ sudo gem update --system
    /opt/ruby-enterprise/lib/ruby/1.8/timeout.rb:60: [BUG] Segmentation fault
    ruby 1.8.7 (2012-02-08 MBARI 8/0x6770 on patchlevel 358) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2012.02
    Where line 60 lives:
    52 def timeout(sec, klass = nil)
    53 return yield if sec == nil or sec.zero?
    54 raise ThreadError, "timeout within critical session" if Thread.critical
    55 exception = klass || Class.new(ExitException)
    56 begin
    57 x = Thread.current
    58 y = Thread.start {
    59 begin
    60 sleep sec
    61 rescue => e
    62 x.raise e
    63 else
    64 x.raise exception, "execution expired" if x.alive?
    65 end
    66 }
    67 yield sec
    68 # return true
    69 rescue exception => e
    70 rej = /\A#{Regexp.quote(__FILE__)}:#{__LINE__-4}\z/o
    71 (bt = e.backtrace).reject! {|m| rej =~ m}
    72 level = -caller(CALLER_OFFSET).size
    73 while THIS_FILE =~ bt[level]
    74 bt.delete_at(level)
    75 level += 1
    76 end
    77 raise if klass # if exception class is specified, it
    78 # would be expected outside.
    79 raise Error, e.message, e.backtrace
    80 ensure
    81 if y and y.alive?
    82 y.kill
    83 y.join # make sure y is dead.
    84 end
    85 end
    86 end

    Yeah! Solved!
    Install gcc45 from the AUR, compile and install it, then download the ruby-enterprise from the AUR and compile it like so:
    CC=gcc-4.5 makepkg
    Install the compiled Ruby EE package, and wham, it works.

  • Why is time-critical thread not interrupting sleepless high priority thread?

    Hello,
    I have two threads running in the same execution system on a real-time PXI platform. The time-critical thread sleeps using "AI Single Scan.VI", and acquires my data at a rate of 8000 Hz.
    I have a slower high priority process that calls a DLL function to calculate some filter coefficients. This function call takes longer than 1/8000 s to complete, and runs in a loop, executing as often as it can (with new data from FIFOs).
    I expected the time-critical thread to interrupt the the high priority thread without problem.
    I am finding that unless I insert a LabVIEW delay (for example a wait for x ms VI) in the loop, the real-time system stops responding. With a small delay (ie 1 ms), t
    he acquisition completes, and a FIFO shuts down the loop of the slow process.
    Why do I need a labVIEW delay in the high-priority loop, when the DLL function call itself is quite slow? Even without a DLL call, I would expect the time-critical VI to interrupt, finish its data acquisition, and shut-down the high-priority thread using its FIFO.
    Any suggestions?
    Thanks in advance,
    Frenk

    Here are a couple things to try/check:
    1) Check the call library node in your high priority VI. If it's orange (runs in UI thread), your high priority VI is actually switching to the UI thread every time your dll runs. That alone is not a problem. But if your TC VI tries to update any control terminals, the TC thread will switch over to the UI thread to access UI resources, possibly while the dll within your high priority VI has a lock on those resources. Why does the dll have a lock on UI resources? Because it was running in the UI thread and got interrupted by the TC thread before it finished doing its business. Not likely, but possible.
    2) There's another possible reason you're seeing this behavior. If the TC VI and the high VI call a mutual subVI, the subVI will be elevated to ALWAYS run in the highest priority thread irrespective of the actual caller (in your case, it's the the TC thread). Even when the *high priority VI* calls the mutual subVI, that subVI runs in the time-critical thread, which means there's a thread switch from high to TC, then back to high after the subVI finishes. And because high and TC VIs are in the same exec system, that mutual subVI will always run in the 1 and only TC thread alotted to that exec system.
    So, while your TC VI is running, you're in the TC thread. While, your high VI is running, you're in a high non-TC thread, and when your high VI calls the mutual subVI, you're again in the TC thread until the subVI finishes.
    So how could this arrangement cause your TC VI to become starved by the high VI? If your TC VI wakes up while the high VI is in the middle of running the mutual subVI, the TC thread responsible for running the TC VI is actually busy (in the middle of running the subVI in your high VI!!!), so the TC thread cannot run your TC VI until it finishes running that mutual subVI.
    The fix: make your TC VI run in a different exec system. It will be given its own TC thread that no one else can mess with. When TC VI wakes up, it's guaranteed a TC thread.
    I think there's a good reason behind why a mutual subVI ALWAYs runs at the highest priority of all its callers, irrespective of the actual caller's priority...but I can't think of the reason at the moment.

  • Why does that entire thread goes to sleep when we put a wait function in time critical loop?

    why does that entire thread goes to sleep when we put a wait function in time critical loop but not when it is not time critical

    Norbert B wrote:
    Ujjval,
    in a RT system, priorities have (in general) increased effect on the execution of the application.
    It is recommended that you only have a single task in your RT program at "time critical". If you have two task "time critical" (that means you are running into issues caused by your quoted "feature"), you have a flaw in your application architecture.
    Since LV 7.1, it is recommended to work with Timed Loops in order to prioritize tasks on a RT system. Timed Loops are executed on priorities between "time critical" and "above normal". Each Timed Loop will execute its content in a single thread in order to keep a good overview of the timing (like finished late [i-1]). Using those structures (and according settings) in a reasoned manner will prevent your RT system to run into priority issues.
    Ujjval Shah wrote:
    [...]also i would really appreciate if i can get more documentations regarding how LV creates threads and assigns subvis to them[...]
    You will have a real hard time to go into this very deep. This is the feature of LV: you can just use multithreading (multicores) without the needed knowledge of scheduling and load balancing. This makes LV programming in general very easy in comparison to e.g. ANSI C (in regard of multithreading). So creation of threads, distribution of tasks to the threads are abstracted and most often not visible to the programmer.
    There are some switches and levers you can "play around" in order to make LV to behave differently in this matter. But this most often requires  deep LV knowledge and cannot be explained in a simple posting.....
    hope this helps,
    Norbert 
    Amen to that!
    The question can not be fully answered without digging into the internals of the OS LV is run on because LV works with the OS and lets it do the scheduling.
    Yes that note applies to pre- LV 7 RT. When run under RT the ONE Time Critical loop was guarenteed to stay determinisitic.
    Since then the Timed Loop was introduced that allowed multiple levels of priority and later allowed us to assign which CPU the code would run on.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Scritical scenarious and critical threads

    Iam attending an interview after 2 days could anyone send me real time scenarios in GL,AP,AR please to this id [email protected]
    please help me ..i will reward this points..
    its very urgent ..hope to see some replys to my email id
    thanks in advance

    Julius wrote:
    > 1 abuse raises an alert.
    > 10 abuses automatically removes the post.
    >
    Otto Gold wrote:
    > Ok, but I don´t want to waste the time of the moderators. Somebody has to go through the abuse report.
    >
    Otto if what Julius says is true then no one needs to go through the abuse/stupid category report. After 10 negatives the post is removed automatically. I guess in your case you would want the offending post to be relocated to the Playground forum rather than removed completely.
    I suppose you could keep the existing abuse button and after 10 negatives the post is relocated to the playground forum. Moderators could then decide what step to take next. Remove the post, leave in playground, reinstate in original forum or reinstate in original forum with warning, etc.
    Che
    Edited by: Che Eky on Dec 22, 2010 5:47 PM

  • A critical error has occured. Processing of the service had to be terminate

    When manager wants to approve the employee leave request its giving following error.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
      Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE   
      Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.lea.form.FcForm.getCustomizing(FcForm.java:1020)
         at com.sap.xss.hr.lea.form.FcForm.onInit(FcForm.java:417)
         at com.sap.xss.hr.lea.form.wdp.InternalFcForm.onInit(InternalFcForm.java:2053)
         at com.sap.xss.hr.lea.form.FcFormInterface.onInit(FcFormInterface.java:184)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.onInit(InternalFcFormInterface.java:1911)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.onInit(InternalFcFormInterface.java:2007)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.xss.hr.lea.worklist.VcWorkList.onInit(VcWorkList.java:267)
         at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.onInit(InternalVcWorkList.java:363)
         at com.sap.xss.hr.lea.worklist.VcWorkListInterface.onInit(VcWorkListInterface.java:164)
         at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkListInterface.onInit(InternalVcWorkListInterface.java:144)
         at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkListInterface$External.onInit(InternalVcWorkListInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Access via 'NULL' object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Customizing_Get(LeaveRequestAdaptiveModel.java:392)
         at com.sap.xss.hr.lea.model.Pt_Arq_Customizing_Get_Input.doExecute(Pt_Arq_Customizing_Get_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 47 more
       kindly help ASAP,

    Hi,
    Did you give enough authorizations to the user at the beack end.
    Just Try giving SAP_ALL authorizations and check.
    Regards,
    Santhosh

  • What are the critical points to validate whether the client uses PP or not?

    Hi,
    We are woking for a project which involves more than 80 SAP instances (80 clients), and with in the same instance we have more than one country (e.g: client 100 may have 5 countries india, srilanka, bangaladesh, china and singapore). Now our challenge is to validate which are the countries using SAP PP Shop floor control activities (Creation of Production orders, settlement etc...). Please list the critical points against which we can validate. Hope my question is clear. Any clarification required please reply to this thread. Expecting quick response from the experts. Thank you.
    Note: I have tried using "workscheduling view" of material master, COOIS report etc.., still i did not get clear validation. I would appreciate if experts provide technical validation points.
    BR
    Raam

    Dear Krishnan,
    First thing is you have to know whether client is using
    Discrete , REM or PP-PI
    From Discrete point of View ( Configurations )
    Check in
    OPJH, OPL8, OPKJ, OPK4, OPKP ( whether for plant & order type combination parameters are maintained are not )
    Coming to REM
    check in OSP2, whether REM profile settings are maintained for the plants
    Coming to Master data
    just refer the below link & check give the plant as input
    [Tables;
    Regards
    kumar

  • Exchange 2010 SP2 RU2 - Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases

    We have been getting intermittent SCOM alarms for our Exchange 2010 MBX server citing "Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases"
    I see events in EventViewer that SCOM is triggering on, but not whats generating the events or how else to test for them.
        get-eventlog -computername SERVERNAME -logname "Application" -after "03/14/2013" | ?{$_.eventid -eq "5604"} | select MachineName,EventID,EntryType,Message | ft -autosize
    One MS Forum post online says it is a bug in RU4, unclear if it may also be a bug in RU2 (our installed version).
        http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/9dcb3011-9327-4935-9479-62b38a6ddd87
        "I was looking for the same error and found this.. it basically says that this is a bug in RU4 and RU4-v2...and it needs to be removed."
    tests using troubleshooting scripts find no issues with search indexer,
        [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\Troubleshoot-CI.ps1
        Get-EventLog : No matches found
        At C:\Program Files\Microsoft\Exchange Server\V14\scripts\CITSLibrary.ps1:622 char:40
        + $msftesqlCrashes = get-eventlog <<<< -computername $Server -after $StartTime -logname "Application" -source $msftesqlServiceName | where {$_.eventId
        -eq $msftesqlCrashEventId}
            + CategoryInfo : ObjectNotFound: (:) [Get-EventLog], ArgumentException
            + FullyQualifiedErrorId : GetEventLogNoEntriesFound,Microsoft.PowerShell.Commands.GetEventLogCommand
        Name IsDeadLocked CatalogStatusArray
        SERVERNAME False {DATABASENAME\SERVERNAME, DATABASENAME\S...
        [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>
    and tests against searches on each DB themselves show no issues and respond typically within 3 seconds.
        [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Test-ExchangeSearch | ft Server, Database, ServerGuid, ResultFound, SearchTimeInSeconds, Error -AutoSize
        Server Database ServerGuid ResultFound SearchTimeInSeconds Error
        SERVERNAME DATABASENAME b16e3461-257c-40dd-a9ad-99a5f41a927e True 2.937
    I also tried to check the Performance Viewer for the MSExchange Search Indexer and MXExchange Search Indices but am unsure which of the many metrics would indicate this issue.
    We have had no reports of search issues from our users and have been unable to duplicate any impairment in our testing.
    Does anyone else have any suggestions for tests to check or steps to take on this alert? Is it simply a false alarm or a timeout of other sorts during testing? We have 80 DAGs on this server (as well as all our servers, some of which have also reported the
    same alert) and the Test-ExchangeSearch command times out before completely testing all DAGs.

    Hi IAMChrisL,
    Any updates?
    Frank Wang
    TechNet Community Support

  • I didnot start my admin server here i am attaching the thread

    awt.toolkit = sun.awt.windows.WToolkit
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = C:\WEBLOG~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WEBLOG~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\WEBLOG~1\JDK160~1\lib\tools.jar;C:\WEBLOG~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\WEBLOG~1\WLSERV~1.3\server\lib\weblogic.jar;C:\WEBLOG~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\WEBLOG~1\WLSERV~1.3\server\lib\webservices.jar;C:\WEBLOG~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\WEBLOG~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\WEBLOG~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\WEBLOG~1\WLSERV~1.3\server\lib\xqrl.jar
    java.class.version = 50.0
    java.endorsed.dirs = C:\WEBLOG~1\JDK160~1\jre\lib\endorsed
    java.ext.dirs = C:\WEBLOG~1\JDK160~1\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
    java.home = C:\WEBLOG~1\JDK160~1\jre
    java.io.tmpdir = C:\Users\veeru\AppData\Local\Temp\
    java.library.path = C:\WEBLOG~1\JDK160~1\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\WEBLOG~1\patch_wls1033\profiles\default\native;C:\WEBLOG~1\patch_ocp353\profiles\default\native;C:\WEBLOG~1\WLSERV~1.3\server\native\win\32;C:\WEBLOG~1\WLSERV~1.3\server\bin;C:\WEBLOG~1\modules\ORGAPA~1.1\bin;C:\WEBLOG~1\JDK160~1\jre\bin;C:\WEBLOG~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\WEBLOG~1\WLSERV~1.3\server\native\win\32\oci920_8
    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
    java.protocol.handler.pkgs = weblogic.net
    java.runtime.name = Java(TM) SE Runtime Environment
    java.runtime.version = 1.6.0_18-b07
    java.security.policy = C:\WEBLOG~1\WLSERV~1.3\server\lib\weblogic.policy
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.6
    java.vendor = Sun Microsystems Inc.
    java.vendor.url = http://java.sun.com/
    java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
    java.version = 1.6.0_18
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 16.0-b13
    javax.management.builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
    javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
    javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
    javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
    javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
    org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
    org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
    org.xml.sax.driver = weblogic.xml.jaxp.RegistryXMLReader
    org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
    os.arch = x86
    os.name = Windows 7
    os.version = 6.1
    path.separator = ;
    platform.home = C:\WEBLOG~1\WLSERV~1.3
    sun.arch.data.model = 32
    sun.boot.class.path = C:\WEBLOG~1\JDK160~1\jre\lib\resources.jar;C:\WEBLOG~1\JDK160~1\jre\lib\rt.jar;C:\WEBLOG~1\JDK160~1\jre\lib\sunrsasign.jar;C:\WEBLOG~1\JDK160~1\jre\lib\jsse.jar;C:\WEBLOG~1\JDK160~1\jre\lib\jce.jar;C:\WEBLOG~1\JDK160~1\jre\lib\charsets.jar;C:\WEBLOG~1\JDK160~1\jre\classes
    sun.boot.library.path = C:\WEBLOG~1\JDK160~1\jre\bin
    sun.cpu.endian = little
    sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
    sun.desktop = windows
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = Cp1252
    sun.management.compiler = HotSpot Client Compiler
    user.country = US
    user.dir = C:\weblogic3\user_projects\domains\weblogic_domain
    user.home = C:\Users\veeru
    user.language = en
    user.name = veeru
    user.timezone = America/New_York
    vde.home = C:\weblogic3\user_projects\domains\weblogic_domain\servers\AdminServer\data\ldap
    weblogic.Name = AdminServer
    weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
    weblogic.ext.dirs = C:\WEBLOG~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\WEBLOG~1\patch_ocp353\profiles\default\sysext_manifest_classpath
    weblogic.home = C:\WEBLOG~1\WLSERV~1.3\server
    weblogic.management.discover = true
    wls.home = C:\WEBLOG~1\WLSERV~1.3\server
    >
    ####<Dec 28, 2011 11:14:29 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088869072> <BEA-000365> <Server state changed to STANDBY>
    ####<Dec 28, 2011 11:14:29 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088869075> <BEA-000365> <Server state changed to STARTING>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <SAFService> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869149> <BEA-281003> <SAF Service has been initialized.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <SAFService> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869187> <BEA-281002> <SAF Service has been started.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <WseeCore> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869196> <BEA-220502> <The Wsee Service is starting>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Deployer> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869270> <BEA-149209> <Resuming.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Diagnostics> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869381> <BEA-320000> <The Diagnostics subsystem is initializing on Server AdminServer.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Store> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869392> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=C:\weblogic3\user_projects\domains\weblogic_domain\servers\AdminServer\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Store> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869429> <BEA-280103> <The persistent file store "WLS_DIAGNOSTICS" will cache in weblogic.store.io.file.direct.FileMapping[granularity=65536 io=mapped].>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Store> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869487> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (af2ca042-301f-4b86-82a6-2f006add155a) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=21.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Log Management> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869512> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\weblogic3\user_projects\domains\weblogic_domain\servers\AdminServer\logs/weblogic_domain.log.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Notice> <Log Management> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869549> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Diagnostics> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869707> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Dec 28, 2011 11:14:29 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088869814> <BEA-000365> <Server state changed to ADMIN>
    ####<Dec 28, 2011 11:14:29 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088869935> <BEA-000365> <Server state changed to RESUMING>
    ####<Dec 28, 2011 11:14:29 AM EST> <Info> <Management> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088869952> <BEA-141052> <The auto deployment poller has started.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Emergency> <Security> <veeru-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088870023> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Error> <Server> <veeru-PC> <AdminServer> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1325088870023> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 192.168.1.3 might be incorrect or another process is using port 7012: java.net.BindException: Cannot assign requested address: JVM_Bind.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Critical> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870025> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870028> <BEA-000365> <Server state changed to FAILED>
    ####<Dec 28, 2011 11:14:30 AM EST> <Error> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870030> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Dec 28, 2011 11:14:30 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870032> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <Diagnostics> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870037> <BEA-320002> <The Diagnostics subsystem is stopping on Server AdminServer.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <WseeCore> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870038> <BEA-220504> <The Wsee Service is halting>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <SAFService> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870039> <BEA-281004> <SAF Service has been suspended.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <SAFService> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870039> <BEA-281005> <SAF Service has been shut down.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMX> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870137> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://192.168.1.3:7012/jndi/weblogic.management.mbeanservers.domainruntime .>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMX> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://192.168.1.3:7012/jndi/weblogic.management.mbeanservers.edit .>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMX> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870139> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://192.168.1.3:7012/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870140> <BEA-220028> <Web Service reliable agents are suspended.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870142> <BEA-220029> <Web Service reliable agents are shut down.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <MessagingBridge> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870157> <BEA-200001> <The messaging bridge service has successfully shut down.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMS> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870237> <BEA-040308> <JMS service is suspending.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMS> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870285> <BEA-040107> <Undeployed 8 default connection factories.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JMS> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870285> <BEA-040015> <JMS shutdown is complete.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JDBC> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870286> <BEA-001144> <Force Suspending the JDBC service.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JDBC> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870287> <BEA-001146> <Force suspend of the JDBC service completed.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JDBC> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870287> <BEA-001147> <Shutting down the JDBC service.>
    ####<Dec 28, 2011 11:14:30 AM EST> <Info> <JDBC> <veeru-PC> <AdminServer> <main> <<WLS Kernel>> <> <> <1325088870288> <BEA-001149> <Shutdown of the JDBC service completed.>
    ####<Dec 28, 2011 11:14:35 AM EST> <Info> <J2EE> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088875165> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Dec 28, 2011 11:14:35 AM EST> <Info> <EJB> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088875711> <BEA-010008> <EJB Deploying file: mejb.jar>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877092> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877341> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877354> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877368> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877387> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <WebService> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1325088877400> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2011 11:14:37 AM EST> <Info> <EJB> <veeru-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325088877521> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
    ####<Dec 28, 2011 11:15:00 AM EST> <Notice> <WebLogicServer> <veeru-PC> <AdminServer> <Thread-12> <<WLS Kernel>> <> <> <1325088900035> <BEA-000378> <Server failed to shutdown within the configured timeout of 30 seconds. The server process will exit now.>
    ####<Dec 28, 2011 11:15:00 AM EST> <Error> <> <veeru-PC> <AdminServer> <Thread-12> <<WLS Kernel>> <> <> <1325088900055> <BEA-000000> <THREAD DUMP from JVM taken at 'Wed Dec 28 11:15:00 2011'
    >

    "Unable to create a server socket for listening on channel "Default". The address 192.168.1.3 might be incorrect or another process is using port 7012: java.net.BindException: Cannot assign requested address: JVM_Bind."
    are you sure that 192.168.1.3 is actually the IP address of one network interface on your machine? Use ifconfig to find out.
    Are you sure no process is already using 7012 port?
    Use lsof to find out. And netstat -a

  • How can I kill all Threads of the same class from within the run() method?

    Ok
    I have a class called Consumer that extends Thread
    I have several Consumer threans running... but, when a certain condition is true (within the run() method) in ANY of the threads, I want to kill ALL the threads of that object.
    is this possible?

    I know this is gonna be too demanding, but can someone please tell me why my Consumer's run() method never reaches the System.out.println( "ALL CONSUMING DONE") line
    Create a multi-threaded prime number calculator that is based on the producer-consumer model
    using semaphores. Your program should be able to check for prime numbers in a range specified
    by the user and with a variable number of threads. Example:
    $ java PrimeFind 3 5000 10000
    should use 1 producer and 2 consumers (3 threads in total, obviously the minimum is 2) to find all
    the prime numbers in the range [5000,10000].
    The producer should: use a buffer to store candidate numbers that have to be checked for
    primality.
    Consumers should: read from the buffer, check if a number is prime and update the status of the
    program accordingly (e.g. show the number on the screen, or save it to a file)
    import java.util.concurrent.Semaphore;
    import java.io.*;
    public class Assign1 {
    static int fromThisNumber;
    static int toThisNumber;
    static int numberOfThreads;
    static int buffer[];
    static Semaphore ready;          /*This semaphore is used by the Producer to signal
                                         an "OK" to the consumers*/
    static Semaphore critical;  /*This is a Mutex semaphore. It allows only 1 consumer
                                         to enter his critical section.
    static Semaphore counter;     /*This semaphore acts as a counter.
                                        Instead of having a global variable
                                         incremented each time, we just release()
                                         this semephore when we find a prime number
                                         Because remember that release() increments permits
    static Producer prod;
    static Consumer cons[];
    static int in=0;
    static int out=0;
    static PrintWriter outFile;
         public static void main (String args[]){
              try{
                   outFile=new PrintWriter(new FileWriter("primes.txt"));
                   }catch(Exception e){}
              numberOfThreads=Integer.parseInt(args[0]);
              fromThisNumber=Integer.parseInt(args[1]);
              toThisNumber=Integer.parseInt(args[2]);
              buffer=new int[Integer.parseInt(args[2])-Integer.parseInt(args[1])+1];
              ready=new Semaphore(0,false); /*We initialise it to 0 because we wait
                                                      for the Producer to produce atleast a
                                                      item. Suppose ready was 1 and if
                                                      Consumer ran first he would be in an
                                                      empty buffer */
              critical=new Semaphore (1,false);/*We initialise it to 1 because when
                                                         the first Consumer thread tries
                                                         to enter its critical section, it
                                                         should be allowed to;
                                                         Subsequent threads will have to
                                                         wait since only 1 thread can
                                                         access its critical section at a time*/
              counter=new Semaphore(0,false); // duh!
              cons=new Consumer[numberOfThreads-1]; /*numberOfThreads-1 because 1 thread
                                                                is taken by the Producer*/
              //Creating Producer object
              prod=new Producer();
              //Creating the Consumer object and start the thread.
              for(int i=0;i<cons.length;i++)
                        cons=new Consumer();
                        cons[i].start();
              prod.start();          
              //Printing to screen and file
    /*          for(int i=0;i<buffer.length;i++)
                   if(buffer[i]!=0)
                             System.out.println(buffer[i]);
                             outFile.println(buffer[i]);
              System.out.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits()+"\n primes.txt written");
              outFile.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits());
              outFile.close();*/                    
    static class Producer extends Thread {
         public void run(){try{
              while(in<buffer.length)     /*'in' should always be more than 'out'.Oherwise the consumer will try to access an empty index*/
                   {     System.out.println("producing");     
                        buffer[in]=fromThisNumber;
                        in++;
                        fromThisNumber++;
                        ready.release();
              catch (Exception e){e.printStackTrace();}
              System.out.println("ALL PRODUCING DONE");
    static class Consumer extends Thread {
         int tempout=0;
         public void run(){try{
              System.out.println("before while"+this.getId());
              while(tempout<=in)
                   System.out.println("before ready"+this.getId()+" "+ready.availablePermits()+" "+in);
                   ready.acquire();
                   System.out.println("before critical.acquire"+this.getId());
                   critical.acquire();
                   tempout=out;
                   out++;
                   critical.release();               
                   if(!isPrime(buffer[tempout]))
                        {System.out.println(buffer[tempout]+" by "+this.getId());buffer[tempout]=0;}
                   else {counter.release();System.out.println("prime added: "+buffer[tempout]+" by "+this.getId());}
                   critical.acquire();
                   tempout=out;
                   System.out.println("tempout:"+tempout+" of "+this.getId());
                   critical.release();
              System.out.println("ALL CONSUMING DONE"+this.getId());
         catch(Exception e){e.printStackTrace();}
         //Prime number-checking method     
         public boolean isPrime(int n){
              for(int i=2;i<=(n/2);i++)
                   if(n%i==0)
                        return false;
              return true;
    ======================
    import java.util.concurrent.Semaphore;
    import java.io.*;
    /* 3 questions to ask Barlas
    * Why error if I start the Consumer threads before Producer
    * Why does the counter semaphore always give a +1 result at the end
    * Is there a way I can verify that all the work is not being done by only 1 consumer thread? In other words, the workload is being shared properly
    * if I put ready.acquire() outside or inside the while loop, its not making any difference, why?
    * Strangely, its not making any difference if I playing with the release() and aquire() of the semaphores, WHY?!?!
    public class Assign1 {
    static int fromThisNumber;
    static int toThisNumber;
    static int numberOfThreads;
    static int buffer[];
    static Semaphore ready;          /*This semaphore is used by the Producer to signal
                                       an "OK" to the consumers*/
    static Semaphore critical; /*This is a Mutex semaphore. It allows only 1 consumer
                                       to enter his critical section.
    static Semaphore counter;     /*This semaphore acts as a counter.
                                  Instead of having a global variable
                                       incremented each time, we just release()
                                       this semephore when we find a prime number
                                       Because remember that release() increments permits
    static Producer prod;
    static Consumer cons[];
    static int in=0;
    static int out=0;
    static PrintWriter outFile;
         public static void main (String args[]){
              try{
                   outFile=new PrintWriter(new FileWriter("primes.txt"));
                   }catch(Exception e){}
              numberOfThreads=Integer.parseInt(args[0]);
              fromThisNumber=Integer.parseInt(args[1]);
              toThisNumber=Integer.parseInt(args[2]);
              buffer=new int[Integer.parseInt(args[2])-Integer.parseInt(args[1])+1];
              ready=new Semaphore(0,false); /*We initialise it to 0 because we wait
                                                      for the Producer to produce atleast a
                                                      item. Suppose ready was 1 and if
                                                      Consumer ran first he would be in an
                                                      empty buffer */
              critical=new Semaphore (1,false);/*We initialise it to 1 because when
                                                      the first Consumer thread tries
                                                      to enter its critical section, it
                                                      should be allowed to;
                                                      Subsequent threads will have to
                                                      wait since only 1 thread can
                                                      access its critical section at a time*/
              counter=new Semaphore(0,false); // duh!
              cons=new Consumer[numberOfThreads-1]; /*numberOfThreads-1 because 1 thread
                                                                is taken by the Producer*/
              //Creating Producer object
              prod=new Producer();
              //Creating the Consumer object and start the thread.
              for(int i=0;i<cons.length;i++)
                        cons[i]=new Consumer();
                        cons[i].start();
              prod.start();          
              //Printing to screen and file
    /*          for(int i=0;i<buffer.length;i++)
                   if(buffer[i]!=0)
                             System.out.println(buffer[i]);
                             outFile.println(buffer[i]);
              System.out.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits()+"\n primes.txt written");
              outFile.println("Total primes found between "+args[1]+" and "+toThisNumber+": "+counter.availablePermits());
              outFile.close();*/                    
    static class Producer extends Thread {
         public void run(){try{
              while(in<buffer.length)     /*'in' should always be more than 'out'.Oherwise the consumer will try to access an empty index*/
                   {     System.out.println("producing");     
                        buffer[in]=fromThisNumber;
                        in++;
                        fromThisNumber++;
                        ready.release();
              catch (Exception e){e.printStackTrace();}
              System.out.println("ALL PRODUCING DONE");
    static class Consumer extends Thread {
         int tempout=0;
         public void run(){try{
              System.out.println("before while"+this.getId());
              while(tempout<=in)
                   System.out.println("before ready"+this.getId()+" "+ready.availablePermits()+" "+in);
                   ready.acquire();
                   System.out.println("before critical.acquire"+this.getId());
                   critical.acquire();
                   tempout=out;
                   out++;
                   critical.release();               
                   if(!isPrime(buffer[tempout]))
                        {System.out.println(buffer[tempout]+" by "+this.getId());buffer[tempout]=0;}
                   else {counter.release();System.out.println("prime added: "+buffer[tempout]+" by "+this.getId());}
                   critical.acquire();
                   tempout=out;
                   System.out.println("tempout:"+tempout+" of "+this.getId());
                   critical.release();
              System.out.println("ALL CONSUMING DONE"+this.getId());
         catch(Exception e){e.printStackTrace();}
         //Prime number-checking method     
         public boolean isPrime(int n){
              for(int i=2;i<=(n/2);i++)
                   if(n%i==0)
                        return false;
              return true;
    ===========================
    BTW, when I tried to change extends Thread to implements Runnable I got some kinda of error.
    Actually, my program is pretty complete... its just that something if messed up in my Consumer's run() method's while loop... I think
    I know guys its crazy to ask ya'll to look at so much code, but.... I'd really appreciate it. This assignment is killing me, been at it since 10 hours now....

  • Rather than persists in the future thread...

    The point I was making would be for Archs documents to pick up where man pages leave off, but whatever.
    If you think I stated Arch must fix man pages, not so. I was intending to show that docs as a whole, leave whole subjects unhandled, Arch could provide the answers in its own docs and come out as a hero.
    Or maybe not.
    And remember, users who cannot configure ppp cannot get on the internet to get the ppp configuration docs. Or any other docs, for that matter. One failed configuration needing web documents might leave the newbie stranded.
    Or maybe not.
    I personally think that a lot of configuration has to be made before Linux (Arch or others) will communicate over the internet to a remote website, so as to allow documentation to be visible..... but hey, maybe I missed something? Like the document to get a modem setup? So I could get web based documents? Chicken and egg?
    Maybe not, eh?
    As for the concept of needing to be an experienced admin - these folks usually do not need any docs. That compares to bad docs to a newbie - essentially no docs. Missing docs and no internet access are also useless. Thus, the newbie without documents needs the only thing which gets anyone else through the issue - the newbie needs experience, because the docs are weak or missing or erroneous. Try as you might, that is an issue I went through. Take, for example, when I needed network assistance. Archs forums were not the first place I went asking for help, believe me; I asked and am still asking. 2 years now, and I'm just getting told Samba. Need I say this is baloney? That issue is not Archs fault, but Arch could have a smashing success on its hands if it were to document a few critical areas as well as 0.2 was documented.
    Installing and partitioning... What can I say... apeiro is not mentioning anything I've PM'd him about: secondary hard disks getting reformatted. My pm brought me the answer that most Archers never repartition, so the script was.... well, I guess you could say it was a shot in the dark. Fine, but the PM stated the alternative was something like 'I usually use the commandline stuff and simply reformat the existing partitions'.
    Why the **** would an inexperienced newbie set up partitions outside of using the installer?? The Arch docs tells the newbie to use the installer to partition their hard disks! What, exactly, is the newbies idea of an installers purpose? Are you a newbie when you decide what a newbie has for skills? The installer obliterated gigabytes of data, I trusted that it was going to perform safely, and yet nobody ever used it to learn of the glitch? Ooookkaaaaayyyy.
    Folks, the docs said to use the installer. Never mentioned possibly partitioning from the command line. Take your pick, the newbie was not at fault for following the docs.
    I'll run along, because I cannot possibly be speaking truth. Neither am I telling you where I had problems. This is cannot be feedback, it must be dunbars rantings. Does Arch have a future when feedback is considered trolling or flaming the developers? Lighten up, folks, I had once been trying to offer help and sought to get help.
    I know this is a labor of love for you all; in many ways, Linux is a labor of mine as well. Sadly, you are not hearing some issue that could help make Arch the distro that some folks want it to be.

    dunbar wrote:Step by step: I mentioned a few weak areas that newbies would not know how to address.
    I mentioned that newbie would not necessarily have the skills to get the correct docs from a myriad of websites.
    Which appear (and frequently are) obsolete.
    Well, then we include the docs and then non-newbies would complain that we are cluttering the filesytem and you would complain because those documents are obsolete. sound familiar? i have seen this argument before and there is not winning it. people bitch about the manpages, docs, etc ALL THE TIME. you must know that. so the best we can do is add your concerns to our own documents and add necessary documents to the files.
    When their internet connection was what had failed, the internet doc is not available.
    And when they had no Xwindows in which to read HTML documents,
    and nothing tells the newbie about CLI browsers.
    i would expect that no absolute green newbies would try arch so those newbies that do show up i would assume have some linux experience (one can be a newbie and have some experience) so i would assume that they would know about lynx or links browsers or at least know how to use cat and less.
    another point about this is that if a newbie does not even know how to use cat, less, or a cli editor to view files then they would be very very f**ked with arch linux and having self contained documents would be pretty pointless. so again i would ask is it not wise to print out/write down any relevent install/configuration instructions? you do know how to write since you already say you don't have a printer?
    okay so if we include install configuration data in the installer will you know how to access it? is it fair to tell the user that it is in such and such directory and you can access it through say vc1-4? should we scrap our online docs altogether and just have them self contained?
    The network thing was changed along the way - IPX/SPX was part of the issue, my 5 port switch is another part. I am not berating you, sarah31, nor am I asking anyone to re-write man pages, etc. as several posts seemed to attribute to me. The man pages are the weak spot, Arch docs need to go from there. Never wanted to say more than that.
    and all i wanted to know is what apps do we extend our documentation to? all of them? are you saying that all our apps need extended docs? can you point me to one distro that has extended documents of all their applications? besides ppp what would YOU extend? it is fair to ask this of arch developers/users but they really need to know just what manpages are defunct and have no bearing on arch.
    i would not expect a request like this would get fulfilled too quickly there are lots of applications' man pages and docs to go through then the developers would have to determine what is needed and what is not.
    as for manpages......i used to find them unreliable but to be honest most manpages i have viewed lately have been very clear and concise about how to operate/configure apps. i am not saying this to contradict you but i say it honestly. when i have been unable to find someone to ask on this forum or irc manpages normally do the trick for me. (and don't say it is because i am some expert with linux because i a definitely not)
    I'm trying to point out that A] with a presumed goal of gaining Linux users,
    B] Arch, being small, uncluttered and likely attractive to newbies (small draws newbies because it is so small (dialup accessible but only one big download at a time) and older systems where XP won't fit on their disks, etc) and also
    C] since Arch had very tight documents covering what needed to be done (but might need more topics covered), I felt that was likely going to lead to newbies arriving here in some situations that
    D] Arch clearly tries to assume will not need the attentions of forum members (which have the skills) and
    E] the newbie does not have the skills.
    That would lead to the assumption that Arch was not interested in the users needs.
    with respect to this.....well what can i say but you are a complete ***hole. for one thing small does not always attract newbies in fact i know ALOT ALOT ALOT of people that will not even try arch or similar distros because they are small. most people want the choice to kludge up their system if they like but arch is not in this realm yet because we do not offer alot of packages.
    i agree we need more stuff covered in our documents and you would not find a single user or developer that would disagree with you. So i guess this point you make throws out your idea of extending the manpages because that is not a concise project (for example manpages for transcode are good but to get into all the basics a newbie would need to know would require one to be alot more verbose similarily with networking documents)?
    to say that we here do not pay attention to users is ABSOLUTELY THE WRONG ANSWER. there are only two pages of unanswered post and considering there are always post that are merely statements that do not need to be answered that is very good. in fact if you even bothered to check there are only 79 unanswered posts out of 4512. that's 1.75% of the posts on the forum are unanswered. besides that there are always questions that no one has an answer to. obscure problems do exist i know i have hit many in my ventures in any OS.
    besides this forums are a free service. no one is under obligation to use it user AND developers alike. no one is paid here so don't diss anyone and don't feel that anyone is obligated to answer you.
    i can also say that you are a complete arrogant ass for saying arch does not care about its users. we don't care about you that is for certain. but i can guarantee that everything i did every package i made, upgraded, donated, fixed, etc was for the user. people wanted openoffice i spent a week building it then it got broken with the upgrade to gcc 3.3 i spent another week trying to fix it without luck then judd spent 3 days compiling and patching 1.1. so do you EVER say we don't fucking care you little ingrate.
    The perceived 'lack of clarity' on my part is because I am still a newbie. I might have a few things working under Slackware, but I'm not certain, today, where I even made the changes. I'm not asking for hints on how to keep a notebook, I have one, it is 40 miles away, I cannot discuss Linux by reading my notes or grepping my config files, they are 40 miles away. I cannot log into my Linux PC, I only have dial up, the only telephone line in my house is for voice communications. DSL is too far away, Cable is too expensive.... have I never said any of this before? No, not in this thread, but I've always been a hardliner on those points sarah31. I do not match up with what is assumed of me. But here I am, posting, despite my ineptitude.
    "Waaagh i'm a newbie. waggh i don't have highspeed pity me pity meee!"
    there are lots of users on dialup here including developers so we don't give a flying f**k.
    I believe the deepest undercurrent I see here is diverging viewpoints of what Arch is and diverging goals for Arch. My views are different from a few who assume the Archer has the skills, hApy seems to have a third viewpoint, and yet a third viewpoint exists.
    yeah and you are saying we have to conform to your view. typical. funny we seem to be getting more and more users all the time both newbie and non newbie and this despite having a completely uncaring development team and a horrendous set of docs. one of the funny things is that many of the newbies recently are all dialup like you and they still take time to make irc interesting or contribute packages.
    If my posts reflect an atmosphere of bewildering viewpoiints, I'm not surprised - I've tried to reply to differing posts which take differing opinions; I suppose it is frustrating to anyone to reply to 3 posts at once. I'm replying in order to offer my view of when I was a frustrated newbie (this morning, I think ;-) ). Remember, I was told by a certain forum member that, most certainly, dunbar was a slackware user and the assumption was that he must be nearly expert - yet, I declared, no, I'm not an expert and I freely admit a lack of skills. I was not the one who estimated dunbars skills, Sarah31.
    oh you are soooo subtle in your insults. come on you tell me after hundreds of installs and two years of using linux you don't know anything? find me five green newbies that know how to grep or know to look online for information. personally i and many others here and elsewhere have little time for someone who cries about being a newbie when they obviously aren't.
    what is it some sort of ploy to make people feel sorry for you or shorten your look online for info that you likely could find in two minutes? spare me. up to one year you are a n00b after that you are not.
    I'm definitely not interested in dissing anyone, not you, nor Gyroplast, nor Apeiro, nor hApy .....
    hmmm you care to stand by that or should i pull out several quotes to the contrary?
    I have pointed out that early on, Arch was interested in being Judds perfect distro... did anyone ask him if he ever said that? As I said, I can offer to cut and paste, if you wish.
    so your point is? is this a bad thing? is it not possible for many of us to believe it is the perfect distro for us as well? why not diss yoper for claiming to be THE distro.
    Yet, I'm clearly getting 2 viewpoints in response to me repeating that fact. Thus, in order to push the reader away from their position, so as to get them to walk in my shoes, I post from different directions aiming toward one central condition. Is the issue me, and me alone? Or did the issue exist, and I'm guilty of responding to all viewpoints and thus I'm guilty of pointing it out?
    i have been in your shoes and i often get put back in your shoes when i start to use or investigate applications or areas of linux i have never explored before. so whats your point? if it was to fix up the documentation? that was a goal for some time now in fact a few users have made it an ongoing thing.
    you are not the only one that is a newbie here nor are you the only one here. there are many things that developers must balance when they do their duties. there will never be a distro that will satisfy all a user's needs but i can tell you that the arch team does try to please as many people as possible. so yeah i think you are the issue to some extent. you could have come in here and politely explained what it is that you felt needed improvement but instead you came in and whine and cried that you were so abused and that we had to change to please you. it was all about you anyone can easily extract that from the way you keep flipping between i'm a newbie, i'm not a newbie but i speak for newbies. if you cannot find the offesive comments you have made along the way or see how some people came to the conclusions they did then it is your fault.
    Anyway, you mentioned the ethernet thread.... thydian is evidently new here. Lets explain that issue out loud (since you already raised the matter). I offered to write a document regarding Ethernet setup, I was not shown what to do (frozdsolid posted that they were "pretty sure that's necessary"). I do not assume that every member here reads every posted message; thus, I believe I had read the opinion of someone who was as newbie to Arch as I myself was a newbie (frozdsolids title still shows only 4 posts even today). Nobody here 'handed me an answer' as some might conclude from your post.
    well YOU may not have gotten answer but people DID try to answer your question and, in fact, the answer is there. but you could not extract it or did not know how to ask the question properly to get the result you desired.
    but of course we are the bad guys here because we took the time to try and give you an answer. man you are such a wanker....
    I posted everywhere else on the internet about my situation using IPX/SPX, I heard that it was a dead protocol. I finally found information about IPX/SPX, it was not herein, so the forum was of no use in that instance - that is a fact, sarah31. Now that I have concluded that IPX/SPX was not the best choice and changed the rest of the household over to TCP/IP...... the IPX/SPX issue is no longer the focus, so I dropped the subject; until I was  6 months later, I came back here, saw BluPhoenixs post and was a bit confused. That lead to him suggesting DOSemu, I stated no, that was not preferred, etc. etc. I ultimately thanked BluPhoenix, stated why I was going to drop the issue, and I left the thread cold.
    so why insist on blaming us for something that we tried to answer but was obviously beyond our knowledge? you did it at the end of that thread and you constantly do it here. how many other people did you verbally assault along the way?
    The whole thing got misdirected, away from what I was asking for, as if the topic was no longer my decision alone.
    what a pile of BS. it was YOUR thread so get in there and assert yourself. threads get out of hand sometimes but the original poster can easily get control again if they have a pair.
    i know for a fact that the people he chose to insult would and have tried to help him but he blows them off. i know too that the head developer is VERY open to user contributions yet dunbar chose not to contribute.
    The reasons should be evident by now - when I offered to contribute, I had the time; 6 months of time transpired, I was not able to write because I had no answers with which to generate such a document. I had to revoke the offer. I am taken by surprise that anyone would say I was given the necessary information!
    BS again you just stated that you got your answer (outside of our forum) so you could have easily posted back with what you had found out and then provided documentation later. and you mean to tell me that you have not had time in the last six months to wing something together. shit you have practically written a novel here.
    it is obvious to me that you just want to guard that knowledge and us it to flame and troll here. once you had the answers you were sure to come back and flame that thread and continue flaming on a regular basis. what an ass.
    I've known you to be patient, sarah31 (and you are yet teaching me as I write), but when you say I'm taking great pains to insult someone - while I'm waiting months for forum responses and I'm reading internet documents that are obsolete and these are docs which talk about a different distro, refer to a different kernel, puts files in a different location????
    yeah so you waited for an answer and didn't get one...it happens. you stated that barely anyone knew the answer. fianlly you got one and then came back and rudely blamed us for poor documentation and a barrel of other things. nice guy.
    all i saw was orelein answer you in a nice and proper fashion and you called him eliteist. you also were rather rude about judd in your first post in the future thread. so yes i see all throughout attempts to belittle and brate and not one instance of sober commentary from you.
    and here you are again balming us for online docs that are not ours.
    That is not appropriate, ever, to assume that the newbie will not find older docs and will know enought to discard the incorrect ones.
    this is not limited to newbies.....it can definitely be difficult finding what you need online.
    And since most internet docs are coasting along since, for example, 1999 (re: the IPX/SPX how-to)
    well if you are checking out and obscure problem that is actually now obsolete then sure the fucking doc will be old but you make is sound like ALL docs are old. so i have to assume that you are very much an idiot because i have found most documentation for most current issues to have current docs. most applications will upgrade their docs as they upgrade or do you even notice that? are you to self absorbed to go around and find out if your wild accusations actually have any merit?
    once again, and I'll ask this, and directly of you, sarah31, why would any newbie assume that 4 year old document applied to their situation??
    well knowing how many newbies are i would expect them to ask if docs are relevant. or they could possibly look into some of the information. if it was not producing answers...wow i think they would ask for help again. shit do you even pay attention to how newbies act on justlinux?
    :oops: I'd ask that people remove useless web documents, but I fear that I'd get only 4 responses. That is reality, not sarcasm.
    hmmm remove docs, add docs which is it? fyi arch removes most docs except in rare circumstances. if those docs are html they are html. if a n00b doesn't know how to view them i expect they would ask( that is if they are outside x).
    dunbar...stick with slack because arch will never please you. slack is a very nice distro that should have the balance arch does not afford you. that is the great thing about a linux .... if you don't like one flavour then try another. just don't go back to the ice cream dealer and berate him for selling you your choice...get the point (if you don't then fine i expected that)

  • How to get a gmail style thread / conversation view

    Does anyone know of a plugin or hack to allow viewing of threads or conversations in Apple Mail the same way the gmail does? Mail's "Organize by Thread" only goes halfway and lacks three critical aspects of gmail's "conversation" method:
    1 suppression of quoted text
    2 collapsable display of the thread messages in the same window, where read messages are collapsed and unread messages are expanded
    3 inclusion os sent messages in the thread view. For some reason, Apple Mail tucks these away in a separate mailbox, and you don't what you wrote unless it's quoted back to you.

    Two main reasons: I want my mail to be searchable on my laptop (I use a tagging system), and I need to be able to process my mail offline. Otherwise I would use the web interface, and sometimes I still do.
    Minor reasons include not wanting to see the ads all the time and the fact that gmail bogs down my browser sometimes.

Maybe you are looking for