Mms to servlet general methodology?

I am working on a project that involves mobile device to servlet communication. It allows doctors to submit voice-recorded requests for medical information. The recorded data is run thru speech recognition and nlp software and used to generate various back-end queries for data. We are fairly clear about how to do this using local wi-fi connection to a server via http. We're also interested in using mobile messaging facilities for the same purpose. I understand that mobile messaging (text and multimedia) involves going out to a wireless gateway from the phone, and from there to a phone carrier's messaging center server (whose usual purpose is just to send the message back out to another wireless phone user). Does anyone know of methods whereby our application server could gain access to the wireless message, either by linking to the carrier's messaging center, or by any other means? Any tutorials or know of any existing projects that use a mobile phone message to send data to an application server? Thanks in advance...

Locutus wrote:
          > Is there a way to configure weblogic to allow more than 2 concurrent
          > accesses from the same client to the same servlet with the same session id?
          Servlets are concurrent by default regardless of the session unless you're
          using SingleThreadModel. It's your job to make sure shared data (instances
          stored in the session qualify) is thread-safe.
          Alex

Similar Messages

Newbie JSP/Servlet general question

Hi,
I am currently studying the life cycle of a JSP page from the Java EE 5 Tutorial (http://java.sun.com/javaee/5/docs/tutorial/doc/bnahe.html). This document says that: "+If an instance of the JSP pages servlet does not exist, the container loads the JSP pages servlet class, instantiates an instance of the servlet class, initializes the servlet instance by calling the jspInit method+".
My two questions are:
i) Does this JSP servlet implement the HttpJspPage interface defined in javax.servlet.jsp?
ii) Does Struts and Spring MVC provide such JSP servlet Java classes implementations or are these part of other packages? If not, which packages offer such implementations?
Thanks,
J.

Jrm wrote:
Hi,
I am currently studying the life cycle of a JSP page from the Java EE 5 Tutorial (http://java.sun.com/javaee/5/docs/tutorial/doc/bnahe.html). This document says that: "+If an instance of the JSP pages servlet does not exist, the container loads the JSP pages servlet class, instantiates an instance of the servlet class, initializes the servlet instance by calling the jspInit method+".
My two questions are:
i) Does this JSP servlet implement the HttpJspPage interface defined in javax.servlet.jsp?Yes.
>
ii) Does Struts and Spring MVC provide such JSP servlet Java classes implementations or are these part of other packages? If not, which packages offer such implementations?No, the implementation for the JSP servlet is usually provided by the Servlet Container, not a framework, since the Servlet Container is responsible for creating and compiling the JSP.
>
Thanks,
J.

Error 404 -- Not Found, when a Servlet is invoked from browser

Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
          even the simplest servlet.
          I painstakenly went through all the steps that are listed in the WebLogic
          Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
          have missed a step somewhere.
          I have modified the weblogic.properties file as per all the instrustions,
          but the server simply won't recognize any servlets, not even the SqlServlet
          that came with the server as an example.
          It would require more than 1 exchange of posts to resolve it for me, and I
          am wondering if one of you is willing to work with me on this until I have
          managed to configure the server to make a servlet work on it.
          The server does function as a Web server as I can run the index.html
          document by entering the URL: http://localhost:7001/index.html
          I am pasting the contents of weblogic.properties file below to get the
          person who is willing to help me started.
          The machine I have is a Pentium III with Windows 2000 Professional on it.
          It's a home machine and the WebLogic server is the freely downloadable
          version. I am using it to prepare for a potential contract work.
          I have managed to modify setEnv.cmd file and have managed to compile the
          SqlServlet.java, which is an example servlet. Neither this particular
          servlet nor a HelloWorld type of very basic servlet I have written are
          recognized by the server.
          As you can see from my weblogic.properties file (pasted at the end of this
          post), the SqlServlet has been registered. I have also uncommented the lines
          to allow for the following type of URL:
          http://localhost:7001/servlet/myServlet
          Thanks!
          Anjum Jaleel
          CONTENTS OF MY weblogic.properties file
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic XML demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JSP properties
          # WebLogic JHTML properties
          # WebLogic RMI over IIOP properties
          # User-written and demo servlet registrations
          # 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=lovkako1
          # 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=true
          # 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*
          # 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.administrator.location=3355 California Drive, West Hampshire, CA
          94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # 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=g:/weblogic/myserver/public_html/docs51/adminhel
          p/
          # 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:
          #weblogic.ejb.deploy=\
          # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
          # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
          # g:/weblogic/myserver/ejb_subclass.jar, \
          # g:/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=g:/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=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

Problem Resolved!
          I found out that I had 'http' instead of 'httpd' in the statement where I
          registered my servlet, SqlServlet.
          Now, I am having difficulty with hot deployment. The server is returning
          error 404.

In general, how do I put code into a loop?

