Unregistered servlets in weblogic5.1

Hi
1)In am calling from javascript file:
parent.frames[1].hiddenfrm.action = "/servlet/login.AdminMainServlet";
For this the entry in weblogic properties file is:
weblogic.httpd.register./servlet/login.AdminMainServlet=login.AdminMainServlet
This works fine.
2) But now I am calling a servlet like this, from a javascript file:
window.open("../../servlet/Sales.ProdResrvServlet?mode=addition&act=CustomerPopup&cmpcd="+cmpcd+"&finyr="+finyr+"&searchby=sname", "CustomerPopup", "width=725, height=200, top= 5, left=60");
how can i call a unregistered servlet?..Even i commented for servletservlet, weblogic.httpd.register.servlets=weblogic.servlet.ServletServlet
My directory structure for servlets is:
C:\weblogic\myserver\servletclasses\sales
C:\weblogic\myserver\servletclasses\login
But i am calling the servlets like above,because i am shifting from someother webserver to weblogic5.1
Cheers

Sample web.xml
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 1.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<servlet>
<servlet-name>com.final1.servlets.LoginServlet</servlet-name>
<servlet-class>com.final1.servlets.LoginServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>RouterServlet</servlet-name>
<servlet-class>com.final1.servlets.RouterServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>com.final1.servlets.LoginServlet</servlet-name>
<url-pattern>/com.final1.servlets.LoginServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>RouterServlet</servlet-name>
<url-pattern>/RouterServlet</url-pattern>
</servlet-mapping>
</web-app>

