• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WSAD Keeps Crashing :-(

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For the last couple days, my WSAD 5.1.2 is crashing very frequently. The jvm exit code is 1073807364 if that helps. It's turning into a real pain in the neck due to the additional complication that often it crashes the UI however my test server remains running some how and cannot be shutdown or restarted once I start the UI up again so I have to re-boot the entire freaking PC. Can anybody point me in some direction by which I might be able to figure this thing out?
Thanks
Chris "Ticked Off In Tallahassee" Skinner
 
Ranch Hand
Posts: 1934
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I can help you on the stop and start of your test server. There should be a startServer.bat that can be used to start the server in appserver/bin directory.

There is also a stopserver.bat to take care of stopping the server.
 
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I dont know why the WSAD keeps crashing, but to get around the server problem, do not reboot your PC. just kill the process using the task manager. Go to the Process tab of the task manager and kill the javaw.exe task (easy way to identify it is that it uses a high amount of your RAM).
This should allow you to restart WSAD and the server again
[ May 03, 2006: Message edited by: Pratik Lohia ]
 
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mr Ticked-Off?

There are many facets to this apparently wonderful tool that have made me lose the will to live on numerous occaisions.

I take it there are no exception stack traces you are able to post? Or nothing specified in the WSAD log files?
 
Chris Skinner
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'll keep an eye out for the logs next time it happens.

Kishore, where would the stopserver.bat file be located? I looked in my workspace under the Server directory and found nothing.

Thanks
Chris
 
Chris Skinner
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Found it under C:\WSAD\runtimes\base_v51\bin
 
Why fit in when you were born to stand out? - Seuss. Tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic