MSExchangerepl is killing my server

Good day
I have 4 Exchange Server
2 HUB-CAS (WNLB)
2 Mailbox Server (DAG) (MBX1 -MBX2)
All are running Exchange 2010 SP2
Everything was ok , but yesterday for unknown reason MSExchangeRepl consume all the CPU resources 100%, even I can not access the server using the console.. clicking on anything will take 5 minuts to respone.
Event Log show a lot of failure regarding for MSExchanerepl as it can not the health check for DB failed.
Other Services also failed as there is no more resource on the server.
once I stop MSExchangeRepl... the server respone again quick and other service are working fine
I set Replication Log level to highest but not helping.. no good information.
When i restart the server, the service work for about 2 minuts and then freeze the entire server.
I can not find anything about how to deeply debug this service and whats going on.
can anyone help

On the Copy Status.  I have some DB Copy Status for some DB seem to be health (I am sure its not), I can not switch as the replication service is down and if I try to bring it up it will fail as the server will not respone back
Other Database are "Failed And Suspended"
My Servers in the same network
Event Log Show error like:
Database redundancy health check failed.
Database copy: DB3 IT Dep
Redundancy count: 1
Error: Passive copy 'DB3 IT Dep\MBX01' is not in a good state. Status: ServiceDown.
Name                 Status RealCopyQueu InspectorQue  ReplayQueue      CIState
                                       e          
ue                          
DB3 IT Dep\AU       Mounted            0            0           
0      Healthy
D-MAIL-MBX02                                                                 
DB3 IT Dep\AU   ServiceDown            0            0            0     
Unknown
D-MAIL-MBX01
===============
 Full Status
===============
Identity                         : DB3 IT Dep\MBX02
Name                             : DB3 IT Dep\MBX02
DatabaseName                     : DB3 IT Dep
Status                           : Mounted
MailboxServer                    : MBX02
ActiveDatabaseCopy               : mbx02
ActivationSuspended              : False
ActionInitiator                  : Service
ErrorMessage                     :
ErrorEventId                     :
ExtendedErrorInfo                :
SuspendComment                   :
SinglePageRestore                : 0
ContentIndexState                : Healthy
ContentIndexErrorMessage         :
CopyQueueLength                  : 0
ReplayQueueLength                : 0
LatestAvailableLogTime           :
LastCopyNotificationedLogTime    :
LastCopiedLogTime                :
LastInspectedLogTime             :
LastReplayedLogTime              :
LastLogGenerated                 : 0
LastLogCopyNotified              : 0
LastLogCopied                    : 0
LastLogInspected                 : 0
LastLogReplayed                  : 0
LogsReplayedSinceInstanceStart   : 0
LogsCopiedSinceInstanceStart     : 0
LatestFullBackupTime             : 12/7/2014 4:02:56 PM
LatestIncrementalBackupTime      :
LatestDifferentialBackupTime     :
LatestCopyBackupTime             : 12/5/2014 5:00:27 PM
SnapshotBackup                   : True
SnapshotLatestFullBackup         : True
SnapshotLatestIncrementalBackup  :
SnapshotLatestDifferentialBackup :
SnapshotLatestCopyBackup         : True
LogReplayQueueIncreasing         : False
LogCopyQueueIncreasing           : False
OutstandingDumpsterRequests      : {}
OutgoingConnections              :
IncomingLogCopyingNetwork        :
SeedingNetwork                   :
ActiveCopy                       : True
Identity                         : DB3 IT Dep\MBX01
Name                             : DB3 IT Dep\MBX01
DatabaseName                     : DB3 IT Dep
Status                           : ServiceDown
MailboxServer                    : MBX01
ActiveDatabaseCopy               :
ActivationSuspended              : False
ActionInitiator                  : Unknown
ErrorMessage                     : A server-side administrative operation has f
                                   ailed. The Microsoft Exchange Replication se
                                   rvice may not be running on server
                                   MBX01.Domain.local. Specific RPC error messa
                                   ge: Error 0x6d9 (There are no more endpoints
                                    available from the endpoint mapper) from cl
                                   i_GetCopyStatusEx2