I have access to a procedure that takes a parameter and spits out a single result. I need to figure out how to use that procedure and spit out many results. This example should clear things up.
VARIABLE enum NUMBER;
EXEC :enum := 7566;
-- my procedure. Cannot change code here.
-- Prints out a formatted name and job, given an empno stored in :enum
SELECT ename || ' (' || job || ')' AS "myrow"
FROM scott.emp
WHERE empno = :enum;
-- end of my procedureHere, I can't change anything from the SELECT to the semi-colon. Now I would like to put this into a PL/SQL LOOP, but I can't figure it out. Let's say I want to print out all of the employees with a job of manager. Somehow I will need enum to take the value of the current iteration from within the loop.
something like this:
BEGIN
-- first get the list of employees
CURSOR e_cur IS
SELECT empno
FROM scott.emp
WHERE job="MANAGER';
END;
BEGIN
FOR r_cur IN e_cur LOOP
:enum = r_cur.empno
-- my procedure. Cannot change code here.
-- Prints out a formatted name and job, given an empno stored in :enum
SELECT ename || ' (' || job || ')' AS "myrow"
FROM scott.emp
WHERE empno = :enum;
-- end of my procedure
END LOOP;
END;
{code}
of course, this code does not work, and I don't know what else to try.
Thanks in advance for any help!
Skip

Oh boy, do I owe you guys an apology. Absolutely no excuse, but I screwed up big time yesterday. I am working on a couple of projects and got some wires crossed. I would like to start over. Forget everything I asked yesterday. I wouldn't be surprised if no one answered, but I could still use some help. I am embarrassed because I am usually pretty good at these things, and again, I humbly apologize.
Still with me? Here we go:
I have a SQL script that is quite long. It has 25 select statements, 4 unions, 7 minus'es, lots of joins, sub-queries, etc. The script expects two bind variables to be set before running. The code was written to execute once (like a report). But the code does exactly what I need, but I need to run it on a much larger set. So I would like to wrap it in a loop. Now, I am pretty good at other programming languages (I know, hard to believe given yesterday's exchange). If I have some java code that I want to wrap in a FOR-NEXT loop, often all I need to do is put one line at the top of the code and one line at the bottom. Then I make sure the variables that need t be updated through each iteration are properly updated. Bada-bing, bada-boom, it's done.
It doesn't seem as easy here. I know that I will have to convert my SQL script to PL/SQL. But I am wrestling with the DECLAREs, BEGINs and LOOPs, and changes to the existing code to ensure the bind variables are updated each iteration. I have tried all of what I thought would be the simple solutions as I described with my java example above, but it has not worked. So, as my subject line indicates, I was wondering if there was a general methodology to LOOP-ifying existing code. I know this is a pretty nebulous question, and I probably blew it yesterday, but I really do need some help. Even if it is "read this and that website/book/etc". That's really it. sigh All that stuff yesterday about "unmodifiable code"--forget about that. I should never have said that. Anything goes.
Maybe there isn't a simple solution here. SQL isn't Java. And that's OK. At least then I will know I will need to look for a different solution or I will have to get a LOT smarter with SQL and PL/SQL. I thought my super-simple example yesterday was a good enough substitute for what I am faced with, but maybe that isn't a good assumption.

No MMS Setting in my Iphone4

I already upgraded my Iphone4 iOS from 4.1 to 4.3.3.
But, I noticed that some of the features that suppose appear in iOS 4.3.3 but not in my Iphone, such as:
1. MMS Setting in General-Network
2. Call forwarding cannot be setup....keep on turn off by itself even thought have enter the alternate telephone number
Anyone could answer and help me?

1st, thank you for your reply.
I have check the setting under the Message menu, and it was set as "ON", but I still can not locate the place for me to enter my carrier setting for the MMS. This MMS Setting are supposingly seated in the "Network" menu.

Legacy servlets

greetings,
I am used to working with apache servers with the tomcat servlet engine, which is compliant with the servlet 2.3 specs -- entails the concept of web applications that are self contained . I am now working with an s1ws , specifically on a virtual server, and two directories have been created for me: 'public_html' and 'classes'. The public_html directory contains jsp/html and static content. The classes directory contains the servlet packages and classes.
I am told that the servlet path is http:/domain_name:8000/servlet/ and I am also told that I must register the servlets with the server.
How does one go about registering the servlets with the web server. Is is as simple as creating a deployment descriptor and placing it in the classes directory? According to servlet 2.3 specs the classes directory is supposed to be inside of the WEB-INF directory which contains the file web.xml. I have no WEB-INF directory. Any one know what the deal is?
much obliged
-Mani

First, note that Web Server 6.1 supports Servlet 2.3 web applications and Web Server 6.0 supports Servlet 2.2 web applications.
"Legacy Servlets" refers to a Servlet deployment methodology that predates both Servlet 2.2 and Servlet 2.3 (and hence predates the concept of web applications). Legacy Servlet support was deprecated in Web Server 6.0 and removed in Web Server 6.1. For information on using Legact Servlets, refer to the Programmer's Guide to Servlets at http://docs.sun.com/db/prod/s1websrv#hic

Servlet implements MessageListener?

