Session problem in cluster

Hello!
          We have 3 servers, one main server (A) and 2(B,C) managed servers in
          cluster.
          All requests will always go to server B first, if it is run.
          Assume, that session have been created on server B. Since, We have the
          cluster, this session must be replicated to server C.
          Next, I shut down server B from cluster. And everything is ok, session is
          alive. All requests go to server C.
          Next, I run server B.
          The problem is in following: the existing session from server C isn't
          replicated to server B :(
          So, if my request goes to server B first, there is no session on it !
          The problem is not with session only, I think, that the problem is in all
          objects, that must be replicated. How to replicate all objects, that must be
          replicated, to a new started up server.
          Help, please !
          Thank you
          in advance.

          We had some funky problems with in-memory replication.
          They were not exactly as you described, but somewhat similar.
          We use Apache plugin to proxy our weblogic cluster. It turns out we had an old versino
          of the apache proxy and this caused all the strange behavior.
          I'm not sure if this will help you at all, but I thought I would mention it, just
          in case.
          "Seeniraj" <[email protected]> wrote:
          >
          >We are also seeing exactly the same behaviour!
          >Any experts who can help us?
          >We are using WLS 6.1 SP2
          >
          >Thanks,
          >Seeniraj
          >
          >"shark79" <[email protected]> wrote:
          >>Hello!
          >>
          >>We have 3 servers, one main server (A) and 2(B,C) managed servers in
          >>cluster.
          >>All requests will always go to server B first, if it is run.
          >>
          >>Assume, that session have been created on server B. Since, We have the
          >>cluster, this session must be replicated to server C.
          >>Next, I shut down server B from cluster. And everything is ok, session
          >is
          >>alive. All requests go to server C.
          >>Next, I run server B.
          >>
          >>The problem is in following: the existing session from server C isn't
          >>replicated to server B :(
          >>So, if my request goes to server B first, there is no session on it !
          >>
          >>The problem is not with session only, I think, that the problem is in all
          >>objects, that must be replicated. How to replicate all objects, that must
          >>be
          >>replicated, to a new started up server.
          >>
          >>Help, please !
          >>
          >>Thank you
          >> in advance.
          >>
          >>
          >>
          >>
          >>
          >

Similar Messages

Session Problem With Cluster Environment

Issue:
To test our web application, we build a simply cluster environment containing 2 nodes, web server and admin. server. if we start all related servers and nodes in the following manner, the web server can not maintain the correct session ID, and mirror them across the nodes due to which the first session/request goes to the first node (node1) and the second request goes to the second (Node2). But Node2 does not have a successful session ID. Thus, our deployed application get a Session Time Out message.
1.     Start WebLogic Application server
2.     Started the nodes.
3.     First start the Webserver
However, when we change the start sequence as follows, the issue will disappear.
1.     First start the WebServer
2.     Start WebLogic Application server
3.     Lastly started the nodes.
Question:
Why does the different start sequences effect the different result of Session Affinity in the cluster environment?
Thanks for any responses!

Hmmm... Never thought about it.
Somehow I always start the environment in this sequence:
- Admin Server
- WebServer
- Cluster
I assume you are using the Apache HTTP server with the WebLogic proxy plug-in as your WebServer.
Here you can configure
- WebLogicCluster - which is a static starting point for the server list, and
- DynamicServerList - enables that WebLogic automatically adds new servers to the server list when they become part of the cluster.
What I can think of is that the last option is set to OFF in which case when new servers are added to the cluster, the plug-in cannot proxy requests to the new server.
This could explain why the start-up sequence matters, i.e., when you first start the WebServer than the cluster nodes, the static list will do its work.
When on the other hand, the cluster nodes are started before the WebServer the starting point for the server list is not created, because somehow
to WebServer is not receiving notifications.
One remark is in order, is that when you did not alter the DynamicServerList property, the default is ON.
Hope the above makes some sense to you. (http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/index.html)

Java Session problem while sending mail(using javamail) using Pl/SQL

Hello ...
i am using Java stored procedure to send mail. but i'm getting java session problem. means only once i can execute that procedure
pls any help.

props.put("smtp.gmail.com",host);I doubt javamail recognizes the 'smtp.gmail.com' property. I think it expects 'mail.host'. Of course since it cannot find a specified howt it assumes by default localhost
Please format your code when you post the next time, there is a nice 'code' button above the post area.
Mike

Session problem in jsp application

I face a session problem. I setting everything in a session and when pass back to a main page, the value is not display in the screen. But after refresh the value will display in the screen and this kind of problem only come out very few time and i dun knw how to solve this...
Anyone here can give me some idea and suggestion or the way to solve this kind of problem!!!

define "2 different clients"
1) You have 2 different PCs and it's using the same session ID for both? I doubt this. I think the server is advanced enough not to use give a session ID that's already been created.
2) You have 1 PC and are using IE or Netscape and using File > New Window to open a new window and connect again. This you can't fix without using only URL rewriting to manage session, because the different windows will share the same session cookies.

