Strange InterruptedIOException

Question

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]
          

Answer 1

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=[e-mail],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