Is it possible to use a servlet that implements MessageListener?
I have an application that sends a JMS Message (gif format) into QueueA, the servlet needs to retrieve the Message from QueueA and write it into a file.
I understand that Message-Driven Beans are not recommended to use java.io package, somebody suggested a remedy to this -> use servlet to listen to the JMS Queue.
When I used a servlet that implements the MessageListener interface, the onMessage is not invoked.
The web.xml looks like:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'><web-app> <display-name>test</display-name> <servlet> <servlet-name>testServlet</servlet-name> <display-name>testServlet</display-name> <servlet-class>com.testServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>testServlet</servlet-name> <url-pattern>/test</url-pattern> </servlet-mapping> <session-config> <session-timeout>30</session-timeout> </session-config></web-app>Is there a more elegant solution to this problem?

It is also illegal to call setMessageListener from inside the web services container. Servlets generally do a synchronous receive().

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

WL Cluster with NES Proxy

We are evaluating the Cluster features of WebLogic and got a eval
          license for the Cluster Support.
          I am running a default cluster (mycluster) using the default Multicast
          address (237.0.0.1) and am seeing
          some strange behaviour/errors.
          Would appreciate some asistance in this matter.
          Our Environment
          I created directory in a shared file system to host the cluster.
          (h:\kkanth\weblogic)
          Created the mycluster directory and other directories as recommended in
          the Administrator's guide.
          I have two WL Servers (asera190 and asera162) with permanent IP
          addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
          I'm using a NES proxy on asera190 with the plugin for WL specified in
          obj.conf alongwith the other parameters.
          I'm able to have both the servers join to cluster mycluster and the WL
          Admin Console does display a tree that depicts the cluster as well as
          servers in it (server61 and server70). The individual server directories
          are being created in h:\kkanth\weblogic\mycluster directory with the
          appropriate access.log and weblogic.log files.
          When a browser attempts to access a URL such as
          http://asera190/weblogic/snoop it does return the proper response, but
          all requests are processed by asera162 which is listed first in the
          obj.conf. Opening multiple sessions does not cause the requests to be
          sent to asera190 which is the second server in the cluster. When
          asera162 is shutdown and removed from the cluster, I hoped that
          subsequent requests would go to asera190. However , depending on the
          origin of the request, different errors were thrown. If I try to access
          http://asera190/weblogic/snoop from a browser on asera190, I get an
          error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
          from asera162 cause "Failure at line 706 of file proxy.cpp".
          I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
          directory as well as the obj.conf file in the ....\config\ directory of
          asera190.
          We are running NES 3.5.1 and have setup proxy35.dll appropriately.
          weblogic.properties
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in
          this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs45/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # T3AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file
          should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except
          those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JHTML properties
          # User-written and demo servlet registrations
          # 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/docs45/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/docs45/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=kaykayka
          # 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/docs45/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.ClientAuthenticationServlet
          # Limits number of unclaimed stored tokens
          weblogic.security.certificateCacheSize=3
          # Capture CA root of client servlet
          weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
          # 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*
          # 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.administrator.location=3355 California Drive, West Hampshire,
          CA 94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # 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=d:/weblogic/myserver/public_html/docs/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/docs45/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/docs45/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
          # Other system startup files for use with VisiBroker
          # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
          # You must have installed Visigenic 2.5 for use with
          # the WebLogic Server before you uncomment these properties
          #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
          #weblogic.system.startupArgs.dovisi=\
          # clientName=T3Client Manager,\
          # connName=T3Connection Manager
          # 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/docs45/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.SimpAppServlet
          # 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.statefulSession.Trader 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 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.multihello=examples.rmi.multihello.HelloImpl
          #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          # 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=\
          # d:/weblogic/myserver/cluster_ejb.jar, \
          # 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_isModified.jar, \
          # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
          # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
          # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
          # d:/weblogic/myserver/ejb_subclass.jar, \
          # d:/weblogic/myserver/jolt_ejb_bankapp.jar
          # Servlets used by the EJB basic examples beanManaged and
          # containerManaged. Uncomment to use:
          #weblogic.httpd.register.beanManaged=\
          # examples.ejb.basic.beanManaged.Servlet
          #weblogic.httpd.register.containerManaged=\
          # examples.ejb.basic.containerManaged.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.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
          #weblogic.password.user1=user1Password
          #weblogic.password.user2=user2Password
          # 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
          # 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/docs45/admindocs/properties.html
          # Set up ACLs for this connection pool with the following:
          #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
          # 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

