Sockets problem HELP!!

I am trying to create a peer-to-peer messager using Sockets. I have a Listener class that listens for connections and accepts them and creates a new socket for each connection and also calls a ChatHandler which is passed the new socket. Exept the StartConv class which connects to the listener class initially never finds out about the new Socket and thinks it is still connected to the listener port :(( Here is some of the code i am trying to use for each of the classes:-
Listener
public class Listener implements Runnable {
  public void run () {
  try{
  listen();
}catch(Exception e){
System.out.println("Error in listener:"+e );
  public static void listen() throws IOException{
    int port = 4444;
    ServerSocket server = new ServerSocket (port);
    try{
    System.out.println("Listening...");
         while (true) {
         System.out.println("Listening...11");
         Socket client = server.accept ();
         System.out.println ("Accepted from " + client.getInetAddress ());
         ChatHandler handler = new ChatHandler (client);
         handler.start ();
  }catch (IOException ex){
  System.out.println("Error in listener"+ex);
ChatHandler
public class ChatHandler extends JFrame implements Runnable {
  protected Socket socket;
  public ChatHandler (Socket socket) {
    this.socket = socket;
  protected DataInputStream dataIn;
  protected DataOutputStream dataOut;
  protected Thread listener;
  public void start () {
  System.out.println("Entered ChatHandler.start()");
      try {
        dataIn = new DataInputStream
          (new BufferedInputStream (socket.getInputStream ()));
        dataOut = new DataOutputStream
          (new BufferedOutputStream (socket.getOutputStream ()));
        listener = new Thread (this);
        listener.start ();
        run();
      } catch (IOException ignored) {
  public synchronized void stop () {
    if (listener != null) {
      try {
        if (listener != Thread.currentThread ())
          listener.interrupt ();
        listener = null;
        dataOut.close ();
      } catch (IOException ignored) {
  public void run () {
  System.out.println("Entered ChatHandler.run()");
try{
        String message = dataIn.readUTF ();
   }catch(IOException e) {   
   System.out.println("Problem receiving message: dataIn.readUTF");
        String title = "Conversation from "+socket.getInetAddress();
    JFrame cframe = new JFrame(title);
    // Create a component to add to the frame
    JPanel top=new JPanel();
    JPanel bottom=new JPanel();
    TextArea conv = new TextArea(10,75);
    TextArea msg = new TextArea(8,75);
top.add(conv);
bottom.add(msg);
    // Add the component to the frame's content pane;
    // by default, the content pane has a border layout
    cframe.getContentPane().add(top, BorderLayout.NORTH);
    cframe.getContentPane().add(bottom, BorderLayout.CENTER);
    // Show the frame
    cframe.setSize(600, 500);
    cframe.setVisible(true);
    stop ();
StartConv
public abstract class StartConv extends JFrame implements Runnable {
public static void run (String userip){
try{
connect(userip);
}catch(Exception e){
System.out.println("Error in StartConv:"+e);
showframe();
public static void showframe(){
String title = "Frame Title";
    JFrame frame = new JFrame(title);
    // Create a component to add to the frame
    JPanel top=new JPanel();
    JPanel bottom=new JPanel();
    TextArea conv = new TextArea(10,75);
    TextArea msg = new TextArea(8,75);
top.add(conv);
bottom.add(msg);
    // Add the component to the frame's content pane;
    // by default, the content pane has a border layout
    frame.getContentPane().add(top, BorderLayout.NORTH);
    frame.getContentPane().add(bottom, BorderLayout.CENTER);
    // Show the frame
    frame.setSize(600, 500);
    frame.setVisible(true);
  protected DataInputStream dataIn;
  protected DataOutputStream dataOut;
  protected Thread listener;
public static void connect (String userip) throws IOException {
      String host=userip;
      int port=4444;
      Socket socket = new Socket (host, port);
      try {
         DataInputStream dataIn = new DataInputStream
          (new BufferedInputStream (socket.getInputStream ()));
         DataOutputStream dataOut = new DataOutputStream
          (new BufferedOutputStream (socket.getOutputStream ()));
      } catch (IOException ex) {
        socket.close ();
        throw ex;
      Thread listener = new Thread ();
      listener.start ();
  }

It says at the top :) think i posted too much code but that way everyone knows exactly what is happening. Cant get the StartConv class to commmunicate with the ChatHandler basically

Similar Messages

  • My daughter has just bought me an iPad 2 from Dubai and set it all up for me but unfortunately the iMessage function doesn't seem to work. We keep getting messages,when trying to activate it, that there is a network connection problem - help!

    My daughter has just bought me an iPad 2 from Dubai and set it all up for me but unfortunately the iMessage function doesn't seem to work. We keep getting messages,when trying to activate it, that there is a network connection problem - help!

    Thank you both for your responses but my daughter was reassured by the salesman in the iStyle store (official Apple store in the UAE) that iMessages would work but conceded that FaceTime wouldn't. My iTunes account is registered in the uk and my daughter's iPhone has iMessages even though she bought it (and uses it) in Dubai. Can anyone else throw any light on this?

  • I couldn't log into my apple account on my iPad, then i couldn't unlock it resulting in it being disabled, however it's the same as my iPhones password, I then called apple, i was hung up on twice and they said it will cost £70 to fix THEIR problem, help?

    I couldn't log into my apple account on my iPad, then i couldn't unlock it resulting in it being disabled, however it's the same as my iPhones password, I then called apple, i was hung up on twice and they said it will cost £70 to fix THEIR problem, help?

    If you cannot remember the passcode, you will need to restore your device using the computer with which you last synced it. This allows you to reset your passcode and resync the data from the device (or restore from a backup).
    If you restore on a different computer that was never synced with the device, you will be able to unlock the device for use and remove the passcode, but your data will not be present.
    You may have to force iPad/iPod into Recovery Mode
    http://support.apple.com/kb/ht4097

  • IPad syncing problem - HELP!

    iPad sync problem - HELP!  I keep getting this message "...cannot be synced because there is not enough free space to hold all of the items in the iTunes library (additional ...space needed)"  and yet I seem to have plenty of space on the iPad.  This just started today.  I even tried deleting some things to make even more room, but it didn't help.  Any ideas??? 
    I was thinking of restoring, but I've never done it...  should I? 
    thank you!

    Hello florafromnv,
    Welcome to Apple Support Communities.
    The following article addresses how to resolve the issues related to this message:
    iOS: "Not enough free space" alert when trying to sync
    http://support.apple.com/kb/TS1503
    Regards,
    Jeff D.

  • MOVED: KT333 Ultra; fuzzy logic, 1.6xp overclocking problem help !!!!!

    This topic has been moved to Overclockers & Modding Corner.
    KT333 Ultra; fuzzy logic, 1.6xp overclocking problem help !!!!!

    Not that I am an expert o/c but here are some thoughts on the matter.
    My comments are based on my experiences of the KT3 Ultra2 which is basically the same as the Ultra version.
    This mobo does not have the ability to lock the PCI/AGP bus freely from the FSB. However, it does have dividers. At 133 a 1/4 divider kicks in. Above 152FSB the 1/5 divider works, so that at 166 the PCI & AGP buses will be back in sync. If you are o/c your cpu, don't go from 133 to 145, etc since you will be running the PCI/AGP buses further out of whack. Just go to either the mid 150's or to 166 in one jump. The other problem / issue relates to your cpu. From what you say you have one of the old Palominos which are not great o/c's. I would personally o/c your cpu from the BIOS rather than 'Fluffy Logic' which I would tend to stay away from. 
    With a 166FSB cpu a very stable o/c would be 175-177 beyond 180 gets decidedly tricky.
    Hope this helps

  • Itunes keeps closing as soon as i open it and states 'windows has detected a problem' HELP!!!!

    Help!! Itunes keeps closing straight away and message states 'windows has detected a problem' HELP ASAP PLEASE!!!!

    For general advice see Troubleshooting issues with iTunes for Windows updates.
    The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
    Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
    If you've already tried a complete uninstall and reinstall try opening iTunes in safe mode (hold down CTRL+SHIFT as you start iTunes) then going to Edit > Preferences > Store and turning off Show iTunes in the Cloud purchases. You may find iTunes will now start normally.
    tt2

  • I have installed photoshop elements 12. when I try use the editing features it said that i must login to Adobe to register the product. but each time i try to it said there is a problem. help the problem stated that the internet is not connected, but that

    i have installed photoshop elements 12.
    when I try use the editing features it said that i must login to Adobe to register the product.
    but each time i try to it said there is a problem.
    help
    the problem stated that the internet is not connected, but that is not the case.

    I had the same issue and I'm running Windows 7.  Tried working with technical support for several hours but they were no help.  They just had me doing the same things over and over, offering no real answers.  I finally got fed up and have decided to return my product for a full refund.

  • I can't install the itunes to my windows 7 X86 APPCRASH problem, help me guys

    i can't install the itunes to my windows 7 X86 APPCRASH problem, help me guys??  i don't know what to do..

    Why are you unable to install the iPod Updater? Are you getting an error message? Please be specific.
    Cheers!
    -Bryan

  • Camera (focus) problem - help?

    Duplicate post, please see: Camera (focus) problem - help?
    Message was edited by: Admin Moderator

    Warranty is valid only in country of original purchase. You have to return
    the iPhone to the US for evaluation. Either you return it personally or send
    it to a friend/relative/co-worker in the US to take into Apple. Apple will not
    accept international shipments for evaluation nor will Apple ship out of the
    country after repair/replacement.
    Have you tried the standard trouble shooting steps: restart, restore, restore
    as new iPhone?

  • After update iPhone4 to iOS6, its stuck, showing only USB to iTunes on the screen. What to do, how to solve problem, help

    after update iPhone4 to iOS6, its stuck, showing only USB to iTunes on the screen. What to do, how to solve problem, help 

    Connect your phone to iTunes on your computer like the diagram has indicated and restore the phone

  • Serversock/socket problem pls Help

    Hi all,
    I have a serversocket that accepts client's connections, reads from this stream, processes the data and sends back response to the client. This works fine for a standard scenario.
    The problem occurs if for some reason the client looses connection after writing to the serversocket. The server behaves as if nothing happens and sends back the response. I want the server to be able to detection any connection loss and report back. My code snippet is shown below
    ServerSocket server;
    Socket conn;
    BufferedReader input;
    PrintWriter out;
    try{
    server= new ServerSocket(4550,10);
    conn=server.accept();
    input = new BufferedReader(new InputStreamReader(conn.getInputStream()));
    String data=input.readLine();
    process data .....
    out = new PrintWriter(conn.getOutputStream(), true);     
    out.println(processed_data);
    }catch(IOException e){
    e.printStackTrace();
    }finally{
    try{
    input.close();
    out.close();
         conn.close();
         }catch(Exception uncaught){}
    If during process data, the client looses connection, the program behaves as if the connection still exist. Any suggesion would be highly appreciated
    Regards
    Tim

    err, yeah, i got that bit....
    and there is nothing, nothing at all in java, C, C++, any and i mean ANY TCP/IP programming that can tell if the client has been unplugged without trying to send something to it
    you can use a keepAlive in Socket to automatically occasionally send a dummy packet (for which it expects a response)
    but apart from that the Socket cannot know it is not connected unless it recieves indication from the client (the end that is closed first sends a FIN packet and the other end replies with ACK FIN)
    a pair of Sockets connectd through a network does not get a permanent physical connection, they give the impression of such by exchanging packets with sequence numbers and ack numbers coresponding to the last packet recived.
    if neither Socket has nothing to send, nothing is sent and it is assumed that the connection is still valid, so isConnected() will return true unless it actually knows that the client has closed the connection or an Exception occured when it tried to send something
    isConnected() does not test the connection, just reports true if it has been connected and there has not been an IOException or either end has closed
    maybe you could explain why you need to avoid sending the response if the client has been unplugged?

  • Please help, URGENT, socket problem

    my program got a server socket for listening for connection
    Socket socket = serverSocket.accept()
    after the remote client has close the connection,
    the socket on my server program cannot detect the connection closed.
    When i call socket.isClosed or isConnected, they return false and true respectively,
    also there is no IOException being thrown when I use available() ,
    what are the possible methods to detect a connection closed by the remote side?
    thanks

    I'm not sure why ejp has not yelled at the both of you yet... hope he's okay.
    Anyway.. as you've discovered none of those methods are of any use in discovering if the client closed the connection (or it was otherwise aborted/interrupted).
    Generally speaking in a protocol there is an agreed upon time/situations where you disconnect. Otherwise the way to detect the socket has been closed is when you catch the exception when you attempt to read from or write to the socket.
    So yslee4 if you want to see if a client is still alive you could build some sort of echo message into your proctocol. And I have no idea what the other poster is on about.

  • APP Server Problem - HELP!!!!

    I've read all the previous postings and can't resolve this after a week of re-installs, deleting files, PATH, Environment Variable changes, etc. Can someone please provide definitive advice on this? I'm installing on XP for now. Server Log File is as follows:
    Thanks,
    Jeremy
    [#|2007-03-18T11:31:37.703-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2007-03-18T11:31:37.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Sun/java\bin\java
    -client
    -XX:PermSize=32m
    -XX:MaxPermSize=128m
    -XX:+CMSPermGenSweepingEnabled
    -XX:+CMSClassUnloadingEnabled
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
    -Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
    -Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=creator
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/SunAppServer8/domains/creator
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=creator
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/SunAppServer8/config
    -Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/SunAppServer8/lib\commons-launcher_fr.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ja.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ko.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh_CN.jar;C:/Sun/SunAppServer8/lib\commons-logging.jar;C:/Sun/SunAppServer8/lib\deployhelp_es.jar;C:/Sun/SunAppServer8/lib\deployhelp_fr.jar;C:/Sun/SunAppServer8/lib\deployhelp_ja.jar;C:/Sun/SunAppServer8/lib\deployhelp_ko.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh_CN.jar;C:/Sun/SunAppServer8/lib\dom.jar;C:/Sun/SunAppServer8/lib\driveradapter.jar;C:/Sun/SunAppServer8/lib\j2ee-svc.jar;C:/Sun/SunAppServer8/lib\j2ee.jar;C:/Sun/SunAppServer8/lib\j2ee_es.jar;C:/Sun/SunAppServer8/lib\j2ee_fr.jar;C:/Sun/SunAppServer8/lib\j2ee_ja.jar;C:/Sun/SunAppServer8/lib\j2ee_ko.jar;C:/Sun/SunAppServer8/lib\j2ee_zh.jar;C:/Sun/SunAppServer8/lib\j2ee_zh_CN.jar;C:/Sun/SunAppServer8/lib\jax-qname.jar;C:/Sun/SunAppServer8/lib\jaxr-api.jar;C:/Sun/SunAppServer8/lib\jaxr-impl.jar;C:/Sun/SunAppServer8/lib\jaxrpc-api.jar;C:/Sun/SunAppServer8/lib\jaxrpc-impl.jar;C:/Sun/SunAppServer8/lib\jdic_0_9.jar;C:/Sun/SunAppServer8/lib\jmxremote.jar;C:/Sun/SunAppServer8/lib\jmxremote_optional.jar;C:/Sun/SunAppServer8/lib\jsf-api.jar;C:/Sun/SunAppServer8/lib\jsf-impl.jar;C:/Sun/SunAppServer8/lib\mail.jar;C:/Sun/SunAppServer8/lib\PEtray.jar;C:/Sun/SunAppServer8/lib\relaxngDatatype.jar;C:/Sun/SunAppServer8/lib\rmissl.jar;C:/Sun/SunAppServer8/lib\saaj-api.jar;C:/Sun/SunAppServer8/lib\saaj-impl.jar;C:/Sun/SunAppServer8/lib\smbase.jar;C:/Sun/SunAppServer8/lib\smdb2.jar;C:/Sun/SunAppServer8/lib\sminformix.jar;C:/Sun/SunAppServer8/lib\smoracle.jar;C:/Sun/SunAppServer8/lib\smresource.jar;C:/Sun/SunAppServer8/lib\smspy.jar;C:/Sun/SunAppServer8/lib\smsqlserver.jar;C:/Sun/SunAppServer8/lib\smsybase.jar;C:/Sun/SunAppServer8/lib\smutil.jar;C:/Sun/SunAppServer8/lib\xalan.jar;C:/Sun/SunAppServer8/lib\xercesImpl.jar;C:/Sun/SunAppServer8/lib\xsdlib.jar;C:/Sun/SunAppServer8/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/SunAppServer8/imq/lib/jaxm-api.jar;C:/Sun/SunAppServer8/imq/lib/fscontext.jar;C:/Sun/SunAppServer8/lib/ant/lib/ant.jar
    com.sun.rave.tray.RavePEMain
    start
    display
    native|#]
    [#|2007-03-18T11:31:46.921-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\SunAppServer8\imq\bin].|#]
    [#|2007-03-18T11:31:46.937-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2007-03-18T11:31:47.531-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
    [#|2007-03-18T11:31:47.546-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2007-03-18T11:31:47.812-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
    [#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
    [#|2007-03-18T11:31:48.984-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/24700"|#]
    [#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22060"|#]
    [#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22061"|#]
    [#|2007-03-18T11:31:50.015-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [24700]|#]
    [#|2007-03-18T11:31:53.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2007-03-18T11:31:53.515-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear for autodeployment.|#]
    [#|2007-03-18T11:31:55.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
    [#|2007-03-18T11:31:55.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2007-03-18T11:31:55.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
    [#|2007-03-18T11:31:56.000-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1688 msec, Total EJB Compiler Module Time: 63 msec, Portion spent EJB Compiling: 3%
    Breakdown of EJBC Module Time: Total Time for EJBC: 63 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 47 msec (74%),
    |#]
    [#|2007-03-18T11:31:56.093-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
    [#|2007-03-18T11:31:56.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
    [#|2007-03-18T11:31:56.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:31:56.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
    [#|2007-03-18T11:31:56.437-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 76954462832623616|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear.|#]
    [#|2007-03-18T11:31:56.578-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
    [#|2007-03-18T11:31:56.875-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
    [#|2007-03-18T11:31:59.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2007-03-18T11:31:59.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 3468 msec, Total EJB Compiler Module Time: 3031 msec, Portion spent EJB Compiling: 87%
    Breakdown of EJBC Module Time: Total Time for EJBC: 3031 msec, CMP Generation: 594 msec (19%), Java Compilation: 2359 msec (77%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 16 msec (0%),
    |#]
    [#|2007-03-18T11:32:00.109-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
    [#|2007-03-18T11:32:00.156-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.187-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:32:00.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.343-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 76954463102959616|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear.|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
    [#|2007-03-18T11:32:00.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
    [#|2007-03-18T11:32:00.796-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2007-03-18T11:32:00.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
    [#|2007-03-18T11:32:00.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
    [#|2007-03-18T11:32:00.921-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2007-03-18T11:32:00.953-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
    [#|2007-03-18T11:32:01.062-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
    [#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:32:02.671-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@1a428d5 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]|#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
         at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
    Caused by: java.io.IOException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
         at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:177)
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
         ... 4 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
         at javax.naming.InitialContext.bind(InitialContext.java:359)
         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
         ... 6 more
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
         ... 10 more
    Caused by: java.net.SocketTimeoutException: Read timed out
         at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:123)
         at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:81)
         at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:73)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
         at java.io.DataInputStream.readByte(DataInputStream.java:241)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
         ... 14 more
    |#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
    [#|2007-03-18T11:33:02.968-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
         at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
    |#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:33:03.125-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2007/03/18 11:33:03]|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 :  Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
    [#|2007-03-18T11:33:03.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
    [#|2007-03-18T11:33:03.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
    [#|2007-03-18T11:33:03.890-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
    [#|2007-03-18T11:38:11.046-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2007-03-18T11:38:11.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Sun/java\bin\java
    -client
    -XX:PermSize=32m
    -XX:MaxPermSize=128m
    -XX:+CMSPermGenSweepingEnabled
    -XX:+CMSClassUnloadingEnabled
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
    -Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
    -Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=creator
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/SunAppServer8/domains/creator
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=creator
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/SunAppServer8/config
    -Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/Sun

    Hi,
    Seems you are having socket time out exception. I use to get the same while deploying on XP with (640MB RAM) but able to re-run after freeing some memory. Creator needs optimally atleast 1GB RAM. You have not mentioned your machine RAM...
    It might just help..
    dr.am mohan rao

  • Sockets problem

    Hi ,
    I written a server class that simply writes the numbers and the client simply reads those numbers and prints them. When I run the both client and server on tha same machine there is no data loss found. But when I run the server on different machine than client I found heavy dataloss.(while theserver written numbers from 1-9000 the client is able read only 6000 plus). The data loss is increased when the data read from the server socket created by the VB application. Here with i am pasting the code snippet for the Server and the Client java files . Please help me in solving this problem.
    Client.java
    import java.net.*;
    import java.io.*;
    public class Client
         static Socket client = null;
         ObjectInputStream is = null;
         public Client() throws Exception
              client = new Socket("rajsekhar",3333);
              is = new ObjectInputStream (client.getInputStream());
              while(true){
                   Integer in = (Integer)is.readObject();
                   System.out.println(in.toString());
         public static void main(String[] args) throws Exception
              new Client();
    Server.java
    import java.net.*;
    import java.io.*;
    public class Server
         public static void main(String[] args) throws Exception
              ServerSocket server = null;
              server = new ServerSocket(3333);
              Socket s = server.accept();
              ObjectOutputStream os = new ObjectOutputStream(s.getOutputStream());
              int i =1;
              while(true)
                   os.writeObject(new Integer(i));
                   System.out.println(i);
                   i++;
    please help me .
    thanks in advance,
    Sridhar Reddy .R

    This has nothing to do with JSSE; please post in a more appropriate forum.

Maybe you are looking for