Invalidate Session at all Cluster Weblogic

hi all,
i try to save user session in a hashmap on every cluster. and when i need to invalidate it, i will take specified session id. and invalidate it where the session created with normal way to invalidate session.
public class SessionListener implements HttpSessionListener {
public HashMap<String, HttpSession> sessionHolder = new HashMap<String, HttpSession>();
@Override
public void sessionCreated(HttpSessionEvent se) {
sessionHolder.put(se.getSession().getId(), se.getSession());
public void invalidate(String sessionId){
if(this.sessionHolder.get(sessionId)!= null){
System.out.println("Invalidate session ID : " + sessionId);
HttpSession session = sessionHolder.get(sessionId);
session.invalidate();
} else {
System.out.println("Session is not created in this cluster ID : " + sessionId);
@Override
public void sessionDestroyed(HttpSessionEvent se) {
System.out.println("Session " + se.getSession().getId() + " has been destoryed");
sessionHolder.remove(se.getSession().getId());
session will perish where invalidate occur. but on other cluster session is still avaliable.
why the session on other cluster is still. and how to also invalidate session on other cluster.
thanks.
Edited by: jeggy on Jan 20, 2011 8:47 PM

Can you provide little bit more information on how many servers, clusters you have and what kind of replication etc?

Session problem on clustered sun fire with SP6.1

Hi All,
I am having a problem with a webapplication on a clustered system.
In the following I describe the current system setup.
I will then describe the setup of the web application.
Following this, I explain the trouble I'm having with sharing sessions in this environment.
Finally, I pose the key question.
SYSTEM SETUP:
Our group has a clustered server setup. I believe the two machines are Sun Fire systems running Solaris 9. Let me know if you need more information concerning the HW.
To manage the cluster, we use Sun Cluster software. Let me know if you need to know the version number. I do not have it handy. We just recently setup the system (in the past 6 months).
Also, we have the newest Sun Web Server installed 6.1. We used the default installation. The only thing we changed was the dynamicreloadinterval variable from "-1" to "60".
WEB APPLICATION:
We have a fairly simple MVC web application setup, which works well on a single-server system. Essentially, the web application (1) asks for a certain input via a webform, (2) takes this input, and uses it to get information from a database, (3) puts this information into a httpsession attribute, (4) redirects the response to a JSP. The JSP gets the httpsession attribute (populated in step 3) and prints it out.
So, HTML with form posts to Servlet, Servlet gets data from database and populates a session attribute, JSP gets that session attribute and prints it out.
Between each transition from HTML, Servlet and JSP, the currently processing server may switch. I.e. the HTML may be served, for instance, by ClusterServer1, the Servlet may be handled, for instance, by ClusterServer2, and the JSP may be served at random by either.
THE TROUBLE I'M HAVING
Sometimes, my JSP is able to find the session attribute and print out whatever I put into the session during the Servlet step. However, sometimes, the JSP will print out "null" (the session attribute isn't available to the JSP).
For the HTML and the JSP, I have the page print out what server it is being served from. Thus, I can tell that the HTML is served from, for instance, ClusterServer1 while JSP is served from, for instance, ClusterServer2. Sometimes, the same server serves both.
KEY QUESTIONS:
Why would this be happening?
How can I have a session stick to the user and be shared across both servers?
What other information would you need to provide an answer concerning this issue?
I appreciate your efforts very much!
Matthias Edrich
dailysun

Hi All,
Hi Elving,
I read through the documentation and have the following questions:
(1) It seems that I can share sessions amongst both servers if I
configure the web server to store sessions in a persistant manner such as in a file or in a database. Is this correct?
(2) To enable this persistent storage of a session, I would need to change the Session Manager used. Is this correct?
(3) If yes, I have the choice between the following managers. Please correct me if I have misunderstood the options.
- PersistentManager: Instead of securing session information
in memory, this manager saves session information within
a file on the server in a directory, which I specify within
sun-web.xml
- IWSSessionManager: With this manager, I can store sessions
in a defined database or file on the server.
- MMapSessionManager: This manager also stores sessions in
a file on the server
(4) What is the difference between PersistentManager and
MMapSessionManager if my web server is running in
single-process mode?
(5) If MMapSessionManager is a file-based manager, where do I
specify to what directory the related file is stored to as I
do in PersistentManager?
(6) What are the advantages and disadvantages of
Persistent/IWS/MMap managers?
(7) In looking at SessionManagers, am I even barking up
the right tree? It seems like these would help me share
sessions across clustered servers.
(8) Finally, I guess my plan of action would be the following:
-> Identify what session manager to use
-> Include a sun-web.xml file in /WEB-INF containing
the manager-specific info
-> Reload my web application
-> done...
Is this correct?
Elving, I appreciate your help. Thanks!
dailysun

Session problem in a new window created by window.open()

hello,
I have a drugsearch.jsp page, I sessioned an durgCollection object on this jsp page using session.setAttribute("drugCollection",drugCollection);
there is a link on this jsp which will call a javascript to open a new window .
here is the javascript to open another new window:
function openReportWindow()
window.open("/drug/Report.jsp","report", "toolbar,scrollbars,width=800,height=800,left=100,top=10");
but in the Report.jsp, I won't be able to get the same session object as in the calling jsp ( drugsearch.jsp) by calling session.getAttribute("drugCollection").
if I change the link on drugsearch.jsp to link to the Report.jsp directly instead of opening a new window, then I can get the same session object from the Report.jsp.
what's the problem? can someone give me an advice?
thanks

A session is assosiated with one client(browser).
when you open a new browser, a new session is created. In order to have common place for both the browsers, try storing the data in the 'Servlet Context'

Session problem in ADF BC

We have an application developed in Jdev 10.1.3.4 (JSP, Struts, ADF BC) and running on OAS. Now we have a big problem with session, hope somebody can help with some ideas.
We set session time to 45 min in the web.xml. The problem is that sometimes some user work on a page with form,for instance performing some edit activity. If he/she leave the page open inactive for more than 45 minutes and come back from lunch, press the ’save’ button, the application would then commit the change to the wrong row in database, most probably the top row in the View Object(VO) instance. This is because the application module actually does a rollback when session expires, it loses all user data.(e.g. row currency in VO instance).
To avoid saving wrong data to the wrong place, we implemented a session Filter(see att. Below: ApplicationSessionExpiryFilter.java) to catch session time-out and forward request to an error page alerting user that their session has expired due to long time of inactivity. The Filter works as it should but it gives another problem. If user already has one of our application page open for very long time and open another page in a new browser (e.g. click a link from an email), he/she will get session-expire error immediately in the new browser. I guess it is because the session in the first browser already expires and the newly opened the browser shares the same session with the first one. That is how browsers works, we can do nothing about it.
But our users are of course not very happy about getting the session errors in a newly opened browser. So we tried implementing a heartbeat funtion in AJAX(see att. Below: Heartheat.html and Template.jsp) to keep the session alive until the page is closed. Basically what we do is adding an invisible div tag in every jsp page and invoke AJAX funtion to periodically update the div tag with a small html page. In this way, a request is being sent to the server every 5 minutes thus the session should be kept alive until the page/browser is closed.
It sounds to us like a very logical solution but it doesn’t work very properly. We sometimes still get the session error page immediately after opening a new page while we have another page open for long time.
Could anyone please help to look at our Filter and heatbeat funtion? Is there anything wrong with our Filter or the heartbeat? Why does the session still expire before we close the page?
All we do here is to try to avoid the initial probelm with saving data after session and the application module expires. If anyone has a better solution to this problem, we would very much like to try. Appreciate if anyone can share some ideas!
Thanks in advance!
*1. ApplicationSessionExpiryFilter.java*
public class ApplicationSessionExpiryFilter implements Filter {
private FilterConfig _filterConfig = null;
public void init(FilterConfig filterConfig) throws ServletException {
_filterConfig = filterConfig;
public void destroy() {
_filterConfig = null;
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain) throws IOException, ServletException {
HttpServletRequest httpRequest = (HttpServletRequest)request;
boolean sessionInvalid = false;
if(httpRequest.getRequestedSessionId() != null) {
if(!httpRequest.isRequestedSessionIdValid()) {
if (!httpRequest.getRequestURI().endsWith("sessionExpired.do")) {
sessionInvalid = true;
if (sessionInvalid) {
((HttpServletResponse) response).sendRedirect(_filterConfig.getInitParameter("SessionTimeoutRedirect"));
else {
chain.doFilter(request, response);
*2. Heartheat.html* (A small html page to be invoked by template.jsp periodically)
<html>
<head>
<META Http-Equiv="Cache-Control" Content="no-cache, must-revalidate">
<META Http-Equiv="Pragma" Content="no-cache">
<META Http-Equiv="Expires" Content="Expires: Mon, 26 Jul 1997 05:00:00 GMT">
</head>
<body>
heartbeat to keep session alive!
</body>
</html>
*3. Template.jsp* (Template page to be extended by all jsp pages, invoke heart.html every 5 min)
<Html>
<body>
<div id="heartbeat" style="display:none">
</div>
<script type="text/javascript" language="javascript">
new Ajax.PeriodicalUpdater('heartbeat','jsp/template/heartbeat.html',{ method: 'post', frequency: 300, decay: 1 }); // update heartbeat.html every 300 sec(5min)
</script>
</body></html>

Hi Shay,
Reviewing ADFContex methods it seems that this object shouldn't be accessible from BC. Example:
public static ADFContext initADFContext(java.lang.Object context,
                                        java.lang.Object session,
                                        java.lang.Object request,
                                        java.lang.Object response)
    Initializes the ADFContext for the environment of the specified context.
    Parameters:
        context - the ServletContext or PortletContext of the current execution environment.
        session - the HttpSession or PortletSession of the current execution environment. OPTIONAL.
        request - the HttpServletRequest or PortletRequest of the current execution environment. OPTIONAL.
        response - the HttpServletResponse or PortletResponse of the current execution environment. OPTIONAL.
    Returns:
        the ADFContext that was current when init was invoked. Should be passed back to resetADFContext after the block requiring the ADFContext has completed.Kuba

What causes "Timed out server" in WL Cluster and a question about session in WL Cluster

          Hi.
          We are using Weblogic 5.1 with SP 8. We have been encountering a problem in our
          clustered environment. We setup our (clustered)environment to have 3 instances(WL1,
          WL2, WL3) of weblogic running in one box. When one instance, let say WL1, responds
          to a request(1st request for a session), the session is binded to that instance
          till the session is terminated/expired. Which means succeeding request for that
          session can only be served by WL1(we tried stopping WL1 but WL2 and WL3 wont accept
          the request--which only causes the page to time out). Shouldnt it behave in such
          a way that other instances can get serve the request(failover)?
          Also, occasionally we encounter "Time out server" in one of the instance of WL.
          When this happens, that instance no longer takes in requests. Would anyone know
          what causes "Time out server"? Does it only happen in clustered environment?
          Need some help ASAP.
          Tnx in adv.


          What do you have in front of WebLogic for Load Balancing?
          What are the IP addresses/hostnames of your three instances? What hostname are
          you using in your http requests? Is your DNS configured to do failover?
          Make sure that you have session replication turned on. See the edocs.bea.com.
          Mike Reiche
          "clstrproblem" <[email protected]> wrote:
          >
          >Hi.
          >
          >We are using Weblogic 5.1 with SP 8. We have been encountering a problem
          >in our
          >clustered environment. We setup our (clustered)environment to have 3
          >instances(WL1,
          >WL2, WL3) of weblogic running in one box. When one instance, let say
          >WL1, responds
          >to a request(1st request for a session), the session is binded to that
          >instance
          >till the session is terminated/expired. Which means succeeding request
          >for that
          >session can only be served by WL1(we tried stopping WL1 but WL2 and WL3
          >wont accept
          >the request--which only causes the page to time out). Shouldnt it behave
          >in such
          >a way that other instances can get serve the request(failover)?
          >
          >Also, occasionally we encounter "Time out server" in one of the instance
          >of WL.
          >When this happens, that instance no longer takes in requests. Would anyone
          >know
          >what causes "Time out server"? Does it only happen in clustered environment?
          >
          >
          >Need some help ASAP.
          >
          >Tnx in adv.
          >
          >
          >
          >
          >
          >
          >

Problem: Stopping cluster due to unhandled exception .. Unable to refresh

Greetings
While testing a rolling upgrade of an application that uses Coherence 3.5.2 on 62-jvm cluster hosted on
11 physical machines, we encountered a situation where after the upgrade was completed, most jvms
in the system abruptly left the cluster. The physical hosts are running CentOS 5.4, the java used is
the 64-bit server version 1.6.0_16-b01. The test was run under a scenario that imposed "moderate"
load, with cpu usage on the physical machines never exceeding 60% busy, network bandwidth never
exceeding 5%, and with some free physical memory. Swapping did not occur during any time during
the test. I believe we are using the default tangosol-coherence.xml. We got the error below in
our coherence.log files on all of the systems, all at about the same time (within 10 milliseconds).
55 of the jvms left the cluster during the incident. There were 55 copies of the error message in
the various logs, all nearly identical except for the time and member id.
My questions include
- what does the error mean?
- what could cause it? (I investigated system logs, and found no evidence of the NIC cards
going off line at the time. Any suggestions about how to look for evidence of broadcast storm?)
- how can we keep it from happening again?
Many thanks for your help -
Mike Murphy
2011-04-26 17:34:14,629 Coherence Logger@9224544 3.5.2/463 ERROR 2011-04-26 17:34:14.629/1929.311 Oracle Coherence GE
3.5.2/463 <Error> (thread=PacketListenerN, member=30): Stopping cluster due to unhandled exception: com.tangosol.net.mes
saging.ConnectionException: Unable to refresh sockets: [UnicastUdpSocket{State=STATE_OPEN, address:port=10.48.88.116:809
1}, MulticastUdpSocket{State=STATE_OPEN, address:port=224.3.5.2:10013, InterfaceAddress=10.48.88.116, TimeToLive=4}, Tcp
SocketAccepter{State=STATE_OPEN, ServerSocket=10.48.88.116:8091}]; last failed socket: MulticastUdpSocket{State=STATE_OP
EN, address:port=224.3.5.2:10013, InterfaceAddress=10.48.88.116, TimeToLive=4}
at com.tangosol.coherence.component.net.Cluster$SocketManager.refreshSockets(Cluster.CDB:91)
at com.tangosol.coherence.component.net.Cluster$SocketManager$MulticastUdpSocket.onInterruptedIOException(Cluste
r.CDB:9)
at com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:33)
at com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:4)
at com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketLis
tener.CDB:19)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
at com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:20)
at com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:4)
at com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketLis
tener.CDB:19)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)

Hi Mike,
It looks like you are having problems with multicast. You can run the multicast test described here
[http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/tune_multigramtest.htm]
which will help in diagnosing the problem

Urgent: Sessions problem pls help me

Hi all,
Its already late to post this problem.pls help me urgently.
I have a servlet & two jsp's. first i request servlet, it processes something and forwards request to my first jsp. In that jsp on a button click, i'm displaying a new popup by calling showModalDialog. this dialog gets data from the same servlet but it forwards to my second jsp.(second jsp can be seen in dialog)
Now if i submit form from my second(dialog) jsp, the servlet reports that session has expired. I tried a lot but invain. any one who helps me is appreciated well by all of our forum.
waiting 4 u r reply,

It could be that you have cookies turned off and you're not using URL Rewriting.
In J2EE, the first time your browser makes a request to the server, the server responds and appends a SESSION_ID parameter to the request as well as storing a cookie with the SESSION_ID.
The second time your browser makes a request, the server checks for the cookie. If it doesn't exist it checks for the parameter. If neither exist the server assumes its the first time your browser has made a request and behaves as describe in the previous paragraph.
In your case when you submit the form if you have disabled cookies and the action attribute doesn't have the SESSION_ID paramter appended to the url, the browser will assume it's a first request. The user will not be logged in, hence your session has expired error.
To fix this you need to encode the URL in your JSP. You can use the struts html:rewrite tag or the HttpServletReponse.encodeURL method, or if you're using JSP 2.0 the JSTL c:url tag.

Session problems in tomcat 5.0.28

Even I shutdown the tomcat 5.0.28 server the session variable is still existing and it is showing the old values. What I have to do to disable the old values? Is it the problem with tomcat 5.0.28 or with JSP coding!

Tomcat serializes sessions to the hard drive when it shutsdown. If you don't want this you have three choices:
1: you can disable this functionality in the server.xml. Check the documentation.
2: you could just delete the session.ser file when you shut down tomcat. This file is under work/standalone/{webapp name}
3: you could close and re-open the browser so that the old jsessionid will not be sent and a new session will be created. The old session will eventually time out.
The third option is probably the easiest.

JSP Session Problems

Hi, i am facing a problem of the Object set into a session not being visible to the others pages. what did i done wrongly?
here is the code:
in login.jsp (currently hardcode cos i haven recieve that part):
<%@page import="fantasy.team.*,java.util.Vector" session="true"%>
<%
Team t = new Team("Kacheek FC");
session.setAttribute("team",t);
if( session.getAttribute("team") ==null){
     out.write("how come null");
}else{
     out.write("not null");
%>
Select
//End of coding
not null will be printed
Following code belong to selectPlayer.jsp:
if( session.getAttribute("team") == null){
          out.write("i am null");               }else{
          out.write("i am not null");
i am null is printed
what is wrong with my coding?
thanks.

i do a
if(session.isNew())
out.write("New");
and the result is new.
meaning that my session is invalidate.
that explain my value from "gone" rite?
how to solve this?
thanks.

Session Problems(ConcurrentModificationException)

Hi,
I am facing some problems with session here.
I get a java.util.ConcurrentModificationException whenever i try to empty the shopping cart.
Could somebody pls kindly advise?
Thanks in advance
below is the code:
<% String item = request.getParameter("itemName");
if(item != null && item.equals("emptyCart")) {
java.util.Enumeration attributeNames = session.getAttributeNames();
while(attributeNames.hasMoreElements()) {
String attributeName = (String)attributeNames.nextElement();
session.removeAttribute(attributeName);
} else if(item != null) {
String attributeName = item + "CD";
session.setAttribute(attributeName, item);
%>

Similar qus answered int his forum ..
refer
http://forum.java.sun.com/thread.jsp?thread=244532&forum=45&message=897268

Session problems on wls6.1

We have two domains with an identical application but one can pass out login
credential through the session without any problems and the other just
cannot retrieve the reference from the session. Both have the same session
settings. Can any one point me a direction to look at? Thank you.
Jack Shieh

We found out what the problem was. Turned out the domain name we used on the
client side didn't match the one on the host, and therefore the session is
recreated for every request.
"Jack Shieh" <[email protected]> wrote in message
news:41e5acba$1@mail...
We have two domains with an identical application but one can pass out
login credential through the session without any problems and the other
just cannot retrieve the reference from the session. Both have the same
session settings. Can any one point me a direction to look at? Thank you.
Jack Shieh

Session problem in cluster

Similar Messages

Maybe you are looking for