Try the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
          Init fn="load-types" mime-types="mime.types"
          Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
          Init fn="wl-init"
          Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
          \"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
          <Object name="tg" ppath="*/weblogic/*">
          Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
          </Object>
          <Object name="default">
          NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
          NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
          NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
          NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
          PathCheck fn="nt-uri-clean"
          PathCheck fn="check-acl" acl="default"
          PathCheck fn="find-pathinfo"
          PathCheck fn="find-index" index-names="index.html,home.html"
          ObjectType fn="type-by-extension"
          ObjectType fn="force-type" type="text/plain"
          Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
          Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
          Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
          Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
          AddLog fn="flex-log" name="access"
          </Object>
          <Object ppath="/usr/suitespot/docs/.perf">
          Service fn="service-dump"
          </Object>
          <Object name="cgi">
          ObjectType fn="force-type" type="magnus-internal/cgi"
          Service fn="send-cgi"
          </Object>
          Hope this helps
          Krishna Kanth wrote:
          > We are evaluating the Cluster features of WebLogic and got a eval
          > license for the Cluster Support.
          > I am running a default cluster (mycluster) using the default Multicast
          > address (237.0.0.1) and am seeing
          > some strange behaviour/errors.
          > Would appreciate some asistance in this matter.
          >
          > Our Environment
          > ----------------
          >
          > I created directory in a shared file system to host the cluster.
          > (h:\kkanth\weblogic)
          > Created the mycluster directory and other directories as recommended in
          > the Administrator's guide.
          >
          > I have two WL Servers (asera190 and asera162) with permanent IP
          > addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
          > I'm using a NES proxy on asera190 with the plugin for WL specified in
          > obj.conf alongwith the other parameters.
          >
          > I'm able to have both the servers join to cluster mycluster and the WL
          > Admin Console does display a tree that depicts the cluster as well as
          > servers in it (server61 and server70). The individual server directories
          > are being created in h:\kkanth\weblogic\mycluster directory with the
          > appropriate access.log and weblogic.log files.
          >
          > When a browser attempts to access a URL such as
          >
          > http://asera190/weblogic/snoop it does return the proper response, but
          > all requests are processed by asera162 which is listed first in the
          > obj.conf. Opening multiple sessions does not cause the requests to be
          > sent to asera190 which is the second server in the cluster. When
          > asera162 is shutdown and removed from the cluster, I hoped that
          > subsequent requests would go to asera190. However , depending on the
          > origin of the request, different errors were thrown. If I try to access
          > http://asera190/weblogic/snoop from a browser on asera190, I get an
          > error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
          > from asera162 cause "Failure at line 706 of file proxy.cpp".
          >
          > I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
          > directory as well as the obj.conf file in the ....\config\ directory of
          > asera190.
          >
          > We are running NES 3.5.1 and have setup proxy35.dll appropriately.
          >
          > weblogic.properties
          > *********
          > # THE WEBLOGIC PROPERTIES FILE
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # This file, which conforms to the java.util.Properties file
          > # definition, configures your WebLogic products. You cannot run
          > # WebLogic Server without setting required configuration properties in
          > this
          > # file. Required properties are marked and appear first in the file.
          > #
          > # Details on each entry and important information about configuration
          > # and security are documented on our website. Please go to:
          > #
          > # http://www.weblogic.com/docs45/admindocs/properties.html
          > #
          > # for full instructions on how to edit this file.
          > #
          > # You do not need to include properties in this file unless you want to
          > # change the default, embedded property. Some properties on the
          > # T3AdminProps page are not listed here because the default property
          > # is being used. You can change the default by adding the property and
          > # its value to this file.
          > #
          > # You cannot set weblogic.system.home in this file, since the WebLogic
          > Server
          > # must know where home is in order to retrieve this file. You can
          > # change WebLogic home on the command line when you start the
          > # WebLogic Server.
          > #
          > # CLUSTER USERS: Note that the (shared) per-cluster properties file
          > should
          > # contain most all of the properties in this file. The only properties
          > # that potentially belong in a per-server properties file for a server
          > # running in a cluster are the registration (startup class) of pinned
          > # RMI objects, and a few tuning properties that may be different for
          > # servers in the cluster, depending upon hardware and memory. If you use
          >
          > # a per-server properties file, please REMOVE all properties except
          > those
          > # that are specifically required in the per-server properties file. You
          > # can find specific notes on clusters by searching through this file for
          >
          > # "CLUSTER USERS".
          > #
          > # -------------------------------------------------
          > # The way this file is organized:
          > # Core properties (includes REQUIRED and RECOMMENDED)
          > # Core system properties
          > # Core security-related properties
          > # Core security-related properties for SSL
          > # Core HTTPD administrative properties
          > #
          > # Optional properties
          > # Administrator properties
          > # System properties
          > # System startup files
          > # System shutdown files
          > # Security-related properties for Workspaces
          > # Jolt for WebLogic properties
          > # WebLogic Enterprise Connectivity properties
          > # WebLogic File properties
          > # WebLogic JMS demo properties
          > # WebLogic RMI demo properties
          > # WebLogic EJB demo properties
          > # WebLogic ZAC demo properties
          > # HTTPD administrative properties
          > # WebLogic JDBC driver properties
          > # WebLogic JDBC connection pool management
          > # WebLogic demo connection pool
          > # WebLogic HTTP Servlet properties
          > # Proxy servlet registration
          > # Classpath servlet registration
          > # File servlet registration
          > # ServerSideInclude servlet registration
          > # PageCompileServlet (used by JHTML)
          > # JSPServlet (used by JSP)
          > # ServletServlet registration
          > # Servlet reload properties
          > # Servlet ACLs
          > # WebLogic JHTML properties
          > # User-written and demo servlet registrations
          > # -------------------------------------------------
          >
          > #################################################################
          > # 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/docs45/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/docs45/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=kaykayka
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # 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/docs45/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.ClientAuthenticationServlet
          >
          > # Limits number of unclaimed stored tokens
          > weblogic.security.certificateCacheSize=3
          > # Capture CA root of client servlet
          > weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
          >
          > # 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*
          >
          > #################################################################
          > # 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.administrator.location=3355 California Drive, West Hampshire,
          > CA 94104
          > #weblogic.administrator.name=Joe Administrator
          > #weblogic.administrator.phone=1 415 555 1234
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # 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=d:/weblogic/myserver/public_html/docs/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/docs45/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/docs45/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
          > #
          > # Other system startup files for use with VisiBroker
          > # ------------------------------------------------
          > # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
          > # You must have installed Visigenic 2.5 for use with
          > # the WebLogic Server before you uncomment these properties
          > #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
          >
          > #weblogic.system.startupArgs.dovisi=\
          > # clientName=T3Client Manager,\
          > # connName=T3Connection Manager
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # 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/docs45/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.SimpAppServlet
          >
          > #
          > # 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.statefulSession.Trader 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 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.multihello=examples.rmi.multihello.HelloImpl
          >
          > #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # 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=\
          > # d:/weblogic/myserver/cluster_ejb.jar, \
          > # 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_isModified.jar, \
          > # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
          >
          > # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
          > # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
          > # d:/weblogic/myserver/ejb_subclass.jar, \
          > # d:/weblogic/myserver/jolt_ejb_bankapp.jar
          > #
          > # Servlets used by the EJB basic examples beanManaged and
          > # containerManaged. Uncomment to use:
          > #weblogic.httpd.register.beanManaged=\
          > # examples.ejb.basic.beanManaged.Servlet
          > #weblogic.httpd.register.containerManaged=\
          > # examples.ejb.basic.containerManaged.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.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
          >
          > #weblogic.password.user1=user1Password
          > #weblogic.password.user2=user2Password
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # 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 t