Similar Messages

  • PathInfo Problem with unregisterd servlets!

    Hi!
              When accessing unregistered servlets (with the ServletServlet), the
              pathinfo is not correct in WL 5.1.
              With BETA 2 this problem didn't exist.
              The falling call is made:
              registered:
              http://server/com.servlet.TestServlet/0/frame/test
              -> PathInfo: /0/frame/test
              ServletServlet:
              http://server/servlet/com.servlet.TestServlet/0/frame/test
              -> PathInfo: /com.servlet.TestServlet/0/frame/test
              When will this bug be fixed?
              Dipl. Ing. Alexander Sommer
              Software Development Manager
              http://www.TIScover.com
              TIS
              Tourismus Informations Systeme GmbH
              Softwarepark Hagenberg, Hauptstr. 99
              A-4232 Hagenberg, Austria
              Tel: +43(7236)3343-777
              Fax: +43(7236)3343-782
              e-mail: [email protected]
              

    There is a 'major' difference in the Web server provided in Jdev 3.2.3 and Jdev 9i. The Jdev 3.2.3 web server is a simple 'tes server' ( a light version of WebToGo) to allow for running servlets and JSP pages. In Jdev 9i, we use OC4J which is a J2EE application server for WEB and EJB applications. The Jdev 9i server configuration information cannot be used in Jdev 3.2.3. I dont recommend developing under JDev 9i and running inde Jdev 3.2.3. Since Jdev 9i is now released, I highly recommend that you move up to this release.

  • Servlet Reloading

    Client: Internet Explorer version 4.0.
    Server: Weblogic 4.5 on Windows NT 4.0 using JDK1.1.X.
    I have included the following in my weblogic.properties file.
    weblogic.httpd.servlet.classpath=/xyz;/xyz/test
    weblogic.httpd.servlet.reloadCheckSecs=10
    These directories ( /xyz;/xyz/test ) are completely separate from the
    WebLogic install directories.
    I have replaced the servlet class files in /xyz and /xyz/test with newer
    class files but I don’t see the updated output even after I close Internet
    explorer and try it again.
    NOTE:
    (1) I am invoking unregistered servlets
    (2) I understand that the custom classloader from Weblogic needs to be
    invoked. I have made sure that the NT system CLASSPATH variable makes no
    reference to /xyz OR /xyz/test directories.
    (3) I have altered the weblogic.class.path to include \ (Root dir) so that I
    can invoke the custom servlets with a URL such as
    http://myDomain/servlet/xyz.First OR
    http://myDomain/servlet/xyz.test.Second.
    Am I missing something?

    you'll probably get a faster answer by posting this on the oas forum.
    or the ias 9i forum

  • Scope of instance variables in servlets..

    Hi all,
              Sorry for asking a dumb question..
              What is the scope of instance variables in a servlet? Is the scope is
              limited to thread?
              In other words, in the following example, i am setting "testStr", in one
              request and when i tried to access the same instance variable from another
              request, i am getting it as null. Does it mean instance variable is limited
              to that particular thread/request?
              thanks in advance..
              -ramu
              

    Oops ... I had misunderstood and had the problem backwards ;-)
              > Is it known behavior? With registered servlet its working fine (a
              > instance variable is shared by all requests)
              I believe so; I typically deploy in a WAR so have not seen the problem that
              you describe. Servlets can be reloaded, so what you saw could have been
              caused bye a date/time mismatch between the .class file and the server's
              current time. On the other hand, that could be how WebLogic works.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com
              +1.617.623.5782
              WebLogic Consulting Available
              "Ramu" <[email protected]> wrote in message
              news:[email protected]...
              > Hi Purdy,
              >
              > I got it. I am testing the servlet as a unregistered servlet, which is
              > creating instance for every new request!!!, which created this whole
              > confusion. Is it known behavior? With registered servlet its working fine
              (a
              > instance variable is shared by all requests)
              >
              > > What theory? ;-) Instance variables are on the object, and the object
              can
              > > be used by multiple threads, thus allowing multiple threads to access
              the
              > > same instance variables.
              > what i mean by theory here is, all instance variables in servlet should
              be
              > shared by all requests. Now i got it sir.
              >
              > Thank you..
              > -ramu
              >
              >
              > >
              > > Peace,
              > >
              > > --
              > > Cameron Purdy
              > > Tangosol, Inc.
              > > http://www.tangosol.com
              > > +1.617.623.5782
              > > WebLogic Consulting Available
              > >
              > >
              > > "Ramu" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > Hi,
              > > >
              > > > > No, an instance variable in a servlet class is not limited to a
              > thread.
              > > > There
              > > > > is exactly one copy of the servlet created in memory and all
              requests
              > > pass
              > > > > through the same instance, thus sharing any instance variables. A
              > > couple
              > > > of
              > > > > things to remember:
              > > > I totally agree with you, But i am wondering why my sample servlet(i
              am
              > > > attaching the file) is not sharing the instance variables across
              > > > threads/reqs. (in 1st request set some string to "testStr" instance
              > > > variable, in next request if you read the same instance variable, you
              > will
              > > > get null!!)
              > > > Our current code is having instance variables. But right now we are
              not
              > > > getting any problems. But as per theory, instance variables should be
              > > shared
              > > > across threads/requests..
              > > >
              > > > Any how we are changing our code to remove all instance variables.
              > > >
              > > > thanks,
              > > > -ramu
              > > >
              > > > >
              > > > > 1.) Using instance or class variables in servlets that are not
              > read-only
              > > > is not
              > > > > a good thing to do. This makes the servlet not thread-safe. To
              > > maintain
              > > > > variables across requests, sessions, etc., use the servlet-defined
              > > objects
              > > > to
              > > > > store the state (e.g., request, session, etc.).
              > > > >
              > > > > 2.) If you modify the servlet class on disk, WebLogic will reload
              the
              > > > servlet
              > > > > class thus discarding the old instance and creating a new one (of
              > > course,
              > > > this
              > > > > depends on some configuration parameters for servlet reloading).
              > > > >
              > > > > Hope this helps,
              > > > > Robert
              > > > >
              > > > > Ramu wrote:
              > > > >
              > > > > > Hi,
              > > > > > thanks for quick reply.
              > > > > > I am not at all using SingleThreadModel. See the following code.
              > > > > > In first request i am passing "abc" value to testStr. But in
              second
              > > > request,
              > > > > > I am getting null for testStr in second request. It looks like
              (for
              > > me)
              > > > for
              > > > > > non single threaded model also, scope of instance variables is
              > > limited
              > > > to
              > > > > > Thread/Request.. But as per theory, because its not single
              threaded
              > > > model,
              > > > > > only one instance should be there AND testStr(instace variables)
              > > should
              > > > be
              > > > > > shared across the all threads. But i am not able see that
              behaviour
              > > > here.
              > > > > > But if declare instance variable as static, o am able to share
              it
              > > > across
              > > > > > all threads/requests.
              > > > > >
              > > > > > note:
              > > > > > From browser i am setting testStr to "abc" with URL like
              > > > > > "localhost/test1?testStr=abc"
              > > > > > And 2nd req from browser is like "localhost/test1" (on server
              > output
              > > i
              > > > am
              > > > > > getting null for testStr)
              > > > > >
              > > > > > Any ideas?
              > > > > >
              > > > > > thanks,
              > > > > > -ravi
              > > > > >
              > > > > > import java.io.*;
              > > > > > import javax.servlet.*;
              > > > > > import javax.servlet.http.*;
              > > > > >
              > > > > > public class test1 extends HttpServlet
              > > > > > {
              > > > > > public String testStr;
              > > > > >
              > > > > > public void doGet (HttpServletRequest req, HttpServletResponse
              res)
              > > > > > throws ServletException, IOException
              > > > > > {
              > > > > > doPost(req, res);
              > > > > > }
              > > > > >
              > > > > > public void doPost (HttpServletRequest req,
              HttpServletResponse
              > > res)
              > > > > > throws ServletException, IOException
              > > > > > {
              > > > > > try {
              > > > > > res.setContentType("text/html");
              > > > > > PrintWriter out = res.getWriter();
              > > > > > if(req.getParameter("testStr") != null)
              > > > > > {
              > > > > > testStr = req.getParameter("testStr");
              > > > > > System.out.println("set testStr = " + testStr);
              > > > > > }
              > > > > > else{
              > > > > > System.out.println("get testStr = " + testStr);
              > > > > > }
              > > > > >
              > > > > > }
              > > > > > catch(Exception e){
              > > > > > e.printStackTrace();
              > > > > > }
              > > > > >
              > > > > > }
              > > > > > }
              > > > > >
              > > > > > "Cameron Purdy" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > > Yes or no, depending on if your servlet implements
              > > SingleThreadModel.
              > > > > > >
              > > > > > > See the servlet 2.2 spec for documentation on how many instances
              > of
              > > a
              > > > > > > servlet will be created. See the doc for the SingleThreadModel
              > > > interface.
              > > > > > >
              > > > > > > Peace,
              > > > > > >
              > > > > > > --
              > > > > > > Cameron Purdy
              > > > > > > Tangosol, Inc.
              > > > > > > http://www.tangosol.com
              > > > > > > +1.617.623.5782
              > > > > > > WebLogic Consulting Available
              > > > > > >
              > > > > > >
              > > > > > > "Ramu" <[email protected]> wrote in message
              > > > > > > news:[email protected]...
              > > > > > > > Hi all,
              > > > > > > >
              > > > > > > > Sorry for asking a dumb question..
              > > > > > > >
              > > > > > > > What is the scope of instance variables in a servlet? Is the
              > scope
              > > > is
              > > > > > > > limited to thread?
              > > > > > > >
              > > > > > > > In other words, in the following example, i am setting
              > "testStr",
              > > in
              > > > one
              > > > > > > > request and when i tried to access the same instance variable
              > from
              > > > > > another
              > > > > > > > request, i am getting it as null. Does it mean instance
              variable
              > > is
              > > > > > > limited
              > > > > > > > to that particular thread/request?
              > > > > > > >
              > > > > > > > thanks in advance..
              > > > > > > >
              > > > > > > > -ramu
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > >
              > > > > > >
              > > > >
              > > >
              > > >
              > > >
              > >
              > >
              >
              >
              

  • Servlet instances being destroyed?

    Hi,
              I converted my web app from 5.1 to 6.0 and tried hitting a jsp page. All of
              a sudden, I get the following:
              <[WebAppServletContext kiko] *.html: destroy>
              ####<Nov 7, 2000 4:44:37 PM PST> <Info> <HTTP> <> <myserver> <main> <guest>
              <> <101142>
              <Error unregistering servlet runtime
              mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              yserver,Type=ServletRuntime>
              javax.management.InstanceNotFoundException:
              mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              yserver,Type=ServletRuntime
              at
              javax.management.MBeanServer.unregisterMBean(MBeanServer.java:866)
              at
              weblogic.management.internal.RemoteMBeanServerImpl.unregisterMBean(RemoteMBe
              anServerImpl.java:106)
              at
              weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDele
              gate.java:96)
              at
              weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.jav
              a:442)
              at
              weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              a:526)
              at
              weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.jav
              a:464)
              at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:29
              8)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :201)
              at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              ntext.java:1114)
              at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              :1388)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:133)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:116)
              --------------- nested within: ------------------
              weblogic.management.ManagementException: - with nested exception:
              [javax.management.InstanceNotFoundException:
              mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              yserver,Type=ServletRuntime]
              at
              weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDele
              gate.java:98)
              at
              weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.jav
              a:442)
              at
              weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              a:526)
              at
              weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.jav
              a:464)
              at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:29
              8)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :201)
              at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              ntext.java:1114)
              at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              :1388)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:133)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:116)
              Why is the FileServlet instance being destroyed by WL?
              Gene Chuang
              Join Kiko.com!
              

    I suspect that what is happening here is that when the jsp gets compiled, the
              code that detects changes in the applications directory notices that the app
              has changed and tries to reload it. This seems like a bug to me. I have
              entered CR038194 to track this problem.
              mark
              Gene Chuang wrote:
              > Hi,
              >
              > I converted my web app from 5.1 to 6.0 and tried hitting a jsp page. All of
              > a sudden, I get the following:
              >
              > <[WebAppServletContext kiko] *.html: destroy>
              > ####<Nov 7, 2000 4:44:37 PM PST> <Info> <HTTP> <> <myserver> <main> <guest>
              > <> <101142>
              > <Error unregistering servlet runtime
              > mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              > yserver,Type=ServletRuntime>
              > javax.management.InstanceNotFoundException:
              > mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              > yserver,Type=ServletRuntime
              > at
              > javax.management.MBeanServer.unregisterMBean(MBeanServer.java:866)
              > at
              > weblogic.management.internal.RemoteMBeanServerImpl.unregisterMBean(RemoteMBe
              > anServerImpl.java:106)
              > at
              > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDele
              > gate.java:96)
              > at
              > weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.jav
              > a:442)
              > at
              > weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              > a:526)
              > at
              > weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.jav
              > a:464)
              > at
              > weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:29
              > 8)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :201)
              > at
              > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > ntext.java:1114)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > :1388)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:133)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:116)
              > --------------- nested within: ------------------
              > weblogic.management.ManagementException: - with nested exception:
              > [javax.management.InstanceNotFoundException:
              > mydomain:Name=myserver_kiko_kiko_weblogic.servlet.FileServlet_170,Location=m
              > yserver,Type=ServletRuntime]
              > at
              > weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDele
              > gate.java:98)
              > at
              > weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.jav
              > a:442)
              > at
              > weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              > a:526)
              > at
              > weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.jav
              > a:464)
              > at
              > weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:29
              > 8)
              > at
              > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :201)
              > at
              > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > ntext.java:1114)
              > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > :1388)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:133)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:116)
              >
              > Why is the FileServlet instance being destroyed by WL?
              >
              > --
              > Gene Chuang
              > Join Kiko.com!
              

  • How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

    Dear All,
    I have one statement int weblogic 5.1 weblogic.propertis as follow,
    weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
    but after converting to weblogic 6.1 there are no corresponding statement in
    the file config.xml. And when i start the new application, error occured.
    what should I do?
    The error message is:
    <2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
    .\config\tbcn\config.xml
    <2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
    server: 'Fatal initializatio
    Throwable: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
    at
    weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception

    Dear Satya,
    My weblogic propertis file as follow,
    # CORE PROPERTIES
    # You should set these before you start the WebLogic Server the first time.
    # If you need more instructions on individual properties in this
    # section, check the same section in the Optional Properties, where
    # we've left the long explanations. Or, better yet, go to our
    # website and read all about properties, at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # CORE SYSTEM PROPERTIES
    # TCP/IP port number at which the WebLogic Server listens for connections
    weblogic.system.listenPort=7001
    # CORE SECURITY-RELATED PROPERTIES
    # Read important information about security at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # REQUIRED: The system password MUST be set in order to start the
    # WebLogic Server. This password is case-sensitive, at least 8 characters.
    # The username for the privileged user is ALWAYS "system".
    # This username and password also includes httpd access (see
    # HTTPD properties below).
    weblogic.password.system=12345678
    # RECOMMEND Set to 'everyone' if HTTPD is enabled
    weblogic.allow.execute.weblogic.servlet=everyone
    # Set individual ACLs to restrict access to HTTP-related resources,
    # such as the Administration servlets.
    # To make your own servlets generally available, follow this
    # pattern (provide a weblogic.allow.execute) for your packages and
    # set ACLs as appropriate.
    # CORE SECURITY-RELATED PROPERTIES FOR SSL
    # Read important information about SSL at:
    # http://www.weblogic.com/docs51/classdocs/API_secure.html
    # Enable SSL
    # (default if property not defined is false)
    weblogic.security.ssl.enable=true
    # SSL listen port
    weblogic.system.SSLListenPort=7002
    # Servlets for SSL
    # Authentication servlet for creating tokens for applets
    weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
    ervlet
    # Limits number of unclaimed stored tokens
    weblogic.security.certificateCacheSize=3
    # Capture CA root of client servlet
    weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
    # Certificates for SSL
    # Name of acceptable CA roots
    # For client authentication change value to a valid .pem file
    #weblogic.security.clientRootCA=SecureServerCA.pem
    # Server certificates for SSL
    weblogic.security.certificate.server=democert.pem
    weblogic.security.key.server=demokey.pem
    weblogic.security.certificate.authority=ca.pem
    # registration for certificate generator servlet
    weblogic.httpd.register.Certificate=utils.certificate
    weblogic.allow.execute.weblogic.servlet.Certificate=system
    # CORE HTTPD ADMINISTRATIVE PROPERTIES
    # True permits the HTTPD to run (default)
    # Uncomment this property to disable HTTPD
    #weblogic.httpd.enable=false
    # If authentication is required, add username/password for each user
    # who will be included in an ACL, as in this commented-out example:
    #weblogic.password.peter=#8gjsL4*
    # SYSTEM PROPERTIES
    # System properties in this section are set to system defaults
    # Performance pack. The shared library must be accessible from your
    # PATH (NT) or from your shared library path (UNIX; the name of the
    # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
    weblogic.system.nativeIO.enable=true
    # Outputs logging information to the console as well as to the log file
    weblogic.system.enableConsole=true
    # Sets the directory or URL for the WebLogic Admin help pages
    # The help pages are shipped in the "docs/adminhelp" directory, in the
    # default document root in public_html
    weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
    # If you prefer to access the most recent help pages, you can do so online
    # by commenting out the previous property and uncommenting this one:
    #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
    # Properties for tuning the server's performance
    # Number of WebLogic Server execute threads.
    weblogic.system.executeThreadCount=15
    # Other optional system properties
    # Limits size of weblogic.log (in K) and versions old log
    weblogic.system.maxLogFileSize=1024
    # Adjust minimum length of password
    weblogic.system.minPasswordLen=8
    # UNIX only: If running on port 80 on UNIX, enable the setUID program
    #weblogic.system.enableSetUID=false
    # UNIX only: Unprivileged user to setUID to after starting up
    # WebLogic Server on port 80
    #weblogic.system.nonPrivUser=nobody
    # CLUSTER-SPECIFIC PROPERTIES
    # Cluster-specific properties in this section are set to system defaults.
    # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
    # in the per-cluster properties file ONLY.
    # Time-to-live (number of hops) for the cluster's multicast messages
    # (default 1, range 1-255).
    #weblogic.cluster.multicastTTL=1
    # Sets the load-balancing algorithm to be used between
    # replicated services if none is specified. If not specified,
    # round-robin is used.
    #weblogic.cluster.defaultLoadAlgorithm=round-robin
    # SERVER-SPECIFIC CLUSTER PROPERTIES
    # Cluster-related properties in this section are set to system defaults.
    # CLUSTER USERS: Note that these server-specific cluster-related properties
    # should be set in the per-server properties file ONLY.
    # Sets the weight of the individual server for the weight-based
    load-balancing.
    # Range is 0 - 100.
    # Larger numbers increase the amount of traffic routed to this server.
    #weblogic.system.weight=100
    # SYSTEM STARTUP FILES - Examples
    # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
    # objects should be registered in the per-server properties file.
    # All other startup classes should be registered in the per-cluster
    # properties file.
    # For more info on writing and using startup file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a startup class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.startupClass.[virtual_name]=[full_pathname]
    # Add arguments for the startup class
    #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/StartupQuery.java
    #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
    #weblogic.system.startupArgs.doquery=\
    # query=select * from emp,\
    # db=jdbc:weblogic:pool:demoPool
    # SYSTEM SHUTDOWN FILES - Examples
    # For more info on writing and using shutdown file, see the
    # Developers Guide "Writing a WebLogic Client application," at
    # http://www.weblogic.com/docs51/classdocs/API_t3.html
    # Register a shutdown class by giving it a virtual name and
    # supplying its full pathname.
    #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
    # Add arguments for the shutdown class
    #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
    # This example shows the entry for examples/t3client/ShutdownTest.java
    #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
    #weblogic.system.shutdownArgs.ShutdownTest=\
    # outfile=c:/temp/shutdown.log
    # SECURITY-RELATED PROPERTIES FOR WORKSPACES
    # For backward compatibility, the following entries disable Access
    # Control on Workspaces
    weblogic.allow.read.weblogic.workspace=everyone
    weblogic.allow.write.weblogic.workspace=everyone
    # JOLT FOR WEBLOGIC PROPERTIES
    # These properties configure a BEA Jolt connection pool for use with
    # the simpapp and bankapp examples, and register a servlet for use with
    # with the simpapp example. The default server address provided here
    # points to a public TUXEDO server that is hosted by BEA for use with
    # this example.
    # Servlet registration for simpapp example:
    #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
    t
    # Pool creation and cleanup
    # note this example is set up to work with the public
    # demo TUXEDO server available from BEA's website:
    #weblogic.system.startupClass.demojoltpoolStart=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
    #weblogic.system.startupArgs.demojoltpoolStart=\
    # poolname=demojoltpool,\
    # appaddrlist=//beademo1.beasys.com:8000,\
    # failoverlist=//beademo1.beasys.com:8000,\
    # minpoolsize=1,\
    # maxpoolsize=3
    #weblogic.system.shutdownClass.demojoltpoolStop=\
    # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
    #weblogic.system.shutdownArgs.demojoltpoolStop=\
    # poolname=demojoltpool
    # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
    # The registrations enable a BEA IIOP connection pool and
    # register servlets for use with the simpapp and university examples.
    # Configure for your environment and uncomment to use.
    # Uncommenting these properties requires WebLogic Enterprise Connectivity
    # and an operating WebLogic Enterprise Server.
    # Servlet registration for simpapp servlet example
    #weblogic.httpd.register.SimpappServlet=\
    # examples.wlec.servlets.simpapp.SimpappServlet
    #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
    # Servlet registration for simpapp EJB example
    # (You'll need to add the wlec_ejb_simpapp.jar to the
    # weblogic.ejb.deploy property in this file.)
    #weblogic.httpd.register.ejbSimpappServlet=\
    # examples.wlec.ejb.simpapp.ejbSimpappServlet
    #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
    # Pool creation and cleanup for the simpapp example
    #weblogic.CORBA.connectionPool.simplepool=\
    # appaddrlist=//wlehost:2468,\
    # failoverlist=//wlehost:2468,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # domainname=simpapp
    # Servlet registration for university Servlet example:
    #weblogic.httpd.register.UniversityServlet=\
    # examples.wlec.servlets.university.UniversityServlet
    #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
    # Pool creation and cleanup for the University example:
    #weblogic.CORBA.connectionPool.Univpool=\
    # appaddrlist=//wlehost:2498,\
    # failoverlist=//wlehost:2498,\
    # minpoolsize=2,\
    # maxpoolsize=3,\
    # username=wleuser,\
    # userrole=developer,\
    # apppassword=wlepassword,\
    # domainname=university
    # WEBLOGIC FILE PROPERTIES
    # Maps a volume name to a path, for client file read/write
    #weblogic.io.fileSystem.[volumeName]=[fullPathName]
    # WEBLOGIC JMS DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL JMS deployment should be done in the
    # per-cluster properties file ONLY.
    # You set up a JDBC connection pool if you want persistent messages
    # (including durable subscriptions). To use JMS and EJBs in the same
    # transaction, both must use the same JDBC connection pool. Uncomment
    # the following property to use the default JDBC connection pool
    # 'demo', which is defined in the Demo connection pool section of this file.
    #weblogic.jms.connectionPool=demoPool
    # The JMS Webshare example demonstrates how the ClientID for a
    # durable subscriber is configured in the connection factory:
    #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
    #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
    #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
    #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
    # The JMS trader example shows how to use JMS with an EJB. In addition
    # to uncommenting the following properties, you must also set up and
    # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
    # ejb_basic_statelessSession.jar to try out this JMS example:
    #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
    #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
    #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
    #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
    # Registers the underlying servlet
    #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
    # These properties are used with the ServerReceive JMS example,
    # which demonstrates how to establish a JMS message consumer
    # in a startup class:
    #weblogic.system.startupClass.serverReceive=\
    # examples.jms.startup.ServerReceive
    #weblogic.system.startupArgs.serverReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    # These properties are used with the PoolReceive JMS example,
    # which demonstrates how to establish a pool of JMS message consumers
    # in a startup class:
    #weblogic.system.startupClass.poolReceive=\
    # examples.jms.startup.PoolReceive
    #weblogic.system.startupArgs.poolReceive=\
    # connectionFactory=javax.jms.TopicConnectionFactory,\
    # topic=javax.jms.exampleTopic
    #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
    # WEBLOGIC RMI DEMO PROPERTIES
    # CLUSTER USERS: Note that pinned RMI objects should be registered
    # in the per-server properties file ONLY. All other RMI startup
    # classes should be registered in the per-cluster properties file.
    # Remote classes registered at startup after the pattern:
    #weblogic.system.startupClass.[virtualName]=[fullPackageName]
    # These examples can be compiled to see RMI in action. Uncomment to use:
    #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
    #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
    #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
    # WEBLOGIC EJB DEMO PROPERTIES
    # CLUSTER USERS: Note that ALL EJB deployment should be done in the
    # per-cluster properties file ONLY.
    # See WebLogic Demo Connection Pool below for a connection pool
    # to use with these examples.
    # Deploys EJBeans. Uncomment the appropriate lines below and
    # modify DBMS-related info and paths to match your particular installation:
    # TBCN EJB PROPERTIES
    weblogic.ejb.deploy=\
    C:/weblogic/myserver/AccountSB.jar, \
    C:/weblogic/myserver/AddressEntryDet.jar, \
    C:/weblogic/myserver/AddressEntry.jar, \
    C:/weblogic/myserver/Affiliate.jar, \
    C:/weblogic/myserver/ContactPerson.jar, \
    C:/weblogic/myserver/ContactSB.jar, \
    C:/weblogic/myserver/Factory.jar, \
    C:/weblogic/myserver/FactorySups.jar, \
    c:/weblogic/myserver/LoginUsers.jar, \
    c:/weblogic/myserver/Member.jar, \
    c:/weblogic/myserver/MemberQuotaUsage.jar,\
    c:/weblogic/myserver/MemberToCategory.jar,\
    c:/weblogic/myserver/Organization.jar, \
    c:/weblogic/myserver/Person.jar, \
    c:/weblogic/myserver/QuotaType.jar,\
    c:/weblogic/myserver/Registration.jar, \
    c:/weblogic/myserver/TempAccounts.jar, \
    c:/weblogic/myserver/TempDomain.jar, \
    c:/weblogic/myserver/UserAccount.jar, \
    c:/weblogic/myserver/UserRole.jar, \
    c:/weblogic/myserver/BuyerProducts.jar, \
    c:/weblogic/myserver/Catalog.jar, \
    c:/weblogic/myserver/Categories.jar, \
    c:/weblogic/myserver/CategoryToCategory.jar, \
    c:/weblogic/myserver/CountryToCategory.jar, \
    c:/weblogic/myserver/InvitedMember.jar, \
    c:/weblogic/myserver/ProductOrigin.jar, \
    c:/weblogic/myserver/ProductOtherFee.jar,\
    c:/weblogic/myserver/ProductSups.jar, \
    c:/weblogic/myserver/Products.jar,\
    c:/weblogic/myserver/ProductToCategory.jar, \
    c:/weblogic/myserver/SecondaryQcEntry.jar, \
    c:/weblogic/myserver/CodeClass.jar,\
    c:/weblogic/myserver/ConfirmationSB.jar, \
    c:/weblogic/myserver/PurchasedPackage.jar,\
    c:/weblogic/myserver/RejectReasonCode.jar, \
    c:/weblogic/myserver/ServiceOrder.jar,\
    c:/weblogic/myserver/ServiceOrderLog.jar,\
    c:/weblogic/myserver/ServiceOrderState.jar,\
    c:/weblogic/myserver/ServiceOrderType.jar,\
    c:/weblogic/myserver/ServicePackageDetails.jar, \
    c:/weblogic/myserver/ServicePackage.jar, \
    c:/weblogic/myserver/ServicePayment.jar, \
    c:/weblogic/myserver/ServiceReqSB.jar, \
    c:/weblogic/myserver/TAM.jar, \
    c:/weblogic/myserver/SubscriptionEB.jar, \
    c:/weblogic/myserver/PostingCategoryEB.jar, \
    c:/weblogic/myserver/PostingBrowsedEB.jar, \
    c:/weblogic/myserver/PostingInfoEB.jar, \
    c:/weblogic/myserver/TransactionLogEB.jar, \
    c:/weblogic/myserver/PostingSB.jar
    #weblogic.ejb.deploy=\
    # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
    # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
    # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
    # d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
    # d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
    # d:/weblogic/myserver/ejb_subclass.jar, \
    # d:/weblogic/myserver/jolt_ejb_bankapp.jar
    # Servlet used by the EJB basic beanManaged example
    # Uncomment to use:
    weblogic.httpd.register.beanManaged=\
    examples.ejb.basic.beanManaged.Servlet
    # Add a list of users (set the password with
    weblogic.password.[username]=XXX)
    # to set an ACL for this servlet:
    #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
    #weblogic.password.user1=user1Password
    #weblogic.password.user2=user2Password
    # WEBLOGIC XML DEMO PROPERTIES
    # These properties are required to run the XML examples.
    # Uncomment to use.
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
    # BizTalk example properties
    #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
    #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
    #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
    dapter
    #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
    # WEBLOGIC ZAC DEMO PROPERTIES
    # These registrations enable the ZAC Publish Wizard.
    weblogic.zac.enable=true
    # Set the publish root for a WebLogic Server. Edit and
    # uncomment to use.
    #weblogic.zac.publishRoot=d:/weblogic/zac
    # Set an ACL for each package you publish. The [name] is
    # the "Package name" you assign in the ZAC Publish Wizard.
    # Publish a package, edit this property, and uncomment to use.
    #weblogic.allow.read.weblogic.zac.[name]=[user list]
    #weblogic.allow.write.weblogic.zac.[name]=system
    # HTTPD ADMINISTRATIVE PROPERTIES
    # Enables logging of HTTPD info in common log format and
    # sets the log file name (default is "access.log" in "myserver")
    weblogic.httpd.enableLogFile=true
    weblogic.httpd.logFileName=access.log
    # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
    weblogic.httpd.enableEvents=false
    # Enables HTTP sessions
    weblogic.httpd.session.enable=true
    # Sets an optional cookie name. The default name is "WebLogicSession".
    # Prior to version 4.0, the default was "TengahSession". To make
    # this backward compatible with cookies generated from previous
    # installations, you should set this property to "TengahSession".
    # Uncomment this line and set this to any string of your choice,
    # or comment out this property to use the default.
    #weblogic.httpd.session.cookie.name=WebLogicSession
    # MIME types
    weblogic.httpd.mimeType.text/html=html,htm
    weblogic.httpd.mimeType.image/gif=gif
    weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
    weblogic.httpd.mimeType.application/pdf=pdf
    weblogic.httpd.mimeType.application/zip=zip
    weblogic.httpd.mimeType.application/x-java-vm=class
    weblogic.httpd.mimeType.application/x-java-archive=jar
    weblogic.httpd.mimeType.application/x-java-serialized-object=ser
    weblogic.httpd.mimeType.application/octet-stream=exe
    weblogic.httpd.mimeType.text/vnd.wap.wml=wml
    weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
    weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
    weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
    weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
    # In seconds, the keep-alive for HTTP and HTTPS requests
    weblogic.httpd.http.keepAliveSecs=60
    weblogic.httpd.https.keepAliveSecs=120
    # WEBLOGIC JDBC DRIVER PROPERTIES
    # Enables JDBC driver logging and sets the file name for the log
    # The weblogic.jdbc.logFile is placed in the per-server
    # directory (default is "myserver")
    weblogic.jdbc.enableLogFile=false
    weblogic.jdbc.logFileName=jdbc.log
    # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # For creating JDBC connection pools. This example shows a connection
    # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
    # to use 4 JDBC connections (with a potential for up to 10 connections,
    # incremented by two at a time, with a delay of 1 second between each
    # attempt to connect to the database), to an Oracle database server called
    # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
    # connections are dropped from the pool until only 4 connections remain
    open.
    # Every 10 minutes, any unused connections in the pool are tested and
    # refreshed if they are not viable.
    #weblogic.jdbc.connectionPool.oraclePool=\
    # url=jdbc:weblogic:oracle,\
    # driver=weblogic.jdbc.oci.Driver,\
    # loginDelaySecs=1,\
    # initialCapacity=4,\
    # maxCapacity=10,\
    # capacityIncrement=2,\
    # allowShrinking=true,\
    # shrinkPeriodMins=15,\
    # refreshMinutes=10,\
    # testTable=dual,\
    # props=user=SCOTT;password=tiger;server=DEMO
    # Get more details on each argument for this property in the
    # Administrators Guide on setting properties at:
    # http://www.weblogic.com/docs51/admindocs/properties.html
    # Set up ACLs for this connection pool with the following:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    # guest,joe,jill
    #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
    # joe,jill
    # This property is an ACL that specifies the users who can
    # create dynamic connection pools:
    #weblogic.jdbc.connectionPoolcreate.admin=joe,jill
    # Read more about setting up and using connection pools in the
    # developers guide for WebLogic JDBC at:
    # http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
    # TBCN JDBC CONNECTION POOL MANAGEMENT
    weblogic.jdbc.connectionPool.oraclePool=\
    url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
    driver=oracle.jdbc.driver.OracleDriver,\
    loginDelaySecs=1,\
    initialCapacity=2,\
    maxCapacity=10,\
    capacityIncrement=2,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshMinutes=10,\
    testTable=dual,\
    props=user=tbcn;password=ca91768
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
    weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
    weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
    # WEBLOGIC DEMO CONNECTION POOL PROPERTIES
    # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
    # in the per-cluster properties file ONLY.
    # This connection pool uses the sample Cloudscape database shipped
    # with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
    # Uncomment to use:
    #weblogic.jdbc.connectionPool.demoPool=\
    # url=jdbc:cloudscape:demo,\
    # driver=COM.cloudscape.core.JDBCDriver,\
    # initialCapacity=1,\
    # maxCapacity=2,\
    # capacityIncrement=1,\
    # props=user=none;password=none;server=none
    # Add a TXDataSource for the connection pool:
    #weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
    # Add an ACL for the connection pool:
    #weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
    # WEBLOGIC HTTP SERVLET PROPERTIES
    # CLUSTER USERS: Note that ALL servlets should be set up
    # in the per-cluster properties file ONLY.
    # WebLogic offers different types of servlets for various uses.
    # Classpath servlet registration
    # The ClasspathServlet is used to serve classes from
    # the system CLASSPATH. It is used by applets to load
    # classes they depend upon, and is registered against
    # the virtual name 'classes' here by default. This means
    # you should set your applet codebase to "/classes".
    # You can register multiple virtual names for this servlet.
    # Note that it can also be used to serve other
    # resources/files from the system CLASSPATH.
    # Don't confuse the ClasspathServlet with the ServletServlet. The
    # ClasspathServlet is used for serving classes for client-side Java only.
    # The ServletServlet is used to invoke unregistered servlets.
    # See the Administrators Guide "Setting up WebLogic as an HTTP server"
    # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
    info.
    weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
    # We also set an open ACL for everyone to call the ClasspathServlet
    # so that applets work without requiring further changes.
    weblogic.allow.execute.weblogic.servlet.classes=everyone
    # File servlet registration
    # FileServlet searches below the documentRoot for the requested file
    # and serves it if found. If the requested file is a directory,
    # FileServlet will append the defaultFilename to the requested path
    # and serve that file if found.
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    weblogic.httpd.indexFiles=zh_TW/index.htm
    # ServerSideInclude servlet registration
    # SSIServlet searches below the documentRoot for the
    # requested .shtml file and serves it if found.
    weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
    # Example URL: http://localhost:7001/portside/welcome.shtml
    # for the file /weblogic/myserver/public_html/portside/welcome.shtml
    # PageCompileServlet (used by JHTML)
    # See the information below under WebLogic JHTML
    # JSPServlet (used by JSP)
    # See the information below under WebLogic JSP
    # ServletServlet registration
    # Allows unregistered servlets in the servlet classpath (see Servlet
    # reload properties below) to be r

  • Strange InterruptedIOException

    Hi, all
              I'm testing an application within a cluster of 1+2 WL 5.1 SP8 on Win2K
              The first WL is a proxy that processes only static data and has
              HttpClusterServlet to transfer all other stuff onto 2 equal app servers
              which made a cluster.
              So, I start walking around our app and everything works fine for some
              time. But suddenly (not always, but offten) some of the servlets (not
              all and not the same, although there are leaders) start having a
              problem reading PostData.
              They hang for weblogic.httpd.postTimeoutSecs and throw an exception
              below. The exception happens (if happens) on the first attempt of
              request.getParameter("...") in servlet's service method.
              And the exception happens ONLY when 2 instances of WL's cluster are up
              and running. If I stop one of them (doesn't matter primary, which has
              already thrown that exception, or secondary) everything works fine. And
              it never happens without cluster.
              I tried separated machines or multihomed with no effect.
              I also varied some properties like
              weblogic.httpd.session.timeoutSecs
              weblogic.httpd.session.neverReadPostData
              weblogic.httpd.postTimeoutSecs
              weblogic.system.nativeIO.enable
              again with no effect
              It looks like smth is wrong with session replication (it works fine
              without cluster or when there is only one WL alive in a cluster). But
              error on reading PostData makes me confused. Look, I'd like to be sure
              that the configuration is OK before reporting that the error is within a
              code.
              I saw some postings in the servlet newsgroup with the same exception,
              but my situation looks somewhat differ. Anyway, those postings are
              unanswered since previous century.
              Help, please.
              java.io.InterruptedIOException: Read timed out
              at java.net.SocketInputStream.socketRead(Native Method)
              at java.net.SocketInputStream.read(SocketInputStream.java:86)
              at weblogic.socket.PostInputStream.read(PostInputStream.java:90)
              at java.io.InputStream.read(InputStream.java:91)
              at
              weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:44)
              at
              weblogic.servlet.internal.CountingInputStream.read(ServletRequestImpl.java:1540)
              at java.io.InputStreamReader.fill(InputStreamReader.java:173)
              at java.io.InputStreamReader.read(InputStreamReader.java:249)
              at
              weblogic.servlet.internal.ServletRequestImpl.mergePostParams(ServletRequestImpl.java:502)
              at
              weblogic.servlet.internal.ServletRequestImpl.parseQueryParams(ServletRequestImpl.java:357)
              at
              weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:542)
              at
              weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:528)
              at com.foo.bar.MyServlet.service(MyServlet.java:41)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              [att1.html]
              

    Prasad,
              I think, to reproduce the behaviour you should install the whole
              application, which is hardly possible :-). Look, it was written without
              clustering in mind. I just try to make it working in a cluster and find
              possible "reefs" to be avoided in the future release. I can't just cut
              piece of code and send you for testing. I will certainly write some
              simple app to see if it behaives the same way, but not this time.
              And, as a last attempt to localize a problem:
              1. Once I wasn't able to pass the very first (login) page without
              disabling browser's cookie support. The app uses cookie (no URLRewriting
              :((( ) for session tracking so I can't pass further (it just fails), but
              it was strange: turn on cookie, restart IE, go to login, press submit
              --- read timed out exception, nested within can't read POST data. Then
              turn off cookies, restart IE, go to login, submit -- everything is fine
              (as long as app doesn't look for the session, but that is the other
              story). Try to turn cookies on -- exception again. But even this
              behaviour isn't deterministic. It worked like that only once. That time
              I started proxy, then one of app servers, worked with app (everything
              fine as usual), then started the second server, restarted IE and saw the
              menthioned behavior on a second server.
              2. Proxy server throws a lot of SocketExceptions, (see below) even when
              the whole app seems to be working fine
              3. I've added DebugConfigInfo=ON to the HttpClusterServlet initArgs, but
              haven't found any log appeared neither on screen nor on disk. By the
              way, what are the other options available for debugging? I know only
              weblogic.debug.httpd.servlet but it's not the case.
              I attached weblogic.properties files for proxy and cluster (the global
              one is empty) and start_servers command files. That's all I can post for
              now.
              Thank you for your help.
              --Andrew
              P.S. that is the Exception which the proxy throws at least once per each
              user request
              java.net.SocketException: Connection aborted by peer: socket write error
              at java.net.SocketOutputStream.socketWrite(Native Method)
              at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
              at
              java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:72
              at
              java.io.BufferedOutputStream.flush(BufferedOutputStream.java:130)
              at java.io.FilterOutputStream.flush(FilterOutputStream.java:126)
              at
              weblogic.servlet.internal.HttpClusterServlet$Server.writeHeaders(Http
              ClusterServlet.java:697)
              at
              weblogic.servlet.internal.HttpClusterServlet$Server.proxy(HttpCluster
              Servlet.java:868)
              at
              weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServl
              et.java:146)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:106)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:907)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:851)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java:252)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a:364)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              java.net.SocketException: Connection aborted by peer: socket write error
              at java.net.SocketOutputStream.socketWrite(Native Method)
              at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
              at
              java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:72
              at
              java.io.BufferedOutputStream.flush(BufferedOutputStream.java:130)
              at java.io.FilterOutputStream.flush(FilterOutputStream.java:126)
              at
              weblogic.servlet.internal.HttpClusterServlet$Server.writeHeaders(Http
              ClusterServlet.java:697)
              at
              weblogic.servlet.internal.HttpClusterServlet$Server.proxy(HttpCluster
              Servlet.java:868)
              at
              weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServl
              et.java:146)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:106)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:907)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
              textImpl.java:851)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
              ContextManager.java:252)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
              a:364)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              Prasad Peddada wrote:
              > Andrew,
              > I checked with the web team and they think this could be a bug.
              > Could you send us a reproducible test case.
              >
              > Thanks
              >
              > -- Prasad
              >
              > Andrew Solgan wrote:
              >
              >> Prasad,
              >>
              >> Prasad Peddada wrote:
              >>
              >> > Andrew,
              >> >
              >> > Post data has nothing to do with replication. I would rule that
              >> > out.
              >>
              >> I'd also. But it never happens without cluster or when only one
              >> server is alive in a cluster?????
              >>
              >> > You said you tried both with native IO and java io.
              >>
              >> A-ha. And saw starting "IO performance pack..." message appeared or
              >> not correspondingly. But the first line in the error stack is always
              >> from the native method
              >> at java.net.SocketInputStream.socketRead(Native Method)
              >> .....
              >>
              >> > Are you using browser to test this?
              >>
              >> IE 5.5
              >>
              >> >
              >> >
              >> > I will followup with servlet team to find out if they know about
              >> > this problem and post back again.
              >> >
              >> > -- Prasad
              >> >
              >>
              >> Thanks,
              >> --Andrew
              >>
              >> >
              >> >
              >> > Andrew Solgan wrote:
              >> >
              >> >> Hi, all
              >> >>
              >> >> I'm testing an application within a cluster of 1+2 WL 5.1 SP8 on
              >> >> Win2K
              >> >>
              >> >> The first WL is a proxy that processes only static data and has
              >> >> HttpClusterServlet to transfer all other stuff onto 2 equal app
              >> >> servers which made a cluster.
              >> >> So, I start walking around our app and everything works fine for
              >> >> some time. But suddenly (not always, but offten) some of the
              >> >> servlets (not all and not the same, although there are leaders)
              >> >> start having a problem reading PostData.
              >> >> They hang for weblogic.httpd.postTimeoutSecs and throw an
              >> >> exception below. The exception happens (if happens) on the first
              >> >> attempt of request.getParameter("...") in servlet's service
              >> >> method.
              >> >> And the exception happens ONLY when 2 instances of WL's cluster
              >> >> are up and running. If I stop one of them (doesn't matter
              >> >> primary, which has already thrown that exception, or secondary)
              >> >> everything works fine. And it never happens without cluster.
              >> >> I tried separated machines or multihomed with no effect.
              >> >> I also varied some properties like
              >> >> weblogic.httpd.session.timeoutSecs
              >> >> weblogic.httpd.session.neverReadPostData
              >> >> weblogic.httpd.postTimeoutSecs
              >> >> weblogic.system.nativeIO.enable
              >> >> again with no effect
              >> >>
              >> >> It looks like smth is wrong with session replication (it works
              >> >> fine without cluster or when there is only one WL alive in a
              >> >> cluster). But error on reading PostData makes me confused. Look,
              >> >> I'd like to be sure that the configuration is OK before reporting
              >> >> that the error is within a code.
              >> >>
              >> >> I saw some postings in the servlet newsgroup with the same
              >> >> exception, but my situation looks somewhat differ. Anyway, those
              >> >> postings are unanswered since previous century.
              >> >>
              >> >> Help, please.
              >> >>
              >> >>
              >> >>
              >> >> java.io.InterruptedIOException: Read timed out
              >> >> at java.net.SocketInputStream.socketRead(Native Method)
              >> >> at java.net.SocketInputStream.read(SocketInputStream.java:86)
              >> >> at weblogic.socket.PostInputStream.read(PostInputStream.java:90)
              >> >>
              >> >> at java.io.InputStream.read(InputStream.java:91)
              >> >> at
              >> >> weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:44)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.CountingInputStream.read(ServletRequestImpl.java:1540)
              >> >>
              >> >> at java.io.InputStreamReader.fill(InputStreamReader.java:173)
              >> >> at java.io.InputStreamReader.read(InputStreamReader.java:249)
              >> >> at
              >> >> weblogic.servlet.internal.ServletRequestImpl.mergePostParams(ServletRequestImpl.java:502)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletRequestImpl.parseQueryParams(ServletRequestImpl.java:357)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:542)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:528)
              >> >>
              >> >> at com.foo.bar.MyServlet.service(MyServlet.java:41)
              >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              >> >> at
              >> >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
              >> >>
              >> >> at
              >> >> weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              >> >>
              >> >> at
              >> >> weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              >> >>
              >> >> at
              >> >> weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              >> >>
              >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              >> >>
              >> >
              [att1.html]
              [startServer.cmd]
              # THE WEBLOGIC PROPERTIES FILE
              weblogic.system.listenPort=80
              weblogic.password.system=proxy
              weblogic.allow.execute.weblogic.servlet=everyone
              weblogic.httpd.register.cluster=\
              weblogic.servlet.internal.HttpClusterServlet
              weblogic.httpd.initArgs.cluster=\
              defaultServers=172.16.43.102:80:7002|172.16.43.103:80:7002,DebugConfigInfo=ON
              weblogic.httpd.defaultServlet=cluster
              weblogic.security.ssl.enable=true
              weblogic.system.SSLListenPort=7002
              weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
              weblogic.security.certificateCacheSize=3
              weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
              weblogic.security.clientRootCA=SecureServerCA.pem
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              weblogic.httpd.register.Certificate=utils.certificate
              weblogic.allow.execute.weblogic.servlet.Certificate=system
              weblogic.httpd.enable=true
              weblogic.system.nativeIO.enable=true
              weblogic.system.enableConsole=true
              weblogic.system.executeThreadCount=50
              weblogic.system.maxLogFileSize=1024
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              weblogic.httpd.enableEvents=true
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.cookie.name=WebLogicSession
              weblogic.httpd.session.neverReadPostData=true
              weblogic.jdbc.enableLogFile=false
              weblogic.allow.execute.weblogic.servlet.classes=everyone
              weblogic.httpd.register.*.html=weblogic.servlet.FileServlet
              weblogic.httpd.initArgs.*.html=defaultFilename=index.html
              weblogic.httpd.register.*.jpg=weblogic.servlet.FileServlet
              weblogic.httpd.register.*.gif=weblogic.servlet.FileServlet
              #weblogic.httpd.register.proxy=weblogic.t3.srvr.HttpProxyServlet
              #weblogic.httpd.initArgs.proxy=redirectURL=http://web1/
              weblogic.httpd.documentRoot=public_html/
              [startproxy.cmd]
              # THE WEBLOGIC PROPERTIES FILE
              # CORE PROPERTIES
              # You should set these before you start the WebLogic Server the first time.
              # If you need more instructions on individual properties in this
              # section, check the same section in the Optional Properties, where
              # we've left the long explanations. Or, better yet, go to our
              # website and read all about properties, at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # CORE SYSTEM PROPERTIES
              # TCP/IP port number at which the WebLogic Server listens for connections
              weblogic.system.listenPort=80
              # CORE SECURITY-RELATED PROPERTIES
              # Read important information about security at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # REQUIRED: The system password MUST be set in order to start the
              # WebLogic Server. This password is case-sensitive, at least 8 characters.
              # The username for the privileged user is ALWAYS "system".
              # This username and password also includes httpd access (see
              # HTTPD properties below).
              # RECOMMEND Set to 'everyone' if HTTPD is enabled
              weblogic.allow.execute.weblogic.servlet=everyone
              # Set individual ACLs to restrict access to HTTP-related resources,
              # such as the Administration servlets.
              # To make your own servlets generally available, follow this
              # pattern (provide a weblogic.allow.execute) for your packages and
              # set ACLs as appropriate.
              # CORE SECURITY-RELATED PROPERTIES FOR SSL
              # Read important information about SSL at:
              # http://www.weblogic.com/docs51/classdocs/API_secure.html
              # Enable SSL
              # (default if property not defined is false)
              weblogic.security.ssl.enable=true
              # SSL listen port
              weblogic.system.SSLListenPort=7002
              weblogic.security.certificateCacheSize=3
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              # CORE HTTPD ADMINISTRATIVE PROPERTIES
              # True permits the HTTPD to run (default)
              # Uncomment this property to disable HTTPD
              #weblogic.httpd.enable=false
              weblogic.httpd.authRealmName=APM server
              # If authentication is required, add username/password for each user
              # who will be included in an ACL, as in this commented-out example:
              weblogic.password.apm_user=tiger@cat
              weblogic.password.apm_admin=admin@moon
              # OPTIONAL PROPERTIES
              # These properties affect the behavior of the WebLogic Server.
              # You only need to set these properties if you want
              # to change the default setting, which is the property shown.
              # ADMINISTRATOR PROPERTIES
              # Administrator properties are optional information properties,
              # particularly useful for clusters.
              weblogic.password.system=weblogic
              weblogic.administrator.email=
              weblogic.administrator.name=Administrator
              # SYSTEM PROPERTIES
              # System properties in this section are set to system defaults
              # Performance pack. The shared library must be accessible from your
              # PATH (NT) or from your shared library path (UNIX; the name of the
              # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              weblogic.system.nativeIO.enable=true
              # Outputs logging information to the console as well as to the log file
              weblogic.system.enableConsole=true
              # Properties for tuning the server's performance
              # Number of WebLogic Server execute threads.
              weblogic.system.executeThreadCount=30
              #weblogic.system.percentSocketReaders=33
              # Other optional system properties
              # Limits size of weblogic.log (in K) and versions old log
              weblogic.system.maxLogFileSize=1024
              # Adjust minimum length of password
              weblogic.system.minPasswordLen=8
              # CLUSTER-SPECIFIC PROPERTIES
              # Cluster-specific properties in this section are set to system defaults.
              # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              # in the per-cluster properties file ONLY.
              # Time-to-live (number of hops) for the cluster's multicast messages
              # (default 1, range 1-255).
              weblogic.cluster.multicastTTL=5
              weblogic.cluster.multicastAddress=237.0.0.5
              # Sets the load-balancing algorithm to be used between
              # replicated services if none is specified. If not specified,
              # round-robin is used.
              weblogic.cluster.defaultLoadAlgorithm=round-robin
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              # SERVER-SPECIFIC CLUSTER PROPERTIES
              # Cluster-related properties in this section are set to system defaults.
              # CLUSTER USERS: Note that these server-specific cluster-related properties
              # should be set in the per-server properties file ONLY.
              # Sets the weight of the individual server for the weight-based load-balancing.
              # Range is 0 - 100.
              # Larger numbers increase the amount of traffic routed to this server.
              #weblogic.system.weight=100
              # SYSTEM STARTUP FILES - Examples
              # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              # objects should be registered in the per-server properties file.
              # All other startup classes should be registered in the per-cluster
              # properties file.
              weblogic.system.startupClass.serverservice.class=com.al.pm.util.ServerService
              # SYSTEM SHUTDOWN FILES - Examples
              # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              # For backward compatibility, the following entries disable Access
              # Control on Workspaces
              weblogic.allow.read.weblogic.workspace=everyone
              weblogic.allow.write.weblogic.workspace=everyone
              # WEBLOGIC FILE PROPERTIES
              # Maps a volume name to a path, for client file read/write
              #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              # WEBLOGIC EJB DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              # per-cluster properties file ONLY.
              # See WebLogic Demo Connection Pool below for a connection pool
              # to use with these examples.
              # Deploys EJBeans. Uncomment the appropriate lines below and
              # modify DBMS-related info and paths to match your particular installation:
              weblogic.ejb.deploy=\
                   //our ejb jars//
              weblogic.resource.MailSession.MailSessionResource=mail.from=test@apm.com,mail.host=192.168.3.6
              # HTTPD ADMINISTRATIVE PROPERTIES
              # Enables logging of HTTPD info in common log format and
              # sets the log file name (default is "access.log")
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              weblogic.httpd.enableEvents=true
              # Enables HTTP sessions
              weblogic.httpd.session.enable=true
              weblogic.httpd.session.timeoutSecs=1200
              weblogic.httpd.session.neverReadPostData=true
              #weblogic.httpd.postTimeoutSecs=120
              # Sets an optional cookie name. The default name is "WebLogicSession".
              # Prior to version 4.0, the default was "TengahSession". To make
              # this backward compatible with cookies generated from previous
              # installations, you should set this property to "TengahSession".
              # Uncomment this line and set this to any string of your choice,
              # or comment out this property to use the default.
              weblogic.httpd.session.cookie.name=APMSession
              weblogic.httpd.session.URLRewriting.enable=true
              # MIME types
              weblogic.httpd.mimeType.text/html=html,htm
              weblogic.httpd.mimeType.image/gif=gif
              weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
              weblogic.httpd.mimeType.application/pdf=pdf
              weblogic.httpd.mimeType.application/zip=zip
              weblogic.httpd.mimeType.application/x-java-vm=class
              weblogic.httpd.mimeType.application/x-java-archive=jar
              weblogic.httpd.mimeType.application/x-java-serialized-object=ser
              weblogic.httpd.mimeType.application/octet-stream=exe
              weblogic.httpd.mimeType.text/vnd.wap.wml=wml
              weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
              weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
              weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
              weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
              # In seconds, the keep-alive for HTTP and HTTPS requests
              weblogic.httpd.http.keepAliveSecs=180
              weblogic.httpd.https.keepAliveSecs=360
              # WEBLOGIC JDBC DRIVER PROPERTIES
              # Enables JDBC driver logging and sets the file name for the log
              # The weblogic.jdbc.logFile is placed in the per-server
              # directory
              weblogic.jdbc.enableLogFile=true
              weblogic.jdbc.logFileName=jdbc.log
              # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
              # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
              # in the per-cluster properties file ONLY.
              # For creating JDBC connection pools. This example shows a connection
              # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
              # to use 4 JDBC connections (with a potential for up to 10 connections,
              # incremented by two at a time, with a delay of 1 second between each
              # attempt to connect to the database), to an Oracle database server called
              # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
              # connections are dropped from the pool until only 4 connections remain open.
              # Every 10 minutes, any unused connections in the pool are tested and
              # refreshed if they are not viable.
              weblogic.jdbc.connectionPool.oraclePool=\
              url=jdbc:weblogic:oracle,\
              driver=weblogic.jdbc.oci.Driver,\
              loginDelaySecs=0,\
              initialCapacity=2,\
              maxCapacity=40,\
              capacityIncrement=2,\
              allowShrinking=true,\
              shrinkPeriodMins=15,\
              refreshMinutes=10,\
              testTable=dual,\
              props=user=pm;password=pm;server=APM
              # Get more details on each argument for this property in the
              # Administrators Guide on setting properties at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # Set up ACLs for this connection pool with the following:
              weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=apm_user
              #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=apm_user
              #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=apm_user
              weblogic.jdbc.TXDataSource.JtsDataSource=oraclePool
              weblogic.jdbc.DataSource.NonJtsDataSource=oraclePool
              # WEBLOGIC HTTP SERVLET PROPERTIES
              # CLUSTER USERS: Note that ALL servlets should be set up
              # in the per-cluster properties file ONLY.
              # WebLogic offers different types of servlets for various uses.
              # Classpath servlet registration
              # The ClasspathServlet is used to serve classes from
              # the system CLASSPATH. It is used by applets to load
              # classes they depend upon, and is registered against
              # the virtual name 'classes' here by default. This means
              # you should set your applet codebase to "/classes".
              # You can register multiple virtual names for this servlet.
              # Note that it can also be used to serve other
              # resources/files from the system CLASSPATH.
              # Don't confuse the ClasspathServlet with the ServletServlet. The
              # ClasspathServlet is used for serving classes for client-side Java only.
              # The ServletServlet is used to invoke unregistered servlets.
              # See the Administrators Guide "Setting up WebLogic as an HTTP server"
              # http://www.weblogic.com/docs51/admindocs/http.html#classfile for more info.
              weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
              # We also set an open ACL for everyone to call the ClasspathServlet
              # so that applets work without requiring further changes.
              weblogic.allow.execute.weblogic.servlet.classes=everyone
              # File servlet registration
              # FileServlet searches below the documentRoot for the requested file
              # and serves it if found. If the requested file is a directory,
              # FileServlet will append the defaultFilename to the requested path
              # and serve that file if found.
              weblogic.httpd.register.file=weblogic.servlet.FileServlet
              weblogic.httpd.indexDirectories=false
              weblogic.httpd.register.ourServlet=com.foo.bar.ourServlet
                   //our servlets registration//
              # ServerSideInclude servlet registration
              # SSIServlet searches below the documentRoot for the
              # requested .shtml file and serves it if found.
              weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
              # Example URL: http://localhost:7001/portside/welcome.shtml
              # for the file /weblogic/myserver/public_html/portside/welcome.shtml
              # PageCompileServlet (used by JHTML)
              # See the information below under WebLogic JHTML
              # JSPServlet (used by JSP)
              # See the information below under WebLogic JSP
              # ServletServlet registration
              # Allows unregistered servlets in the servlet classpath (see Servlet
              # reload properties below) to be requested by class name, including
              # full package name. An instance of the best matching servlet class
              # is created, initialized, and executed with the remainder of the
              # URI being passed in as PATH_INFO. Requires servlet classpath set.
              # This servlet registration is shipped commented out because it
              # may pose a security risk if improperly used. Please see the
              # Administrators Guide "Setting up WebLogic as an HTTP server"
              # at http://www.weblogic.com/docs51/admindocs/http.html for more info.
              weblogic.httpd.register.servlets=weblogic.servlet.ServletServlet
              # Example URL: http://localhost:7001/servlets/myservletclasses/foo/baz
              # for the file /myservlets/myservletclasses/foo/baz.class
              # DocumentRoot configuration
              # The documentRoot is by default set to this directory; change
              # as desired. FileServlet, SSIServlet, PageCompileServlet
              # and JSPServlet use it.
              weblogic.httpd.documentRoot=public_html/
              #weblogic.httpd.errorPage.500=/error.html
              #weblogic.httpd.errorPage.404=/error.html
              # Default servlet registration
              # Virtual name of the default servlet if no matching servlet is found
              weblogic.httpd.defaultServlet=file
              # Servlet reload properties
              # Put servlets and classes they depend on below this directory to take
              # advantage of dynamic reloading. (WebLogic classes don't belong
              # here, and NO directories can be both in your system/environment
              # CLASSPATH and in the servlet classpath.) WebLogic checks for modified
              # servlets every reloadCheckSecs and reloads servlets and classes they
              # depend on as needed. If reloadCheckSecs is set to -1, classes will
              # never be reloaded.
              weblogic.httpd.servlet.classpath=apmserver/servletclasses
              weblogic.httpd.servlet.reloadCheckSecs=1
         

  • Is Servlet failover supported by WebLogic5.1

              Hi,
              I want to know whether servlet failover is supported
              by WebLogic5.1. To illustrate with an example:
              I have a server instance(which is part of cluster)
              which is running a servlet. If the Server instance
              fails when the servlet service method is in progress,
              will the failover happen? I mean will the secondary
              server re-invoke the service method of the servlet?
              I have tried Servlet failover with weblogic clusters
              and it simply doesnt work.
              For Object(EJB) clustering there is an option of
              declaring the Object as idempotent, but in case
              of servlets there is no such provision. Shouldn't
              Servlets be idempotent by default?
              Any ideas/comments about the same will be appreciated.
              Regards,
              Amol
              ><
              

              if ConnectTimeoutSecs is less than HungServerRecoverSecs
              then
              wouldn't the connection timeout occur before server fail-over
              happens?
              Viresh Garg <[email protected]> wrote:
              >
              >
              >Amol wrote:
              >
              >> Hello.
              >> Thanks Mike, Kumar and Glen for your responses.
              >> I got another query, but before that, just
              >a couple
              >> of notings from my experiences with weblogic
              >> clustering - servlet failure. (Our configuration
              >> uses iPlanet Webserver with NSAPI plugin)
              >>
              >> --- NOTINGS ---
              >> In the obj.conf file, i needed to add the
              >following
              >> parameters: HungServerRecoverSecs, ConnectRetrySecs,
              >> ConnectTimeoutSecs. Also I noted that(correct
              >me if
              >> i'm wrong) the foll relation ought to be maintained
              >> to allow Servlet failover to take place:
              >> "ConnectRetrySecs < HungServerRecoverSecs
              >< ConnectTimeoutSecs"
              >
              >There is no connection of connectretrySecs and
              >HungServerRecoverSecs.
              >
              >HungServerRecoverSecs means we connected to
              >WLS successfully and now
              >waiting for response in proxy code, if response
              >doesn't come back in
              >these many secs, we assume server is hung (
              >you can connect to it but
              >can't get a response back) and we do failover.
              >
              >ConnectRetrySecs is the time for which we sleep
              >before retrying once we
              >have tried all the servers in static and dynamic
              >list and we couldn't
              >connect to a server.
              >
              >ConnectTimeoutSecs is the time upto which we
              >will keep on sleeping and
              >trying to connect to a server in loop until
              >we can either connect, or
              >connection timeout has expired.
              >
              >Viresh Garg
              >Principal Developer Relations Engineer
              >BEA Systems
              >
              >>
              >>
              >> This is not mentioned in the docs and more
              >importantly
              >> the default values assigned to these parameters
              >do
              >> NOT satisfy the above mentioned condition
              >hence even
              >> though Servlets may be IDEMPOTENT by default
              >as Kumar
              >> points out, Servlet fail-over would not work.
              >>
              >> Also some coding change is required if one
              >is using
              >> servlet calling Beans in a transaction. We
              >need to
              >> maintain servlet-level transactions by setting
              >a flag
              >> in the session.
              >> --- END OF NOTING ---
              >>
              >> Finally the new query :)
              >> "Consider the foll scenario:
              >> Request comes to Servlet, is fwded to SessionBean
              >> which calls multiple methods on EntityBean
              >in a
              >> SINGLE transaction. Now consider the situation
              >> wherein the app server continues working fine,
              >> but network connection for the machine hosting
              >the
              >> app server is disconnected. The proxy receives
              >no
              >> response from the concerned app server and
              >fails over
              >> to the secondary server. However the first
              >app server
              >> cannot perform the update because of the lock
              >n the
              >> DB by the first app server. How does one resolve
              >such
              >> a situation?"
              >>
              >> We simulated this situation by removing the
              >network
              >> cord while the transaction was in progress...
              >and the
              >> response to the client was an ugly "Proxy
              >failed"
              >> error!
              >>
              >> Thanks and Best Regards,
              >>
              >> Amol
              >> ><
              >> Any ideas would be greatly appreciated.
              >> I think we need to
              >>
              >> glen wilcox <[email protected]> wrote:
              >> >I guess we are all assuming that one of the
              >"Bridge" products
              >> >(Netscape,Apache) is being used otherwise
              >idempotent
              >> >doesn't apply. The
              >> >failover will work but you need a proxy server
              >in front
              >> >of the cluster.
              >> >If you are using the session you will also
              >need to configure
              >> >for session
              >> >replication.
              >> >
              >> >Glen
              >> >
              >> >Kumar Allamraju wrote:
              >> >
              >> >> BTW, idempotent is "ON" by default
              >> >>
              >> >> Mike Reiche wrote:
              >> >>
              >> >> > Look for an 'idempotent' setting for
              >specific URLs.
              >> >> >
              >> >> > http://www.weblogic.com/docs51/admindocs/nsapi.html
              >> >> >
              >> >> > Mike
              >> >> >
              >> >> > "Amol" <[email protected]> wrote:
              >> >> > >
              >> >> > >Hi,
              >> >> > >I want to know whether servlet failover
              >is supported
              >> >> > >by WebLogic5.1. To illustrate with an
              >example:
              >> >> > >I have a server instance(which is part
              >of cluster)
              >> >> > >which is running a servlet. If the Server
              >instance
              >> >> > >fails *when the servlet service method
              >is in progress*,
              >> >> > >will the failover happen? I mean will
              >the secondary
              >> >> > >server re-invoke the service method
              >of the servlet?
              >> >> > >
              >> >> > >I have tried Servlet failover with weblogic
              >clusters
              >> >> > >and it simply doesnt work.
              >> >> > >
              >> >> > >For Object(EJB) clustering there is
              >an option of
              >> >> > >declaring the Object as idempotent,
              >but in case
              >> >> > >of servlets there is no such provision.
              >Shouldn't
              >> >> > >Servlets be idempotent by default?
              >> >> > >
              >> >> > >Any ideas/comments about the same will
              >be appreciated.
              >> >> > >
              >> >> > >Regards,
              >> >> > >Amol
              >> >> > >><
              >> >
              >
              

  • How to Configure a Servlet Chain Using MIME Types with weblogic5.1?

    Hi ,
              I want to configure a servlet(cocoon) in weblogic 5.1 such that the
              servlet so configured is invoked each
              time a response with the mime-type "text/xml" is generated.
              1.) will weblogic support to configure a servlet with a particular
              mime-type so that it post-process any
              servlet's response with the corresponding mime-type?
              2.) if not what is the alternative?
              Thanks
              sumanth
              [sumo.vcf]
              

    We suggest that use the request dispatcher interface instead. Servlet
              chaining is not a standard's based possibility.
              Michael Girdley
              WLS Product Manager
              Sumanth Chinthagunta <[email protected]> wrote in message
              news:[email protected]..
              > Hi ,
              > I want to configure a servlet(cocoon) in weblogic 5.1 such that the
              > servlet so configured is invoked each
              > time a response with the mime-type "text/xml" is generated.
              > 1.) will weblogic support to configure a servlet with a particular
              > mime-type so that it post-process any
              > servlet's response with the corresponding mime-type?
              > 2.) if not what is the alternative?
              >
              > Thanks
              > sumanth
              >
              

  • How to support 30+ clients using weblogic5.1 with hpux11.0

    Hi,all
    I am using weblogic 5.1 in hp ux 11.0, and we are doing stress test ,
    with
    little numbers (<20)clients, it can work properly,but when the client number
    increase to nearly 30, the speed is very
    slow,and then weblogic server hangs.
    we are using java t3 client ,and some session beans running in welogic
    server to do some simple query.
    the environment is :
    hpux 11.0,weblogic5.1 with sp6,
    jdk1.2.2_02, oracle database 805,
    weblogic oci driver .
    executeThreadCount=60.
    connection pool is min=20,max=100
    performance pack is used.
    the machine is a T280 with 512M ram,
    we are using min 320,max 384 for heap
    size.
    the problem:
    1.weblogic hangs as decriped before.
    2.the message in weblogic.log.
    Fri Oct 13 21:26:36 CST 2000:<I> <EJB> Enterprise JavaBeans
    initializing
    Fri Oct 13 21:26:44 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Admin.jar> EJB home interface:
    'tbcs.ejb.AdminHome' deployed bound to the JNDI name: 'Admin'
    Fri Oct 13 21:26:45 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_BankCollect.jar> EJB home interface:
    'tbcs.ejb.BankCollectHome' deployed bound to the JNDI name: 'BankCollect'
    Fri Oct 13 21:26:46 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_AccountService.jar> EJB home interface:
    'tbcs.ejb.AccountServiceHome' deployed bound to the JNDI name:
    'AccountService'
    Fri Oct 13 21:26:47 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_FraudProcess.jar> EJB home interface:
    'tbcs.ejb.FraudProcessHome' deployed bound to the JNDI name: 'FraudProcess'
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Resource.jar> EJB home interface:
    'tbcs.ejb.ResourceHome' deployed bound to the JNDI name: 'Resource'
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB> 5 EJB jar files loaded, containing 5
    EJBs
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB> 5 deployed, 0 failed to deploy.
    Fri Oct 13 21:26:50 CST 2000:<I> <HTTP> Log rotation is size based
    Fri Oct 13 21:26:50 CST 2000:<I> <ZAC> ZAC ACLs initialized
    Fri Oct 13 21:26:50 CST 2000:<I> <ZAC> ZAC packages stored in local
    directory /o8i/weblogic/zac
    Fri Oct 13 21:26:50 CST 2000:<I> <WebLogicServer> Invoking main-style
    startup initDataBuffer tbcs.common.InitDataBuffer
    Fri Oct 13 21:27:10 CST 2000:<I> <Security> Switched to user weblogic
    Fri Oct 13 21:27:10 CST 2000:<I> <ListenThread> Listening on port: 80
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> System has file
    descriptor limits of - soft: '2048', hard: '2048'
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> Using effective
    file descriptor limit of: '2048' open sockets/files.
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> Allocating: '3'
    POSIX reader threads
    Fri Oct 13 21:27:11 CST 2000:<I> <WebLogicServer> WebLogic Server started
    Fri Oct 13 21:30:04 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:04 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:19 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:47 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:48 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:37 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:37 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:40 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:41 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:41 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:42 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:42 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:32:53 CST 2000:<I> <ServletContext-General> temp: init
    Fri Oct 13 21:33:29 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:33:29 CST 2000:<I> <CliCon-#|myserver|0.971443580882>
    Connection to client for ClientContext - id: '#|myserver|0.971443580882',
    bound: 'true', dead: 'false' has been unexpectedly lost because
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: No such file or directory: No such file or
    directory].
    Initiating hard disconnect.
    Fri Oct 13 21:33:29 CST 2000:<I> <CliCon-#|myserver|0.971443580882> Removing
    ClientContext - id: '#|myserver|0.971443580882', bound: 'false', dead:
    'false' because of hard disconnect timeout
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1793.
    7
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1792.
    6
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1790.
    5
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1788.
    4
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1775.
    3
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1774.
    2
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1773.
    1
    Fri Oct 13 21:34:07 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:34:07 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:34:14 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:14 CST 2000:<I> <ServletContext-General> Do: init
    Fri Oct 13 21:35:14 CST 2000:<I> <ServletContext-General> touchWhere: init
    Fri Oct 13 21:35:18 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:19 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> AdminProps: init
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> result: init
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> T3AdminMain: init
    Fri Oct 13 21:35:23 CST 2000:<I> <ServletContext-General> touch: init
    Fri Oct 13 21:35:23 CST 2000:<I> <ServletContext-General> classes: init
    Fri Oct 13 21:35:24 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> AdminEvents: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> AdminMain: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> *.shtml: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> do: init
    Fri Oct 13 21:35:26 CST 2000:<I> <ServletContext-General> agentsigncnt: init
    Fri Oct 13 21:35:28 CST 2000:<I> <ServletContext-General> snoop: init
    Fri Oct 13 21:35:28 CST 2000:<I> <ServletContext-General> drp-publish: init
    Fri Oct 13 21:35:29 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:30 CST 2000:<I> <ServletContext-General> where: init
    Fri Oct 13 21:35:31 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:31 CST 2000:<I> <ServletContext-General> touchTree: init
    Fri Oct 13 21:35:31 CST 2000:<I> <TX> Transaction TxC (7365032, xid =
    971443586063_1418, timeout = 300, txState = Rolledback, root = null rolled
    back because client is no longer alive
    Fri Oct 13 21:35:32 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Admin.jar> Exception during commit of
    transaction: '971443586063_1418'
    javax.transaction.RollbackException: Transaction TxC (7365032, xid =
    971443586063_1418, timeout = 300, txState = Rolledback, root = null has been
    rolled back.Reason: Transaction rolled back because client disconnected
    at
    weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CoordinatorImpl
    .java:731)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:352)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at
    weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.
    java:88)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:740)
    at tbcs.ejb.AdminBeanEOImpl.logWorkContext(AdminBeanEOImpl.java:2979)
    at tbcs.ejb.AdminBeanEOImpl_WLSkel.invoke(AdminBeanEOImpl_WLSkel.java:1864)
    at
    weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    at
    weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:69)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:32 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:35:32 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:40 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> servletimages:
    init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> applet: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> ConsoleHelp: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> DO: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> cookies: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> helloKona: init
    Fri Oct 13 21:35:41 CST 2000:<I> <ServletContext-General> survey: init
    Fri Oct 13 21:35:45 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:48 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:49 CST 2000:<I> <ServletContext-General> touchMain: init
    Fri Oct 13 21:35:49 CST 2000:<I> <ServletContext-General> AdminJDBC: init
    Fri Oct 13 21:35:50 CST 2000:<I> <ServletContext-General>
    AdminCaptureRootCA: init
    Fri Oct 13 21:35:50 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:51 CST 2000:<I> <ServletContext-General> recommand: init
    Fri Oct 13 21:35:51 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:35:51 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> touchLogin: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> session: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> dO: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> touchExecute: init
    Fri Oct 13 21:35:53 CST 2000:<I> <ServletContext-General> AdminRealm: init
    Fri Oct 13 21:35:53 CST 2000:<I> <ServletContext-General> simple: init
    Fri Oct 13 21:35:55 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:58 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:58 CST 2000:<I> <ServletContext-General> admin: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> error: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> detail: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> AdminLicense: init
    Fri Oct 13 21:36:00 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:36:01 CST 2000:<I> <ServletContext-General> prolog: init
    Fri Oct 13 21:36:03 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> Certificate: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> helloWorld: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> AdminConnections:
    init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone:
    PhoneServlet.initialize: enter
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone:
    PhoneServlet.initialize: filename = /weblogic/examples/servlets/phonelist
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone: Phone
    servlet file not found. java.io.FileNotFoundException:
    /weblogic/examples/servlets/phonelist (No such file or directory)
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> drp-exports: init
    Fri Oct 13 21:36:41 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:36:41 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:36:44 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:44 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:45 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:45 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:47 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:48 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:37:02 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:06 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:07 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:37:07 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:37:10 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:13 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:41:14 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '1'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:14 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '2'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:25 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '3'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:26 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '4'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:27 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '5'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:27 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '6'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:28 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '7'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:29 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '8'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:44:33 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:44:33 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (4045094, xid =
    971443586063_2310, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (4616970, xid =
    971443586063_2312, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (2802643, xid =
    971443586063_2313, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (1996325, xid =
    971443586063_2314, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (6200418, xid =
    971443586063_2315, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (7140343, xid =
    971443586063_2316, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (331414, xid =
    971443586063_2317, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (41620, xid =
    971443586063_2318, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (3265875, xid =
    971443586063_2311, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90

    1. check out path settings
    2. check out read/write etc.. permissions
    3. no. of file descriptors
    "raymond zhang" <[email protected]> wrote:
    Hi,all
    I am using weblogic 5.1 in hp ux 11.0, and we are doing stress test ,
    with
    little numbers (<20)clients, it can work properly,but when the client number
    increase to nearly 30, the speed is very
    slow,and then weblogic server hangs.
    we are using java t3 client ,and some session beans running in welogic
    server to do some simple query.
    the environment is :
    hpux 11.0,weblogic5.1 with sp6,
    jdk1.2.2_02, oracle database 805,
    weblogic oci driver .
    executeThreadCount=60.
    connection pool is min=20,max=100
    performance pack is used.
    the machine is a T280 with 512M ram,
    we are using min 320,max 384 for heap
    size.
    the problem:
    1.weblogic hangs as decriped before.
    2.the message in weblogic.log.
    Fri Oct 13 21:26:36 CST 2000:<I> <EJB> Enterprise JavaBeans
    initializing
    Fri Oct 13 21:26:44 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Admin.jar> EJB home interface:
    'tbcs.ejb.AdminHome' deployed bound to the JNDI name: 'Admin'
    Fri Oct 13 21:26:45 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_BankCollect.jar> EJB home interface:
    'tbcs.ejb.BankCollectHome' deployed bound to the JNDI name: 'BankCollect'
    Fri Oct 13 21:26:46 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_AccountService.jar> EJB home interface:
    'tbcs.ejb.AccountServiceHome' deployed bound to the JNDI name:
    'AccountService'
    Fri Oct 13 21:26:47 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_FraudProcess.jar> EJB home interface:
    'tbcs.ejb.FraudProcessHome' deployed bound to the JNDI name: 'FraudProcess'
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Resource.jar> EJB home interface:
    'tbcs.ejb.ResourceHome' deployed bound to the JNDI name: 'Resource'
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB> 5 EJB jar files loaded, containing 5
    EJBs
    Fri Oct 13 21:26:49 CST 2000:<I> <EJB> 5 deployed, 0 failed to deploy.
    Fri Oct 13 21:26:50 CST 2000:<I> <HTTP> Log rotation is size based
    Fri Oct 13 21:26:50 CST 2000:<I> <ZAC> ZAC ACLs initialized
    Fri Oct 13 21:26:50 CST 2000:<I> <ZAC> ZAC packages stored in local
    directory /o8i/weblogic/zac
    Fri Oct 13 21:26:50 CST 2000:<I> <WebLogicServer> Invoking main-style
    startup initDataBuffer tbcs.common.InitDataBuffer
    Fri Oct 13 21:27:10 CST 2000:<I> <Security> Switched to user weblogic
    Fri Oct 13 21:27:10 CST 2000:<I> <ListenThread> Listening on port: 80
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> System has file
    descriptor limits of - soft: '2048', hard: '2048'
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> Using effective
    file descriptor limit of: '2048' open sockets/files.
    Fri Oct 13 21:27:10 CST 2000:<I> <Posix Performance Pack> Allocating: '3'
    POSIX reader threads
    Fri Oct 13 21:27:11 CST 2000:<I> <WebLogicServer> WebLogic Server started
    Fri Oct 13 21:30:04 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:04 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:19 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:20 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:47 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:30:48 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:37 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:37 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:38 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:39 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:40 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:41 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:41 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:42 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:31:42 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:32:53 CST 2000:<I> <ServletContext-General> temp: init
    Fri Oct 13 21:33:29 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:33:29 CST 2000:<I> <CliCon-#|myserver|0.971443580882>
    Connection to client for ClientContext - id: '#|myserver|0.971443580882',
    bound: 'true', dead: 'false' has been unexpectedly lost because
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: No such file or directory: No such file or
    directory].
    Initiating hard disconnect.
    Fri Oct 13 21:33:29 CST 2000:<I> <CliCon-#|myserver|0.971443580882> Removing
    ClientContext - id: '#|myserver|0.971443580882', bound: 'false', dead:
    'false' because of hard disconnect timeout
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1793.
    7
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1792.
    6
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1790.
    5
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1788.
    4
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1775.
    3
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1774.
    2
    Fri Oct 13 21:33:29 CST 2000:<I> <EventProxy> Auto Unregistered
    WEBLOGIC.ADMIN.6142101462458162217/-2108345596/6/80/80/7002/7002/80/-1/1773.
    1
    Fri Oct 13 21:34:07 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:34:07 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:34:14 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:14 CST 2000:<I> <ServletContext-General> Do: init
    Fri Oct 13 21:35:14 CST 2000:<I> <ServletContext-General> touchWhere: init
    Fri Oct 13 21:35:18 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:19 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> AdminProps: init
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> result: init
    Fri Oct 13 21:35:19 CST 2000:<I> <ServletContext-General> T3AdminMain: init
    Fri Oct 13 21:35:23 CST 2000:<I> <ServletContext-General> touch: init
    Fri Oct 13 21:35:23 CST 2000:<I> <ServletContext-General> classes: init
    Fri Oct 13 21:35:24 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> AdminEvents: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> AdminMain: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> *.shtml: init
    Fri Oct 13 21:35:25 CST 2000:<I> <ServletContext-General> do: init
    Fri Oct 13 21:35:26 CST 2000:<I> <ServletContext-General> agentsigncnt: init
    Fri Oct 13 21:35:28 CST 2000:<I> <ServletContext-General> snoop: init
    Fri Oct 13 21:35:28 CST 2000:<I> <ServletContext-General> drp-publish: init
    Fri Oct 13 21:35:29 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:30 CST 2000:<I> <ServletContext-General> where: init
    Fri Oct 13 21:35:31 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:31 CST 2000:<I> <ServletContext-General> touchTree: init
    Fri Oct 13 21:35:31 CST 2000:<I> <TX> Transaction TxC (7365032, xid =
    971443586063_1418, timeout = 300, txState = Rolledback, root = null rolled
    back because client is no longer alive
    Fri Oct 13 21:35:32 CST 2000:<I> <EJB JAR deployment
    /o8i/weblogic/hpcluster/ejb_Admin.jar> Exception during commit of
    transaction: '971443586063_1418'
    javax.transaction.RollbackException: Transaction TxC (7365032, xid =
    971443586063_1418, timeout = 300, txState = Rolledback, root = null has been
    rolled back.Reason: Transaction rolled back because client disconnected
    at
    weblogic.jts.internal.CoordinatorImpl.throwRollbackException(CoordinatorImpl
    ..java:731)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:352)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at
    weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.
    java:88)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:740)
    at tbcs.ejb.AdminBeanEOImpl.logWorkContext(AdminBeanEOImpl.java:2979)
    at tbcs.ejb.AdminBeanEOImpl_WLSkel.invoke(AdminBeanEOImpl_WLSkel.java:1864)
    at
    weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    at
    weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:69)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:32 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:35:32 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:40 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> servletimages:
    init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> applet: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> ConsoleHelp: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> DO: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> cookies: init
    Fri Oct 13 21:35:40 CST 2000:<I> <ServletContext-General> helloKona: init
    Fri Oct 13 21:35:41 CST 2000:<I> <ServletContext-General> survey: init
    Fri Oct 13 21:35:45 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:48 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:49 CST 2000:<I> <ServletContext-General> touchMain: init
    Fri Oct 13 21:35:49 CST 2000:<I> <ServletContext-General> AdminJDBC: init
    Fri Oct 13 21:35:50 CST 2000:<I> <ServletContext-General>
    AdminCaptureRootCA: init
    Fri Oct 13 21:35:50 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:51 CST 2000:<I> <ServletContext-General> recommand: init
    Fri Oct 13 21:35:51 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:35:51 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> touchLogin: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> session: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> dO: init
    Fri Oct 13 21:35:52 CST 2000:<I> <ServletContext-General> touchExecute: init
    Fri Oct 13 21:35:53 CST 2000:<I> <ServletContext-General> AdminRealm: init
    Fri Oct 13 21:35:53 CST 2000:<I> <ServletContext-General> simple: init
    Fri Oct 13 21:35:55 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:58 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:35:58 CST 2000:<I> <ServletContext-General> admin: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> error: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> detail: init
    Fri Oct 13 21:36:00 CST 2000:<I> <ServletContext-General> AdminLicense: init
    Fri Oct 13 21:36:00 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:36:01 CST 2000:<I> <ServletContext-General> prolog: init
    Fri Oct 13 21:36:03 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> Certificate: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> helloWorld: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> AdminConnections:
    init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone: init
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone:
    PhoneServlet.initialize: enter
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone:
    PhoneServlet.initialize: filename = /weblogic/examples/servlets/phonelist
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> phone: Phone
    servlet file not found. java.io.FileNotFoundException:
    /weblogic/examples/servlets/phonelist (No such file or directory)
    Fri Oct 13 21:36:08 CST 2000:<I> <ServletContext-General> drp-exports: init
    Fri Oct 13 21:36:41 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:36:41 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:36:44 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:44 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:45 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:45 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:46 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:47 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:36:48 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:37:02 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:06 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:07 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:37:07 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:37:10 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:13 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    java.io.IOException: No such file or directory
    Fri Oct 13 21:37:32 CST 2000:<E> <ConMan> Attempt to sendMsg using a closed
    connection
    Fri Oct 13 21:37:32 CST 2000:<E> <RJVM> Exception on send :
    weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection
    Fri Oct 13 21:41:14 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '1'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:14 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '2'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:25 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '3'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:26 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '4'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:27 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '5'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:27 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '6'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:28 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '7'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:41:29 CST 2000:<E> <ListenThread> Listen failed, failure
    count: '8'
    java.net.SocketException: No such file or directory
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    at java.net.ServerSocket.implAccept(ServerSocket.java:240)
    at java.net.ServerSocket.accept(ServerSocket.java:224)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:277)
    Fri Oct 13 21:44:33 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:44:33 CST 2000:<I> <JDBC Pool> Connection for pool "tbcsPool"
    created.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (4045094, xid =
    971443586063_2310, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (4616970, xid =
    971443586063_2312, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (2802643, xid =
    971443586063_2313, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (1996325, xid =
    971443586063_2314, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (6200418, xid =
    971443586063_2315, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (7140343, xid =
    971443586063_2316, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (331414, xid =
    971443586063_2317, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (41620, xid =
    971443586063_2318, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:49:30 CST 2000:<I> <TX> Transaction (TxC (3265875, xid =
    971443586063_2311, timeout = 300, txState = Marked Rollback, root = null)
    rolled back after 300 sec.
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Performance Pack> Failure in
    processSockets()
    java.net.SocketException: No such file or directory: No such file or
    directory
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:327)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
    Fri Oct 13 21:52:46 CST 2000:<E> <Posix Perfo

  • Getting an error while running the servlet

    getting an error while running the servlet
    Sep 3, 2008 2:09:48 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\app\UK-Dasari\product\11.1.0\db_1\bin;D:\oracle\product\10.2.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Java\jdk1.6.0_05\bin
    Sep 3, 2008 2:09:48 AM org.apache.coyote.http11.Http11Protocol init
    SEVERE: Error initializing endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1059)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 2:09:48 AM org.apache.catalina.startup.Catalina load
    SEVERE: Catalina.start
    LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1061)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 2:09:48 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 399 ms
    Sep 3, 2008 2:09:48 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Sep 3, 2008 2:09:48 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
    Sep 3, 2008 2:09:49 AM org.apache.coyote.http11.Http11Protocol start
    SEVERE: Error starting endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:513)
         at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:202)
         at org.apache.catalina.connector.Connector.start(Connector.java:1132)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 2:09:49 AM org.apache.catalina.startup.Catalina start
    SEVERE: Catalina.start:
    LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.start(Connector.java:1139)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 2:09:49 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 515 ms
    Sep 3, 2008 3:06:31 AM org.apache.coyote.http11.Http11Protocol pause
    INFO: Pausing Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:06:31 AM org.apache.catalina.connector.Connector pause
    SEVERE: Protocol handler pause failed
    java.lang.NullPointerException
         at org.apache.jk.server.JkMain.pause(JkMain.java:679)
         at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
         at org.apache.catalina.connector.Connector.pause(Connector.java:1074)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:489)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:06:32 AM org.apache.catalina.core.StandardService stop
    INFO: Stopping service Catalina
    Sep 3, 2008 3:06:33 AM org.apache.catalina.connector.MapperListener destroy
    WARNING: Error unregistering MBeanServerDelegate
    java.lang.NullPointerException
         at org.apache.catalina.connector.MapperListener.destroy(MapperListener.java:162)
         at org.apache.catalina.connector.Connector.stop(Connector.java:1180)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:519)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:06:33 AM org.apache.coyote.http11.Http11Protocol destroy
    INFO: Stopping Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:06:33 AM org.apache.catalina.connector.Connector stop
    SEVERE: Coyote connector has not been started
    Sep 3, 2008 3:06:54 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\app\UK-Dasari\product\11.1.0\db_1\bin;D:\oracle\product\10.2.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\
    Sep 3, 2008 3:06:54 AM org.apache.coyote.http11.Http11Protocol init
    SEVERE: Error initializing endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1059)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:06:54 AM org.apache.catalina.startup.Catalina load
    SEVERE: Catalina.start
    LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1061)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:06:54 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 369 ms
    Sep 3, 2008 3:06:54 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Sep 3, 2008 3:06:54 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
    Sep 3, 2008 3:06:54 AM org.apache.coyote.http11.Http11Protocol start
    SEVERE: Error starting endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:513)
         at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:202)
         at org.apache.catalina.connector.Connector.start(Connector.java:1132)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:06:54 AM org.apache.catalina.startup.Catalina start
    SEVERE: Catalina.start:
    LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.start(Connector.java:1139)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:06:54 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 526 ms
    Sep 3, 2008 3:07:05 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\app\UK-Dasari\product\11.1.0\db_1\bin;D:\oracle\product\10.2.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Java\jdk1.6.0_05\bin
    Sep 3, 2008 3:07:05 AM org.apache.coyote.http11.Http11Protocol init
    SEVERE: Error initializing endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1059)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:07:05 AM org.apache.catalina.startup.Catalina load
    SEVERE: Catalina.start
    LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1061)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:07:05 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 391 ms
    Sep 3, 2008 3:07:05 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Sep 3, 2008 3:07:05 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
    Sep 3, 2008 3:07:05 AM org.apache.coyote.http11.Http11Protocol start
    SEVERE: Error starting endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:513)
         at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:202)
         at org.apache.catalina.connector.Connector.start(Connector.java:1132)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:05 AM org.apache.catalina.startup.Catalina start
    SEVERE: Catalina.start:
    LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.start(Connector.java:1139)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:05 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 462 ms
    Sep 3, 2008 3:07:05 AM org.apache.catalina.core.StandardServer await
    SEVERE: StandardServer.await: create[8005]:
    java.net.BindException: Address already in use: JVM_Bind
         at java.net.PlainSocketImpl.socketBind(Native Method)
         at java.net.PlainSocketImpl.bind(Unknown Source)
         at java.net.ServerSocket.bind(Unknown Source)
         at java.net.ServerSocket.<init>(Unknown Source)
         at org.apache.catalina.core.StandardServer.await(StandardServer.java:373)
         at org.apache.catalina.startup.Catalina.await(Catalina.java:616)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:576)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:05 AM org.apache.coyote.http11.Http11Protocol pause
    INFO: Pausing Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:07:05 AM org.apache.catalina.connector.Connector pause
    SEVERE: Protocol handler pause failed
    java.lang.NullPointerException
         at org.apache.jk.server.JkMain.pause(JkMain.java:679)
         at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
         at org.apache.catalina.connector.Connector.pause(Connector.java:1074)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:489)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:645)
    Sep 3, 2008 3:07:06 AM org.apache.catalina.core.StandardService stop
    INFO: Stopping service Catalina
    Sep 3, 2008 3:07:06 AM org.apache.catalina.connector.MapperListener destroy
    WARNING: Error unregistering MBeanServerDelegate
    java.lang.NullPointerException
         at org.apache.catalina.connector.MapperListener.destroy(MapperListener.java:162)
         at org.apache.catalina.connector.Connector.stop(Connector.java:1180)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:519)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:645)
    Sep 3, 2008 3:07:06 AM org.apache.coyote.http11.Http11Protocol destroy
    INFO: Stopping Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:07:06 AM org.apache.catalina.connector.Connector stop
    SEVERE: Coyote connector has not been started
    Sep 3, 2008 3:07:14 AM org.apache.coyote.http11.Http11Protocol pause
    INFO: Pausing Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:07:14 AM org.apache.catalina.connector.Connector pause
    SEVERE: Protocol handler pause failed
    java.lang.NullPointerException
         at org.apache.jk.server.JkMain.pause(JkMain.java:679)
         at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
         at org.apache.catalina.connector.Connector.pause(Connector.java:1074)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:489)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:15 AM org.apache.catalina.core.StandardService stop
    INFO: Stopping service Catalina
    Sep 3, 2008 3:07:15 AM org.apache.catalina.connector.MapperListener destroy
    WARNING: Error unregistering MBeanServerDelegate
    java.lang.NullPointerException
         at org.apache.catalina.connector.MapperListener.destroy(MapperListener.java:162)
         at org.apache.catalina.connector.Connector.stop(Connector.java:1180)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:519)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:15 AM org.apache.coyote.http11.Http11Protocol destroy
    INFO: Stopping Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:07:15 AM org.apache.catalina.connector.Connector stop
    SEVERE: Coyote connector has not been started
    Sep 3, 2008 3:07:20 AM org.apache.catalina.core.AprLifecycleListener init
    INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\app\UK-Dasari\product\11.1.0\db_1\bin;D:\oracle\product\10.2.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Java\jdk1.6.0_05\bin
    Sep 3, 2008 3:07:20 AM org.apache.coyote.http11.Http11Protocol init
    SEVERE: Error initializing endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1059)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:07:20 AM org.apache.catalina.startup.Catalina load
    SEVERE: Catalina.start
    LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.initialize(Connector.java:1061)
         at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
         at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:792)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
         at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
    Sep 3, 2008 3:07:20 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 381 ms
    Sep 3, 2008 3:07:20 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Catalina
    Sep 3, 2008 3:07:20 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
    Sep 3, 2008 3:07:21 AM org.apache.coyote.http11.Http11Protocol start
    SEVERE: Error starting endpoint
    java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
         at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:513)
         at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:202)
         at org.apache.catalina.connector.Connector.start(Connector.java:1132)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:21 AM org.apache.catalina.startup.Catalina start
    SEVERE: Catalina.start:
    LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind:80
         at org.apache.catalina.connector.Connector.start(Connector.java:1139)
         at org.apache.catalina.core.StandardService.start(StandardService.java:457)
         at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:07:21 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 485 ms
    Sep 3, 2008 3:34:44 AM org.apache.coyote.http11.Http11Protocol pause
    INFO: Pausing Coyote HTTP/1.1 on http-80
    Sep 3, 2008 3:34:44 AM org.apache.catalina.connector.Connector pause
    SEVERE: Protocol handler pause failed
    java.lang.NullPointerException
         at org.apache.jk.server.JkMain.pause(JkMain.java:679)
         at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
         at org.apache.catalina.connector.Connector.pause(Connector.java:1074)
         at org.apache.catalina.core.StandardService.stop(StandardService.java:489)
         at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
         at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
         at org.apache.catalina.startup.Catalina.start(Catalina.java:577)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
    Sep 3, 2008 3:34:45 AM org.apache.catalina.core.StandardService stop
    INFO: Stopping service Catalina
    Sep 3, 2008 3:34:45 AM org.apache.catalina.connector.MapperListener destroy
    WARNING: Error unregistering MBeanServerDelegate
    java.lang.NullPointerE

    uk-dasari wrote:
    java.net.BindException: Address already in use: JVM_Bind:80You've another service (a HTTP server?) running on port 80.
    Either shut it down or assign the current server another port.

  • Servlets and EJBs in weblogic 5.1

              Me somebody can say like communicating servlet that this in a machine with Weblogic 5,1 with a EJB in another machine also with weblogic5.1
              When trying gives it to me Comunication Exception .
              But if I have the 2 in the same machine it works well
              

    We have the same scenario and had the same CommunicationException.
              We had the remote & home interfaces of the ejb and the helper classes
              avaliable
              to the server#1 , and still encountered the following CommunicationException
              Tue Feb 06 17:53:54 GMT+05:30 2001:<I> <ServletContext-General>
              scripInfoServletWAP25:
              ScripInfoServlet.init()javax.naming.CommunicationException [Root exception
              is weblogic.rmi.UnmarshalException: Unmarshalling return
               - with nested exception:
              [java.lang.ClassNotFoundException: class
              ITS.beans.order.ScripInfoSessionEJBHomeImpl_ServiceStub previously not
              found]]
              Tue Feb 06 17:53:54 GMT+05:30 2001:<E> <ServletContext-General> Servlet
              failed with Exception
              javax.servlet.ServletException: javax.naming.CommunicationException [Root
              exception is weblogic.rmi.UnmarshalException: Unmarshalling return
              - with nested exception:
              [java.lang.ClassNotFoundException: class
              ITS.beans.order.ScripInfoSessionEJBHomeImpl_ServiceStub previously not
              found]]
              at ITS.wap.ScripInfoServletWAP25.init(ScripInfoServletWAP25.java:83)
              at
              weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
              :390)
              at
              weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
              va, Compiled Code)
              at
              weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
              a:338)
              at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:16
              4)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :99)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:742)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:686)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.java:247)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
              Only when the jar file was made available to the server#1(i.e. present in
              weblogicclasspath but not deployed) was the servlet on server#1 able to call
              the ejb on server#2.
              When calling the ejb through a Java Application or through a servlet
              deployed on the same server as the ejb,
              the stub classes are not required to be specified in the weblogicclasspath.
              Has anybody else encountered a similar situation?
              Thanks in advance.
              Aparna
              "Cameron Purdy" <[email protected]> wrote in message
              news:[email protected]...
              > You can have a Servlet on server #1 talk to an EJB on server #2. It is
              > accomplished by having the client classes for the EJB available to the
              > Servlet on server #1 and using JNDI on server #1 to get initial context
              for
              > server #2 and using that to look up the EJB.
              >
              > (Sorry, no habla espanol.)
              >
              > --
              > Cameron Purdy
              > Tangosol, Inc.
              > http://www.tangosol.com
              > +1.617.623.5782
              > WebLogic Consulting Available
              >
              >
              > "Javier Fdez" <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > Me somebody can say like communicating servlet that this in a machine
              with
              > Weblogic 5,1 with a EJB in another machine also with weblogic5.1
              > > When trying gives it to me Comunication Exception .
              > > But if I have the 2 in the same machine it works well
              >
              >
              

  • Servlet not reachable by name in WebToGo

    Every time I launch a servlet from the debugger, it comes up with a url of http://<myserver>/servlets/servlet. The servlet becomes unreachable by name. This makes the servlet unreachable by other pages and servlets when debugging.
    I think this is occurs because everytime I launch a file for debugging, the file %JDEV_HOME%/myhtml/WebAppRunner.html runs first. In this file is a command to direct to the url described above.
    What changes do I need to make to reach a servlet by name?

    See the following topic in the JDeveloper online help:
    User Guides
    Developing Applications
    Developing Web Applications
    Developing Java Servlets
    Registering a Servlet
    You register your servlets with the Web-to-Go server via the Web Object Manager (available from the Wizards menu), by providing a path and classname for each servlet you want to run or debug in JDeveloper.
    This allows you to call one servlet from the other by the name and path you register.
    The servlets/servlet name is the 'default' used if the servlet is unregistered.
    This was all new to me, so thanks for helping me learn something new about the product!

  • How to invoke a servlet from an application-URGENT

    Hi,
              My requirement is as follows :
              I have to invoke a servlet from a client application. I am using
              java.net.URL and java.netURLConnection classes to
              open a connection and invoke the servlet.
              I am using WebLogic5.1
              my code snippet is as follows :
              URL url = new URL("http://localhost:7001/urlservlet");
              URLConnection connection = url.openConnection();
              connection.setRequestMethod("GET");
              connection.setDoOutput(true);
              connection.setDoInput(true);
              PrintStream outStream = new PrintStream( connection.getOutputStream() );
              outStream.print("message=hai");
              outStream.flush();
              outStream.close();
              When I execute the application, Webloigc server console is displaying the
              following line.
              <Listen Thread> Adding Address : <machine name><ip address>
              But the service method of servlet is not getting invoked at all.
              Help me to find the answer.
              Jeelani
              

    jeelani <[email protected]> wrote:
              > Hi Dimitri,
              > Thanks a lot.That worked for me.
              > But if I want to send java objects (Vectors,beans),what is the best way to
              > do it.
              > This is exactly what our requirement is..
              If you want to send Java object you have to use POST:
              URLConnection conn = ...
              conn.setDoOutput(true); // makes this a POST
              OutputStream os = conn.getOutputStream();
              ...write your objects here...
              os.flush();
              os.close();
              InputStream in = conn.getInputStream(); // sends data to the server and
              // opens input stream
              ..read servlet response..
              .. ot just close the stream...
              in.close();
              > my client application need to send some java components to our main server
              > located in our head office.The servlet will read the objects and execute the
              > functionality..
              > I really appreciate for the fast response from you.
              > Dimitri Rakitine <[email protected]> wrote in message
              > news:[email protected]...
              >> Try it like this:
              >>
              >> URL url = new URL("http://localhost:7001/urlservlet?message=hai");
              >> URLConnection connection = url.openConnection();
              >> InputStream in = connection.getInputStream();
              >> in.close();
              >>
              >>
              >> jeelani <[email protected]> wrote:
              >> > Thanks for the quick response.
              >>
              >> > Actually right now it doesn't matter whether it is by GET or by POST.
              >> > Add my clinet application just needs to send data to Servlet and nothing
              > to
              >> > get in return.Thats why I am using connection.getOutputStream().
              >>
              >> > since application will not be reading anything from servlet, I don't
              >> > think it is required to use connection.getInputStream().
              >> > (I am sorry, if I am wrong).
              >>
              >> > Can you please help me out. weblogic server is able to get the address
              >> > from where the request is coming. Only problem is servlet is not getting
              >> > invoked.
              >>
              >> > regards,
              >> > Jeelani
              >>
              >>
              >> > Dimitri Rakitine <[email protected]> wrote in message
              >> > news:[email protected]...
              >> >> Are you trying to do get or post? First you set method to GET
              >> >> and then you do the POST.
              >> >>
              >> >> And add InputStream is = connection.getInputStream() - that will
              >> >> result in HttpURLConnection sending data to the server and getting
              >> >> back the response.
              >> >>
              >> >> jeelani <[email protected]> wrote:
              >> >> > Hi,
              >> >>
              >> >> > My requirement is as follows :
              >> >>
              >> >> > I have to invoke a servlet from a client application. I am using
              >> >> > java.net.URL and java.netURLConnection classes to
              >> >> > open a connection and invoke the servlet.
              >> >>
              >> >> > I am using WebLogic5.1
              >> >>
              >> >> > my code snippet is as follows :
              >> >>
              >> >> > URL url = new URL("http://localhost:7001/urlservlet");
              >> >>
              >> >> > URLConnection connection = url.openConnection();
              >> >>
              >> >> > connection.setRequestMethod("GET");
              >> >> > connection.setDoOutput(true);
              >>
              >> >> > PrintStream outStream = new
              >> > PrintStream( connection.getOutputStream() );
              >> >> > outStream.print("message=hai");
              >> >> > outStream.flush();
              >> >> > outStream.close();
              >> >>
              >> >> > When I execute the application, Webloigc server console is displaying
              >> > the
              >> >> > following line.
              >> >>
              >> >> > <Listen Thread> Adding Address : <machine name><ip address>
              >> >>
              >> >> > But the service method of servlet is not getting invoked at all.
              >> >>
              >> >> > Help me to find the answer.
              >> >>
              >> >> > Jeelani
              >> >>
              >> >> --
              >> >> Dimitri
              >> >> http://dima.dhs.org
              >>
              >>
              >>
              >> --
              >> Dimitri
              >> http://dima.dhs.org
              Dimitri
              http://dima.dhs.org
              

  • Running multiple instances of same servlet

    I am trying to run multiple webapps off of the same weblogic5.1 instance.
              I have setup the webapps and they work individually, but I need one servlet
              to load at startup.
              I have only been able to do that by including it by name in
              weblogic.properties
              #webApp named
              weblogic.httpd.webApp.demand=d:/stat_forecast/
              #register servlet so it runs on startup
              weblogic.httpd.register.AppInitServlet=com.ai.servlets.AppInitServlet
              weblogic.httpd.initArgs.AppInitServlet=AppConfigFilename=d:/stat_forecast/pr
              operties/forecast.properties
              weblogic.system.startupClass.aiservlet=weblogic.servlet.utils.ServletStartup
              weblogic.system.startupArgs.aiservlet=servlet=AppInitServlet
              This works until I try to add another instance of AppInitServlet for a
              different webApp
              #webApp named
              weblogic.httpd.webApp.supply=d:/supply/
              #register servlet so it runs on startup
              weblogic.httpd.register.AppInitServletS=com.ai.servlets.AppInitServlet
              weblogic.httpd.initArgs.AppInitServletS=AppConfigFilename=d:/supply/supply.p
              roperties
              weblogic.system.startupClass.aiservletS=weblogic.servlet.utils.ServletStartu
              p
              weblogic.system.startupArgs.aiservletS=servlet=AppInitServletS
              The servlet does not run a second time.
              Is there a way to move the AppInitservlet to inside the webApp and maybe use
              the web.xml to start each one individually?
              Thank you for any insight
              John Norton
              Indent Inc
              John Norton
              Indent Inc.
              (Innovative decision technologies, inc.)
              [email protected]
              

    Replying to myself to try and clarify.
              We are trying to run 2 or more webapps, each webapp tryes to call the
              servlet AppInitServlet.
              The servlet will not allow more than one instance to be in a context.
              In tomcat the servlet works to give a separate instance for each app.
              "JohnNorton" <[email protected]> wrote in message
              news:[email protected]...
              > I have sp8 on one version and that does work for the load on startup. One
              > problem solved, thank you.
              > Second part of same problem
              > In tomcat where we were developing, we could have multiple instances
              of
              > the AppInitservlet (for different Apps) and it kept them all separate.
              > In WL51 it starts the first correctly, but does not keep them
              separate,
              > so the second instance does not happen. It is designed so that
              multiple
              > calls do not instantiate (this would normally be within one instance of
              one
              > App).
              > I had thought that if the servlet was load-on-startup from the webApp
              > web.xml file that they would be separate. Any more ideas or clues?
              >
              > Thank you
              >
              > John Norton
              >
              > "Dimitri Rakitine" <[email protected]> wrote in message
              > news:[email protected]...
              > > Try it with the latest service pack - load-on-startup in web.xml was not
              > > supported until sp8 or so.
              > >
              > > JohnNorton <[email protected]> wrote:
              > > > I am trying to run multiple webapps off of the same weblogic5.1
              > instance.
              > > > I have setup the webapps and they work individually, but I need one
              > servlet
              > > > to load at startup.
              > > > I have only been able to do that by including it by name in
              > > > weblogic.properties
              > >
              > > > --------------
              > > > #webApp named
              > > > weblogic.httpd.webApp.demand=d:/stat_forecast/
              > >
              > > > #register servlet so it runs on startup
              > > > weblogic.httpd.register.AppInitServlet=com.ai.servlets.AppInitServlet
              > > >
              >
              weblogic.httpd.initArgs.AppInitServlet=AppConfigFilename=d:/stat_forecast/pr
              > > > operties/forecast.properties
              > > >
              >
              weblogic.system.startupClass.aiservlet=weblogic.servlet.utils.ServletStartup
              > > > weblogic.system.startupArgs.aiservlet=servlet=AppInitServlet
              > > > ---------------
              > > > This works until I try to add another instance of AppInitServlet for a
              > > > different webApp
              > > > #webApp named
              > > > weblogic.httpd.webApp.supply=d:/supply/
              > >
              > > > #register servlet so it runs on startup
              > > > weblogic.httpd.register.AppInitServletS=com.ai.servlets.AppInitServlet
              > > >
              >
              weblogic.httpd.initArgs.AppInitServletS=AppConfigFilename=d:/supply/supply.p
              > > > roperties
              > > >
              >
              weblogic.system.startupClass.aiservletS=weblogic.servlet.utils.ServletStartu
              > > > p
              > > > weblogic.system.startupArgs.aiservletS=servlet=AppInitServletS
              > >
              > >
              > > > The servlet does not run a second time.
              > > > Is there a way to move the AppInitservlet to inside the webApp and
              maybe
              > use
              > > > the web.xml to start each one individually?
              > > > Thank you for any insight
              > >
              > > > John Norton
              > > > Indent Inc
              > > > --
              > > > *************************************************
              > > > John Norton
              > > > Indent Inc.
              > > > (Innovative decision technologies, inc.)
              > > > [email protected]
              > >
              > > > *************************************************
              > >
              > >
              > >
              > >
              > > --
              > > Dimitri
              >
              >
              >
              

