L2461X in a multi-moni​tor environmen​t

Hello,
it's tricky to integrate the Lenovo L2461X into a multi-monitor environment. It looks like only if the L2461X is the main monitor you can use it as a touchscreen - if you choose an other monitor as main, the touch input from the  L2461X effects only the main monitor.
Any tipps from the community?

> Hi, everyone. I think it is very interesting that displaying more than two VI
> panels in each different monitors in Windows 98. As you know Windows 98
> supports up to 9 monitors. Then how can we control the position of VI panels?
> Which monitor and Where can we position them? If you know the tips, please
> let me know. I'll be very appreciated. Thanks and good luck to everyone!
>
Use the server. VIs have a property to set their panel window position.
The Application server class has a setting to read the array of monitor
information. You can also just arrange the panels interactively and
save them.
Greg McKaskle

Similar Messages

  • Hp pavilion all-in-one wanting to multi-moni​tor

    I have a HP Pavilion All-in-one and am wanting to multi(dual monitor), for webcasting purposes of a co-host show(co-host's in diff locations) was told i would need to dual monitor and "highjack" skype. i would like to have live video of co-host as well as audio. any suggestions..?? ty
    Solved!
    Go to Solution.

    Wouldn't it be easier to use something like this and cheaper http://www.bestbuy.com/site/Tritton+Technologies+-​+SEE2+External+VGA+Video+Adapter/9325241.p?id=1218​...
    Crystal
    Superuser
    Forum Guidelines | Terms & Conditions | Community Guidelines | What is a Superuser?
    *Remember to mark your questions solved and click the star to give kudos to show your thanks!*
    While I used to be a Best Buy Employee, I no longer have any affiliation with Best Buy.
    My opinions do not in any way shape or form represent Best Buy's Official decisions.

  • Two different monitors as multi-moni​tors

    Is it possible to run a two-monitor display using two completely different monitors? I'm replacing an ancient desktop with a Pavillion 500-c60 (Win 8.1), and also bought a W2371d monitor for the new machine. The old PC used a perfectly good, but ancient, Samsung 17-inch monitor.
    What would happen if I tried to include my old monitor in my new setup? If I were able to use dual monitors, I would of course make the new HP the primary one. Still, it would be valuable to me if I could have the additional display acreage from the old monitor. However, the displays are not only from different manufacturers -- they are from different vintages, different sizes, different standard resolutions. Is it even possible to do this?
    This question was solved.
    View Solution.

    Hi,
    Yes, you can use TWO different monitors as mentioned:
    AMD Radeon HD 8400 graphics (combined with the processor)
    Supports DX11
    DVI and VGA output ports (both ports can be used at the same time)
    Full specs:
       http://h10025.www1.hp.com/ewfrf/wc/document?cc=au&​lc=en&docname=c04058837#N247
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • X-Fi Mixer App Probs with Multi Moni

    Hello, I bought an X-Fi Fatality card, and I love it. There is only one issue with the software. I have 3 lcd screens in XP in multi-monitor configuration. Two DVI connected to a 7800GTX, and another on my other 7800GTX. When i'm not gaming, i'm not in SLI mode, and use the video cards for a tri-monitor setup. The mixer app (game, entertainment, creation) widget will not drag off the main screen. It looks like it WANTS to drag but once the app gets to the edge of the primary screen, it will not move any further and just flickers as you attempt to move it onto a secondary monitor.
    Is there any ETA on fixing this? I want to have my mixer app open on a side monitor since I do most of my work on my main monitor fully maximized.
    Also, can anyone really explain what the black module on the end of the card is with the light emblem? I heard it was a physical relay. I'd have a hard time believing it was there JUST for the light.

    Having a similar problem, except mine will go to the other screen but not completely. The left edge stays on the right side of the screen of monitor #. If you try drag it further it snaps right back. I'm using nvidia fx5200 graphics card and latest drivers.Message Edited by fresh0 on 09-30-2005 05:36 AM

  • Lion and Multi-Display (2 external monitors + built-in Display) [Thunderbolt, USB adapters/eVGA UV+]

    Hi everyone,
    I just completed an upgrade to Lion and while I love it I've suddenly found myself short 1 display. I use 2x24" with my MacBook Pro - 1 via mini Display Port [the Thunderbolt port] and another via an eVGA UV+ [both displays have a resolution of 1920x1080].
    There are two things that I am wondering about:
    Has anyone else who's upgraded found their UV+ adapter to be useless all of the sudden? I'm contacting eVGA to find out how soon we can expect a functional OSX 10.7 Lion driver for that but in the meantime...
    Has anyone heard anything of a Thunderbolt splitter "adapter" - it is obvious that you can have 2 displays chained to a MacBook Pro, as long as both of these displays are of the Thunderbolt Cinema Display variety ... seeing as I don't have two grand and already own 2 smaller monitors that I'd been using with Snow Leopard for quite some time now I was curious if there's just a way to ditch the USB adapter and just have the Thunderbolt port on my 2011 MBP drive both displays (I am fully aware that the GPU is capable of it but have yet to find a hardware display port or thunderbolt cable that splits in 2 so I can just hook each display into it and call it a day).
    Thank in advance to anyone and everyone who provides any information related to that stuff as I'd greatly appreciate your help ... once you're used to the extra screen real estate going down from 3 screens to 2 can be pretty painful.
    On that same note a general observation about Lion is that while I love full-screen apps I'll barely ever use them whenever I have external displays hooked up as Lion seems to insist on making the full screen app go to the primary display while completely blocking off the secondary display (rendering it useless). Hoping that Apple will make the UX for mulit-display folks nicer someday, I know their focus was just to release Lion now but there's absolutely room for improvement as far as that goes.
    Thanks in advance to anyone and everyone who responds to this post!

    nickdotvr wrote:
    Turns out that's not truly the case - see http://www.macrumors.com/2011/09/16/apple-thunderbolt-display-with-multiple-moni tors/ for details but the short of it is that if you just get one and plug in a Display Port Monitor you won't get that extra screen real estate after all.
    Yes... the actual marketing 'statement' says you are unable to connect the mDP display "directly" to the back of the new TB display.  Yes...
    But... from what i hear...  if you have some other TB display "directly" connected to the downstream of the TB display, you can 'then' add your older mDP display to the chain at that point.  You just can't have the older mDP directly to the new TB display.
    And this still stands true if you read previous info from Apple website.  It's all about the wording...
    So basically, you should still be able to have your MBPro + New TB display + (some other TB device w/ 2 ports) + old mDP display.

  • R400/T400/T500/W500: display driver "amdkmdap" crashes

    Executive summary: All current Lenovo ThinkPads with switchable graphics (R400, T400, T500, and W500) have usability issues in connection with Vista and the use of external monitors. For more than half a year, users were plagued by frequent Windows crashes. During that time frame, Lenovo did not comment on the various available reports and complaints. By the end of April 2009, Lenovo resolved many issues by releasing a new official driver. Though several problems, including severe ones, remain as of today. Lenovo has said to be actively working on the remaining issues (without outcomes so far).
    Important information for affected users: If you're having one of the issues reported here, then Lenovo advises you to call your local Lenovo Support. Demand that a case is submitted to hardware engineering. In particular, you should ask for "a CMVC case to be created and escalated". Using these "code words" ensures that your case is properly addressed.
    Old problem description
    On Vista 32 and Vista 64, the ATI display driver "amdkmdap" crashes when an external monitor was active before OR an application (game) using DirectX technology is used. The user typically receives a couple of so-called "Timeout Detection and Recovery" (TDR) messages from Vista:
    (Click here for an explanation of the message from Microsoft)
    Sometimes, amdkmdap crashes several times in a row. Then Windows crashes with a so-called "BSOD", likely resulting in data loss. Typically, Windows detects "atikmpag.sys" as the crashing driver. Sometimes, also an instantaneous reboot happens independent of prior TDR crashes. In such a case, no BSOD is displayed.
    The following movie illustrates the phenomenon: http://www.youtube.com/watch?v=LBX9QsCmrpY
    This behavior above has been confirmed for the following ThinkPad models: R400, T400, T500, and W500 (see below). Problem reports indicate that the symptoms are often related to playing games and/or the notebook being docked and the external monitor being connected via DVI.
    Though, the presence of these two conditions is not necessary to trigger the driver crash:
    There are reports where no dock was involved and the external monitor was connected directly to the notebook's VGA port.
    Furthermore, there are reports where the notebook was docked and an external monitor was connected to the DVI port.
    So far, there has been no report relating to a monitor being connected to the Display Port which is available on some models. (Possibly because this port is not used.)
    There are a few reports where neither a dock nor an external monitor was involved.
    Playing certain games reliably triggers the crash.
    Steps to reproduce
    While intially (around September 2008 - October 2008) the crash could be triggered easily, the situation is now (December 2008) more complex. The crashes do still occur, though there is no clear pattern anymore. According to various reports, the display driver crash can be triggered as follows:
    Resuming from standby
    Watching a DVD.
    Playing one of these games: Fallout 3, Bioshock, Team Fortress 2, Knights of the Old Republic.
    Arbitrarily during normal work. On a normal working day, the problem occurs at least once.
    Further issues
    Here are more issues which seem to be related. More information can be found in other posts of this thread:
    The notebook display and/or the external monitor runs at a low resolution after resuming from standby.
    After the login both monitors flicker while adjusting the resolution of the monitor.
    The external monitors cannot be activated using Presentation Director.
    The external monitor is blank after docking or undocking.
    There are some reports about display driver crashes on machines running Windows XP.
    The switchable graphics drivers limit the useable RAM under Vista 32 to 2.5GB (i.e. 500MB-1GB less than usual).
    Workarounds
    Lenovo has released a new "tip" document which provides a link to a new driver. Get it here but be sure to read the instructions!
    (Old tips follow below the line. Consider them as obsolete.)
    Here are some tips which might make the problem occur less often. I have not tried all of them. Though, A. and B. have improved the situation for me; your mileage may vary.
    A. If you do not have to use an external monitor, then switch to Intel graphics for time being.
    Otherwise:
    B. Make some changes to your system:
    Disable Aero.
    Create a new profile in the power manager with the following setting: When running on AC, turn off the monitor after 40 minutes. (Thereby, the notebook goes less often to standby.)
    Install the newest graphics drivers.
    Install the newest BIOS.
    Install the newest Hotkey utility.
    Install the newest drivers.
    C. Disable the switchable graphics in the BIOS setup and install modded drivers from ATI (see zilla's post in this thread for instructions).
    The last workaround (C.) has been confirmed to work reliably by several users. Though, thereby you use drivers which have not been tested by Lenovo. It's possible (but not very likely) that damage results by doing so. Also, it might be difficult to install a future Lenovo driver which resolves the issues reported here. Finally, you cannot use the power-saving Intel graphics. Thus, you should only use this workaround if you know what you are doing.
    The programs can be downloaded from the following locations. Notice that System Update does not always offer you immediately the lastest versions.
    R400 and T400 users: Go here.
    T500 and W500 users: Go here.
     User opinions
    "Is there any chance this will be fixed, or should I just get used to my "workstation-class" machine crashing regularly?"
    "I [am] thinking about to sell my w500 if this problems won't be fixed in the next weeks."
    "I've got a T400 w/ Vista 64 and I'll say the Switchable drivers on it S[**]K bad."
    "Unfortunately for Lenovo, our IT Manager is at the point of a awarding a new and rather substantial Enterprise Agreement for our whole organization's PC's, which included a rollout of many new PC's for 2009. The contract was going to go to Lenovo. He mumbled something about HP when I asked him about the state of affairs with my PC... [O]ur firm's IT Manager decided to return all the faulty Lenovo's for a refund and would replace them with HP's."  
    "Is someone from Lenovo paying attention[?]"
    "i'm getting angry with ati and lenovo."
    "there are no new drivers and no ETA for a fix."
    "ThinkPads are supposed to be good, so you'd think there wouldn't be a problem like this."
    "honestly it is completely unacceptable for lenovo to have done nothing this long. I paid extra to get the ATI card, and now I can't hook up my laptop to an external monitor without it crashing. I will probably end up selling the laptop soon since using an external monitor is extremely important to me and lenovo doesn't seem to care about fixing the situation."
    Update:
    - Lenovo support has informed me today (2008-10-24) that they are working on the problem.- changed subject (was: Major troubles with DVI-port and a T400) to reflect new information.- changed message body to reflect new information
    - See MIGR-70490 (dated 2008-09-21) for an official statement from Lenovo.
    - 2008-11-15: The problems are still present and there is still no ETA for a fix.
    - As expected, also R400 models are affected. See below for reports.
    - 2008-11-26: Still no word from Lenovo when the problem will be fixed. Added information on (partial) workarounds.
    - 2008-12-03: Lenovo updated MIGR-70490. Though, problems persist.
    - 2008-12-13: Updated problem description on the basis of new reports.
    - 2008-12-16: Updated problem description on the basis of new reports.
    - 2009-01-07: Updated problem description on the basis of new reports. Still no word from Lenovo. I called Lenovo's customer service in the Netherlands and was promised to receive a callback. Though, so far they didn't (want to) get back to me.
    - 2009-01-08: Updated workaround description on the basis of new reports.
    - 2009-01-10: Updated executive summary on the basis of new reports.
    - 2009-01-14: Updated problem description on the basis of new reports (movie).
    - 2009-01-19: Updated workaround section.
    - 2009-01-21: Happy birthday MIGR-70490! It's now 4 months. Updated workaround section. I called Lenovo's customer service in the Netherlands again.
    - 2009-01-22: Added section "User opinions"
    - 2009-01-23: Updated problem description on the basis of new reports.
    - 2009-01-24: Small updates.
    - 2009-02-02: Small updates.
    - 2009-02-03: Changes to section "Executive summary". Added section "Important information for affected users".
    - 2009-02-04: Update to section "Credits".
    - 2009-02-19: Update to section "Credits".
    - 2009-02-27: Quick update to "Executive summary" and "Workarounds".
    - 2009-03-10: Quick updates to section "Executive summary" and "Important information for affected users".
    - 2009-03-21: Quick update to "Executive summary"
    Credits
    Workaround "Aero off": Bubbi, TonyK
    Workaround "Modded ATI drivers": jtull89,  zilla
    Thanks to Mark_Lenovo and Confederate for their work behind the scenes 
    Thanks to feedback from: ajgiordano, Andy_7575, ben2e, brettgri, bri0831, Brimstar, Bubbi, CodeNameSly, cpueschner, dandill, diablo2man, ewilansky, gaccounts, gan, gandalf7, golffreaksi, Homer, hubertlam, Jiraiya, johnsonjf, jordan_moss, jmark, jtull89, kbarina, lenardg, lukest, misitmichaelf, mlb, MMetts, ojisan, pendaluent, Qot, rmccallen, sarnil, shaofengsd, Snakecharmed, StephanK, tarzan23, Texas1040, TheNewNumber2, TonyK, trickyDick, vedman, Vitalus, Waschbecken, xpnet, xrafx, zilla, ZPrime
     (Please don't expect that this list is complete. I am not paid to keep it accurate and complete and, actually, I have a life besides writing about Lenovo's problems. )
    Original post
    Hi there!
    I have major troubles using a Dell 2709W monitor with my T400. 
    The notebook is attached to a Advanced Mini Dock to which the monitor is connected via DVI.
     The problems are as follows.
    A. Activating the external monitor often fails
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T40
    2. Start Windows and make sure that the T400 is running on the ATI card.
    => Dell monitor enters power saving mode because no signal is coming.
    3. In Windows use either the Presentation Director, Windows, or the ATI tools to activate the Dell monitor.
    Expected result: The Dell monitor is activated and the Windows desktop is shown on it.
    Actual result: It takes 1-3 seconds for the Dell monitor to display something. The monitor shows the Windows desktop for a short period. Then it's black again and the monitor returns to the power saving mode .
    Analysis: It seems that the Presentation Director, Windows, or the ATI tools (or more aptly, I guess, the ATI driver) expect a quick response from the DVI-port that a monitor is present. If they do not receive the response, the DVI-port is deactivated again. Since the monitor is too slow to respond and enters the power saving mode too quickly, the monitor can hardly ever be activated.
    Suggested change: Change these tools (or the ATI driver) so that they wait longer for a response on the DVI-port.
    B. Resuming from monitor sleep causes Windows to fall back to a low resolution if the Dell monitor was activated before
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T400
    2. Start Windows and make sure that the T400 is running on the ATI card.
    3. Select the Energy Star profile
    4. Activate the Dell monitor
    5. Don't use Windows until the notebook display and the Dell monitor are set to sleep by Windows.
    6. Wake up the displays (e.g. by pressing some keys)
    Expected result: Both displays are run in the display mode as before.
    Actual result: The Dell monitor still sleeps. The notebook displays is run at a lower resolution (I guess 800x600). The Windows login prompt is not visible and it has to be guessed that it is shown. Though the typical Windows login background is visible. If the password is entered, then Windows can be used again. Though, the resolution is still low and the Dell monitor still sleeps.
    Analysis: It seems that by sending the Dell monitor to sleep, the monitor deactivates the DVI-interface or enters a low-power interface mode. This seems to disturb some component in Windows (the Presentation Director, Windows, the ATI tools, the ATI driver) in a way that Windows only activates the notebook display when it resumes from "monitor sleep".
    Suggested change: Change these tools (or the ATI driver) so that they can cope with the situation that the DVI-interface is deactivated and wait longer for the interface to be in a useable state. Reactivate an external monitor even if it "sleeps very deeply".
    Relevant system information
    - T400 2767-CTO (T9400, 2x2GB RAM, ATI, WXGA+ LED)
    - Advanced Mini Dock
    - Vista 32 Business (German) - fully updated
    - All Lenovo updates via System Update are installed- Dell 2709W
    - The system runs the ATI graphic card in the described scenarios
    Message Edited by Izmi on 05-21-2009 10:34 AM
    Message Edited by Izmi on 06-29-2009 03:13 PM
    Solved!
    Go to Solution.

    Lenovo support made me reinstall presentation director to rule out this component as a factor. After the reinstallation, the amdkmdap-problem is still present. Letting Windows go to standby and waking the system up afterwards, is a reliable method in my case to reproduce the problem on condition that an external monitor was active. The problem does not occur if no external monitor is present.
    A web search for "amdkmdap", "atikmpag","BSOD" with one of the ThinkPad-series names (like "T400") shows that other persons also have this problem with R400s, T400s, T500s, and W500s:
    - t400: Display driver crashes
    - W500 Display Driver
    - My W500
    - T400 Display driver stopped working...
    - T500 Video/Video Driver Issues (2056-4SU)
    - NUS T400 issues
    - T400 Display Driver Issue
    - Vista64 + 4GB RAM + External Display = BSOD
    - R400 problem report (in Chinese)
    - T500 problem report (in Chinese)
    - Bioshock keeps crashing (seems related)
    -  Vista x64, ATI graphics, dock + external LCD = bluescreens? (a report by a W500 user)
    - many problems with lenovo w500
    - another R400 problem report (in Chinese)
    -  Vista BSOD on Lenovo T500 with new Switchable Graphics
    - switchable graphics and external monitor through port replic
    - Problem with Lenovo T500 notebook & external LCD
    - Lenovo ThinkPad T400 - some impressions.
    - T400 freezes with graphics Intense programes
    - Standard Laptop mit ein paar Macken (in German)
    Some possibly related Non-Lenovo cases: 
    - Why Vista crashes so often when dual display is enabled?
    - Vista and 7.3 Display driver atikmdag stopped responding error
    - 4870 vista x64 multi-mon = atikdmag BOOM
    In the cases in which people observe the "amdkmdap"-problem and describe the circumstances, the use of an external monitor is always a factor. These other reports also indicate that it is likely not an issue with the hardware of my notebook (or then a general problem for many batches of these machine types). For it happens a) on many systems and b) on different kinds of systems.
    If others want to contribute to the problem solution, then we should provide Lenovo and ATI a good problem description. So, please add your description.
    Message Edited by Izmi on 02-03-2009 11:53 AM

  • New Windows 10 Insider Preview Build 10074 now available

    New Windows 10 Insider Preview Build 10074 now available, see here- http://blogs.windows.com/bloggingwindows/2015/04/2​9/new-windows-10-insider-preview-build-10074-now-a​...
    and from that page:
    New Windows 10 Insider Preview Build 10074 now available
    April 29, 2015April 29, 2015 by Gabe Aul // PC, Tablet // 0 Comments
    113
    532
    37
    Hi everyone from the Build 2015 conference happening right now in San Francisco! If you haven’t already, check out Terry’s blog post about all the Windows 10 announcements we made today. If you’re at Build this week or at Ignite in Chicago next week – keep your eye out for me and say hello!
    Today we have a new build available to both the Fast and Slow ring for Windows Insiders (that means we’ll have ISOs available too for those of you who like a clean install.) With this build we continue to evolve the features and design for Windows 10, and you’ll see a lot of subtle changes and improvements, many of which were influenced directly by Windows Insiders. One of those changes is the reintroduction of some Aero Glass elements in the UI, but there are many more things throughout the product as well. We continue to use your feedback directly day to day in how our feature teams operate, and we hope that Windows 10 will be the best version of Windows yet because you had a direct hand in its creation.
    One other subtle change that you’ll notice is that we’ve changed how we talk about the builds from “Technical Preview” to “Insider Preview” to reflect the importance of the Windows Insider community in how we’re building Windows 10.
    And speaking of Windows Insiders, we were super excited to host the 10 winners of our Windows Insiders to Campus contest in Redmond last week and hear their thoughts on the program and the product. We’ll share more on that soon.
    Here is what’s newSome of the things that Joe demoed on stage earlier today during the Build keynote are not yet included in this build and will be in future builds. But we still have a bunch of new stuff for you to check out!
    General UX improvements: We made a bunch of UX improvements with the last build and you’ll see even more in this build. For example, you’ll notice a new Live Tile animation for Start in addition to in addition to some performance and stability improvements for Live Tiles.
    We’ve done work to better support high DPI displays. And we know many Windows Insiders are running multi-mon setups – often with 2 monitors with different DPI. You will start to see some work we’re doing to make sure core UX components in Windows scale correctly on both your monitors so things look nice regardless of DPI.
    We’ve also heard loud in clear that many Windows Insiders want to see Aero Glass from Windows 7 make a comeback. We’ve been working out how to satisfy this request, and are trying some things out with this build to see how you like them. We’re running a little A/B test with this build. 50% of you will normal transparency on the Start menu and taskbar while the other 50% will see a blur effect on the Start menu and taskbar (like frosted glass). If Windows Insiders really like the blur effect, we will add it to more areas and even consider making it the default instead of standard transparency. Which one did you get? Send us feedback about it via the Windows Feedback app!
    Even more improvements to Continuum: We’re continuing to make Continuum better and invest in a simplified taskbar. Additionally when you close an application in Tablet mode, we take you back to the Start screen instead of the desktop as you would expect when using a tablet. You will see general polish on snapping, and the shared divider between two snapped windows now let’s you adjust the size.
    Multi-tasking improvements: We’re continuing to refine and complete our mulit-tasking experience with Windows 10. Check out Alt-Tab, Task-View, and Snap Assist. Snap Assist also now supports the ability to close a window during Snap Assist.
    New default Windows sounds: We’ve heard a lot of feedback from people that they want some fresh system sounds for Windows 10. Check them out and let us know what you think.
    Visual refresh for Cortana: You will see a visual refresh for Cortana in this build that makes the experience feel more ingrained into the overall Windows experience. Start and Cortana are now more tightly integrated. As you start to search for an app from within Start, Cortana can seamlessly take over and bring back the right result. The new Windows split view control has been added to Cortana’s left rail, offering quick access to key Cortana functionality like the Notebook, Reminders or Feedback on how Cortana’s doing. This split view control helps anchor Cortana to the rest of the Windows UI and provides navigation consistent with many other Windows first party applications.
    New experiences in Cortana: We are making available some new and updated experiences in Cortana powered by Bing Instant Answers. Cortana will aim to answer your question while you’re still typing. Here are a few questions you can try:
    Weather – “Seattle Weather”
    Finance – “MSFT stock”
    Dictionary – “define astounding”
    Calculator – “48*92”
    Flight Status – “UA 238”
    Reference – “how tall is brad pitt”
    Showtimes – “movies near me”
    Tech Help – “memory in my computer”
    Time Zone – “time in London”
    Unit Conversion – “42 ft in meters”
    Chit Chat – “tell me a joke”
    Updates for the Music and Video Preview apps: We’ve also shipped updates to these apps. The Music Preview app (3.6.999.0) has some UX improvements including a more immersive Now Playing experience with a true full screen mode. With the Video Preview app (3.6.999.0) – you can download movies, TV shows, and TV seasons and check progress, pause, resume, cancel the download. You can also download, delete, and even re-download videos as many times as you want on up to three devices (we’re planning to increase the number of devices you can download content too!). Closed captioning for purchased content now appears. You will see a list of new features when you first launch these app after each update!
    Xbox app April 2015 update: The Xbox app for Windows 10 has been updated (your version number should be 4.4.9014.0 or higher) with new features like Game DVR for PC games, screenshots, a Live Tile, user profiles, and real-name sharing. Oh and the drivers for Xbox controllers are now included with Windows 10, so you no longer have to download and install controller drivers on Windows 10. For more on this month’s Xbox app for Windows 10 update as well as the new Avatars app – read this blog post.
    Windows Store Beta improvements: We’re excited about delivering a single unified Store experience in Windows 10 which we’re talking more about this week at Build. We’ve made some improvements to the Store Beta which is now a blue tile instead of grey. Xbox Live games should be working and so are in-app purchases. Apps you purchased on a PC running Windows 8.1 will now show up in the Store Beta on Windows 10 as owned (and vice-versa). We’re also expanding the Store Beta from 41 markets with the addition of these new markets: Afghanistan, Åland Islands, Albania, Algeria, American Samoa, Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Armenia, Aruba, Azerbaijan, The Bahamas, Bangladesh, Barbados, Belize, Benin, Bermuda, Bahrain, Bhutan, Bolivia, Bonaire, Bosnia and Herzegovina, Botswana, Bouvet Island, Cyprus, Dominican Republic, El Salvador, Georgia, Ghana, Guatemala, Iceland, Iraq, Kazakhstan, Malta, Pakistan, Qatar, Sri Lanka, Jordan, Lebanon, Nicaragua, Oman, Panama, Puerto Rico, Paraguay, Trinidad and Tobago, Uganda, Venezuela.
    Discovering features and apps in Windows 10: We are investing in easy “bite-sized” learning and discovery experiences so that users can get more out of Windows 10. This ranges from tips and tricks on the Lock screen, to helping users discover high quality apps through Start, the Lock screen and Cortana. Be confident that you won’t miss out on new features and enjoy the ease of having high quality apps curated for you. It’s optional, and if anything doesn’t strike your fancy, you can provide feedback directly, such as whether you like an image or an app. These new experiences will be rolling out over time, so you may not see them in your market yet.
    Here are some things we fixed
    You can now launch Win32 (desktop) apps from the Start menu again. Sorry about this bug!
    You should be able to download music in the Xbox Music and Music Preview apps.
    When you minimize an app playing audio, it should continue playing in the background.
    Here are some known issues
    Developers cannot enable Developer Mode in the Settings app for installing and testing apps on this build. We’ll enable this in an upcoming build. In the meantime, you will need enable your device for development using the Group Policy Editor.
    There is an issue in this build preventing some games from playing in full screen mode. We’re working to get a fix out via WU as soon as possible.
    The People app continues to crash. We’re planning to release an update for the People app through the Store Beta that fixes this.
    We hope you’ll agree that 10074 has some nice improvements and is another step forward towards delivering a great Windows 10 release. Please put it through the paces and keep sending us feedback on the things that you like and the things you want us to keep working on using the Windows Feedback app. I hope that you’ll also download the development tools released at Build and will build some terrific Universal Windows apps as well!
    Thanks,
    g
    S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!****

    Which computer? There is a label on the bottom.
    Try an older version of the driver for your model.
       Touchpad stopped working
    -Jerry

  • Satellite P200: How do i calibrate monitor to get same colors using Photoshop CS3

    How do i calibrate monitor to get print that looks like pic on screen?
    I am using Photoshop CS3.
    When I get a pic the way I want it on the screen and try to print it, it prints much darker. I could calibrate my iMac monitor for photoshop but can't find a way of doing it with my Satellite P200.
    My printer is a Canon ip4300 and I'm using Canon ink and paper.

    I think you need additional software and hardware to calibrate yout monitor.
    Start Here http://search.lycos.co.uk/searchframe.html?url=http%3A%2F%2Fwww.drycreekphot o.com%2FLearn%2Fmonitor_calibration.htm&query=moni tor+calibration

  • WL 6.1 sp3 hanging, requests time out

    Hi,
    We're using WL 6.1 with SP3 and a patch - CR080901_61sp3.jar - has been applied.
    The server runs on a 4 CPU NT Server.
    We observe that under moderate load conditions (200 concurrent users), the WL
    server stops responding to requests. The thread count in the default execute queue
    is 15. The thread dump is produced below.
    Increasing the thread count does not seem to be the best solution in this case.
    Any feedback is appreciated though.
    Thanks in advance,
    - Gagan
    Full thread dump:
    "ListenThread" prio=5 tid=0x7ffd90 nid=0x1eb runnable [0x49fef000..0x49fefdc8]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
    at java.net.ServerSocket.implAccept(ServerSocket.java:238)
    at java.net.ServerSocket.accept(ServerSocket.java:217)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:257)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d2480 nid=0x1e8
    waiting on mon
    itor [0x48a4f000..0x48a4fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d1080 nid=0x210
    waiting on mon
    itor [0x48a0f000..0x48a0fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d1c60 nid=0x76
    waiting on moni
    tor [0x489cf000..0x489cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d0860 nid=0x180
    waiting on mon
    itor [0x4898f000..0x4898fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cf840 nid=0x1f7
    waiting on mon
    itor [0x4894f000..0x4894fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ce440 nid=0x22d
    waiting on moni
    tor [0x4890f000..0x4890fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cd040 nid=0x1b1
    waiting on moni
    tor [0x488cf000..0x488cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cc040 nid=0x21f
    waiting on moni
    tor [0x4888f000..0x4888fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cb040 nid=0x216
    waiting on moni
    tor [0x4884f000..0x4884fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cb820 nid=0x1ff
    waiting on moni
    tor [0x4880f000..0x4880fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ca020 nid=0x1d0
    waiting on moni
    tor [0x487cf000..0x487cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ca6c0 nid=0x1c1
    waiting on moni
    tor [0x4878f000..0x4878fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c98f0 nid=0x1df
    waiting on moni
    tor [0x4874f000..0x4874fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c9490 nid=0x190
    waiting on moni
    tor [0x4870f000..0x4870fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c9d20 nid=0x1b7
    waiting on moni
    tor [0x486cf000..0x486cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x7c5d00 nid=0x1
    94 waiting on monitor [0x4868f000..0x4868fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x7c4450 nid=0x1
    bb waiting on monitor [0x4864f000..0x4864fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x7c4660 nid=0x2
    36 waiting on monitor [0x4860f000..0x4860fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x7b4260
    nid=0x16e wa
    iting on monitor [0x485cf000..0x485cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x7b5d00
    nid=0x66 wai
    ting on monitor [0x4858f000..0x4858fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "HighPriority TimeEventGenerator" daemon prio=9 tid=0x7b3050 nid=0x23e waiting
    on monitor [0x4854f00
    0..0x4854fdc8]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x7ad2c0
    nid=0x170 w
    aiting on monitor [0x484ff000..0x484ffdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x7abec0
    nid=0x227 w
    aiting on monitor [0x484bf000..0x484bfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x7ab3d0 nid=0x174 waiting on monitor [0x4847f000..0x4847fdc8
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "TimeEventGenerator" daemon prio=5 tid=0x7a9070 nid=0x1b9 waiting on monitor [0x4843f000..0x4843fdc8
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" daemon prio=5 tid=0x7a64a0 nid=0x20d waiting on monitor
    [0x483ff000..0x483ffdc
    8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
    at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x7a40a0 nid=0x1af
    runnable [0x483bf000
    .0x483bfdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x7a4c80 nid=0x1e5
    runnable [0x4837f000
    .0x4837fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x7a3880 nid=0x10b
    runnable [0x4833f000
    .0x4833fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x7a2480 nid=0x167
    runnable [0x482ff000
    .0x482ffdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x7a1080 nid=0x121
    runnable [0x482bf000
    .0x482bfdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x7a1c60 nid=0x10c
    runnable [0x4827f000.
    .0x4827fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x7a0860 nid=0x201
    runnable [0x4823f000.
    .0x4823fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x79f300 nid=0x144
    waiting for monitor e
    ntry [0x481ff000..0x481ffdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x79fec0 nid=0x1cf
    waiting for monitor e
    ntry [0x481bf000..0x481bfdc8]
    at weblogic.socket.NTSocketMuxer.trigger(NTSocketMuxer.java:302)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x79eac0 nid=0x45
    waiting for monitor en
    try [0x4817f000..0x4817fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x79d6d0 nid=0x20c
    waiting for monitor e
    ntry [0x4813f000..0x4813fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x79de20 nid=0x1d7
    waiting for monitor e
    ntry [0x480ff000..0x480ffdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=5 tid=0x79ca20 nid=0x200
    waiting for monitor e
    ntry [0x480bf000..0x480bfdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x79b8f0 nid=0x1ec
    waiting for monitor e
    ntry [0x4807f000..0x4807fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=5 tid=0x79bb70 nid=0x23c
    waiting for monitor e
    ntry [0x4803f000..0x4803fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '0' for queue: 'navigateCatalog'" daemon prio=5 tid=0x79bcb0 nid=0x142
    waiting on mo
    nitor [0x47fff000..0x47fffdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=10 tid=0x798b10 nid=0x1b2 waiting on monitor [0x47fbf000..0x47fbfdc8]
    at java.lang.Thread.sleep(Native Method)
    at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:15
    69)
    at java.lang.Thread.run(Thread.java:479)
    "Signal Dispatcher" daemon prio=10 tid=0x76b150 nid=0x32 waiting on monitor [0..0]
    "Finalizer" daemon prio=9 tid=0x7698f0 nid=0x3b waiting on monitor [0x4716f000..0x4716fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
    "Reference Handler" daemon prio=10 tid=0x769df0 nid=0x15e waiting on monitor [0x4712f000..0x4712fdc8
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
    "main" prio=5 tid=0x762330 nid=0x17f waiting on monitor [0x6f000..0x6fc44]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:647)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:211)
    at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=5 tid=0x7688a0 nid=0x224 runnable
    "VM Periodic Task Thread" prio=10 tid=0x76a150 nid=0x1ca waiting on monitor
    "Suspend Checker Thread" prio=10 tid=0x76b780 nid=0x20b runnable

    Gagan,
    Can you post the command line arguments and the machine configuration.
    -Kiran
    "Chandra Bommas" <[email protected]> wrote in message news:<[email protected]>...
    I would presume that you are experiencing a JVM pause. Set up the verbose gc option
    on your JVM and check if a FULL GC is happening when your server seems to be hanging.
    If this is what is indeed happening, then you need to tune your JVM to minimize
    pause times.
    hth,
    CB.
    "Gagan Bhatnagar" <[email protected]> wrote:
    Hi,
    We're using WL 6.1 with SP3 and a patch - CR080901_61sp3.jar - has been
    applied.
    The server runs on a 4 CPU NT Server.
    We observe that under moderate load conditions (200 concurrent users),
    the WL
    server stops responding to requests. The thread count in the default
    execute queue
    is 15. The thread dump is produced below.
    Increasing the thread count does not seem to be the best solution in
    this case.
    Any feedback is appreciated though.
    Thanks in advance,
    - Gagan
    Full thread dump:
    "ListenThread" prio=5 tid=0x7ffd90 nid=0x1eb runnable [0x49fef000..0x49fefdc8]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
    at java.net.ServerSocket.implAccept(ServerSocket.java:238)
    at java.net.ServerSocket.accept(ServerSocket.java:217)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:257)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d2480
    nid=0x1e8
    waiting on mon
    itor [0x48a4f000..0x48a4fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d1080
    nid=0x210
    waiting on mon
    itor [0x48a0f000..0x48a0fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d1c60
    nid=0x76
    waiting on moni
    tor [0x489cf000..0x489cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7d0860
    nid=0x180
    waiting on mon
    itor [0x4898f000..0x4898fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cf840
    nid=0x1f7
    waiting on mon
    itor [0x4894f000..0x4894fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ce440
    nid=0x22d
    waiting on moni
    tor [0x4890f000..0x4890fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cd040
    nid=0x1b1
    waiting on moni
    tor [0x488cf000..0x488cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cc040
    nid=0x21f
    waiting on moni
    tor [0x4888f000..0x4888fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cb040
    nid=0x216
    waiting on moni
    tor [0x4884f000..0x4884fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7cb820
    nid=0x1ff
    waiting on moni
    tor [0x4880f000..0x4880fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ca020
    nid=0x1d0
    waiting on moni
    tor [0x487cf000..0x487cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7ca6c0
    nid=0x1c1
    waiting on moni
    tor [0x4878f000..0x4878fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c98f0
    nid=0x1df
    waiting on moni
    tor [0x4874f000..0x4874fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c9490
    nid=0x190
    waiting on moni
    tor [0x4870f000..0x4870fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x7c9d20
    nid=0x1b7
    waiting on moni
    tor [0x486cf000..0x486cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5
    tid=0x7c5d00 nid=0x1
    94 waiting on monitor [0x4868f000..0x4868fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5
    tid=0x7c4450 nid=0x1
    bb waiting on monitor [0x4864f000..0x4864fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon
    prio=5
    tid=0x7c4660 nid=0x2
    36 waiting on monitor [0x4860f000..0x4860fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x7b4260
    nid=0x16e wa
    iting on monitor [0x485cf000..0x485cfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5
    tid=0x7b5d00
    nid=0x66 wai
    ting on monitor [0x4858f000..0x4858fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "HighPriority TimeEventGenerator" daemon prio=9 tid=0x7b3050 nid=0x23e
    waiting
    on monitor [0x4854f00
    0..0x4854fdc8]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
    prio=5 tid=0x7ad2c0
    nid=0x170 w
    aiting on monitor [0x484ff000..0x484ffdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
    prio=5 tid=0x7abec0
    nid=0x227 w
    aiting on monitor [0x484bf000..0x484bfdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x7ab3d0 nid=0x174 waiting on
    monitor [0x4847f000..0x4847fdc8
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "TimeEventGenerator" daemon prio=5 tid=0x7a9070 nid=0x1b9 waiting on
    monitor [0x4843f000..0x4843fdc8
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" daemon prio=5 tid=0x7a64a0 nid=0x20d waiting on
    monitor
    [0x483ff000..0x483ffdc
    8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
    at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x7a40a0
    nid=0x1af
    runnable [0x483bf000
    ..0x483bfdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x7a4c80
    nid=0x1e5
    runnable [0x4837f000
    ..0x4837fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x7a3880
    nid=0x10b
    runnable [0x4833f000
    ..0x4833fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x7a2480
    nid=0x167
    runnable [0x482ff000
    ..0x482ffdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x7a1080
    nid=0x121
    runnable [0x482bf000
    ..0x482bfdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x7a1c60
    nid=0x10c
    runnable [0x4827f000.
    .0x4827fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x7a0860
    nid=0x201
    runnable [0x4823f000.
    .0x4823fdc8]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:583)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x79f300
    nid=0x144
    waiting for monitor e
    ntry [0x481ff000..0x481ffdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x79fec0
    nid=0x1cf
    waiting for monitor e
    ntry [0x481bf000..0x481bfdc8]
    at weblogic.socket.NTSocketMuxer.trigger(NTSocketMuxer.java:302)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x79eac0
    nid=0x45
    waiting for monitor en
    try [0x4817f000..0x4817fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x79d6d0
    nid=0x20c
    waiting for monitor e
    ntry [0x4813f000..0x4813fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x79de20
    nid=0x1d7
    waiting for monitor e
    ntry [0x480ff000..0x480ffdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '2' for queue: 'default'" daemon prio=5 tid=0x79ca20
    nid=0x200
    waiting for monitor e
    ntry [0x480bf000..0x480bfdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x79b8f0
    nid=0x1ec
    waiting for monitor e
    ntry [0x4807f000..0x4807fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=5 tid=0x79bb70
    nid=0x23c
    waiting for monitor e
    ntry [0x4803f000..0x4803fdc8]
    at weblogic.socket.NTSocketMuxer.cleanup(NTSocketMuxer.java:541)
    at weblogic.servlet.internal.MuxableSocketHTTP.endOfStream(MuxableSocketHTTP.java:217)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1037)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2265)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '0' for queue: 'navigateCatalog'" daemon prio=5 tid=0x79bcb0
    nid=0x142
    waiting on mo
    nitor [0x47fff000..0x47fffdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "Thread-0" daemon prio=10 tid=0x798b10 nid=0x1b2 waiting on monitor [0x47fbf000..0x47fbfdc8]
    at java.lang.Thread.sleep(Native Method)
    at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:15
    69)
    at java.lang.Thread.run(Thread.java:479)
    "Signal Dispatcher" daemon prio=10 tid=0x76b150 nid=0x32 waiting on monitor
    [0..0]
    "Finalizer" daemon prio=9 tid=0x7698f0 nid=0x3b waiting on monitor [0x4716f000..0x4716fdc8]
    at java.lang.Object.wait(Native Method)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
    "Reference Handler" daemon prio=10 tid=0x769df0 nid=0x15e waiting on
    monitor [0x4712f000..0x4712fdc8
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
    "main" prio=5 tid=0x762330 nid=0x17f waiting on monitor [0x6f000..0x6fc44]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:415)
    at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:647)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:211)
    at weblogic.Server.main(Server.java:35)
    "VM Thread" prio=5 tid=0x7688a0 nid=0x224 runnable
    "VM Periodic Task Thread" prio=10 tid=0x76a150 nid=0x1ca waiting on monitor
    "Suspend Checker Thread" prio=10 tid=0x76b780 nid=0x20b runnable

  • GE FANUC PROTOCOL PLC ADDRESS

    I have a CMM with dual ports, acting on RS-232, I am unable to complete the project as i cannot get the correct communications to go. I have setup one port as SNP, correct speeds and settings, in lookout as well, but when it comes to the PLC address do i use the CPUs SNP ID? or the port id?
    Second reference, the next thing to try is the ModBus control, the GE uses RTU, how would i correctly connect to the ge with the modbus control from lookout?
    Mike Crabtree - Lead Developer
    Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
    (866) 964-6948 / (760) 247-9512

    The lookout GE_Series90 object only supports SNPX (via serial), and is pretty specific about selecting either a 90-30 or 90-70 series. I'm not familiar with a CMM, but it may not communicate with the GE object in lookout. But if it does, the PLC address would be the SNP address configured for the port you are connected to on the PLC (each port can have a different address).
    As for using Modbus RTU protocol, that should work great in place of the SNP protocol (works quite well for me). Here is a link that will help with the difference in register numbering.
    http://www.gefanuc.com/support/plc/faq00005.htm
    You will notice that not all registers are accessible using the RTU Protocol (%M is one example), but you do get the additional diagnostic tools to moni
    tor communication with the Modbus object.

  • DEFECT: (Serious!) Truncates display of data in multi-byte environment

    I have an oracle 10g database set up with the following nls parameters:
    NLS_CALENDAR      GREGORIAN
    NLS_CHARACTERSET      AL32UTF8
    NLS_COMP      LINGUISTIC
    NLS_CURRENCY      $
    NLS_DATE_FORMAT      DD-MON-YYYY
    NLS_DATE_LANGUAGE      AMERICAN
    NLS_DUAL_CURRENCY      $
    NLS_ISO_CURRENCY      AMERICA
    NLS_LANGUAGE      AMERICAN
    NLS_LENGTH_SEMANTICS      CHAR
    NLS_NCHAR_CHARACTERSET      UTF8
    NLS_NCHAR_CONV_EXCP      TRUE
    NLS_NUMERIC_CHARACTERS      .,
    NLS_RDBMS_VERSION      10.2.0.3.0
    NLS_SORT BINARY
    NLS_TERRITORY      AMERICA
    NLS_TIMESTAMP_FORMAT      DD-MON-RR HH.MI.SSXFF AM
    NLS_TIMESTAMP_TZ_FORMAT      DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_TIME_FORMAT      HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT      HH.MI.SSXFF AM TZR
    I am querying a view in sqlserver 2000 via an odbc database link.
    When I query a 26 character wide column in the view in sql developer, it will only return up to 13 characters of the data.
    When I query the exact same view in the exact same sql server database from the extact same oracle database using the exact same odbc database link using sql navigator, I get the full 26 characters worth of data.
    It also works just fine from the sql command line tool from 10g express.
    Apparently, sql developer is confused about how to handle multi-byte data. If you ask it the length of the data in the column, it will tell you 26, but it will only show you 13.
    I have found a VERY PAINFUL work around, to do a cast(column_name as varchar2(26) when I query it. But I've got hundreds of views and queries...

    In all other respects, the settings I have appear to be working correctly.
    I can enter multi-byte characters into the sql worksheet to create a package, save it, and re-open the package with the multi-byte characters still visible.
    I'm using a fallback directory for my jdk with the correct font installed, so I can see and edit multi-byte data in the data grids.
    In this case, I noticed the problem on a column that only contains the standard ascii letters and digits.
    Environment->Encoding = UTF-16
    All the fonts are set to a font that properly displays western and ge'ez characters. The font has been in use for years, and is working correctly in all other circumstances.
    The Database->NLS Parameters tab under sql developer preferences shows:
    language: American
    territory : American
    sort: binary
    comp: binary
    length: char (I've also tried byte)
    If there are other settings that you think might be relevant, please let me know.
    I've done some more testing. I created an oracle table with a single column and did an insert into ... select from statement across the database link. The correct, full-length data appeared in the oracle table.
    So, it's not a matter of whether the data is being returned or not, it is. It is simply not being displayed correctly. It appears that sql developer is making some unwarranted decisions about the datatable across the database link when it decides to display the data, because sql plus and sql navigator have no such issues.
    This is really a very serious problem, because if I cannot trust the data the tool shows me, I cannot trust the tool.
    It is also an invitation to make an error based upon the erroneous data display.

  • Need help in Multi mapping

    Hi experts,
    we have a scenario need to send an EDI text file to 2 different receivers. We are receving the EDI file using the JMS adapter as Sender and File/FTP adapter as a receiver.
    We are using Multi mapping (includes Java mapping and Graphical ) to send the Messages to receivers, While sending we are getting the Error In Moni as "Error in creating Multi XML Document".
    In Java Mapping we are Converting the EDI text to EDI xml with <ns0:Messages1> and the output of Java mapping to Graphical Mapping,
    While testing in Interface Mapping Test it works fine.
    Please provide your Valuable inputs.
    Thanks,
    Ramg

    HI
    The below is the output im getting from Interface mapping
    =====
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><ns2:MT_Req xmlns:ns2="http://test.com/CommonServices"><DataConversionArea><SapQtySign>P</SapQtySign><Filler>                                                              </Filler></DataConversionArea><DataElement><RspShipToLoc>000000</RspShipToLoc><Filler>                                                                       </Filler></DataElement></ns2:MT_Req></ns0:Message1>
    <ns0:Message2><ns2:MT_In_Req xmlns:ns2="http://test.com/CommonServices"><DataElements><ProdSchedNbr>             </ProdSchedNbr><Filler>0030</Filler></DataElements></ns2:MT_In_Req></ns0:Message2></ns0:Messages>
    =====
    Thanks
    Ramg

  • Error in Multi-mapping without BPM

    Hi frnds,
    I am doing a scenario File-XI-File. I am using the multi-splitting thing in the Message mapping. I have taken care of all the occurance's and "enhanced" thing in the IR and ID resp. I m using SP16. I want to avoid BPM.
    But therez sme error cming up. When I check the MONI, its shwing "No messages created from split mapping" and when I test my interface using the Test Configuration in the ID, its shwing error in the Receiver Determination -- "HTTP connection to ABAP Runtime failed. Error: 403 Forbidden"
    I have checked most of the blogs and forum suggestions. I have checked the ICF activations as well ...
    So, do come back to me with your valuable suggestions, and I will award them points, if they really help me out.
    Thanks and regards.
    Neetesh

    Hi Neetesh,
    <i>
    When I check the MONI, its shwing "No messages created from split mapping"</i>
    For this, Can you check the source XML. Does it contain Tags like <messages> .. If yes, you need to remove them from your source XML.
    If i am right, you have copied the XML from the TEST tab of the message mapping and pasted it in a notepad and saved it without making any changes at all..... Just do as i have mentioned above and i am sure you will no more get that error message in your MONI....
    Also go through this weblog which talks about multi-mapping without BPM,
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    Regards,
    Abhy

  • ABAP Mapping :: for multi files

    Dear Experts,
    We are doing an Idoc to file interface, using ABAP mapping.
    This is 1:n mapping i.e receiver message interface is 0..unbounded.
    We have achieved the mapping for 1:1. But when I test for multi, i get an error in moni saying
    Parsing error after multi mapping.Expected Message<i> instead of Item
    Item is the name of the node that has to be created multiple times.
    Has anyone done multi mapping in ABAP?? Any idea why this error....may be we are missing something.
    Any idea as to how we can progress???
    Thanks in advance
    Regards
    Shobha

    Hi,
    Surely u can use an ABAP mapping for this.
    Sounds like your problem is your not using correct output structure for multi mapping.
    As with any type of multi mapping your structure should reflect this. Your target payload must thus have the following structure:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
         <ns0:Message1>
              <unboundedPayload/>
         </ns0:Message1>
    </ns0:Messages>
    The <unboundedPayload> element in above should of course be replaced with your actual payload - I believe 'Item' in your case, if that is in fact the root node of your actual payload.
    Regards,
    Daniel

  • Multi Mapping in Java Mapping

    Hello Everyone,
    My scenario has a flat file that needs to be grouped and split into multiple xml files
    Since the source is a flat message I have used a java mapping where the splitting happens.
    I've also made sure to add the <mesages> and <messages1> tags for the target message so that my file asapter can split it
    The problem is when i test this interface i get  'Eror while constructing multi-XML Doucment' in my moni
    Anybody had similar problems..??
    Thanks
    Bharath

    Yes,
    I've worked on a few multi mappings before successfully.. so the obvious doubts can be ruled out..
    however this is the first time Im using Java mapping to do this..
    One doubt that however is hovering is "can flat files be used as input ??" or should I use FCC to convert into a simple XML with just one node and parse it to get my payload?

Maybe you are looking for

  • Design Premium CS5 installation problem on OS 10.9.2 Mavericks.

    I recently switched over to a new macbook pro and tried migrating everying over with the Apple migration manager.  While Photoshop and other products seemed to move over just fine, InDesign continued crashing everytime I tried to open.  I tried the s

  • Currency translation taking more time at first time in the report

    Hi All, Here is an issue regarding the currency translation in the report. when we click on the currency translation from the contaxt menu on the report, its taking more time for the first time to get the selection options. But it is fast from the se

  • Enabling Email template in Web UI

    Hi One of the requirements with respect to email templates is that the on the web UI screen, say for example, the service order screen, there would be a button on the screen(for Emails), on the click of which the user views an email template with aut

  • The table ' ' could not be found

    Hello everyone. I just created a custom report for Raiser's Edge using crystal reports and when trying to run the report for the first time I am getting the error message "The table ' ' could not be found". I created an export in Raiser's Edge in MDB

  • No amount in Biilling document

    when i created a contract with billing plan then i go to create a billing document the item line come from the contract but without the amount that i entered in the contract.