Getting Session Info In A Normal Class

I want to get session info from a class that is not servlet (generally from in a bean). When we use servlets it is so easy to get session info by just using request.getSession() method. Is it possible to get this session info in a normal class which is not servlet Technology?

Is it possible to get this session info in a normal class which is not >servlet Technology? No reason you cannot.
But do remember that normal java classes which arent Servlets/Jsps arent invoked by the container as part of the standard request processing.
Beans, for example, are instantiated (& reused) from within a Servlet or a Jsp.
So all you have to do is retrieve the session info (or a part thereof) from within a Servlet/Jsp that's part of the request cycle and pass this data onto the bean when you invoke its methods.
ram.

Insert BLOB error in IAS but not in JDeveloper

Hi
Our application have a Servlet who executes an INSERT using a PrepareStatement (created by the Transaction of an ApplciationModule)
In Jdeveloper (10.1.2) this works OK
But when deploy it in the IAS (904) we have an error:
java.sql.SQLException: Io exception: Connection reset
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:345)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2094)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1986)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2697)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:457)
at com.asorco.sgie.controller.servlets.general.Archivo.uploadFile(Archivo.java:176)
at com.asorco.sgie.controller.servlets.general.Archivo.doPost(Archivo.java:118)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:733)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.ja
va:192)
at java.lang.Thread.run(Thread.java:534)
In the IAS, Im using the jars used in JDeveloper (classes12.jar, classes12dms.jar, nls_classes12.jar).
Any knows the reason?
Thank you!

          The effect to use <jsp:forward> or RequestDispatcher.forward is different between
          BEA and Tomcat (even Websphere). Weblogic stores the output in a buffer, before
          the buffer reaches the limit, you can call those forward methods without obvious
          problems. Tomcat (and Websphere I ever tested) is not so tolerable. If you have
          send out something via Servlet writer or JSPWriter, or have something like HTML
          tags/text before forwards, chances are big to encounter the exceptions you have.
          So I use more include methods to assemble my JSPs and servlets, for the purpose
          of portability.
          "Aidan Monroe" <[email protected]> wrote:
          >
          >I have a .war file that runs perfectly in WebLogic 7.0. Today I tried
          >to run that
          >same .war in Tomcat 4.0.6. Unfortunately, it did not run. I get the following
          >error:
          >
          >java.lang.IllegalStateException: Cannot forward after response has been
          >committed
          >
          >Now, I know what this error means, but I don't know why I would get it
          >when I
          >run in Tomcat but not WebLogic. Does WebLogic do something to "insulate"
          >me from
          >this error that perhaps Tomcat does not do?
          >
          >Aidan
          >

Deployed EJB Not Bound