And Another Error when Replication Service Start
The log copier was unable to communicate with server 'MBX02'. The copy of database 'Database\MBX01' is in a disconnected state. The communication error was: A timeout occurred while communicating with server 'MBX02. Error: The network read operation didn't
complete within 15 seconds. The copier will automatically retry after a short delay.

Similar Messages

  • X connection to :0.0 host broken (explicit kill or server shutdown)

    Hello All,
    I strongly believed in using JAVA Swing GUI, for huge data visualization.
    Now I encounter a problem:
    I start up my application, and things work very well and looks pretty fast.
    I try and create a JPanel with is almost 11.3MPixels (just length), and I don't have any problem. However, if I try and create a JPanel 15.4MPixels (just length), my application crashes and I receive a weird error - "X connection to :0.0 host broken (explicit kill or server shutdown)". This happens only on Linux (I am using Debian). I bumped Xmx till 1024m (My system has more than that).
    If I run same application in Windows, I do not have this error at all, everything displays fine. I am using -Xmx200m.
    This is not a Memory issue. I am assuming something is wrong with Java-on-Linux or I am unaware of what is happening.
    Can anyone of you enlighten, and help me solve this issue?
    Thanks in advance,
    Jazz

    Hello All,
    I strongly believed in using JAVA Swing GUI, for huge data visualization.
    Now I encounter a problem:
    I start up my application, and things work very well and looks pretty fast.
    I try and create a JPanel with is almost 11.3MPixels (just length), and I don't have any problem. However, if I try and create a JPanel 15.4MPixels (just length), my application crashes and I receive a weird error - "X connection to :0.0 host broken (explicit kill or server shutdown)". This happens only on Linux (I am using Debian). I bumped Xmx till 1024m (My system has more than that).
    If I run same application in Windows, I do not have this error at all, everything displays fine. I am using -Xmx200m.
    This is not a Memory issue. I am assuming something is wrong with Java-on-Linux or I am unaware of what is happening.
    Can anyone of you enlighten, and help me solve this issue?
    Thanks in advance,
    Jazz

  • Setting up key combination trapping to kill X server?

    How can I trap a key combination (ctrl+alt+backspace) in order to kill the X-server with these?

    Actually, I may have marked this as answered too quickly...
    So I followed the guide at the back of the getting started manual, and set everything up as follows:
    - PCI ethernet card is set up as the connection to the outside world. It is plugged into a switch which connects to a wall jack. In Network under System Preferences, it is set up as the first internet conection to try. It has a static IP address, and is set up to use the organization's DNS servers. It is NOT plugged into the upstream port, but is instead in port #9. The light on the router is on.
    - Built-in wireless is set up to be the internal connection. It is plugged into the upstream slot on anouther switch. It has a static IP address, and is set up to use the organization's DNS servers. The light on the router is on, so it appears there is a connection.
    - A different computer is plugged into the second switch, which a static IP address and to use the organization's DNS servers.
    So basically, unlike in the scenario in the manual, I am not using the OS X Server for DNS, DHCP or NAT services. That should, if anything, simplify it.
    The firewall service is started, and is set to allow all traffic in and out, no problems. Nice and simple to start.
    The server has an okay connection to the outside world via the PCI ethernet card. I can ping other machines and load web pages. I cannot, however, access the machine connected to the router which is connected to the built-in ethernet. Likewise, that machine has no access to either the OS X Server or the outsideworld.
    How does OS X Server decide which ethernet card is to be connected to the outside world, and which is for the internal firewall? Is the confusion possible because I'm connected to two routers?

  • Kill rmi server, but Naming.list still works

    Hi,
    i have built an rmi server program, which creates some remote objects and a program which lists them. However, the program still lists the objects after the server has shudown. Only as soon as i kill the rmiregistry, the listing stops. Why?
    import java.rmi.*;
    import java.rmi.server.*;
       This server program instantiates two remote objects,
       registers them with the naming service, and waits for
       clients to invoke methods on the remote objects.
    public class ProductServer2
       public static void main(String args[])
          try
             System.out.println
                ("Constructing server implementations...");
             ProductImpl p1
                = new ProductImpl("Blackwell Toaster");
             ProductImpl p2
                = new ProductImpl("ZapXpress Microwave Oven");
             System.out.println
                ("Binding server implementations to registry...");
             Naming.rebind("toaster2", p1);
             Naming.rebind("microwave2", p2);
             System.out.println
                ("Waiting for invocations from clients...");
          catch(Exception e)
             e.printStackTrace();
    }The following program lists the remote objects:
    import java.rmi.*;
    import java.rmi.server.*;
    public class ShowBindings
         public static void main(String[] args)
              try
                   String[] bindings= Naming.list("");
                   for (int i=0; i<bindings.length; i++)
                        System.out.println(bindings);               
              catch(Exception e)
                   e.printStackTrace();

    The RMI Registry holds references to remote objects. Your "list" goes against the Registry, not the remote objects.
    The Registry doesn't care what remote objects are alive or dead. That's not it's purpose.
    Use unbind() to remove references in the Registry before ending your server.

  • Logout Hook to kill Window Server

    Hi there,
    I have a problem with my users hanging at logout, the computer just freezes still displaying the desktop picture and doesn't make it to the login window.
    I've tried to track down the cause to no avail. I can still ssh into the machine that's frozen and force a reboot remotely, kill the Window Server or do a hard reset.
    None of these are ideal so I'd thought perhaps a logout script to kill the Window Server!?
    Trouble is I don't seem to be having much luck trying to implement it. I can find lots of stuff about logout hooks in Tiger but not much in Leopard. I know you're supposed to be able to set them through Workgroup Manager but despite making my scripts executable, I can't get workgroup manager to see them as selectable when I try to add one.
    I'm also confused about setting the appropriate login window preferences in ~root/Library/Preferences/com.apple.loginwindow.plist
    Can anybody point me in the right direction?
    Thanks in advance!

    I looked through the report compiled and I found that APE (Application Enhancer) was still being called even though it doesn't exist along with OSS3D which wasn't working either. I got rid of both of those using their provided installers and it appears to work. WindowServer didn't crash which usually triggers the abnorminally high cpu usage.

  • BlazeDS with WAS 6.1 streaming channel killing the server?

    Hi,
    We are experiencing a strange issue with WAS (websphere server) 6.1 with BlazeDS
    after a while severe performance degrades and then system hungs shortly after
    Some prelimenary observations:
    we are seeing following errors in Server Log:
    [6/22/10 16:41:26:828 EDT] 000000b0 ThreadMonitor W   WSVR0605W: Thread "WebContainer : 3-in-streaming-mode" (0000002a) has been active for 656127 milliseconds and may be hung.  There is/are 1 thread(s) in total in the server that may be hung.
    [6/22/10 16:48:00:144 EDT] 000000b1 ThreadMonitor W   WSVR0605W: Thread "WebContainer : 0" (00000027) has been active for 753457 milliseconds and may be hung.  There is/are 2 thread(s) in total in the server that may be hung.
    We do see that there is always one active connection maintained betweeb browser and server(which is connected to ):
    messagebroker/streamingamf
    and  that keeps sending keep-alive signals , now is this a reason we are getting hung messages? can we safely ingore it?
    basically can streaming chanell cause that error? and what would be suggestions tweaks/modifications to fix that issue?
    our destination config :
    <destination id="alerts-Push-jms" >
            <properties>
                <jms>
                    <destination-type>Topic</destination-type>
                    <message-type>javax.jms.TextMessage</message-type>
                    <connection-factory>jms/***JMSTopicConnectionFactory</connection-factory>
                    <destination-jndi-name>jms/AlertEventingTopic</destination-jndi-name>
                    <delivery-mode>PERSISTENT</delivery-mode>
                    <message-priority>DEFAULT_PRIORITY</message-priority>
                    <preserve-jms-headers>"true"</preserve-jms-headers>
                    <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
                    <max-producers>1</max-producers>
                </jms>
            </properties>
            <adapter ref="jms" />
        <channels>
            <channel ref="my-streaming-amf" />
        </channels>
        </destination>

    Actually we did not fix it from WAS perspective, but what we did is ditched a blazeds streaming channel in favor of polling channel,
    that solved the issue.
    it appears that WAS has issues with connections that are Held open for a long time.

  • Dreamweaver with network homes kills the server

    1. Dreamweaver is very slow to open on both our laptops and
    desktops. The start page menu pops up, but the color-wheel cursor
    continues to spin for between one and two minutes before the user
    is able to start working in Dreamweaver. If one disables the start
    screen, it doesn't happen, but it definitely feels like a bug.
    2. Dreamweaver also keeps slowing down our entire server.
    We've discovered that Dreamweaver is writing temp files to the
    server under ... Library/Application Support/Adobe/Dreamweaver
    9/Configuration/temp. This happens when multiple
    users have Dreamweaver open, and slows down logins and such
    for everyone, even users who do not have Dreamweaver open.
    I tried redirecting the temp folder locally, but it did not
    improve performance.

    "jdobbie" <[email protected]> wrote in
    message
    news:fe18sk$ge7$[email protected]..
    > 1. Dreamweaver is very slow to open on both our laptops
    and desktops. The
    > start page menu pops up, but the color-wheel cursor
    continues to spin for
    > between one and two minutes before the user is able to
    start working in
    > Dreamweaver. If one disables the start screen, it
    doesn't happen, but it
    > definitely feels like a bug.
    >
    > 2. Dreamweaver also keeps slowing down our entire
    server. We've
    > discovered
    > that Dreamweaver is writing temp files to the server
    under ...
    > Library/Application Support/Adobe/Dreamweaver
    9/Configuration/temp. This
    > happens when multiple
    > users have Dreamweaver open, and slows down logins and
    such for everyone,
    > even
    > users who do not have Dreamweaver open.
    >
    > I tried redirecting the temp folder locally, but it did
    not improve
    > performance.
    Hi jdobbie,
    I'm just starting to use dreamweaver on the mac, however your
    analysis
    puzzles me.
    Temp files shouldn't have much negative effect on logins, why
    do you think
    this is causing the slowdowns?
    Are your users logging on to the server via Remote Desktop or
    VNC or have
    you redirected a local folder to a network location?
    One thing that may impact network performance is dreamweaver
    refreshing the
    remote site, or the local site when it's root is on the
    network.
    Joris

  • Can't get back to GDM after killing X server with ALT CTRL BACKSPACE

    the killing is working but i get into a black screen with a couple of lines, and can't do nothing there... (i don't have a command line there)
    (it is the screen i get before gnome is talking control after my computer starts.)
    the problem started(i think) with gnome 3.16.
    in gnome 3.14 it worked great, and after killing X, i get into gdm again automatically.
    Last edited by andav (2015-04-17 11:44:51)

    bulletmark wrote:
    andav wrote:p.s.
    now there is something strange before gnome is started.
    after i login in gdm, i get a black screen with 2 diagonal lines, made from litlle squares, with some colors, and after this gone(2 seconds or so), gnome takes control.
    Since 3.16 gdm uses Wayland to present the login screen (e.g. http://www.phoronix.com/scan.php?page=n … E-Mid-Feb) so that graphical glitch occurs over the transition from Wayland to X. If you don't like it then (I guess) you can force gdm to use X. See https://fedoraproject.org/wiki/Document … ts/Desktop. I don't see any glitch on my intel graphics box.
    great.
    thank you very much! :-)

  • How kill the server cache of tomcat

    I' ve this horrible problem with the cache of tomcat and any time I have to clean the temporary folders and closing the browser.
    Is there an option to eliminate server cache??
    Please help

    could you describe your problem a little bit closer? i also use tomcat and never had problems with caching so i wonder what the problem could be (and maybe find a way to solve it..)

  • X connection to machine.here.sy:14.0 broken (explicit kill or server shutdo

    As a user, not as root, on linux 64, AMD64/EM64T, trying to
    ./jdk-1_5_0_06-nb-5_0-linux.bin*
    I get the error about X connection.
    I'm not using an X connection - is that needed?
    Any other gotchas on a simple install?
    Thanks,
    J

    in this case how i can run xwindow like OUI?

  • How to kill a SQL Server DB?

    How can I completely kill, or delete a SQL Server DB?  I can't seem to detach it or take it offline.  I can't do anything with it at all.  I basically ran out of disk space while loading a table, and not it seems to be corrupted.  How
    can I completely kill the DB, so I can start over.  Every time I try to do something, it says, 'database is currently in use'.
    Thanks.
    Knowledge is the only thing that I can give you, and still retain, and we are both better off for it.

    Rguy first your question was too confusing and then please
    dont mark every post as answer. You never kill SQL Server DB you drop it. Let the answer be one which is crisp and clear and really answers your question you can vote comments as helpful. A new user reading the thread would get confused as to what actually
    is answer
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Failing EJBs without killing server?

              Hi All,
              Is there anyway to fail an EJB to cause failover without actually killing the WLS its deployed on?
              I tried undeploying an EJB using the console but that didn't work.
              I wish to verify EJB failover without the server going down.
              Thanks in advance,
              Andrew Quinan
              

    Killing the server is one way to cause the RemoteException.
              EJB automatic failover can only happen in idempotent stateless session bean
              or read only entity bean. For other ejbs, you have to write special code in
              the CLIENT side to implement the failover.
              You can write special ejb method that can generate the RemoteException, in
              your client side code, you can catch such exception and replace the remote
              interface and make call again.
              Hope this can help.
              Andrew Quinan <[email protected]> wrote in message
              news:3a54f5b6$[email protected]..
              >
              > Hi All,
              >
              > Is there anyway to fail an EJB to cause failover without actually killing
              the WLS its deployed on?
              >
              > I tried undeploying an EJB using the console but that didn't work.
              >
              > I wish to verify EJB failover without the server going down.
              >
              > Thanks in advance,
              > Andrew Quinan
              

  • Session lost after fail over. (I kill down the server during servlet invocation)

              I just tested the failover ability of our WebLogic
              cluster. We have two instances, first, I logged onto
              the web site and created a session, and then I called
              a servlet, in which there is a complicated computation
              which will take about 5 seconds, during the
              invocation, I issued the kill -9 to shut the server
              down at once. It did failover, but the http session
              was lost,So I got the session timeout page. But if I
              kill down that server after the invocation, then it
              can failover succesfully without loss of session.
              Could you tell me is there any difference between
              killing down server during and between invocations of
              servlet or JSP?
              The configuration:
              WLS5.1 with sp8. Solaris 5.8
              Using in memory replication.
              Thank you very much for your help.
              

              I just tested the failover ability of our WebLogic
              cluster. We have two instances, first, I logged onto
              the web site and created a session, and then I called
              a servlet, in which there is a complicated computation
              which will take about 5 seconds, during the
              invocation, I issued the kill -9 to shut the server
              down at once. It did failover, but the http session
              was lost,So I got the session timeout page. But if I
              kill down that server after the invocation, then it
              can failover succesfully without loss of session.
              Could you tell me is there any difference between
              killing down server during and between invocations of
              servlet or JSP?
              The configuration:
              WLS5.1 with sp8. Solaris 5.8
              Using in memory replication.
              Thank you very much for your help.
              

  • Problem with application server shutdown when connecting

    Hi Friends,
    I am new to J2EE applications.
    I developed a web application that uses jxl and mysql for reading excel sheets. The host I am working on is supposed to be the server. The application I am running is working absolutely fine, by creating a directory and saving the excel file in my webapps folder and inserting the data to the database. But the minute I send the file from client system, there is a sudden shutdown in my server.
    I am sending the jsp and java code related to this application and related log file..
    I guess the main problem is with sending the exact path from the remote client, rest all is fine including excel and database interactions.
    I commented the database interaction class just for now as I don't think there is a problem with it.
    I am using Tomcat 4.1, MySQL 3.23
    ====================================================
    JSP FILE
    =====================================================
    <%@ page language="java" import="pdss.*"%>
    <html>
    <head><title>File Upload</title></head>
    <body>
    <%     String action=request.getParameter("go");
    String message=request.getParameter("msg");
    String str="";
    if(message!=null)
         str="Please enter valid filename!";
    ExcelInteraction xlInt=new ExcelInteraction();
    if(action==null)
    %>
    <center><font color="red"><%=str%></font></center>
    <form name="myform" method="post">
    <input type="file" name="filename"></input>
    <input type="submit" name="go" value="Send">
    </form>
    <%
    else if("send".equalsIgnoreCase(action))
         String filename=request.getParameter("filename");
         int ex=0;
         System.out.println("************"+filename.endsWith(".xls"));
         if(filename!=null && (filename.endsWith(".xls")))
              ex=xlInt.fileTransfer(filename, getServletContext());
         else if(filename==null || ("".equals(filename)) || filename.endsWith(".xls")==false)
              response.sendRedirect("uploadFile.jsp?msg=a");
         if(ex>0)
    %>          DONE
    <%     }
         else
    %>          Data Inconsistency found
    <%     }
    %>
    </body>
    </html>
    ======================================================
    JAVA FILES
    ======================================================
    ExcelInteraction:
    package pdss;
    import pdss.*;
    import java.io.*;
    import java.lang.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    public class ExcelInteraction
         //PDSSUtilities pdsUtil=new PDSSUtilities();
         public int fileTransfer(String readFile, ServletContext app) throws Exception
              int i=0, j=0;
              String strDirectory = "pdssexcelfiles";
              System.out.println("..............ReadFile..."+readFile);
              File srcFile=new File(readFile);
              System.out.println(".................Created source file."+srcFile.getAbsolutePath());
              File destFile=null;
              String newDirStr="",srcFileName="",destFileLoc="", realPath="";
              try{
                   realPath=app.getRealPath("/");
                   System.out.println("newDirStr..........."+realPath);
                   newDirStr=realPath+strDirectory;
                   System.out.println("newDirStr..........."+newDirStr);
                   if((new File(newDirStr)).exists()==false)
                        boolean success = (new File(newDirStr)).mkdir();
                        System.out.println("....................success..."+success);
                        if (success) {
                             System.out.println(".................Directory...: " + strDirectory + " created");
                   srcFileName = srcFile.getName();
                   destFileLoc=newDirStr+"\\"+srcFileName;
                   System.out.println("DestFileLoc............"+destFileLoc);
                   if(srcFile.exists()){
                        destFile=new File(destFileLoc);
                        InputStream in = new FileInputStream(srcFile);
                        OutputStream out = new FileOutputStream(destFile);
                        byte[] buf = new byte[1024];
                        int len=0;
                        while ((len = in.read(buf)) > 0){
                             out.write(buf, 0, len);
                        in.close();
                        out.close();
                   System.out.println("............File copied to... "+destFile.getAbsolutePath());
                   System.out.println("......Closing Streams......");
                   /*if(destFile.exists())
                        j=pdsUtil.readXlData(destFileLoc);
                        System.out.println("..........j::"+j+"rows affected");
              catch(Exception e)
                   e.printStackTrace();
                   System.exit(0);
              return j;
    =====================================================
    LOG FILE FROM HOST SYSTEM:
    =====================================================
    2008-09-16 16:53:52 StandardContext[pdss]: Mapping contextPath='/pdss' with requestURI='/pdss/uploadFile.jsp' and relativeURI='/uploadFile.jsp'
    2008-09-16 16:53:52 StandardContext[pdss]: Trying exact match
    2008-09-16 16:53:52 StandardContext[pdss]: Trying prefix match
    2008-09-16 16:53:52 StandardContext[pdss]: Trying extension match
    2008-09-16 16:53:52 StandardContext[pdss]: Mapped to servlet 'jsp' with servlet path '/uploadFile.jsp' and path info 'null' and update=true
    2008-09-16 16:54:01 StandardContext[pdss]: Mapping contextPath='/pdss' with requestURI='/pdss/uploadFile.jsp' and relativeURI='/uploadFile.jsp'
    2008-09-16 16:54:01 StandardContext[pdss]: Trying exact match
    2008-09-16 16:54:01 StandardContext[pdss]: Trying prefix match
    2008-09-16 16:54:01 StandardContext[pdss]: Trying extension match
    2008-09-16 16:54:01 StandardContext[pdss]: Mapped to servlet 'jsp' with servlet path '/uploadFile.jsp' and path info 'null' and update=true
    =====================================================
    LOG FILE FROM CLIENT SYSTEM:
    2008-09-16 16:54:41 StandardContext[pdss]: Mapping contextPath='/pdss' with requestURI='/pdss/uploadFile.jsp' and relativeURI='/uploadFile.jsp'
    2008-09-16 16:54:41 StandardContext[pdss]: Trying exact match
    2008-09-16 16:54:41 StandardContext[pdss]: Trying prefix match
    2008-09-16 16:54:41 StandardContext[pdss]: Trying extension match
    2008-09-16 16:54:41 StandardContext[pdss]: Mapped to servlet 'jsp' with servlet path '/uploadFile.jsp' and path info 'null' and update=true
    2008-09-16 16:54:42 StandardContext[pdss]: Stopping
    2008-09-16 16:54:42 StandardContext[pdss]: Stopping filters
    2008-09-16 16:54:42 StandardContext[pdss]: Processing standard container shutdown
    2008-09-16 16:54:42 ContextConfig[pdss]: ContextConfig: Processing STOP
    2008-09-16 16:54:42 StandardWrapper[pdss:jsp]: Waiting for 1 instance(s) to be deallocated
    2008-09-16 16:54:42 StandardContext[pdss]: Sending application stop events
    2008-09-16 16:54:42 StandardContext[pdss]: Stopping complete
    =====================================================
    Regards
    Vasumitra

    The VERY FIRST message in the server log gives you a hint as to what the problem might be. The server thinks you have spaces in your PATH to the application server. Therefore, the solution is to kill the server however you need to (task manager, whatever) and then reinstall it in a path that doesn't contain spaces. That's the low-hanging fruit here; if that doesn't work, well, then we will have to find some other solution.

  • Problem with Application server

    Hi All,
    I'm facing problem with Application Server. When I installed the appserver and started it.. It started with the message " server has been started and some services will run at back". But when I tried stopping it using the stop default server i got the message that there is no server running but when i saw in the task manager i cud see two process running 1) appserver.exe and 2) imqbroker(something).exe so eventually I had to kill it.
    Now when I'm trying to start the application server again its giving me this message "CLI156 Could not start the domain domain1" and below is the log file attached if its of any help
    [#|2005-08-31T23:37:57.000+1000|WARNING|sun-appserver-pe8.1_01|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.  |#]
    [#|2005-08-31T23:37:57.015+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
    -Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    -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=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\bin].|#]
    [#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2005-08-31T23:38:15.796+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2005-08-31T23:38:16.484+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2005-09-01T00:48:45.484+1000|WARNING|sun-appserver-pe8.1_01|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.  |#]
    [#|2005-09-01T00:48:45.531+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
    -Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    -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=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-09-04T04:12:39.281+1000|WARNING|sun-appserver-pe8.1_01|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.  |#]
    [#|2005-09-04T04:12:39.343+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
    -Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    -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=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -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:/Program Files/netbeans-4.1/SunAppServer8.1/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
    [#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\var\instances|#]
    [#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2005-09-04T04:13:50.453+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
         at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:176)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:101)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
         at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:281)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
         at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
         at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1894)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:712)
         at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:293)
         at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
         at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
         at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
         at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
         at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
         ... 3 more
    Caused by: java.net.ConnectException: Connection refused: no further information
         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
         at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:178)
         at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:156)
         ... 21 more
    |#]
    [#|2005-09-04T04:13:50.484+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
    com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
         at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:376)
         at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
         at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
         at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
         at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]
    Thanks in advance
    Ajay

    The VERY FIRST message in the server log gives you a hint as to what the problem might be. The server thinks you have spaces in your PATH to the application server. Therefore, the solution is to kill the server however you need to (task manager, whatever) and then reinstall it in a path that doesn't contain spaces. That's the low-hanging fruit here; if that doesn't work, well, then we will have to find some other solution.

Maybe you are looking for