Problems with my FX5200
I got this PC lately:
MSI 865PE Neo2
Intel P4 2.6 C Ghz
120 GB Hitachi HDD 7200 RPM
MSI FX5200 128 MB DDR RAM VGA
512 DDR 333 RAM
etc....
Well The problem is that when i am using the pc , while playing a game or not , the computer by itself restarts
does anyone know why?
I have Windows XP with all its updates on my pc (including Service Pack 1)
Thank you
Brand of RAM? Power Supply spec's? Try disabling the "automatically restart" feature in control panel -> system -> advanced -> startup and recovery settings. Is it blue screening when it restarts?
Similar Messages
-
Hello guys,
I bought a MSI GeForce FX5200 TD-128 last year. It's working well, but I can't update its driver, that's why I'm using the driver that comes in the CD with the video card.
I bought Half-Life 2 yeasterday, and the game recommends me to update the video driver in order to have the best graphic quality, but when I install the most up to date driver, the image becomes the worst of all...
I've tried to update the DirectX aswell, but it didn't work...
Now I'm using the DirectX 9.0C
Can someone help me??
Thanks !!Quote
Originally posted by Kafkacell
What version of the drivers are you using?
Did you uninstalled completely the old drivers? Are you using MSI dirvers or nvidia drivers? remenber this: the latest driver are recommended mostly for the geforce 6 series. So i recommend you to download this version: 61.77 those are very stable and you get a good image quality, becasue if you install the latest drivers you could see a very good image but for the sake of performance, and also you could try installing several drivers and check them and stay with the one that you liked most. And remember also that each vid card it's unique! you can't compare them even if they are identical.
are doing overclocking? did you installed the chipset drivers before to reinstall the vid card drivers? -
Problem with my fx5200 128meg card
ok i just orderd an MSI Gforce fx5200 128meg agp card. I used to have an Evga gforce4 fx440 64meg pci card. I replaced the old card with the new one, but when i connect the monitor to the new card it doesnt turn on it just sits there like the computer isnt on, but when i put the old card back in and connect the monitor it works fine.....i dont know if its the card or the monitor or anything else, if you guys could please help me that would be great...thanks
pDuBBlet me guess what board your sticking it in
let me see now what are the max amps on this psu label
nope ive had a net vision failure
so you better look -
Problem with FX5200 it hangs the computer!
Hi every one.
i have a problem with my FX5200 T-128, it hangs my computer.
My system is
Moderboard: AK75-ec from dfi.com
Cpu: Amd athlon 1300Mhz
memory: 512 sdram
Some time the FX5200 works good, but many times it hangs when i am trying to play some games, some times it take few days and some time it hangs and hangs the system but after few mins it working again.
i have checked everything Volts, drivers is up to date, upgrade moderboard bios, and everything i have tryid to reinstall xp pro but nothing helps.
i have tryind to test it in other computer with other mainboards to but same there.
any one can help me ?
Regard PFtelecomi have Nvidias newest driver installed, it hangs when it try to load the games.
what more details do you need me to give ?
and the cpu was a duron 1300mhz not athlon.
memory 2 256mb Sdram pc133.
operative system: win xp pro with sp2 before sp1 but same it hangs.
i have tryid to reset all in bios and make the right settings there to but nothing.
i have tryid to update bios on moderboard, and for the grafic card i already have newest bios update, i have tryid everything now :(
Regard Pftelecom -
Hi, I have a problem with my MSI FX5200 -t128, I dont know why the card is just shutting down the monitor for like 1 or 2 seconds it just stops what it´s doing. The funny thing is that this does´nt occurs when i´m playing this only occurs when im in windows, i though it was windows so i reinstalled it but nothing it continous happening. I dont know if my monitor is going to break it os just the first time i see this problem, it is like if you take the power of the monitor for 2 seconds and plugged it back again.
I´ve done all that averyone can imagine, first i though it was the card that was wrongly inserted in the agp port but then it continued doing, it it´s very annoying I dont know waht to do, im really concerned about it from the first time i realized it was not the monitor it was the graphic card.
If someone can help me urgently i would apreciate it, because this problem is turning to bigger. (The shutting downs are starting to be more often).
Thanks, wilsorPlease post your computer's specification.
Try to install the lastest driver from http://www.nvidia.com -
HEAVY Problems with Linux x86_64 on K8T Neo
Hello, Community!
I experience *HEAVY* Problems with Linux on my MSI K8T Neo (FSR). Since the customer support of the german dependancy seems to ignore my call for help I'm in good hope that maybe you can help me out or give me some useful advise.
First some Hardware Specs of my system:
MSI K8T Neo FSR, Rev 1.1, BIOS 1.5
AMD Athlon 64 3000+
3x 512MB Kingston DDR400
Enermax EG365P-VE (350W) PSU (3.3V/5V 185W Combinded)
MSI GeForce FX5200 TDR 128
Adaptec ATA RAID AAR1200A (HPT370A) in PCI Slot 3
Hauppauge WinTV PCI in PCI Slot 5
Maxtor 4K040H2 (40GB) as Primary Master
JLMS XJ-HD166S DVD-ROM as Primary Slave
LiteOn LDW-411S DVD+/-RW as Secondary Master
LiteOn LTR-52327S CD-RW as Secondary Slave
2x Maxtor 6Y060L0 (60GB) on HPT370A as Primary Master/Slave
Seagate ST380020A (80GB) on HPT370A as Secondary Master
Maxtor 32049U3 on HPT370A as Secondary Slave
KeyTronic KT2001 USB Keyboard
Microsoft Optical Wheel Mouse Blue USB
I've downloaded Fedora Core 1 x86_64 as well as the lately released Fedora Core 2 test 3 x86_64 distribution. Both CD sets have been burnt ok.
If I try to install Core 1 x86_64 (Kernel 2.4.22-1.2179) the kernel crashes with a "attempted to kill idle task" panic. As far as I've learned the workaround is to give idle=poll as kernel parameter. This resolves the kernel panic, but the installer randomly crashes with segfaults at a random stage; sometimes while loading anaconda, sometimes during package install.
If I try to install Core2 test 3 x86_64 (Kernel 2.6.5) I get a, completely new, error message while the kernel does the PCI Scan:
******* Your BIOS seems to not contain a fix for K8 errata #93
******* Working around it, but it may cause SEGVs or burn power
******* Please consider a BIOS update
******* Disabling USB legacy in the BIOS may also help
I removed my USB keyboard, connected a PS/2 keyboard, disabled to USB Legacy option (I need it enabled in order to use Ghost) in the BIOS and booted again.
The error message is gone now, but as in Core 1 the installer still crashes randomly with segfaults. I'm still unable to go all the way through the installation routine.
I even tried to install Fedora Core 1 "i386": again there are segfaults during install.
Contrary to the problems I experience while trying to install Linux my Windows XP (32-Bit), as well as a test installation of Windows XP 64-Bit, run like a charm without any problems. Strange but true.
Since I already read trough several posts in this forum I already tried running my system with memory sticks from another manufacturers as well as with a more powerful PSU. I even removed my tv-card and raid-controller.
Nogo - Linux still crashes randomly and Windows still works without any flaws.
Has anyone a clue what I can/must do to successfully install Linux?
Might it be that the BIOS has some flaws that might cause the problems?
Has anyone managed to install Linux (what distribution) on this Mainboard?
I would greatly appreciate any help. If you need to know something I haven't provided here please feel free to ask. I'll answer ASAP.
Thank you in advance.
P.S.: The system is *NOT* overclocked in any way.And now even the last problem is solved ...
Since I was successful in installing a basic Gentoo system but still failed to install Fedora I reflashed BIOS 1.5. This time I cleared the CMOS by unplugging the PSU, setting the jumper and removing the backup battery.
Yesterday I only flashed it with the /a switch, which should have cleared the CMOS as well - so far for the theory. However, it once went fine as I upgraded from BIOS 1.1 to 1.4.
After setting up the BIOS options again I gave it another try and booted from Fedora (Core 2 test 3) install CD: No more complains about the CPU errata, although USB legacy is enabled, and I even went through the installation without any problems.
It seems as I will stick with Gentoo as my primary distribution since the kernel makes a more "mature" impression than the one from Fedora (i.e. the K8 PowerNOW! Driver seems to be missing in Fedora's Kernel 2.6.5).
By using an spare Athlon XP Mainboard I worked out that only one of my three Kingston memory sticks had errors - I'm going to replace the faulty stick tomorrow.
Now for the conclusio:
Thanks, especially you JLP, for helping me with my issue. Without the advise to use Gentoo, and the included MemTest86, I wouldn't have been able to track down the error to a faulty memory stick that fast since Windows always ran fine. -
Hello
I ahve a problem, I linked two computers in a network and whenver I try to copy something to and from the KT4V Computer it restarts itself. Also the computer reboots randomly in Windows or at windows xp startup screen (5 sec after starting comp).
What should I do ? Can it be a MB problem ? what can It be?
The computer is:
MB: KT4V
CPU: AMD 2000+ Mhz
RAM: 1x 128 DDRAM PC 2100 PQI and 1x 128 DDRAM PC 2700 Samsung
HDD: 40GB Western Digital
Video: FX5200 nVidia
ATX Source 400W: with +12 18A / +5 32A / +3.3 25A
Thanks in advance.Hello,
Download this prgram and use it to test the memory.
http://www.memtest.org/download/1.55.1/memtest86+-1.55.1.floppy.zip
Extract all files to a folder first then run the install.bat and it will create a memtest bootdisk.
Again using 1 stick at a time run the program for at least 1 hour.
Any errors means that there is a problem with the memory/power.
Should everything be ok then try clearing the CMOS using the Jbat jumper.
Also the CPU should be running at 1.667Ghz (133x12.5). -
Hello,
I've just bought MSi 6600GT 128mb VIVO AGP and I am very dissapointed. Why? Because I can't even run it.
The problem is that computer doesnt even boot up. I did everything I was supposed to do-uninstalled drivers from my current card(actually the problem is not windows-problem or driver-problem), switched cards and when I restarted computer it freezed on the BIOS-init-screen. It shows CPU and RAM inicialized, but not the HDs and CDs drives. There is also a new thing(wasnt there before) saying: "ESC-to skip memory test". And there computer stops. You can leave it that way for 30 minutes and nothing happens.
First I thought I'm low on power(I had 350W PSU) so I bought a new 480W PSU, but the same thing still happens. When I switch cards(back to FX5200) computer runs without a problem. I've also plugged the power cord to power connector on my card as it said in the MSI manual (it wasn't in my original manual, I had to download it form MSI page).
Please, help me.OK, so I'm not going for ATI at the end...why?
BECAUSE
IT
FINALLY
WORKS!!!
Here's what I did(so it may help others with same problems):
With my old card I went to BIOS and set the Optimized settings and did also small changes so it would not enable onboard audio,etc. Then I switched to 6600. First, it started booting XP, but froze so I rebooted and went to Safe Mode. Didnt do any changes there, just to let windows know, that a new card is in the case...After restart, I did a small changes in BIOS(my CPU was still on optimized settings ticking on 1100mhz compared to normal 1917) and XP started normally So I installed VGA drivers, restarted(again with small changes in BIOS - if I made too many changes I wouldnt know which one caused the problems) and to test it I did 3dmark- I had 6229 points(which is not bad with CPU running 60% and with AGP4x and other crappy settings). And finally I changed AGP speed to AGP8x and my CPU speed to 1917mhz and it worked.
I wonder what will happen after I plug in my additional harddrive and floppydrive. -
MS6712 Video and LAN problems with Windows 98SE
Can anyone help please with a problem that’s been baffling me for weeks.I
The computer in question is a TIME Powerstation with AMD 2600+ processor with 1024MB RAM, Nvidia Geforce FX5200 and Windows XP Home.
Have set this computer to Dual Boot to Windows 98SE (Using Acronis OS Selector software).
My problem is that after many attempts, have so far been unable to successfully load drivers for the Nvidia GeForce FX5200 graphics card or to get the LAN function to work in Windows 98.
For the graphics card have tried a number of the more recent Nvidia Detonator Win98 drivers, all have either produced an error message (‘While initialising device IFSMGR: Windows Protection Error’) or a blank screen. Necessitating reverting back to the Standard VGA Driver with its maximum of 16 colours! The LAN function does not work at all in Windows 98SE, though it does in Windows XP – again suspect a driver problem.
The motherboard of this computer is a MSI Microstar MS6712. Have tried the ‘VIA Chipset 4 in 1 Driver’ to no avail. Are any more/different drivers required for Windows 98SE?
Would appreciate any advice in what originally was envisaged as a simple task: getting Nvidia Geforce FX 5200 graphics card and the motherboard’s built in LAN to run correctly on Windows 98.I have your board.
1. Windows 98 won't recognize more then 512MB of RAM.
2. I had problems with the FX 5200 Ultra on this board. Occasionally when I booted the system, I would get a black screen right after the post when the OS was about to load. I've been hearing a few people lately stating problems with the KT4V-L mobo and the FX 5200 Ultra. I promptly returned the card and got a Radeon 9700 Pro instead. I have never been more happy since I made that decision. I will never put another Nvidia card in this mobo again. I also had issues with the Geforce4 MX card I had. I've come to the conclusion that Nvidia sucks.
3. Make sure your BIOS is updated to 1.9, and al lyour VIA drivers are updated. That may help you too.
That's all I can offer. -
Will really appreciate any help on this--I'm not sure if I bought a lemon or my new MSI NX7600GT just isn't compatible with my motherboard.
Before buying this card I bought an ECS card with the same Nvidia chipset, but decided to replace it since it had slow DDR3 memory (500mhz). I got a relatively OK deal for the MSI with the standard 700mhz memory clock.
When I installed the MSI card, I started having stability problems and my display kept turning black. Note that I did not encounter any problems with the ECS 7600GT card or my original Inno3D FX5200.
Here is my current setup:
Athlon 64 3000+
ASROCK 939Dual-SATA2
SATA Western Digital hard drive
IDE DVD Writer
2x512 Dual Channel Kingston Value RAM
Huntkey 400-Watt PS (14A and 15A 12-v rails)
Power Supply?
The Huntkey is brand new, and I have experienced the same problems using a different PS, so I don't think I have power supply problems. Also, I think it's good to note that I encounter problems even before I boot to Windows--before the GPU starts sucking power from my 12-volt rails.
Here is a bulleted list of the symptoms:
- pre-Windows/Windows instability (even in BIOS)
- shaky display
- screen turns black once in a while
- motherboard fails to detect SATA drive
Any ideas?Whew! I just resolved this issue. I had to bring my box to the shop where I bought the card, after they found that the card worked perfectly with other computers with varied configurations. They hooked my box up to their monitor and, guess what, everything was smooth and pretty. I even played a few 3D games without hitches.
I went back home to grab my monitor. We've tested everything and it was the only possible cause at this point. Thank god those LCD monitors are light--I have to walk at least 10 minutes to the nearest taxi stop. Anyway, after all the hassle, I found out that the culprit was my VGA cable. I was going to switch to DVI, but I told myself not to switch cables until I fix the problem. A new $1 VGA cable fixed everything.
The moral lesson:
Check the cheap, simple solutions first and keep spares of the cheap stuff, like cables, handy. =) -
I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
LeftyThis was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
boolean active = true;
public void run(){
ss.setSoTimeout(90);
while (active){
try{
serverSocket = ss.accept();
catch (SocketTimeoutException ste){
// do nothing
// interrupt thread
public void deactivate(){
active = false;
// you gotta sleep for a time longer than the
// accept() timeout to make sure that timeout is finished.
try{
sleep(91);
}catch (InterruptedException ie){
interrupt();
} -
Problem with Threads and a static variable
I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
protected static void Init(){
objMainProcess = new Thread() {
public void run() {
while( objMainProcess == Thread.currentThread() ) {
GetState();
objMainProcess.setDaemon( true );
objMainProcess.start();
public static void initStatusTimer(){
if(objTimer == null)
objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
public void actionPerformed( java.awt.event.ActionEvent evt){
SetState();
private static void SetState(){
if( objMainProcess == null ) return;
synchronized( objMainProcess ) {
bChanged = true;
try{
objMainProcess.notify();
}catch( IllegalMonitorStateException e ) {}
private static boolean GetState() {
if( objMainProcess == null ) return false;
synchronized( objMainProcess ) {
if( bChanged) {
SendMessage();
bChanged = false;
return true;
try {
objMainProcess.wait();
}catch( InterruptedException e ) {}
return false;
}Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D. -
Problem with threads running javaw
Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue; // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer) // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
// System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
}catch(Exception a){
JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run -
Problem with threads and camera.
Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
new Thread(new Runnable(){
public void run() {
while((!performing.isShown()) && (backgroundCamera.isShown())){
Thread.yield();
notifyAll();
}).start();
new Thread(new Runnable(){
public void run() {
try {
this.wait();
} catch(Exception e) {
exceptionHandler(e);
photo = camera.snapshot();
display.setCurrent(displayPhoto);
}).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?Hi,
I've finally managed to work this fine.
The code:
Object o = new Object();
display.setCurrent(perform);
new Thread(new Runnable(){
public void run() {
while(!performing.isShown()){
Thread.yield();
synchronized(o) {
o.notify();
}).start();
new Thread(new Runnable(){
public void run() {
try {
synchronized(o) {
o.wait(1);
} catch(Exception e) {
exceptionHandler(e);
photo = camera.snapshot();
display.setCurrent(displayPhoto);
}).start(); -
We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
=============================================================================================
"ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
at java.lang.String.substring(String.java:1446)
at java.lang.String.substring(String.java:1411)
at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
=============================================================================================
String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
=============================================================================================
----------------- lwp# 44 / thread# 44 --------------------
ff31f364 lwp_mutex_lock (e3d70)
fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
0) + 78
fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
fee6575c _start (5941d0, fa1a1600, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
From the thread dump:
"VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
From the first pstack:
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Second pstack
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there. Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this.
We're using the following memory options:
-ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
-verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
Thanks!
--Andy
Maybe you are looking for
-
Error when exporting a pdf in SAP
She sends me the error when exporting a pdf from the SAP system, this is the message: X Object reference not set to an instance of an object. I hope I can support. Annex image
-
My HD took a dump over this 10.4.8 business
Hello, I know quite a few others have experienced this problem and found no fix so far, but I wanted to create a thread about this specific problem we're having... After installing 10.4.8 onto my 12" ABook, it started behaving erratically and then st
-
MBP 2010, bought in July. Running snow leopard 10.6.8. The built-in isight is not working with Photo booth and Skype, but is working perfectly with the FaceTime app. isight does show up in system profiler under USB high speed Bus. In Photo booth and
-
Reversed order of messages and photos in 5s
I got reversed order of messages and photos when I set up my new 5s. My old phone is a 4. I did the set up via iTunes. How do I re-order?
-
After being downloaded from Ringtones #1 I verified the 5 ringtones were functional, listed both in the Itunes Library and in my Iphone 5. But, when I attempt to "sync" these ringtones I receive a display stating the ringtones cannot be found in the