I deplyed a simple EJB on S17AS. The server.log tells me it is deployed successful.
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1017ca1
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@9d5793
LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
The relevant simpleEjb.jar_verified.txt is as follows
     Test Name : tests.ejb.ias.ASEjbJndiName
     Test Assertion :
     Test Description : PASSED [AS-EJB ejb] : jndi-name is simpleHome
However, the server log did not indicate the EJB is bound even if I set the log level to finest.
Therefore when I tried to access it, I get the following error
Exception in thread "main" javax.naming.NameNotFoundException: No object bound f
or java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
ava:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:61)
The client code is as follows
String JNDIName = "java:comp/env/ejb/simpleHome";
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(
               initContext.lookup(JNDIName), GreeterDBHome.class);
The sun-ejb-jar.xml is as follows
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd'>
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
               <bean-pool>
                    <steady-pool-size>2</steady-pool-size>
                    <resize-quantity>5</resize-quantity>
                    <max-pool-size>20</max-pool-size>
                    <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
               </bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
I tried to use lookup for both "java:comp/env/ejb/simpleHome" and "java:comp/env/simpleHome". None succeed.
Does anyone know why the ejb is deployed successful but not bound?
Sha

Hi, Parsuram,
I did restart the server and the error is the same.
Here is the sample code. I did not change them. Only the names in deployment descriptors are modified.
Below is the info.
*************************Remote Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Remote interface for the GreeterDBEJB. The remote interface defines all possible
* business methods for the bean. These are the methods going to be invoked remotely
* by the servlets, once they have a reference to the remote interface.
* Servlets generally take the help of JNDI to lookup the bean's home interface and
* then use the home interface to obtain references to the bean's remote interface.
public interface GreeterDB extends javax.ejb.EJBObject {
* Returns the greeting String such as "Good morning, John"
     * @return the greeting String
public String getGreeting() throws java.rmi.RemoteException;
*************************Home Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Home interface for the GreeterDB EJB. Clients generally use home interface
* to obtain references to the bean's remote interface.
public interface GreeterDBHome extends javax.ejb.EJBHome {
* Gets a reference to the remote interface to the GreeterDBBean.
     * @exception throws CreateException and RemoteException.
public GreeterDB create() throws java.rmi.RemoteException, javax.ejb.CreateException;
*************************Bean Class
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
import java.util.*;
import java.io.*;
* A simple stateless session bean which generates the greeting string for jdbc-simple
* application. This bean implements the business method as declared by the remote interface.
public class GreeterDBBean implements javax.ejb.SessionBean {
private javax.ejb.SessionContext m_ctx = null;
* Sets the session context. Required by EJB spec.
     * @param ctx A SessionContext object.
public void setSessionContext(javax.ejb.SessionContext ctx) {
m_ctx = ctx;
* Creates a bean. Required by EJB spec.
public void ejbCreate() {
System.out.println("ejbCreate() on obj " + this);
* Removes a bean. Required by EJB spec.
public void ejbRemove() {
System.out.println("ejbRemove() on obj " + this);
* Loads the state of the bean from secondary storage. Required by EJB spec.
public void ejbActivate() {
System.out.println("ejbActivate() on obj " + this);
* Keeps the state of the bean to secondary storage. Required by EJB spec.
public void ejbPassivate() {
System.out.println("ejbPassivate() on obj " + this);
* Required by EJB spec.
public void GreeterDBBean() {
* Returns the Greeting String based on the time
* @return the Greeting String.
public String getGreeting() throws java.rmi.RemoteException {
System.out.println("GreeterDB EJB is determining message...");
String message = null;
Calendar calendar = new GregorianCalendar();
int currentHour = calendar.get(Calendar.HOUR_OF_DAY);
if(currentHour < 12) message = "morning";
else {
if( (currentHour >= 12) &&
(calendar.get(Calendar.HOUR_OF_DAY) < 18)) message = "afternoon";
else message = "evening";
System.out.println("- Message determined successfully");
return message;
************************ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<display-name>simple</display-name>
<ejb-name>simpleEJB</ejb-name>
<home>samples.jdbc.simple.ejb.GreeterDBHome</home>
<remote>samples.jdbc.simple.ejb.GreeterDB</remote>
<ejb-class>samples.jdbc.simple.ejb.GreeterDBBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
************************sun-ejb-jar.xml
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>ejb/simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
               <bean-pool>
                    <steady-pool-size>2</steady-pool-size>
                    <resize-quantity>5</resize-quantity>
                    <max-pool-size>20</max-pool-size>
                    <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
               </bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
************************Assemble Info
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar cvf simpleEjb.jar *
added manifest
ignoring entry META-INF/
adding: META-INF/ejb-jar.xml(in = 710) (out= 350)(deflated 50%)
adding: META-INF/sun-ejb-jar.xml(in = 803) (out= 424)(deflated 47%)
adding: samples/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/GreeterDB.class(in = 210) (out= 168)(deflated 20%)
adding: samples/jdbc/simple/ejb/GreeterDBBean.class(in = 1441) (out= 734)(deflated 49%)
adding: samples/jdbc/simple/ejb/GreeterDBHome.class(in = 257) (out= 177)(deflated 31%)
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar tf simpleEJB.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/ejb-jar.xml
META-INF/sun-ejb-jar.xml
samples/
samples/jdbc/
samples/jdbc/simple/
samples/jdbc/simple/ejb/
samples/jdbc/simple/ejb/GreeterDB.class
samples/jdbc/simple/ejb/GreeterDBBean.class
samples/jdbc/simple/ejb/GreeterDBHome.class
******************************** Deployment Info
server1: Applications: EJB Modules: simpleEjb
EJB Module Name: simpleEjb
Location: C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1
******************************** simplEJB.jar_verified.txt
STATIC VERIFICATION RESULTS
     NUMBER OF FAILURES/WARNINGS/ERRORS
     # of Failures : 0
# of Warnings : 1
     # of Errors : 0
     Test Name : tests.ejb.ias.ASEjbJndiName
     Test Assertion :
     Test Description : PASSED [AS-EJB ejb] : jndi-name is ejb/simpleHome
     WARNINGS :
     Test Name : tests.ejb.businessmethod.BusinessMethodException
     Test Assertion : Enterprise bean business method throws RemoteException test
     Test Description : For [ module_simpleEjb#simpleEjb#simpleEJB ]
For EJB Class [ samples.jdbc.simple.ejb.GreeterDBBean ] business method [ getGreeting ]
Error: Compatibility Note: A public business method [ getGreeting ] was found, but EJB 1.0 allowed the business methods to throw the java.rmi.RemoteException to indicate a non-application exception. This practice is deprecated in EJB 1.1 ---an EJB 1.1 compliant enterprise bean should throw the javax.ejb.EJBException or another RuntimeException to indicate non-application exceptions to the Container.
*********************** server log (no binding info)
[05/Jan/2003:17:07:19] FINE ( 1760): [EJBClassPathUtils] EJB Class Path for [simpleEjb] is ...
[C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1, C:\Sun\AppServer7\domains\domain1\server1\generated\ejb\j2ee-modules\simpleEjb]
[05/Jan/2003:17:07:20] FINE ( 1760): Loading StatelessSessionContainer...
[05/Jan/2003:17:07:20] FINE ( 1760): [BaseContainer] Registered EJB [simpleEJB] with MBeanServer under name [ias:instance-name=server1,mclass=stateless-session-bean,name=simpleEJB,root=root,standalone-ejb-module=simpleEjb,type=monitor]
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_RemoteHomeImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_EJBObjectImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDB_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): [Pool-ejb/simpleHome]: Added PoolResizeTimerTask...
[05/Jan/2003:17:07:20] FINE ( 1760): Created container with uinque id: 68275827784351744
[05/Jan/2003:17:07:20] FINE ( 1760): Application deployment successful : com.sun.ejb.containers.StatelessSessionContainer@1083717
[05/Jan/2003:17:07:20] INFO ( 1760): LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
[05/Jan/2003:17:07:22] FINE ( 1760): Started 48 request processing threads
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3274: successful server startup
[05/Jan/2003:17:07:22] FINE ( 1760): The server is now ready to process requests
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@10613aa
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1f52460
[05/Jan/2003:17:07:22] INFO ( 1760): CORE5053: Application onReady complete.
*********************** Client class
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import java.util.Properties;
import java.util.Hashtable;
import javax.ejb.*;
import java.sql.*;
import javax.sql.*;
import samples.jdbc.simple.ejb.*;
public class HelloClient {
     public static void main(String[] args) throws Exception {
javax.ejb.Handle beanHandle;
GreeterDBHome myGreeterDBHome;
GreeterDB myGreeterDBRemote;
InitialContext initContext = null;
Hashtable env = new java.util.Hashtable(1);
initContext = getContextInfo();
String JNDIName = "java:comp/env/ejb/simpleHome";
System.out.println("- Looking up: " + JNDIName);
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(initContext.lookup(JNDIName), GreeterDBHome.class);
myGreeterDBRemote = myGreeterDBHome.create();
          String theMessage = myGreeterDBRemote.getGreeting();
myGreeterDBRemote.remove();
     public static InitialContext getContextInfo() {
     InitialContext ctx = null;
     String url = "iiop://1st:3700";
     String fac = "com.sun.enterprise.naming.SerialInitContextFactory";
try {
     Properties props = new Properties();
     props.put(Context.INITIAL_CONTEXT_FACTORY, fac);
     props.put(Context.PROVIDER_URL, url);
          ctx = new InitialContext(props);
     catch (NamingException ne){
System.out.println("We were unable to get a connection to " +
" the application server at " + url);
ne.printStackTrace();
return ctx;
*********************** Running Client from command line
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>java HelloClient
- Looking up: java:comp/env/ejb/simpleHome
Exception in thread "main" javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:34)

In query SQVI unable to join the table konv

Hi Guru's
I have a requirement from the user, extract the Open PO's with INCO TERMS and CONDITION TYPES.
1. what is the process to extract the OPEN PO's from table EKKO.
In normal process I can extract Open PO's from ME2L and for a perticular Open PO number i can get the INCO TERMS and DOC CONDITION number from table EKKO and by taking the DOC CONDITION number I can get the condition type from table KONV.
But I want to do this process in SQ01 how is it possible?
please help
Regards
ISM

ISM,
No. Such instructions are beyond the scope of these forums, or at least beyond the scope that I would be willing to cover. FYI SAP provides a class [BC407 Reporting|http://www.sap.com/usa/services/education/tabbedcourse.epx?context=%5b%5b%7cBC407%7c%7c%7c063%7cUS%7c%5d%5d%7c] to cover such topics. The class lasts for 2 days.
I can say that I have created a query that meets requirements that are similar to yours. It took me a couple of hours to rough out the original version for user testing, and a couple more hours to finalize for production. It is do-able.
Following is a link to the Query Help doc. This was the doc from which I learned SAP Query (I did have previous experience with other report writers) http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVQUE/BCSRVQUE.pdf
I have already given you the general methodology to obtain your data within SAP Query. If these guidelines are not adequate, then you would probably be better off engaging the services of a programmer to write a custom report.
Best Regards,
DB49

"phantom" ObjectNotFoundException

A small (one servlet) application I have been asked to debug will
          sporadically generate many instances of the following exception. The app
          server gets so busy handling these exceptions that it is effectively shut
          down.
          ####<Feb 5, 2002 11:27:37 AM EST> <Error> <RJVM> <skip> <skip-nih>
          <ExecuteThread: '39' for queue: 'default'> <> <> <000000> <Unsolicited error
          response for: '-1'>
          java.rmi.NoSuchObjectException: RemoteInvokable - id: '377'
          <<no stack trace available>>
          The servlet generally does:
          1.) calls remote stateless EJBs
          2.) does an include of some content from a remote XML server (kinda' like a
          web service).
          3.) reads files
          4.) calls xalan XSLT to do a transform
          5.) the servlet is single threaded
          Here is what I've looked at so far:
          1.) EJB references, all to stateless session, are created immediately before
          use and
          destroyed immediately after.
          2.) The InitialContext, to a tree on a remote box, is created each time it
          is needed.
          3.) There is no explicit RMI (i.e. other than EJB) being used.
          The app server details:
          1.) WLS6.0 SP2
          2.) Redhat Linux 7.2
          3.) JDK 1.3.1
          4.) 2 physical servers in cluster (first is admin and cluster1, second is
          cluster2)
          5.) fronted by Apache
          6.) remote EJB server is similar configuration
          Questions:
          1.) How do I know it is this app? I don't, there are two apps running on
          this
          cluster but the other one is similar.
          2.) Where is the exception coming from that it cannot provide a stack trace?
          3.) Should this be posted on the EJB newsgroup?
          Any hints, help or ideas are appreciated. Please reply to newsgroup.


