Session in servlet

Good morning my dear friends
can nay one explain y we are not using "new" operator to create a object for session in servlet ?

Please take care, that the http protocoll is a stateless protocoll. Without special actions it is not possible to say that this request come from user x and so on.
So you have to use a session.
Create the SessionObject with the request object like this:
HttpSession session = request.getSession(true);
So, now you have a session. This session is identified by a cookie or with some additional work with the sessionid in the url.
If you don't use persistent data you don't have to know which client make the request! Is you use it then store the data with the session object.
If you really need to know the name from the client / user you have to make a login .
I hope this help
regards Dietmar

Similar Messages

How to Create a session in Servlet

will somone show me the code to create a session in servlet?
if a session can be created in servlet file, it can be used all the jsp files in a same web ?
Thanks!!!

Session in Java web application is started by the web server itself.
In a servlet you can get the session by
HttpSession session = request.getSession();
It will return the current session associated with this request, or if the request does not have a session, creates one.

Session in Servlet and JSP

Hi
How do I maintain a session in the scenario below:
(1) Servlet A creates a session
(2) Servlet A dispatch JSP A
(3) JSP A capture some user inputs and post to Servlet B
So far both (1) and (2) are working fine, but to get on to (3) the session is lost upon reaching Servlet B
Pls Advise...

