Session persistence
Hello everyone,
I'm currently working with WL 6.1 and I'm having trouble with the
persistence of some session variables which are initially created
correctly on the server side, and they get lost (null) once the Web
clients need to access its value.
This is the error which is being written on a log file:
<May 13, 2003 3:05:09 PM EDT> <Error> <HTTP Session> <Could not
deserialize session data
java.io.NotSerializableException:
Things were woriking perfectly, but suddenly after bouncing the server
instance several times, in order to pick up the latest changes in my
classes, I started to get this error once the server tries to load the
jsp.
JSP Code:
<%
Integer businessID = (Integer) session.getAttribute("business_id" );
Util.isCapitolBusiness(businessID.intValue())
%>
I appreciate your help.
Regards.
g.
is the object being put in session context serializable.. Also in
other to avoid any generated classes issues delete all the classes
whcih weblogic generates as part of deploying the application. That
should atleast mitigate one explanation for your problem.
Hope this helps
~a
[email protected] (Gabriel Ornelas De Luna) wrote in message news:<[email protected]>...
> Hello everyone,
> I'm currently working with WL 6.1 and I'm having trouble with the
> persistence of some session variables which are initially created
> correctly on the server side, and they get lost (null) once the Web
> clients need to access its value.
> This is the error which is being written on a log file:
>
> <May 13, 2003 3:05:09 PM EDT> <Error> <HTTP Session> <Could not
> deserialize session data
> java.io.NotSerializableException:
>
> Things were woriking perfectly, but suddenly after bouncing the server
> instance several times, in order to pick up the latest changes in my
> classes, I started to get this error once the server tries to load the
> jsp.
>
> JSP Code:
> <%
> Integer businessID = (Integer) session.getAttribute("business_id" );
> Util.isCapitolBusiness(businessID.intValue())
> %>
>
> I appreciate your help.
> Regards.
> g.
Similar Messages
-
Types of session persistence in clustering
does anybody know what are the types of session persistence in clustering(In-memory replication,Database persistence etc..)
what is the advantages and disadvantages of each type?
we r using oracle appserver 10.1.2.Hi,
HttpSession replication is little different from JNDI replication. In JNDI replication the JNDI objects are binded(Replicated) to all the members JNDI tree. But in case of Http Session Replication the HttpSession Object gets binded only to the Primary and Secondary JVM (WebLogic Instances). So if both Promary and Secondary WebLogic Server Goes Down then it is *"DISASTER"* and you cannot prevent the Disasters when it happens.
But you can minimize the Disaster effects by chosing *"Using Replication Groups"*...It means you can decide in which all nodes of the cluster you want your Secondary HttpSession should be replicated.... Please refer to : http://download.oracle.com/docs/cd/E12840_01/wls/docs103/cluster/failover.html
By default, WebLogic Server attempts to create session state replicas on a different machine than the one that hosts the primary session state. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered servers to be used for storing session state replicas. Using the WebLogic Server Console, you can define unique machine names that will host individual server instances. These machine names can be associated with new WebLogic Server instances to identify where the servers reside in your system..
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic/?p=2649 (Middleware Magic Is Here) -
Fatal bug with shared JDBC Session Persistence
We are attempting to launch a three-tier site with two clusters, one at the
web layer (JSP/servlet/images) and a separate cluster at the app server
layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on Solaris
2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs. We
are using the WebLogic kona/oracle driver for session persistence because
the Oracle JDBC driver would not work for this purpose - we are using the
Oracle OCI driver for our EJB persistence in a separate pool in the app
server cluster.
We attempted to configure our web cluster to work with in-memory session
replication. We found the performance of the WebLogic proxy to be abysmal -
causing a 5x to 10x performance degredation over shared JDBC persistence. We
were running the proxy on WebLogic, which we were advised would be slow. Its
performance is beyond slow, it is completely unusable and should NEVER be a
recommended or even supported configuration. We do not wish to purchase
separate licenses for iPlanet, refuse to run IIS in a production setting,
and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
persistence until we can upgrade to 5.1.
Using JDBC session persistence with a shared persistent store amongst all
the clustered web servers results in our users getting brand-new sessions
populated with data from OTHER USERS' SESSIONS. This is very easy to
replicate using the provided test JSP and java class. This behavior results
in new users coming to the site and finding themselves logged in as other
users.
The test.jsp file simply accesses the session, prints out some information,
and then adds a few values to the session. The JSP prints out the value of
session.isNew(), the session's ID, and the number of values in the session
space. If you hit this jsp with a new browser window, the session should be
new, and the number of values should be zero.
The test Java class hits a URL with this test.jsp file repeatedly, and
checks to make sure that the session is empty. It keeps a counter of the
number of hits which resulted in non-empty sessions and the total number of
hits. Because this java class does not maintain cookie data of any kind and
merely opens new HTTP connections, it should always receive a brand-new,
non-empty session.
When we set the JDBC session persistence property
weblogic.httpd.session.persistentStoreShared=true and run the test, we see
periodically see the test.jsp file receiving a brand-new (session.isNew() =
true), yet non-empty (session.getValueNames().length != 0) session. This is
extremely bad behavior and makes the shared JDBC session persistence setting
worthless. We were able to duplicate this behavior with both a single server
and multiple servers in a cluster.
If we set weblogic.httpd.session.persistentStoreShared=false, then this test
works fine. This also means that we cannot cluster web servers.
To run the test, simply start a WebLogic instance using the provided
properties file, put the jsp in the document-root somewhere, and then run
SessionTest.java, providing the URL of the test JSP as the only command-line
argument. You will need to modify the properties file to have the proper
database settings and document-root. The java class will display a running
tally of the number of hits, and the number of hits that result in
non-empty, illegal sessions, with a total at the end.
So, we are now in a position where we are completely unable to launch our
site in a clustered, no-single-point-of-failure configuration. Obviously,
clustering was one of the main reasons to choose WebLogic, and we are
extremely distressed that we are unable to get this configuration to work.
Any help would be appreciated.
[web.standalone.properties]
[SessionTest.java]
[test.jsp]
I hope this is not too far fetched, but we are expieriencing a similar
problem with jms (messages are mixed up between queues). This happens only
if we are using message persistence in an oracle db (everything works ok
when we are not using persistent messages). Could it be that there is a
serious bug in the jdbc code/oracle driver code or connection handling
(regarding multi threading)? This would explain that, whenever you use
persistence with oracle databases, messages/sessions (or other) are mixed
up.
- Falk
"Grant Kushida" <[email protected]> wrote in message
news:[email protected]...
> We are attempting to launch a three-tier site with two clusters, one at
the
> web layer (JSP/servlet/images) and a separate cluster at the app server
> layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on
Solaris
> 2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
> JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs.
We
> are using the WebLogic kona/oracle driver for session persistence because
> the Oracle JDBC driver would not work for this purpose - we are using the
> Oracle OCI driver for our EJB persistence in a separate pool in the app
> server cluster.
>
> We attempted to configure our web cluster to work with in-memory session
> replication. We found the performance of the WebLogic proxy to be
abysmal -
> causing a 5x to 10x performance degredation over shared JDBC persistence.
We
> were running the proxy on WebLogic, which we were advised would be slow.
Its
> performance is beyond slow, it is completely unusable and should NEVER be
a
> recommended or even supported configuration. We do not wish to purchase
> separate licenses for iPlanet, refuse to run IIS in a production setting,
> and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
> persistence until we can upgrade to 5.1.
>
> Using JDBC session persistence with a shared persistent store amongst all
> the clustered web servers results in our users getting brand-new sessions
> populated with data from OTHER USERS' SESSIONS. This is very easy to
> replicate using the provided test JSP and java class. This behavior
results
> in new users coming to the site and finding themselves logged in as other
> users.
>
> The test.jsp file simply accesses the session, prints out some
information,
> and then adds a few values to the session. The JSP prints out the value of
> session.isNew(), the session's ID, and the number of values in the session
> space. If you hit this jsp with a new browser window, the session should
be
> new, and the number of values should be zero.
>
> The test Java class hits a URL with this test.jsp file repeatedly, and
> checks to make sure that the session is empty. It keeps a counter of the
> number of hits which resulted in non-empty sessions and the total number
of
> hits. Because this java class does not maintain cookie data of any kind
and
> merely opens new HTTP connections, it should always receive a brand-new,
> non-empty session.
>
> When we set the JDBC session persistence property
> weblogic.httpd.session.persistentStoreShared=true and run the test, we see
> periodically see the test.jsp file receiving a brand-new (session.isNew()
=
> true), yet non-empty (session.getValueNames().length != 0) session. This
is
> extremely bad behavior and makes the shared JDBC session persistence
setting
> worthless. We were able to duplicate this behavior with both a single
server
> and multiple servers in a cluster.
>
> If we set weblogic.httpd.session.persistentStoreShared=false, then this
test
> works fine. This also means that we cannot cluster web servers.
>
> To run the test, simply start a WebLogic instance using the provided
> properties file, put the jsp in the document-root somewhere, and then run
> SessionTest.java, providing the URL of the test JSP as the only
command-line
> argument. You will need to modify the properties file to have the proper
> database settings and document-root. The java class will display a running
> tally of the number of hits, and the number of hits that result in
> non-empty, illegal sessions, with a total at the end.
>
> So, we are now in a position where we are completely unable to launch our
> site in a clustered, no-single-point-of-failure configuration. Obviously,
> clustering was one of the main reasons to choose WebLogic, and we are
> extremely distressed that we are unable to get this configuration to work.
> Any help would be appreciated.
>
>
>
>
-
Problems disabling restart session persistence in Tomcat
I'm running Tomcat 5.5.17. I've been working on an application for quite some time when the tomcat logs suddenly started to fill up with the following errors each time I restart Tomcat:
2006-09-29 21:15:10,539 | WARN | StandardSession.java | writeObject() | 1468 | Cannot serialize session attribute publicPictures for session 9184A48FEFC99FAA3573A4DE1F75CCD5
I've searched the web, and found out that the reason for this is that Tomcats "Restart Session Persistence" is turned on. So how do I turn that off?
According to a few sites in the web there should be a file called application.xml, in which I can put the line <Manager pathname=""/> to disable the Session Persistence manager. The problem is that on my Tomcat installation there's no such file.
So I tried to create the file $CATALINA_HOME/conf/application.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN'
'http://java.sun.com/dtd/application_1_3.dtd'>
<application>
<Manager pathname=""/>
</application>But this had no effect at all. So can someone please explain to me how I can disable the Session Persistence manager?I had a similar problem in that during restarts sometimes I would get messages about null pointer exceptions which seemed to be related to attempted session persistence. I never paid a lot of attention but eventually decided to do something about it, i.e disable session persistence, since the errors seemed to slowdown restarts.
Based on this:
http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html
I added a Manager element to my main Context element, using the standard manager class and setting the pathname attribute to an empty string:
<Context path="/" debug="1" reloadable="true" crossContext="true">
<Manager class="org.apache.catalina.session.StandardManager" pathname="" />
</Context>
Since the errors I was getting were sporadic anyway I cannot definitively say this fixed it but I have not seen any errors since making the change and shutdowns seem to go faster now. -
Revision: 939
Author: [email protected]
Date: 2008-03-26 13:35:44 -0700 (Wed, 26 Mar 2008)
Log Message:
Bug: BLZ-67 - Should turn off session persistence in the Tomcat server we ship.
QA: No
Doc: No
Checkintests: Pass
Details - Turning off session persistence in the version of Tomcat that ships with BlazeDS. We don't store much in the session so session persistence doesn't make much sense for us. Users should feel free to turn this back on if they feel they need it.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-67
Modified Paths:
blazeds/branches/3.0.x/servers/apache-tomcat-6.0.14/conf/context.xmlHi, thank you for your replies, I found out few things about my servlet, and its portability
and i have few questions, although i marked this topic as answered i guess its ok to post
I am using javax.servlet.context.tempdir to store my files in that servletcontext temporary directory. But i dont know how to give hyperlink
of the modified files to the user for them to download the modified files.
What i am using to get the tempdir i will paste
File baseurl = (File)this.getServletContext().getAttribute("javax.servlet.context.tempdir");
System.out.println(baseurl);
baseurl = new File(baseurl.getAbsolutePath()+File.separator+"temp"+File.separator+"files");
baseurl.mkdirs();so i am storing my files in that temp/files folder and the servlet processes them and modifies them, then how to present them as
links to the user for download ?
and as the servlet is multithreaded by nature, if my servlet gets 2 different requests with same file names, i guess one of them will be overwritten
And i want to create unique directory for each request made to the servlet , so file names dont clash.
one another thing is that i want my servlet to be executed by my <form action> only, I dont want the user to simply type url and trigger the servlet
Reply A.S.A.P. please..
Thanks and regards,
Mihir Pandya -
Are Session Persistence And Clustering Inter-related?
Hi,
I'm attempting to set up session persistence (via jdbc) on WL 4.03. I have
configured weblogic.properties according to the admin guide, and I've
written a very simple test servlet. However, whenever I attempt to save a
value with session.putValue(), the following exception is thrown:
"java.rmi.RemoteException: javax.ejb.FinderException: Refresh:
ClusteredSession:
308978692445-1/-1094565652488309727/-1062731518/4/7011/7011/7012/7012 not
found"
The WL instance I am using is not part of a cluster. Is clustering
required for session persistence? If not, should I be using something other
than the normal HttpSession class?
Thanks,
John
Please disregard. The problem was due to an error in the definition of the
WL_SERVLET_SESSIONS table.
-
Outlook credentials enterprise persistence vs logon session persistence - hosted Exchange
We moved from an internal AD integrated Exchange 2010 environment to an external hosted Exchange 2010. Prior to the move credentials were passed through and never needed. Since the move a large number of Outlook clients have not been storing
credentials correctly. The credentials show up in the windows credential manager with "Logon Session" persistence which means they disappear after the next logoff or restart. The option to remember credentials is checked when Outlook
prompts the user. Client machines are Windows 7 SP1 x64. For Outlook 2010 14.0.7015.1000 I did not find a fix. A workaround I've come up with on Outlook 2013 15.0.4569.1506 is to manually recreate each of the credential manager entries created
by Outlook via "add a generic credential", which then stores them with "Enterprise" persistence which keeps the info across logoffs/restarts. This solves the problem until the password expiration hits in 90 days at which point the
new info has to be reentered into the credential manager. These are the three generic credentials entries I am manually typing into the credential manager including the parentheses character for character, with the user's full email address as username
in each case to gain enterprise persistence:
Internet or network address: MS.Outlook.15:[email protected]:PUT
Internet or network address: [email protected] (Windows Identity)
Internet or network address: external.exchange.server.net
local autodiscover override in use -
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover]
"domain.com"="\\\\domain.com\\sysvol\\domain.com\\scripts\\autodiscover.xml"
"PreferLocalXML"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeScpLookup"=dword:00000001
"ExcludeSrvRecord"=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers]
"external.exchange.server.net"=hex(0):
Why is enterprise persistence not happening automatically when the user checks the option to remember the credentials at an Outlook prompt?Solved, it was a MS patch. After removing the KB2956087
the problem disappeared. -
Hi
I have read about the scope of session only for one web application.
When I need to share the session between more than one web application, I
think about use JDBC session persistence.
Do you know if is it possible ?
Thanks
It's possible, please refer to
http://www.weblogic.com/docs51/admindocs/http.html#sessionjdbc for details.
Alex Rojkov
http://www.ObjectReflection.com
[email protected]
We are coming soon...
"Jin Group" <[email protected]> wrote in message
news:[email protected]..
> Hi
> I have read about the scope of session only for one web application.
> When I need to share the session between more than one web application, I
> think about use JDBC session persistence.
> Do you know if is it possible ?
>
> Thanks
>
>
>
>
-
Cisco ace Load balancer not maintaining session persistence
Hi All,
We have observed from the IIS logs on the internal webservers that loadbalancer is not maintaining session persistence for two specific request for the internal servers.
https://123.xyz.com/Webresource.axd
https://123.xyz.com/ScriptResource.axd
Error
Webresource.axd : 500
Scriptresource.axd: 404
Session persistence is maintained for all other requests hitting loadbalancer.
Issue is observerd on hits for these two specified components. WebResource.axd and ScriptResource.axd are Http Handlers used by ASP.NET and Ajax to add client-side scripting to the outgoing web page.
For e.g /WebResource.axd d=t2GXfySdqWmJ-lZSI0KVbw2&t=634868473645172160 is valid for server 1 and return 200 response but the same request is seen on few other servers where the response is 404 even though load balancer cookie is same. This means that if the request for the both the axd contains a valid decrypter and it connects to the right server then the response seen is 200.
The url passed by the user contains d and t parameters when are unique for each user session.
Solution tried:
Accessed website via another VIP without http redirect rule but could not see difference.
Tried to match machine key across all servers : Failed . Could see the ‘d’ value different for each server.
Load balancer VIP :
x.x.x.x
redirect: http > https
SSL Offload : ON
Poool:
WEB1
WEB2
WEB3
WEB4
WEB5
All servers listening on port 80
sticky config:
sticky ihttp-cookie cookie1 vip-1.1.1.1-80-stickyfarm
cookie insert browser-expire
replicate sticky
serverfarm vip-1.1.1.1_80
sticky http-cookie cookie1 vip-farm:1.1.1.1:443
cookie insert browser-expire
replicate sticky
serverfarm farm:1.1.1.1:443
Has anyone else come across similar issue?
Can you plese check if there is any config on cisco ace that will ensure that session persistence is maintained for these 2 requests.
Thank you for all the help.
regards,
SangramHello Sangram,
We would need simultanous packet traces before and after the ACE to get to the root cause of this issue so I would recommend that you open a cisco tac case for more in depth troubleshooing of this issue.
Joel Lamousnery
CCIE R&S - 36768
Engineer, Customer Support
Technical Services -
Session persistence across web apps
Hi,
I am working on a project where we have two web applications deployed in single enterprise application. I want the session object to be shared across the web applications.
Does weblogic had any mechanism to allow for the session object to be shared across the multiple Servlet contexts inside a single enterprise application?
I am using Weblogic 8.1
Thanks,
AnilSession data is not shared between web applications. User data is definantly important to share between applications. The single-sign-on security option is an example of this. But that's kindof a black box. If you use single-sign-on, then simply getting the remote user from the request in your servlet can be used as a key to get user data from your persistance layer (ejb's or jdbc or even jms).
If you don't want to use single-sign-on, you can use a filter. There's some url prestidigitation, also, but otherwise this approach is pretty simple:
1. Protect access to all of your web-app's urls with some naming convention /webappname/secure*. However, don't use these urls in any web page. All servlets and jsps you use should map names beginning with "secure".
2. Filter all access to your webapp (this is a new feature in servlet spec 2.3). Within the filter, use the session id as a key to find out if the user is already login to any other web application. You will need a stateless session bean to do this. The doFilter would be something like this:
SecurityBean securitybean = Utilities.getSecurityBean();
HttpSession session = request.getSession(true);
if (session.getAttribute("myuserdata") == null){
UserData userdata = securitybean.getUserdata(sessionid);
if(userdata != null)
session.setAttribute("myuserdata",userdata);
... now forward the request to the "secure*" url in the filter. If the user was logged in with the slsb securitybean, then your web app will have all of your user data. If the user is not logged in by the securitybean, then the login prompt established in your web.xml will pop-up.
The only extra work is to have a slsb securitybean. This can use the RoleManager in oc4j or it can use the jaas implementation in oc4j to log the user in, using the sessionid to get the username.
The shared="true" attribute should be used for all application in the *-web-site.xml, so that the sessionid's are the same.
regards,
the elephantwalker
www.elephantwalker.com -
Please, Help me with keeping SESSION persistence
Hi guys,
I run into the problem when I can't pass a Java Bean because session is lost.
What am I doing: First, I start my webserver - tomcat, but DON'T open a browser. Then I start some Agent program in Java which sends a request to Tomcat - URL to JSP page(setAgent.jsp), passing all the parameters (with url.openStream())
This setAgent.jsp creates Java Bean with <jsp:useBean id="sdbean" class=...scope="session"/>, sets all the parameters into the bean.
Then I open my Netscape browser calling another JSP(getAgent.jsp) which wants to access this bean (also with <jsp:useBean.../>, sdbean.getName()) and this bean is empty - no data like brand new bean.
But when I call setAgent.jsp?... directly in the browser and then getAgent.jsp - then that Java Bean is populated.
So I figured that the session is not the same.
How to preserve the session or what is the other approach to pass the data through the web server without opening browser? Or how to retrieve that previous Session? If I simply get Session_ID what can I do with it?
Thanks a lot.
GeneIsn't this the same thing you asked here?
http://forum.java.sun.com/thread.jsp?forum=45&thread=469430 -
HTTPS persistence SSL session, ACN 4.2.1
Customer is experiencing a problem resulting in the ACN software resolving the host.domain.com twice. Webapplication https://host.domain.com/webapp/index.jsp. The customer uses a ACN to proxy the https request. The host.domain gets resolve to 1 of 4 available application servers (webserver). At the application login page (index.jsp) the user is successfully authenticated by the application's Login servlet on webserver 1. The user is then redirected to the select application, local to the webserver 1. It appears that when the ACN receives the response from webserver 1 with the fully qualitfying URL. The redirection cause the ACN to resolve the host.domain against DNS and as a result, the user's browser is redirected to a different webserver. The users previous session is no longer valid, breaking the client/webserver trusted relationship
If the above user uses 1 of the 4 available IP address on the DNS entry, the users successfully maintains the SSL session. The customer is migrating to a Cisco Content Engine 560 running version 4.2.1 ACN software.
I understand there are ACN features that could effect the HTTP session persistence/SSL trust. The services/features include boomerang, Reverse Proxy, content balancing. I request information on the service or feature of the ACN that could cause the problem I speak of from above.
I understand there are different methods of implementing session persistence, like sticky session and SSL sticky, but believe the ACN does provide this feature.The customer is experiencing network issues when attempting to access our application. The customer is experiencing has been seen with a previous customers that had a similar network devices.
The customer uses a Cisco Content Engine CE-560 with Application and Content Networking Software (ACNS) version 4.2.1. The problem seems to a result of the ACNS resolving the hostname.domain.com twice. The webserver's DNS (hostname.domain.com) entry resolves to one of four available webservers (DNS round robining).
nslookup hostname.domain.com
webserver1 webserver2 webserver3 webserver4
nslookup hostname.domain.com
webserver2 webserver3 webserver4 webserver1
and so on.
All client/webserver communication is through SSL. When the customer uses the FQDN URL (https://hostname.domain.com/webapp/index.jsp) to access the application login page, the server portion of the URL is resolved to webserver1. At this time, the customer has an established HTTPS session with webserver1. Once a login servlet running on webserver1, receives the customer supplied login credentials, the servlet sends a server response 302 redirecting the customer to the selected application.
This redirection response seems to cause the ACNS to resolve the hostname.domain.com and as a result, the customer's browser is redirected to a different webserver, webserver2. The users previous session is no longer valid, causing the application to generate a false inactivity timeout.
If the customer sends a HTTPS request using anyone of the four IP address from DNS, the session is maintained and the customer does not receive the false inactivity timeout, because the session is not "broken".
The customer is migrating off of a Netscape (iPlanet) Web Proxy solution and does not experience the problem accessing the application, using the FQDN URL.
DNS caching is enabled on the customer CE. -
What is the lifetime of a session?
Hi all,
I am writing a .NET application that queries an Oracle Database. I am altering the Session variable current_schema in order to execute commands with a different default schema than that of the logged in user. The change to current_schema should persist for the duration of the session, but I'm not sure how long this is. Originally I expected it to be the lifetime of the connection, but this is not the case.
The following code illustrates:
public sub getvalue()
Static Dim done As Boolean
Dim daODP As DataAdapter
Dim conODP As New OracleConnection("Data source=oracleInstance;User ID = username; Password = Password")
Dim cmdODP As New OracleCommand("alter session set current_schema = scott", conODP)
daODP = New OracleDataAdapter("Select columnName from TBLNAME", conODP)
If Not done Then
conODP.Open()
cmdODP.ExecuteNonQuery()
conODP.Close()
done = True
End If
conODP.Open()
Dim dsODP As New DataSet
daODP.Fill(dsODP)
conODP.Close()
end sub
The Alter session command is executed only the first time the method is called, however each subsequent call inherits the same 'session' from oracle, because if it didn't then the call would fail. Once the test application is restarted the session is reset.
When is a session created and when is it ended? Is session length a server property? is it dependent on traffic?(eg:timeout) Is it valid for the life of the application?So, to be clear (I was doing some searching around on connection pooling and sessions just to clarify things in my mind), if I use the default conection pooling enabled then I have to take extra care to ensure that I don't leave anything persistent laying about? For example, package variables set in one transaction could wind up persisting to another transaction by another user if they happen to pick up the connection used by the first user?
Damn, but that really is a pain for anyone with a history of using packages and whose brain just automatically assumes session-persistence for a given user when they're coding - it just simplifies so many things. But I don't particularly care to deal with the overhead of opening and closing connections left and right either. Time-consuming and expensive, especially the way .NET front end users are used to opening and closing them left and right.
Time to do some thinking on this..... -
Failover is work, but Session replication doesn't work!
Dear all,
My Cluster can failover, but can't session replicate....
I start up the 2 WLS 6.0 and the Web Server, then I visit
http://web_server_ip/myWebApp/SessionServlet serveral times, then the
counter variable in the session raise up, then I down the "target" WLS, then
I try http://web_server_ip/myWebApp/SessionServlet now, I can call but the
counter restart.... so the session seems not yet replicated. what I can
do...?!
My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using libproxy.so
with the cluster setting, and use 2 WLS 6.0 (both are running in 7001,7002)
as the Application Server Cluster (WLCluster). one WLS is on Unix Machine
and the other in on a NT. I set the 2 WLSs: the Primary Group is
"WL_rep_group1", and set the secondary is "WL_rep_group2".
Deployment: I deploy the application "myWebApp" (.war) on the servers unix
and nt, adn also deploy to the cluster WLCluster.
I deploy the examplesWebApp to my created domain "demo", and modify the
weblogic.xml:
<weblogic-web-app>
<session-descriptor>
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
</session-descriptor>
<jsp-descriptor>
<jsp-param>
<param-name>
pageCheckSeconds
</param-name>
<param-value>
1
</param-value>
</jsp-param>
<jsp-param>
<param-name>
verbose
</param-name>
<param-value>
true
</param-value>
</jsp-param>
</jsp-descriptor>
</weblogic-web-app>
so ... anything I did wrong, so the WLS can't do Session replication??!!
Please Help or Comment!
Thanks in advance!
with thanks,
Alex Wong
Dear Vinod and Kevin,
Some more information that I think it may help.
First, I want to correct 1 point in my previous message, the Replication
Group is "WLRepGroup1" and the Preferred Secondary Group is "WLRepGroup2"
for the 2 machine WLSs.
Second, I found that the Multicast Communication is not functioning becoz
the switch of my office block the 224.0.0.1's communication, so now I added
a hub for this 2 machine, as a result the multicast is wokring... at least
pass the java utils.MulticastTest....
Thrid, after the mutlicast work, I try the SessionServlet, it is working at
beginning... but after some more clicks, one server will cause the following
error (this time crash on x.y.z.b--NT machine)....
-------- (a long list, the IPs are replaced: x.y.z.a UNIX machine, x.y.z.b
NT machine, x.y.z.c My PC)
Screen caption on demo>Servers>wlserver2 (monitoring> cluster)
Unexpected Error
Connected to x.y.z.a:7001 Active Domain: demo Jun 11, 2001 5:06:23 PM
GMT+08:00
An unexpected error was encountered in processing your request.
Exception
java.lang.NullPointerException
<>
Current Date
Mon Jun 11 17:06:23 GMT+08:00 2001
Console Release Build
6.0 Service Pack 2
Console Build
6.0 Service Pack 2 05/24/2001 11:55:28 #117037
Server Release Build
6.0 Service Pack 2
Server Build
6.0 Service Pack 2 05/24/2001 11:55:28 #117037
All Server Product Versions
WebLogic Server Build: 6.0 Service Pack 2 05/24/2001 11:55:28 #117037
WebLogic XML Module: 6.0 Service Pack 2 05/24/2001 12:34:27 #117037
Request Info
Protocol: HTTP/1.1
ServerName: x.y.z.a
ServerPort: 7001
Secure: false
ContextPath: /console
ServletPath: /panels/mbean/Server.jsp
QueryString:
mbean=demo%3AName%3Dwlserver2%2CType%3DServer
PathInfo: null
PathTranslated: null
RequestURI: /console/panels/mbean/Server.jsp
AuthType: null
ContentType: null
CharacterEncoding: null
Locale: zh_TW
Method: GET
Session:
weblogic.servlet.internal.session.MemorySessionData@661950
RequestedSessionId:
OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX/console
RequestedSessionIdFromCookie: true
RequestedSessionIdFromURL: false
UserPrincipal: system
RemoteUser: system
RemoteAddr: x.y.z.c
RemoteHost: x.y.z.c
Parameters
mbean = demo:Name=wlserver2,Type=Server
Attributes
console.original./console/panels/mbean/Server.jsp.ContextPath = /console
console.original./console/panels/mbean/Server.jsp.Method = GET
console.original./console/panels/mbean/Server.jsp.QueryString =
mbean=demo%3AName%3Dwlserver2%2CType%3DServer
console.original./console/panels/mbean/Server.jsp.RemoteUser = system
console.original./console/panels/mbean/Server.jsp.RequestURI =
/console/panels/mbean/Server.jsp
console.original./console/panels/mbean/Server.jsp.ServletPath =
/panels/mbean/Server.jsp
console.preferences.ContextKey =
/panels/mbean/Server.jsp
javax.servlet.include.context_path = /console
javax.servlet.include.request_uri =
/console/common/requestinfo.jsp
javax.servlet.include.servlet_path =
/common/requestinfo.jsp
javax.servlet.jsp.jspException =
java.lang.NullPointerException
weblogic.httpd.user = system
weblogic.management.console.tags.ContentTag =
java.lang.Object@545f89
weblogic.management.console.tags.HeaderTag =
java.lang.Object@4c5c6c
weblogic.management.console.tags.TabbedDialogTag =
java.lang.Object@7eafc
Headers
Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Accept-Encoding = gzip, deflate
Accept-Language = zh-tw
Connection = Keep-Alive
Cookie =
JSESSIONID=OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX!143710744761
7668081!-896735123!7001!7002!NONE
Host = x.y.z.a:7001
User-Agent = Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
BrowserInfo
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
IE: true
Netscape: false
Supported: true
JavscriptHrefs: false
TableCellClick: true
DocumentReloadedOnResize: false
DropdownStretchable: true
CellSpacingBlank: false
EmptyCellBlank: false
ImgOnclickSupported: true
TableBorderFancy: true
PartialToWideTables: false
Server System Properties
bea.home = /u0/weblogic
file.encoding = ISO8859-1
file.encoding.pkg = sun.io
file.separator = /
java.awt.fonts =
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.printerjob = sun.awt.motif.PSPrinterJob
java.class.path =
/u0/weblogic/wlserver6.0:/u0/weblogic/wlserver6.0/lib/weblogic_sp.jar:/u0/we
blogic/wlserver6.0/lib/weblogic.jar:/opt/oracle/product/8.1.6/jdbc/lib/class
es12.zip
java.class.version = 47.0
java.ext.dirs = /u0/weblogic/jdk130/jre/lib/ext
java.home = /u0/weblogic/jdk130/jre
java.io.tmpdir = /var/tmp/
java.library.path =
/u0/weblogic/jdk130/jre/bin/../lib/sparc/hotspot:/u0/weblogic/jdk130/jre/bin
/../lib/sparc::/lib:/usr/local/easysoft/oob/client:/usr/local/easysoft/lib:/
u0/weblogic/wlserver6.0/lib/solaris:/u0/weblogic/wlserver6.0/lib/solaris/oci
816_8:/usr/lib
java.naming.factory.initial =
weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories
java.protocol.handler.pkgs =
weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|
weblogic.net|weblogic.utils
java.runtime.name = Java(TM) 2 Runtime Environment,
Standard Edition
java.runtime.version = 1.3.0
java.security.policy =
=/u0/weblogic/wlserver6.0/lib/weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.3
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vendor.url.bug =
http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.3.0
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine
Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.3.0
javax.rmi.CORBA.PortableRemoteObjectClass =
weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.parsers.DocumentBuilderFactory =
weblogic.xml.jaxp.RegistryDocumentBuilderFactory
javax.xml.parsers.SAXParserFactory =
weblogic.xml.jaxp.RegistrySAXParserFactory
jmx.implementation.name = JMX RI
jmx.implementation.vendor = Sun Microsystems
jmx.implementation.version = 1.0
jmx.specification.name = Java Management Extensions
jmx.specification.vendor = Sun Microsystems
jmx.specification.version = 1.0 Final Release
line.separator =
os.arch = sparc
os.name = SunOS
os.version = 5.6
path.separator = :
sun.boot.class.path =
/u0/weblogic/jdk130/jre/lib/rt.jar:/u0/weblogic/jdk130/jre/lib/i18n.jar:/u0/
weblogic/jdk130/jre/lib/sunrsasign.jar:/u0/weblogic/jdk130/jre/classes
sun.boot.library.path =
/u0/weblogic/jdk130/jre/lib/sparc
sun.cpu.endian = big
sun.cpu.isalist = sparcv8plus+vis sparcv8plus
sparcv8 sparcv8-fsmuld sparcv7 sparc
sun.io.unicode.encoding = UnicodeBig
user.dir = /u0/weblogic/wlserver6.0
user.home = /
user.language = en
user.name = root
user.region = US
user.timezone = Asia/Hong_Kong
weblogic.Domain = demo
weblogic.Name = wlserver1
weblogic.security.jaas.Configuration =
weblogic.security.internal.ServerConfig
weblogic.security.jaas.Policy =
/u0/weblogic/wlserver6.0/lib/Server.policy
---------- End of the message -----------
any comment?? is that I deploy on wlserver1, wlserver2, WLCluster cause
error??!! anything I did wrong??!
please help!! or Comment
with thanks,
Alex Wong
"Alex Wong" <[email protected]> ¼¶¼g©ó¶l¥ó
news:[email protected]...
> Hi Vinod and Kevin,
>
> Thanks Vinod first, and after I try the session.getClass(), I get the
> following output
> class weblogic.servlet.internal.session.ReplicatedSessionData
> I think that's means I am using "replicated" already, rite?!
>
> About the License, I cat the license.bea, there is a license to the
> "In-memory Replication - Servlet" and "In-memory Replication - EJB",
however
> it is a eval license but seems not yet expired, so I don't think that is
the
> problem, rite?
>
> And a quick question, you tell me "your configuration looks ok" means the
> H/W configuration, or the WLS configuration??!!
> Maybe I tell you more about my WLS configuration, so that, you can
> determinate where I go wrong. (thanks)
>
>
> Vinod and Kevin
> (Kevin, I am Alex Wong from ASL, if you have any comment, you can simply
> reply my personal email, thx)
>
> Steps I did to create the domain, WLS and Cluster and deploy the .war
> --- on Unix ---
> I create a demo domain and wlserver1 using port 7001 and 7002 by the
> installation program (ip x.y.z.a)
> --- on NT ---
> I create a demo domain and wlserver2 using port 7001 and 7002 by the
> installation program (ip x.y.z.b)
>
> --- on Unix ---
> start the wlserver1 with startWebLogic.sh
>
> --- My PC ---
> go http://x.y.z.a:7001/console
>
> create one more server named "wlserver2" using port 7001 and 7002
> create the cluster named "WLCluster" and fill the the cluster ip
> "x.y.z.a:7001,x.y.z.b:7001"
> fill the multi-cast ip 224.0.0.1
> add the "wlserver1" and "wlserver2" to the "WLCluster"
> stop the unix WLS
> start the unix WLS with startWebLogic.sh
>
> --- on NT ---
> start the WLS with startManagedWebLogic.sh wlserver2 http://x.y.z.a:7001
>
> --- on Unix ---
> install the NES 3.6.3 and create a WEB server instance and modify the
> obj.conf
>
> DETAIL
> ----- start of the obj.conf -----
> Init fn="load-modules" funcs="wl-proxy,wl-init"
> shlib="/opt/nes/plugins/weblogic/libproxy.so"
> Init fn="wl-init"
> .
> .
> .
> <Object name="weblogic" ppath="*">
> Service fn=wl-proxy \
> WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
> </Object>
>
> <Object name=default>
> *NameTrans ...
> *NameTrans ...
> *NameTrans ...
> *NameTrans fn=document-root root="/opt/nes/docs"
> Service method="(GET|HEAD|POST|PUT)" type=text/jsp fn=wl-proxy \
> WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
> .
> .
> .
> </Object>
>
> <Object name=cgi>
> .
> .
> .
> </Object>
> ----- End of the obj.conf ----- (I suppose will redirect all HTTP request
to
> WLS from NES)
>
> --- My PC ---
> go http://x.y.z.a:7001/console
> assign the DefaultWebApp_wlserver1 to wlserver1
> assign the DefaultWebApp_wlserver2 to wlserver2
> assign the console the wlserver1 only
> assign the certificate to wlserver1, wlserver2, WLCluster
> go SERVER-wlserver1 assign "WLRepGroup1" to Replication Group and
Preferred
> Secondary Group
> go SERVER-wlserver2 assign "WLRepGroup1" to Replication Group and
Preferred
> Secondary Group
>
> --- on Unix ---
> go to ./config/examples/applications/examplesWebApp/WEB-INF
> modify the weblogic.xml
> go to ./config/examples/applications/examplesWebApp
> jar cvf myWebApp.war *
> copy the myWebApp.war to ./config/demo/applications/.
> and ftp myWebApp.war ro (NT)./config/demo/applicaitons/.
>
> --- My PC ---
> And then now, I can visit http://x.y.z.a:7001/console
> now I can configuration the myWebApp.
> assign the myWebApp to wlserver1,wlserver2,WLCluster
>
> --- on Unix ---
> stop the WLS and start with startWebLogic.sh
>
> --- on NT ---
> stop the WLS and start with startManagedWebLogic.sh wlserevr2
> http://x.y.z.a:7001
>
> --- My PC ---
> visit http://x.y.z.a/myWebApp/SessionServlet (this time no port 7001,
becoz
> I want to use the NES web server to proxy the HTTP request)
>
> Finally... I can failover the SessionServlet, SnoopServlet and all the
other
> html, jsp, servlet, but seems can't load-balancing and Session
Persistence.
>
> Is that anything I did wrong, please comment!
>
>
> with thanks,
>
> Alex Wong
>
>
>
> "Vinod Mehra" <[email protected]> ¼¶¼g©ó¶l¥ó
> news:[email protected]...
> > Your configuration looks ok but I guess somehow your clustering is not
> setup
> > properly. Check if all the servers are listeniong on the same port and
> part
> > of
> > the same cluster. Also check if you have clustering license.
> >
> > Make sure your sessions are of type : "replicated". For that print
> > the value of session.getClass(), the name will give you an idea. Check
> > your logs if you got any error message.
> >
> > --Vinod.
> >
> >
> > "Alex Wong" <[email protected]> wrote in message
> > news:[email protected]...
> > > Dear all,
> > >
> > > My Cluster can failover, but can't session replicate....
> > >
> > > I start up the 2 WLS 6.0 and the Web Server, then I visit
> > > http://web_server_ip/myWebApp/SessionServlet serveral times, then the
> > > counter variable in the session raise up, then I down the "target"
WLS,
> > then
> > > I try http://web_server_ip/myWebApp/SessionServlet now, I can call but
> the
> > > counter restart.... so the session seems not yet replicated. what I
can
> > > do...?!
> > >
> > > My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using
> > libproxy.so
> > > with the cluster setting, and use 2 WLS 6.0 (both are running in
> > 7001,7002)
> > > as the Application Server Cluster (WLCluster). one WLS is on Unix
> Machine
> > > and the other in on a NT. I set the 2 WLSs: the Primary Group is
> > > "WL_rep_group1", and set the secondary is "WL_rep_group2".
> > >
> > > Deployment: I deploy the application "myWebApp" (.war) on the servers
> unix
> > > and nt, adn also deploy to the cluster WLCluster.
> > >
> > > I deploy the examplesWebApp to my created domain "demo", and modify
the
> > > weblogic.xml:
> > > -------------------
> > > <weblogic-web-app>
> > >
> > > <session-descriptor>
> > > <session-param>
> > > <param-name>PersistentStoreType</param-name>
> > > <param-value>replicated</param-value>
> > > </session-param>
> > > </session-descriptor>
> > >
> > > <jsp-descriptor>
> > > <jsp-param>
> > > <param-name>
> > > pageCheckSeconds
> > > </param-name>
> > > <param-value>
> > > 1
> > > </param-value>
> > > </jsp-param>
> > > <jsp-param>
> > > <param-name>
> > > verbose
> > > </param-name>
> > > <param-value>
> > > true
> > > </param-value>
> > > </jsp-param>
> > > </jsp-descriptor>
> > >
> > > </weblogic-web-app>
> > > ---------------------
> > >
> > > so ... anything I did wrong, so the WLS can't do Session
replication??!!
> > >
> > >
> > > Please Help or Comment!
> > >
> > > Thanks in advance!
> > >
> > > with thanks,
> > >
> > > Alex Wong
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
-
WebLogic 5.1 sp6 .. session in cluster not working properly
It seems like there is a problem in Weblogic 5.1 with sessions in a
clustered environment. The problem is immediately visible with sp3 but
also appears in different form with sp6 . I discovered the problem is
actually with session while testing the cluster with a Session servlet
given with the Weblogic 5.1 kit.
I regiestered the servlet as servlet/session.
The environment is briefly as follows:
Solaris 2.6
Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
machine with two multihome addreses like home1:7001 and home2:7001
Cluster properties in mycluster/weblogic.properties are set as,
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
and also started with required cluster properties in startup.
iPlanet 4.0 webserver - obj.conf has entries like
WebLogicCluster="home1:7001,home2:7001"
All requests are made as http://<host>/servlet/session
sp3 ) After both members are booted up, the first call to session
servlet from any new browser session throws a NullException in server,
but subsequent calls work fine. Single server works fine.
After looking at sp6 release notes it appeared to me that it was a known
problem with cluster.
sp6 ) After both members are booted up, all calls to session servlet do
not complete and eventually it times out. Other servlets work fine.
It only works if we do these steps,
- one of the member is booted up and then session servlet is called and
response comes back.
- second member is booted up and it works well if session servlet is
called. Subsequent requests to both members work fine.
Another strange behaviour:
While running a snoop servlet in cluster subsequent requests show,
Requested url :
either http://<host>/servlet/snoop
or http://<host>:7001/servlet/snoop alternatively
which is strange.
You are not using the same service pack on both the servers. let try do that and see how it goes.
1. Also, if you are doing testing why do you so many threads.
2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
- Prasad
Sutanu Ghosh wrote:
> Here are the thread dumps from both members of the cluster. I took the dumps
> about 5 times in 10 secs interval. It will be helpful for us if you can give
> some insight about this problem.
> Also about the snoop servlet, can you explain why the requested url is
> different (one with weblogic port another without it) in every alternate
> requests ?
> thanks
>
> Prasad Peddada wrote:
>
> > Sutanu Ghosh wrote:
> >
> > > It seems like there is a problem in Weblogic 5.1 with sessions in a
> > > clustered environment. The problem is immediately visible with sp3 but
> > > also appears in different form with sp6 . I discovered the problem is
> > > actually with session while testing the cluster with a Session servlet
> > > given with the Weblogic 5.1 kit.
> > > I regiestered the servlet as servlet/session.
> > >
> > > The environment is briefly as follows:
> > > Solaris 2.6
> > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
> > > machine with two multihome addreses like home1:7001 and home2:7001
> > > Cluster properties in mycluster/weblogic.properties are set as,
> > > weblogic.httpd.clustering.enable=true
> > > weblogic.httpd.session.enable=true
> > > weblogic.httpd.session.persistence=true
> > > weblogic.httpd.session.persistentStoreType=replicated
> > > and also started with required cluster properties in startup.
> > >
> > > iPlanet 4.0 webserver - obj.conf has entries like
> > > WebLogicCluster="home1:7001,home2:7001"
> > >
> > > All requests are made as http://<host>/servlet/session
> > >
> > > sp3 ) After both members are booted up, the first call to session
> > > servlet from any new browser session throws a NullException in server,
> > > but subsequent calls work fine. Single server works fine.
> > > After looking at sp6 release notes it appeared to me that it was a known
> > > problem with cluster.
> > >
> > > sp6 ) After both members are booted up, all calls to session servlet do
> > > not complete and eventually it times out. Other servlets work fine.
> > > It only works if we do these steps,
> >
> > Take thread dumps in intervals of 10 seconds and post them again.
> >
> > > - one of the member is booted up and then session servlet is called and
> > > response comes back.
> > > - second member is booted up and it works well if session servlet is
> > > called. Subsequent requests to both members work fine.
> > >
> > > Another strange behaviour:
> > > While running a snoop servlet in cluster subsequent requests show,
> > > Requested url :
> > > either http://<host>/servlet/snoop
> > > or http://<host>:7001/servlet/snoop alternatively
> > > which is strange.
>
> ------------------------------------------------------------------------
> SIGQUIT
> A SIGQUIT has been received. Do you want to:
> [ 0 ] continue program
> [ 1 ] check & print one deadlock
> [ 2 ] check & print all deadlocks
> [ 3 ] dump thread stacks
> [ 4 ] dump lock registry
> [ 5 ] heap inspection
> [ 6 ] terminate program
> Type number corresponding to selected action: Found 0 deadlock
>
> Full thread dump:
> "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
>
> [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
> [3] java.lang.Thread.run(Thread.java:479)
> -------------------
> "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
> [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
> [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
> [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
> [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
> [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
>
> [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
> [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
> [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
> [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
> [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
> [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
> [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
> [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
> [9] weblogic.jndi.Environment.getContext(Environment.java:122)
> [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
> [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
> [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
> [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
> [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
> [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
> [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
> [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
> [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
> [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
> [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
> [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
> [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
> [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
> [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
> [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
> [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.ke
Maybe you are looking for
-
4.7 IDES Installation Error
Hai! I am installing 4.7 Ent. Edition on Oracle 8.1.7 with windows 2003 sp1 Everything goes smoothly till Central Instance installtion. After that when I am trying to Install Database Instance my installation reaches to Database post processing and h
-
Internal error in FORM/FUNCTION get_prkexx(saplckmo) in position 10 with RC
Hi, When we try to post good movements in MFBF, the system gives the error message C+099 which says "Internal error in FORM/FUNCTION get_prkexx(saplckmo) in position 10 with RC". We have been implemented the sap notes which are shown below: 000109689
-
IPod/iTunes/iPod Updater Won't Recognize Connection
I recently got my iPod serviced for this very issue. Neither iTunes nor my iPod nor iPod updater will recognize when I connect the iPod to either my PC or my laptop. I have noticed this problem isn't listed on the site or anything. I could really use
-
Mail 2.1 - Can't find rules on tool bar
I have read several posts regarding activating rules on the menu bar. In my case, nothing has worked to make the rules button activate (show) on the toolbar, no matter what I have read or done, including deleting the mail preferences. The only place
-
I have 100 students and 6 classes. In each class the presence is via a list registred (yes/no). How can i put al the data of the 6 classes in a main list? Example: Mail list met all the students: Student 1 Student 2 Student 20 In Class A were the stu