Chris
          I think you've hit a known issue for which there is a patch, to get it open a
          support case and reference CR053957
          Thanks
          Jim
          Chris Beckey wrote:
          > A small (one servlet) application I have been asked to debug will
          > sporadically generate many instances of the following exception. The app
          > server gets so busy handling these exceptions that it is effectively shut
          > down.
          >
          > ####<Feb 5, 2002 11:27:37 AM EST> <Error> <RJVM> <skip> <skip-nih>
          > <ExecuteThread: '39' for queue: 'default'> <> <> <000000> <Unsolicited error
          > response for: '-1'>
          > java.rmi.NoSuchObjectException: RemoteInvokable - id: '377'
          > <<no stack trace available>>
          >
          > The servlet generally does:
          > 1.) calls remote stateless EJBs
          > 2.) does an include of some content from a remote XML server (kinda' like a
          > web service).
          > 3.) reads files
          > 4.) calls xalan XSLT to do a transform
          > 5.) the servlet is single threaded
          >
          > Here is what I've looked at so far:
          > 1.) EJB references, all to stateless session, are created immediately before
          > use and
          > destroyed immediately after.
          > 2.) The InitialContext, to a tree on a remote box, is created each time it
          > is needed.
          > 3.) There is no explicit RMI (i.e. other than EJB) being used.
          >
          > The app server details:
          > 1.) WLS6.0 SP2
          > 2.) Redhat Linux 7.2
          > 3.) JDK 1.3.1
          > 4.) 2 physical servers in cluster (first is admin and cluster1, second is
          > cluster2)
          > 5.) fronted by Apache
          > 6.) remote EJB server is similar configuration
          >
          > Questions:
          > 1.) How do I know it is this app? I don't, there are two apps running on
          > this
          > cluster but the other one is similar.
          > 2.) Where is the exception coming from that it cannot provide a stack trace?
          > 3.) Should this be posted on the EJB newsgroup?
          >
          > Any hints, help or ideas are appreciated. Please reply to newsgroup.
          [Reply.vcf]

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

Mms to servlet general methodology?

Similar Messages

Maybe you are looking for