Hi mirage2000,
You mean that when you are calling the Servlet B, the request object has no session inside it's a bit strange.
Let's take the following example wich is quite simple:
Servlet A:
package servlet;
import java.io.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class ServletA extends HttpServlet {
public void init (ServletConfig config) throws ServletException {
super.init(config);
public void doGet (HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
doPost(req, res);
public void doPost (HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
String nomClient = "Toto";
HttpSession session = null;
try {
session = req.getSession();
req.setAttribute("servlet.a.nom", nomClient );
getServletConfig().getServletContext().getRequestDispatcher("/jspa.jsp").forward(req, res);
} catch (Exception e) {
System.out.println("Pas cool !");
JSP A:
<%@ page import="java.util.*"%>
<% String nom = (String)request.getAttribute("servlet.a.nom"); %>
<HTML>
<HEAD><TITLE>Age ?</TITLE></HEAD>
<BODY>
<BR>
<BR>
What is your age ?
<BR>
<FORM ACTION="../servlet/ServletB" METHOD="post">
<INPUT TYPE="text" NAME="age" SIZE="3">
<BR>
<INPUT TYPE="submit" NAME="action" VALUE="SEND"> </FORM>
</BODY>
</HTML>
Servlet B:
package servlet;
import java.io.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class ServletB extends HttpServlet {
public void init (ServletConfig config) throws ServletException {
super.init(config);
public void doGet (HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
doPost(req, res);
public void doPost (HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
HttpSession session = null;
PrintWriter out = res.getWriter();
try {
String action = req.getParameter("action");
if (action.equals("SEND") ) {
res.setContentType(CONTENT_TYPE);
session = req.getSession();
String age = (String)req.getParameter("age");
String nomClient = (String)session.getAttribute("servlet.a.nom");
out.println("<HTML><HEAD></HEAD><BODY>");
out.println("Hello mister <B>" + nomClient + "</B>");
out.println("<BR>You are <B>" + age + "</B> years old !!");
out.println("</BODY></HTML>");
out.flush();
out.close();
} catch (Exception e) {
System.out.println("Pas cool !");
This exemple is really simple and is working perfectly on my Apache Tomcat test server.
Be more precise maybe you forgot to do some stuff.
Regards
Julien

Problem with Sessions in Servlets

Hi,
I'm having a problem with sesions with servlets. It seems that if someone logs into my website, which is running on all servlets, while another person is logged on, the second person gets the session of the first person.
I'm using
HttpSession session = request.getSession(true);to get the session in each page. The session contains a user object which shows if the user is logged in and what permissions.
The session should be unique to the client computer right? Or am I jsut screwing this up big time?

Yes, each client will have their own session. However, you may be testing incorrectly:
In Firefox, for example, all instances of the application running on the same machine will share the same cookies, therefore the same session, and would be considered one client.
MS IE will do the same if you use File - New to open a new wondow rather than clicking on the desktop icon.
If the different clients are using different machines and still getting shared data, then you may be using class-level variables in the servlet, which would not be thread safe and could lead to your problems...
public class MyServlet extends HttpServlet {
String data; //bad
int moredata; //bad
public void doGet(...) ... { ... }
}

Disabling session in servlet

In jsp pages session is created by default. To disable it we use <%@ session="false %>. How do we accomplish the same thing in servlets? Thank you in advance. BTW: I looked at the java class file deirved from jsp with disabled session but it didn't make any sense. Obviously it happens in the pageContext initialization but it doesn't appeal to my servlets.

HttpSession session = request.getSession(false);

Session monitoring servlet

Hi
          I am trying to write a servlet to monitor the sessions in a weblogic server
          at a point in time.
          Here is my situation:
          1. We are running a server clustered with three other weblogic server
          instances.
          2. My code looks like this:
          HttpSession ses = req.getSession(true);
          HttpSessionContext ctx = ses.getSessionContext();
          for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          String id = (String) e.nextElement();
          HttpSession curSession = ctx.getSession(id);
          if(curSession == null)
          System.out.println("AdminSessionServlet: Null session
          continue");
          continue;
          long creationL = curSession.getCreationTime();
          3. When I run this without clustering, it works great. I get a list of
          sessions, the creation time, last accessed time etc.
          4. When clustered, the curSession (from ctx.getSession(id)) always comes
          back as null.
          5. I did some poking around only to find that the id that I get looks like a
          long number (for example: -3435089287746960634 ).
          Has anybody run into such a problem? Any idea how I can get it to work?
          thanks,
          Srikanth Meenakshi
          [email protected]


I have to talk the relevant developer. I know exactly what's happening. Since
          JavaOne is going on, we are spending time at the conference. I will try to get
          back to you this week if not, it will be early next week.
          - Prasad
          Srikanth Meenakshi wrote:
          > Thanks for the reply.
          >
          > 1. I used the Servlet api from here:
          >
          > http://jserv.javasoft.com/products/java-server/documentation/webserver1.1/ap
          > idoc/javax.servlet.http.HttpSessionContext.html#_top_
          >
          > which did not say that the methods are deprecated. I did look at the latest
          > spec and they are deprecated. However, since the solution I have works in
          > non-clustered environment, I am wondering what I need to do to make it work
          > in a clustered environment.
          >
          > 2.
          >
          > >
          > > You are poking into internal stuff. I suggest you not to do that.
          >
          > The only poking around I did was to print out the id (String) that I
          > received from a public method in a public API. As in,
          >
          > for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          > {
          > String id = (String) e.nextElement();
          > System.out.println("the id is: " + id);
          > }
          >
          > Thanks,
          >
          > Srikanth
          >
          > "Prasad Peddada" <[email protected]> wrote in message
          > news:[email protected]...
          > > First of all you are using deprecated api method. Those methods will
          > return null
          > > in the near future.
          > >
          > > Srikanth Meenakshi wrote:
          > >
          > > > Hi
          > > >
          > > > I am trying to write a servlet to monitor the sessions in a weblogic
          > server
          > > > at a point in time.
          > > >
          > > > Here is my situation:
          > > >
          > > > 1. We are running a server clustered with three other weblogic server
          > > > instances.
          > > >
          > > > 2. My code looks like this:
          > > >
          > > > HttpSession ses = req.getSession(true);
          > > > HttpSessionContext ctx = ses.getSessionContext();
          > > >
          > > > for(Enumeration e = ctx.getIds(); e.hasMoreElements();)
          > > > {
          > > > String id = (String) e.nextElement();
          > > > HttpSession curSession = ctx.getSession(id);
          > > >
          > > > if(curSession == null)
          > > > {
          > > > System.out.println("AdminSessionServlet: Null
          > session
          > > > continue");
          > > > continue;
          > > > }
          > > > long creationL = curSession.getCreationTime();
          > > > .........
          > > > }
          > > >
          > > > 3. When I run this without clustering, it works great. I get a list of
          > > > sessions, the creation time, last accessed time etc.
          > > >
          > > > 4. When clustered, the curSession (from ctx.getSession(id)) always comes
          > > > back as null.
          > > >
          > > > 5. I did some poking around only to find that the id that I get looks
          > like a
          > > > long number (for example: -3435089287746960634 ).
          > >
          > > You are poking into internal stuff. I suggest you not to do that.
          > >
          > > - Prasad
          > >
          > >
          > > >
          > > > Has anybody run into such a problem? Any idea how I can get it to work?
          > > >
          > > > thanks,
          > > >
          > > > --
          > > >
          > > > Srikanth Meenakshi
          > > > [email protected]
          > >

Concurrent access to JMS session in servlet

          We have a servlet that accepts a request from a browser,
          retrieves info from the request, places it in a JMS message and
          then sends the msg to a JMS Queue. We create all the JMS
          objects (connection, session, etc.) at init time (all these
          objects have class scope). There is only one session and I was
          wondering because servlets are multithreaded, while a request is
          being handled for one client, if there is a context switch in
          the middle of that client's send in order to handle another
          client's request, two different threads will be accessing the
          same session concurrently. I know the spec advises against
          this. Am I thining too much on this one????? All I have to do
          is synchronize the send call however I was just wondering if it
          was truely necessary.
          How are other people doing this out there?
          Let me know,
          Mark


Hi Mark,
          You are definitely not thinking too much on this one! Multi-threading
          session access is unsafe and is definitely against spec. Either
          synchronize
          access, or, if performance is an issue, make sure each simultaneous
          sender has its
          own session.
          The WebLogic JMS Performance white paper on dev2dev.bea.com
          contains an example of a producer pool that looks like it should map
          well to your use case.
          Tom, BEA
          Mark Drifdon wrote:
          > We have a servlet that accepts a request from a browser,
          > retrieves info from the request, places it in a JMS message and
          > then sends the msg to a JMS Queue. We create all the JMS
          > objects (connection, session, etc.) at init time (all these
          > objects have class scope). There is only one session and I was
          > wondering because servlets are multithreaded, while a request is
          > being handled for one client, if there is a context switch in
          > the middle of that client's send in order to handle another
          > client's request, two different threads will be accessing the
          > same session concurrently. I know the spec advises against
          > this. Am I thining too much on this one????? All I have to do
          > is synchronize the send call however I was just wondering if it
          > was truely necessary.
          > How are other people doing this out there?
          >
          > Let me know,
          > Mark

Session tracking (Servlets)

The Problem..
I have a login web-page which requests a username and password. The fields are then checked by a servlet which queries an Access Database. If the username and password are valid, the servlet redirects the browser to the main option page.
I can create a new session in the Login Servlet which stores the username and password, but when the browser moves to the main options page, how do I recover the data (using a different servlet) that was added to the session object during the login procedure. For example, say Fred Smith logged in on the login page, when the browser is redirected to the main options page I want to print "Hello Fred Smith", presumably this information can be recovered from the session object that was created in the login servlet.
Can anyone help? Thanks very much,
Andy.

Hi manalar, thanks for the reply,
I tried this but I'm just getting a null reference returned. This is the code that I'm using in the login servlet:
String username = req.getParameter( "Username" );
// from the textbox on the web-page
HttpSession session = req.getSession(true);
// create a new session
session.putValue("Logon.ok", username);
and this is the code in my other servlet:
HttpSession session = req.getSession(true);
Object test = session.getValue("Logon.ok");
String testString = (String) test;
testString is assigned a null value, any ideas?
Thanks in advance,
Andy

Intiating a Faces session Through Servlet

Hi all,
I have an application that is run as a servlet. It will link to a Faces application that I have written, and the application will have to start with its component tree populated based on variables passed through the servlet.
I don't really know how to go about doing this. Can the original servlet invoke a FacesContext, populate the component tree, and then pass the results to a browser? Is there a smarter way to go about accomplishing what I need?
Thanks,
Elam Daly

Hi,
amother way to add fonctionality to servlet is ServletFilter.
ServletFilter acts as a Decorator pattern.
You can add many filter on many servlet.
Check on the web for more info about it.
Hope this could help you.
Regards,
Sebastien Degardin.

Session management in servlet

Hi,
I am using OC4J Server.
I know the session in servlet can be managed with cookies. In addition, the session can be managed in HTTP session of OC4J. And How about the URL rewriting? Does it mean there are 3 methods to keep track of the servlet session. What are the difference of them. I am quite confused.
Thanks in advance

I see. Thanks.
So it means there are two kinds of cookies, permanent cookies and session cookies.
session cookies are used to store the session information.
I have another question. I want to write a permanent cookies to the browser and get it again even if the browser is closed.
The source code is like:
Cookie cookie = new Cookie(cookieName, cookieValue);
response.addCookie(cookie);
Then I try to write some cookies in the browser, close the browser and open the browser again and I try to retreive the cookies using the following codes but the cookies disappear.
Cookie[] cookies = request.getCookies()
if (cookies != null && cookies.length > 0) {
for (int i = 0; i < cookies.length; i++) {
Cookie cookie = cookies;
Is this the correct way to store and retrieve permanent cookies?
thanks in advance

Session Maintenance in JSp-- Servlet-- JSP

Iam making a browser based Financial Aplication so I want to introduce sessions into it.
My First page is a JSP which takes username and Password. Then it calls a servlet.
So my Problems are-
1. Iam able to start session from servlet (which validates username and password) but after that in the apllication some JSp's are there like for search options so how to maintain sessions in JSP's ?
2. When user quits browser and then opening a browser and directly types a JSP page which is in-between the flow this JSP opens up whereas i want the user to go from starting as its a security loop hole.
So how to maintain a session in a JSP (ie when control passes from Servlet to JSP at that time)?
Plz Help me
Thanks in advance

Hi Innova,
There is a solution .I think while validating the login page entries u should maintain a session variable and give it some constant value if the entered values are valid.And now u should always check this sesson variable for that constant value [ if(session.getParameter("s")==constvalue) ] only then u proceed further else diaplay an error message or link prompting to login
I hope it will work fine check it out.
GoodLuck.
Bye......

Servlet Session Questions

Hi,everybody:
I'm puzzled by two questions about session in servlet.
1.The default timeout of J2EE example WAR is set to 30sec.Is it too short?
2.in J2EE Tutorial1.3 it says"To ensure that an active session is not timed-out, you should periodically access the session in service methods because this resets the session's time-to-live counter",But I can't see any codes in example servlets to access session "periodically".Could you please explain that?
Thank you!

I,
I have a problem with the session.
After the "getMaxInactiveInterval" time, I reload my servlet , but
the session is lost even if I test it :
Before doing anything, I do this :
HttpSession oSession = req.getSession (=(false);
if(oSession == null)
// forward to a login_page
RequestDispatcher rd = getServletContext().getRequestDispatcher(
"login_page");
rd.forward(req, res);
// request to the database to get user'characteristics
// and put then in the session
String sUser = (String)oSession.getValue("COD"); // sUser is null !
The pb is that the session has not been removed from the Server after
the MaxInactiveInterval, so when i make a request , I have in the session :
the req.isRequestedSessionIdValid() gives : true .
and a new session is created with a new id
Something very strange.
Thanks for help.

Calling EJB 3.0 Stateless Session Bean

Dear all,
I created a stateless session bean with a hello world method on it. Now i want to call the method from a BeanDecorator class, through a getter metod. When i use the jndi lookup in my getter, i can call the helloWorld method without a problem. However, when i dont use the jndi lookup, and only use the @EJB annotation, i always get a nullpointer.
This is working:
InitialContext ic = new InitialContext();
test = (TestLocal)ic.lookup("test.be/ear~bd/LOCAL/TestBean/"+TestLocal.class.getName());
test.helloWorld()
This gives nullpointer:
@EJB
private TestLocal test;
test.helloWorld();
What is the correct way to consume session beans without having to explicitly code the jndi lookup?
Kind regards.

Hi,
any annotation like this can be used only in "managed classes" like Session Beans, Servlets etc. Managed classes are those classes managed by the J2EE server. Managed here means, lifetime controlled by server.
You can find this in J2EE specification.
Frank

Problem with form or servlet???

hello..
i am trying to send some form data to a servlet for processing..
here is the code for the form
<table border="0">
<form action="details.upd" method="post" name="upd">
<tr><td>Username</td><td><input name="uname" type="text" size="25" maxlength="30"
value=<%=session.getAttribute("user") %> /></td>
</tr>
<tr>
<td>password</td><td><input name="pass" type="password" size="25" maxlength="30" />
</td></tr>
<tr><td>confirm password</td><td><input name="pass2" size="25" maxlength="30" type="password"/></td></tr>
<tr><td>Email</td><td><input name="mail" type="text" size="25" maxlength="30"
value=<%=session.getAttribute("EMAIL") %> /></td></tr>
<tr><td align="center"><input name="submit" type="button" value="Update" /></td></tr>
<tr><td align="center"><input name="ch" type="hidden" value="det"/></td></tr>
</form>
</table>
here is the web.xml entry for my compiled servlet
<servlet>
<servlet-name>update</servlet-name>
<description>
Servlet used for updates sent from landlord sessions
</description>
<servlet-class>UpdateServlet</servlet-class>
<load-on-startup>5</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>update</servlet-name>
<url-pattern>*.upd</url-pattern>
</servlet-mapping>
the problem is that when i click the submit button to send the data, nothing happens....absolutely nothing. the page just stays as it is...please can u spot any fatal error in the code?
I have looked and looked without success..please help

yeah..i solved that.. but now i am getting another
problem...
why does this code...
Stringuser=(String)session.getAttribute("user");
gives me a class cast exception????
please helpBecause the object named "user" in your session isn't
a String.ok...thks

Problem while assigning Servlet to Execute queue

Hi,
We implement a IMS S-CSCF on BEA container 2.2.
A call for us may be several times reentrant. Meaning that for one call we have to handle at least three different dialogs but in major use cases, it will be 6 or 7 for our next deployment.
We are currently facing to bottlenecks problems and BEA support advised me to try to check if assigning servelt to execute queue could improve the preformances.
I just wanted to make a try with one of our servlet but I have an exception java.lang.NoClassDefFoundError: org/jaxen/JaxenException.
Here is what I did:
In web.xml I have:
<web-app>
<distributable/>
<servlet>
<servlet-name>register</servlet-name>
<servlet-class>com.netcentrex.scscf.registrar.RegistrarServlet</servlet-class>
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>REGISTRARQueue</param-value>
</init-param>
<load-on-startup/>
</servlet>
<listener>
<listener-class>com.bea.wcp.sip.engine.server.ContextEventHook</listener-class>
</listener>
</web-app>
In sip.xml I have:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sip-app
PUBLIC "-//Java Community Process//DTD SIP Application 1.0//EN"
"http://www.jcp.org/dtd/sip-app_1_0.dtd">
<sip-app>
<display-name>SIP Servlet based Registrar</display-name>
<distributable/>
<context-param>
<param-name>usc.configFile</param-name>
<param-value>/etc/neotip/usc.ini</param-value>
</context-param>
<context-param>
<param-name>icscf.configFile</param-name>
<param-value>/etc/neotip/icscf.ini</param-value>
</context-param>
<context-param>
<param-name>usc.dnsSrvFile</param-name>
<param-value>/etc/neotip/uscDnsSrv.cache</param-value>
</context-param>
<listener>
     <listener-class>com.netcentrex.scscf.session.SessionServlet</listener-class>
</listener>
<servlet>
<servlet-name>register</servlet-name>
<servlet-class>com.netcentrex.scscf.registrar.RegistrarServlet</servlet-class>
<load-on-startup/>
</servlet>
<servlet>
     <servlet-name>session</servlet-name>
     <servlet-class>com.netcentrex.scscf.session.SessionServlet</servlet-class>
     <load-on-startup/>
</servlet>
<servlet>
     <servlet-name>route</servlet-name>
     <servlet-class>com.netcentrex.scscf.fork.RouteServlet</servlet-class>
     <load-on-startup/>
</servlet>
<servlet>
     <servlet-name>icscf</servlet-name>
     <servlet-class>com.netcentrex.scscf.embeddedI.IEmbeddedServlet</servlet-class>
     <load-on-startup/>
</servlet>
<servlet-mapping>
<servlet-name>register</servlet-name>
<pattern>
<equal>
     <var>request.method</var>
     <value>REGISTER</value>
</equal>
</pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>session</servlet-name>
<pattern>
     <and>
          <not>
          <equal>
                    <var>request.method</var>
                    <value>REGISTER</value>
          </equal>
          </not>
          <not>
     <exists>
               <var>request.uri.param.uscroute</var>
          </exists>
          </not>
          <not>
     <exists>
               <var>request.uri.param.icscfroute</var>
          </exists>
          </not>
     </and>
</pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>route</servlet-name>
<pattern>
     <and>
          <not>
          <equal>
                    <var>request.method</var>
                    <value>REGISTER</value>
          </equal>
          </not>
          <exists>
          <var>request.uri.param.uscroute</var>
     </exists>
     </and>
</pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>icscf</servlet-name>
<pattern>
     <and>
          <not>
          <equal>
                    <var>request.method</var>
                    <value>REGISTER</value>
          </equal>
          </not>
          <exists>
     <var>request.uri.param.icscfroute</var>
     </exists>
     </and>
</pattern>
</servlet-mapping>
<session-config>
     <session-timeout>30</session-timeout>
</session-config>
</sip-app>
In msi-config.xml, we have:
<Server Cluster="BEA_ENGINE_TIER_CLUST" EnabledForDomainLog="false"
ListenAddress="192.168.150.26" ListenPort="8001" Name="engine1"
NativeIOEnabled="true" NetworkAccessPoints="sipchannel"
ServerVersion="8.1.5.0" StdoutDebugEnabled="true"
StdoutEnabled="true" StdoutSeverityLevel="64">
<NetworkAccessPoint ListenAddress="192.168.150.34"
ListenPort="5060" Name="sipchannel" Protocol="sip"
PublicAddress="192.168.150.34" SourcePorts="41000-42000"/>
<SSL Enabled="false" IdentityAndTrustLocations="KeyStores" Name="engine1"/>
<Log FileCount="10" FileMinSize="60000" Name="engine1" NumberOfFilesLimited="true"/>
<ExecuteQueue Name="sip.transport.Default" QueueLength="2048" ThreadCount="25"/>
<ExecuteQueue Name="REGISTRARQueue" QueueLength="2048" ThreadCount="25"/>
<ExecuteQueue Name="sip.transport.Default" QueueLength="2048" ThreadCount="25"/>
<ExecuteQueue Name="weblogic.kernel.Default"/>
<ExecuteQueue Name="sip.timer.Default" QueueLength="2048" ThreadCount="25"/>
<ExecuteQueue Name="sip.tracing.local" QueueLength="1024"
ThreadCount="1" ThreadsMaximum="1" ThreadsMinimum="1"/>
<ExecuteQueue Name="sip.tracing.domain" QueueLength="1024"
ThreadCount="1" ThreadsMaximum="1" ThreadsMinimum="1"/>
</Server>
Then when I launch a SIP REGISTRATION operation I get the following trace:
2007-05-30 17:37:03,649 ERROR RegistrarServlet [ExecuteThread: '23' for queue: 'sip.transport.Default'] : Error while processing request: REGISTER sip:netcentrexbench.net SIP/2.0
P-Charging-Vector: icid-value=AyretyU0dm+1970294253=0465138796
P-Access-Network-Info: ADSL;dsl-location="netcentrexbench.net;1.2.3.4"
CSeq: 2 REGISTER
Call-ID: [email protected]
Supported: path
Via: SIP/2.0/UDP 192.168.254.56:5063;branch=z9hG4bK-19606-1-2
From: dench0 <sip:[email protected]>;tag=1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
To: dench0 <sip:[email protected]>
Authorization: Digest username="dench0",realm="netcentrexbench.net",cnonce="6b8b4567",nc=00000001,qop=auth,uri="sip:192.168.150.34:5060",nonce="NQei3RIBAAA=le+kkCcrZcahXxQ7M6r7dw==",response="b824a93822b267ddfaa07f4039d99d95",algorithm=MD5
Content-Length: 0
Contact: sip:[email protected]:5063
User-Agent: LYNX_BENCH
Path: <sip:[email protected]:5063;lr>
Require: path
Expires: 36000
Max-Forwards: 70
java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
My first doubt is that I think I should get "ERROR RegistrarServlet [ExecuteThread: '23' for queue: 'REGISTRARQueue'] " instead of "ERROR RegistrarServlet [ExecuteThread: '23' for queue: 'sip.transport.Default'] "
First question: did I miss something or did something wrong in the configuration?
Second question: is it really possible to assign a single servlet (from an application containing many other servlets) to a dediacted execute queue?
Third question: any help is welcome :-)
Thanks in advance,
Lionel,

At teh end I found the basic :-) problem on my exception but anyway , the used execute queue for REGISTER is always sip.transport.default
Help on this point is welcome!
Thanks

Session in servlet

Similar Messages

Maybe you are looking for