Servlet 2.2 support

Which is the minimum version of oracle 9iAS that supports servlet 2.2 specification.
I am using 9iAS 1.0.2.0.0. is there any way to support servlet 2.2 specification without migrating from version 1.0.2.0.0.
Thanks in advance.
Yogesh

Ok, but, what about 9ias v1.0.2.0.0? I >mean, its possible that OC4J run under 9ias >v1.0.2.0.0?
Again, thanks.
Leonardogday Leonardo -
OC4J can be downloaded and installed as a separate component. It will function as a standalone server process. This will provide you with a very fast servlet 2.2 container.
If you want, you can tie it into the 9iAS 1020 release using the mod_proxy functionality provided by the Oracle HTTP Server.
cheers!
-steve-
null

Similar Messages

  • Java 1.5, Servlet 2.4 support in Sun Java System Web Server?

    Hi All,
    Does anyone know when the next version of Sun Java System Web Server will be released? 6.1 has been around a while and it doesn't support the latest Java releases, which is odd for a Java product from the company that owns Java. My Sun rep didn't have an answer for me and suggested posting here.
    I have seen references to people trying to use 1.5 with their server in another forum, but they were reporting problems and their questions weren't answered.
    Thanks!
    Dennis

    Hi,
    Try the new
    SAP NetWeaver Application Server, Java EE 5 Edition
    thus you will have the chance to use the latest Servlet 2.5. The download package includes also the new SAP NetWeaver Developer Studio.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2</a>
    Regards,
    Violeta

  • Full servlet 2.3 support in WLS 6.1 available?

              Hi,
              I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The same code
              generates compile errors when compiling against WLS 6.1 sp4 jar.
              Here is the list of inconsistencies as documented in 6.1 notes - go to http://edocs.bea.com/wls/docs61/notes/new.html
              and search for "Servlet API Classes" you should see table with the following classes
              that are not fully 2.3 compatible.
              javax.servlet.Filter
              javax.servlet.ServletContext
              javax.servlet.ServletContextAttributesListener
              javax.servlet.http.HttpServletResponse
              javax.servlet.http.HttpSession
              javax.servlet.http.HttpSessionAttributesListener
              For some classes I a rename works fine, however other are more problematic.
              Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification? Or,
              what else would you suggest?
              Thanks,
              Radu
              

              WLS6.1 supports Public Final Draft 1 of Servlet 2.3 specification, not the Servlet
              specification 2.3.
              Refer to
              http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls%2FS-10618.htm
              thanks,
              Deepak
              "Radu" <[email protected]> wrote:
              >
              >Hi,
              >
              >I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The
              >same code
              >generates compile errors when compiling against WLS 6.1 sp4 jar.
              >
              >Here is the list of inconsistencies as documented in 6.1 notes - go to
              >http://edocs.bea.com/wls/docs61/notes/new.html
              >and search for "Servlet API Classes" you should see table with the following
              >classes
              >that are not fully 2.3 compatible.
              >
              >javax.servlet.Filter
              >javax.servlet.ServletContext
              >javax.servlet.ServletContextAttributesListener
              >javax.servlet.http.HttpServletResponse
              >javax.servlet.http.HttpSession
              >javax.servlet.http.HttpSessionAttributesListener
              >
              >For some classes I a rename works fine, however other are more problematic.
              >
              >Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification?
              > Or,
              >what else would you suggest?
              >
              >Thanks,
              >Radu
              >
              >
              >
              

  • Servlet 2.4 support - jspx

    Hello,
    In Netweaver Devloper Studio I added the following lines in web.xml file:
    <web-app version="2.4"
             xmlns="http://java.sun.com/xml/ns/j2ee"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    Since the above source file failed to build, can any one tell me whether there is support for servlet 2.4 available
    Naghman

    Hi,
    Try the new
    SAP NetWeaver Application Server, Java EE 5 Edition
    thus you will have the chance to use the latest Servlet 2.5. The download package includes also the new SAP NetWeaver Developer Studio.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2</a>
    Regards,
    Violeta

  • Is servlet chaining (filtering) supported?

    For a given virtual name I would like to set up a chain of servlets
              (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
              ConsumerServlet contains the results of the ServletOutputStream of the
              ProducerServlet. The ConsumerServlet is in effect 'filtering' the results
              of ProducerServlet.
              eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
              BrowserResponse
              Can this be done with WLS 5.1?
              The RequestDispatcher interface does not seem to satisfy these requirements?
              If I understand this interface correctly, it allows requests to be either
              'forwarded' (where the output of the forwarder is not used) or 'included'
              (where the included servlet inserts output in the stream). But it does not
              allow servlets to be connected in a producer-consumer chain.
              Am I missing something?
              Thank you.
              Marko.
              

    Is there any way to achieve the same effect within the current spec?
              Marko.
              Winston Koh <[email protected]> wrote in message
              news:[email protected]...
              > Hey Marko, servlet chaining is not supported in WLS since its a
              proprietary
              > mechanism not specified in the current servlet/jsp specs
              >
              > thanx
              >
              > Winston
              > Marko Milicevic <[email protected]> wrote in message
              > news:[email protected]...
              > > For a given virtual name I would like to set up a chain of servlets
              > > (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
              > > ConsumerServlet contains the results of the ServletOutputStream of the
              > > ProducerServlet. The ConsumerServlet is in effect 'filtering' the
              results
              > > of ProducerServlet.
              > >
              > > eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
              > > BrowserResponse
              > >
              > > Can this be done with WLS 5.1?
              > >
              > > The RequestDispatcher interface does not seem to satisfy these
              > requirements?
              > > If I understand this interface correctly, it allows requests to be
              either
              > > 'forwarded' (where the output of the forwarder is not used) or
              'included'
              > > (where the included servlet inserts output in the stream). But it does
              > not
              > > allow servlets to be connected in a producer-consumer chain.
              > >
              > > Am I missing something?
              > >
              > > Thank you.
              > >
              > > Marko.
              > > .
              > >
              > >
              > >
              >
              >
              

  • Is Servlet failover supported by WebLogic5.1

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

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

  • XDK support for UTF-16 Unicode

    Hi,
    Does the Oracle Java XDK, specifically the XSQL servlet and api,
    support UTF16-Unicode.
    Presumably, .xsql files have to be stored, read and queries
    executed in a Unicode compliant format for this to work. Is this
    possible currently???
    Thanks,
    - Manish

    If you are using XDK 9.0.1 or later, and you are using JDK 1.3,
    this combination supports UTF-16. XSQL inherits the support
    for "free" in this case.

  • When to choose JSP and When to choose Servlet in Web Application

    Hi,
    I know that using JSP over servlet has only one advantage like for huge Application you can devide presentation layer from business logic. Is there any other advantage.
    Also, if anyone can tell me how to handle FTP request in Servlet as HttpServlet supports only HTTP.
    Thanks.
    Subs

    Depends on what you're rying to accomplish. If you want to generate a bunch of HTML then JSP is the way to go. If you just want to extend the server (i.e. add functionality that isn't specific to any one screen of your application), then Servlets are the way to go.
    Additionaly, if you have a lot of HTML forms, and want to do it right, check out Struts. This would be the case if you wanted to both extend the server and generate HTML. It's an MVC framework available from Jakarta. It's fairly tried and true at this point. It makes it very easy to maintain, extend, and develop with. It also comes with a wealth of custom tag libraries out of the box. I have developed two projects with it so far and find it a pleasure to work with.
    http://jakarta.apache.org/struts/index.html
    Regards,
    Kyle

  • Can i create  client program for a servlet(without browser)

    Hai All,
        I have to call a servlet in my normal java program.Please send me code.
    Thanks
    Madhu

    Hi,
    Try getting a URL connection to the servelt and send the request as
    import java.net.URL;                     // New addition
    import com.oreilly.servlet.HttpMessage;  // A support class, shown later
      private String getServlet() {
        try {
          // Construct a URL referring to the servlet
          URL url = new URL(getCodeBase(), "/servlet/myServlet");
          // Create a com.oreilly.servlet.HttpMessage to communicate with that URL
          HttpMessage msg = new HttpMessage(url);
          // Send a GET message to the servlet, with no query string
          // Get the response as an InputStream
          InputStream in = msg.sendGetMessage();
          // Wrap the InputStream with a DataInputStream
          DataInputStream result =
            new DataInputStream(new BufferedInputStream(in));
          // Read the first line of the response, which should be
          // a string representation of the current time
          String response = result.readLine();
          // Close the InputStream
          in.close();
          // Return the retrieved time
          return response;
        catch (Exception e) {
          // If there was a problem, print to System.out
          // (typically the Java console) and return null
          e.printStackTrace();
          return null;
    Regards,
    Uma
    Message was edited by: Uma Maheswari

  • Does WL 9 support JSP 2.1?

    Hi,
    I am writing a web application using Apache's MyFaces. I'm told to use MyFaces 1.2.4 my servlet container must support JSP 2.1 and Servlet 2.5 implementations. Does WebLogic 9.2.2 (Solaris 9), the server I'm running, support these?
    Thanks, - Dave

    Hi Dave,
    WLS 9.2.2 Supports the following :-
    J2EE Servlet 2.4, 2.3, and 2.2
    J2EE JSP 2.0, 1.2, and 1.1
    Details, Link:[http://e-docs.bea.com/wls/docs92/notes/new.html#wp1064437]
    Hope this helps :)
    Regards.

  • Jakarta Datagrid Taglibs and Servlet 2.4

    Dear All,
    Please help me with this situation
    we would require to have this Jakarta Datagrid taglib (with the servlet 2.2 support) in my web application, but my web-applications uses servlet 2.4 version.
    If we change my servlet version to 2.2 for the benefit of Datagrid, we lose JSTL, Expression Language support.
    we got struck here and we are not familiar with struts and jsf, where we came to know the availability of datagrid using these.
    Kindly requesting you to help us to solve this issue or guide us to a datagrid control works servlet 2.4 version.
    I am not a programmer, i am writing this message on behalf of my programmers (freshers). Please do guide us.
    thanking you,
    S. Sithi Vinayagam

    dear all,
    why i am not getting any response from you all,
    Is this a common question, that will not be anwered any more
    or
    is there is a better way to ask this type of help from all the developers over there.
    Kindly i am requesting you once again to suggest me a better solution (not any commercial soultions) with this type of Data Grid solution for my web application

  • Starting new threads from a servlet

    Hi
    I read somewhere that starting new threads from a servlet is not supported in the future releases of J2EE .
    Any one aware of this.
    I have a listener program started as a new thread from the init method of a servlet which is set to load on startup.
    I have to think about another way to do this if this is not suppported in the future releases
    any comments

    Dr clap
    Actually I was getting some warning messages in my websphere server console when I tried to make JDBC connections from the thread I opened in the servlet.
    Everthing works fine but with the warning messages,
    Then someone from IBM answered me in one of the forums quote
    Cause: These messages are being produced due to an
    "unsupported" environment. When application is
    spinning its own threads from an EJB, spinning a
    thread and accessing a database is not supported (per
    the J2EE specification). One exception to this rule is
    if a Servlet is spinning its own threads and accessing
    a database. The J2EE specification is not clear on
    this, so WebSphere Application Server 5.0 must allow
    for it at this time. IBM is working with Sun to
    clarify this in the specification, so eventually (i.e.
    J2EE 1.4) spun threads from a Servlet accessing a
    database outside of a transaction will not be
    supported either.
    Since we don't want to promote the usage of these
    "naked" threads accessing databases, we are producing
    the warning messages. Although they may be filling up
    the logs, we feel that these are necessary to warn the
    user that they are doing something not in-line with
    the intended usage. Customer should consider changing
    their application to comply with the
    J2EE specification.
    """

  • Non-http servlet engine?

    Hi, I'm new to servlet development and I'm not sure this question has been answered here before. So I apologize if it has.
    Basically I want to have an integrated server that can accept both http and non-http requests. So my initial thought was to write an HttpServlet and a GenericServlet. Then I googled for clues on how to implement that and found from the JavaRanch website http://faq.javaranch.com/java/ServletsFaq#otherProtocols that this task could be a daunting one because that'd imply that I have to write a new servlet engine.
    So my question is, is this true in your expert opinion? And, if the custom non-http protocol has a similar syntax as http (e.g. RTSP), is it possible to just extend the http servlet engine to support it? And would that be doable without much effort?
    Thanks,
    Liang.

    Would you actually need the entire servlet system for the new protocol? For your typical simple request/reply protocol you'd normally:
    Create a server socket.
    When a connection arrives, start a thread to service it.
    In the service thread, read and parse request.
    Send reply.
    Close socket, exit thread.
    A servlet system adds a bunch of stuff to that: a layer that allows you to configure pluggable request handlers; methdod-specific functions (POST -> doPost()); a ServletRequest object; etc. Are those things relevant to the new protocol? Do you have requests with URL-like things in the header, allowing routing requests to different servlets? Do you plan to have lots of servlets for the protocol (one servlet -> no much point in XML-configurable request routing)?
    I'd hope that I wouldn't need to implement a configurable request routing infrastructure. It's a lot of work if it's not really needed. Just write a socket server. If you have an associated web server (e.g. HTML pages from which the user starts RTSP requests) you can even run the socket server inside the servlet container if that helps.

  • Rmi, servlet + mysql

    i have a jsp page as follows that requests information from a database
    <body>
    <form method="post" action="http://localhost/servlet/JobServlet">
    View Job Details:
    Enter job number <input name="jobno" type="text" id="jobno" />
    <input name="view" type="submit" id="view" value="View Details" />
    </form> </body>
    my interface:
    import java.rmi.*;
    public interface JobInt extends Remote {
    public String getDetails(int jobno) throws RemoteException; }
    the server:
    import java.rmi.*;
    public class JobServer {
    public static void main(String[] args) {
    try {
    JobImpl j = new JobImpl();
    Naming.rebind("//"+"localhost"+"/JobImpl",j); System.out.println("Registered"); }
    catch (Exception e) {
    System.out.println("Exception occured in JobServer ... " +e); } } }
    implementation:
    import java.rmi.*;
    import java.rmi.server.*;
    import java.sql.*;
    public class JobImpl extends UnicastRemoteObject implements JobInt {
    Connection con; Statement st; ResultSet rs;
    String url = "jdbc:mysql://localhost:3306/db?user=root;password=admin";
    public JobImpl() throws RemoteException {
    super();
    try {
    Class.forName("com.mysql.jdbc.Driver").newInstance();
    con = DriverManager.getConnection(url, "", "");
    st = con.createStatement(); }
    catch (Exception e) {
    System.out.println("problem while establishing connection"+e); } }
    public String getDetails(int jobno) throws RemoteException {
    try {
    rs = st.executeQuery("Select * from job where jobno="+jobno);
    rs.next();
    return(rs.getString(2)); }
    catch (Exception e) {
    e.printStackTrace(); }
    return null; } }
    from the jsp page, when the jobno is entered all the details about the job should be displayed on the servlet
    the servlet:
    import java.rmi.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    public class JobServlet extends HttpServlet {
    public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
    PrintWriter out = res.getWriter();
    res.setContentType("text/plain");
    try {
    int jobno = Integer.parseInt(req.getParameter("jobno"));
    JobInt j = (JobInt)Naming.lookup("//"+"localhost"+"/JobInt");
    System.out.println("Job Details: "+j.getDetails(jobno)); }
    catch (Exception e1) {
    System.out.println(""+e1); } } }
    i get a HTTP 405 error... i really dont know whats the problem and y it doesnt work... im doing an assignment on these... plz help

    You are requesting the servlet via the POST method (<form method="post"...) but you didn't implement the doPost() method in your servlet. Therefore your servlet doesn't support POST requests and you get that error back.
    Either change the HTML to use the GET method or change the servlet to implement doGet() instead of doPost(). In my opinion the GET method would be more suitable for a request that doesn't change anything on the server side.

  • Miracle in servlet (multithreading)

    Hi braza !
    Once upon a time in snow Moscow I try to write servlet with multithreading support. I did simple
    servlet with doGet and doPost methods. See below, please :
    package warehouse2;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    import java.util.*;
    public class MainHandler extends HttpServlet {
    public void init() throws ServletException {
    public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    MainHandlerThread mht = new MainHandlerThread(request,response);
    ... and I have this file:
    package warehouse2;
    import javax.servlet.http.*;
    import java.io.*;
    public class MainHandlerThread extends Thread {
    private HttpServletRequest request;
    private HttpServletResponse response;
    public MainHandlerThread(HttpServletRequest request,
    HttpServletResponse response) {
    this.request = request;
    this.response = response;
    try {
    response.getWriter().println(System.currentTimeMillis()); // IT WORKS !!!!!
    } catch (Exception e) {
    start();
    public void run() {
    PrintWriter pw;
    try {
    try {
    response.setContentType("text/html; charset=windows-1251"); // Get 'NullPointerException' !!!
    // if upper string do rem, than have no responce in browser !
    long m = System.currentTimeMillis();
    pw = new PrintWriter(response.getWriter());
    pw.println(m); // silence !!!!!
    } catch (Exception e) {
    System.out.println("MainHandlerThread.run: " + e.toString());
    e.printStackTrace();
    } finally {
    Dear all, if anyone can help or to explain me my mistake, I will meet you in Moscow :)))
    Thanx in advance.
    Konstantin.

    Once upon a time in snow Moscow I try to write servlet with multithreading supportI'm not quite sure what you're trying to do. Servlets are implicitly multi-threaded, unless you were to implement the SingleThreadModel (which is a really terrible idea). This is why servlet instance variables are not thread-safe. The servlet container (for example tomcat) will invoke the servlet's service method for each HTTP request and more than one thread can execute concurrently in this method. It's already been mentioned that you shouldn't start threads from doGet() (or doPost()), because it won't work as you expect it to.
    So in short, you don't need to do anything to add muti-threading support to servlets. It's already there and it's handled by the servlet container.

Maybe you are looking for