Maybe you are looking for

  • Please Help! Should I buy a New MacBook Air (mid 2013) or iPhone 5S?

    Hey, guys!! I really really need your help! I'm in a bit of a tough situation here. I'm batteling between getting an iPhone 5S (I have an iPhone 4 so I'm waaaaay overdue for an upgrade) which I already saved up enough money for or saving up for a lit

  • GPU Rendering funktioniert nicht

    Sehr geehrte Community, ich kann weder mit Premiere Pro CC noch mit Media Encoder CC mit meiner GPU Rendern. Ich kann zwar den Unterpunkt Mercury Playback Engine (Cuda) auswählen, jedoch wird meine GPU nur zu 1-3% ausgelastet. Ich habe auch schon den

  • Infotype 0017 changes

    Hello All, I have one query from Infotype 0017 (Travel management). How to edit or select the indicator Trip Assigned under Employee has trips in Infotype 0017 as my user was able to select this before but now not. Please suggest. Thanks & Regards, E

  • How to copy a PLD in one database to another.

    Hi, How can we copy a PLD in one database to the other without using Copy Express. I tried openin up the PLD in the Test DB and copying it over to the Live DB, using Edit copy and Paste, but it doesn't work.... Is there any other way it can be done?

  • PopupMenuListener event on JComboBox fires multiple times per selection

              // webAddressBox IS OF TYPE javax.swing.JComboBox            webAddressBox.addPopupMenuListener(new PopupMenuAdapter() {                 /** @uses {@link com.ppowell.tools.ObjectTools.SimpleBrowser.Surf} */                 final Surf surf =