HTTPS HTTP SESSION JAVABEAN JSP
Hello all.
i work in http session...after i redirect in https(login.jsp)
in JavaBean for Login.jsp try get connection with all object or JavaBeans from last http session ...but i cannot do it.
Where my problem ?
Help me please.
i think u want to redirect from login jsp page to another page with request object.
try response.sendRedirect("yourjspfile.jsp");
Similar Messages
-
Use HTTP Session to pass Object from Web Dynpro for Java to JSP page
Is it possible to get a handle on the HTTP Session object from within a Web Dynpro application? I want to place a Java object in there that can be retrieved by a JSP page.
Thanks in advance.Hi Tom Cole,
You can try this. i am not sure if this will work or not.
HttpServletRequest request = ((IWebContextAdapter) WDWebContextAdapter.getWebContextAdapter()).getHttpServletRequest();
You can also try this.
IWDRequest mm_request = WDProtocolAdapter.getProtocolAdapter().getRequestObject();
HttpServletRequest request = (HttpServletRequest)mm_request.getProtocolRequest();
IWDRequest basically wraps the HttpServletRequest. if you are using NW04s then the getProtocolRequest() may not be available.
Regards,
Sanyev -
How can I flag HTTP session attributes to not be replicated ?
WLS 5.1 SP8 - In memory replication of a stateful servlet. Is
there any way to flag data that has been, or is being, loaded into
a HTTP session so as to not be replicated ? It's a long story,
but we have some data loaded into a hashtable, more specifically
a Properties object, stored in our session. With the hastable
already loaded into the HTTP session, weblogic does not detect
when we add values to the table, and therefore does not replicate
the changes. Which is ok since WLS is working as designed. To
get around this we load the hashtable back into the session everytime
we add a value to the hashtable. Yup, I know that's ugly. Anyway,
what I'm trying to find out if is there is an attribute that we
can set to indicate, to not replicate this data or that data.
Something along the lines of a attribute on a per hastable value
basis. For example, I load value A into my hashtable, then I
need to put my hashtable into the session to get it replicated.
Next I load value B into the hastable, and again to get it replicated
I have to load the entire hashtable back into the session. The
problem here is that the entire table gets replciated. Does anyone
know if I can set an attribute on value A, when I'm adding value
B, so as to not replicate value A when I reload the table ? Of
course all goal is to not store so much data in the session, but
I'm trying to find a work around until that is completed.
Thanks,
David
Where can I find documentation on the details of how Weblogic decides what will
be replicated in the HTTPSession object (for example, it only replicates attributes
which are set or updated using "setAttribute()"?
Prasad Peddada <[email protected]> wrote:
>Robert,
>
> It is true that we replicate only when you call setAttribute in case
>of servlets.
>
>In case of EJB it is slightly different. EJB sends diff's across the
>wire. It doesn't
>replicate the entire state with every request.
>
>-- Prasad
>
>Chris Palmer wrote:
>
>> I think Viresh was referring to modifying part of one attribute causing
>the whole
>> of that attribute (i.e. the hashtable) to be replicated.
>>
>> Is it actually true though that the behaviour would be different in
>a stateful
>> session EJB? I had assumed that the WHOLE ejb state would be replicated
>each time
>> (i.e. after each invocation), without even the benefit of having a
>mechanism such
>> as setAttribute() to flag the attributes that had changed...
>>
>> Chris
>>
>> Robert Patrick wrote:
>>
>> ? Huh? Since when does it always replicate the entire HttpSession?
> We were
>> ? told that it uses a hook in the setAttribute() call to determine
>which
>> ? attributes have changed and only replicates those attributes. I
>know this to
>> ? be the case because if I retrieve a previously stored attribute from
>the
>> ? HttpSession and modify it, my changes do not get replicated unless
>I call
>> ? setAttribute again...
>> ?
>> ? Robert
>> ?
>> ? Viresh Garg wrote:
>> ?
>> ? ? Servlet sessions don't work on diffs, so no matter what you do,
>entire
>> ? ? Hashtable will be replicated. If you want the optimization for
>only
>> ? ? replicating the diff ( the stuff that has changed between 2 updates)
>,
>> ? ? consider using stateful session bean and having hashtable part
>of
>> ? ? conversational state of stateful session bean.
>> ? ?
>> ? ? The solution that you suggested on your own for your problem is
>not ugly
>> ? ? as the same solution is used by many customers that I know of.
>This is
>> ? ? particularly a problem for people that use Java Beans and use the
>set
>> ? ? Property directive of Java Bean in JSP. There also in our auto
>generated
>> ? ? code, we put the JavaBean back in HTTP Session, when a setter is
>called to
>> ? ? enforce replication.
>> ? ?
>> ? ? Keep in mind that whatever we do for replication, we want to support
>it
>> ? ? using ONLY standard servlet API and we don't want to introduce
>any WLS
>> ? ? specific API to achieve this, and so putting value back in session
>is the
>> ? ? only way.
>> ? ?
>> ? ? Viresh Garg
>> ? ? Principal Developer Relations Engineer
>> ? ? BEA Systems
>> ? ?
>> ? ? Dave Javu wrote:
>> ? ?
>> ? ? ? WLS 5.1 SP8 - In memory replication of a stateful servlet.
>Is
>> ? ? ? there any way to flag data that has been, or is being, loaded
>into
>> ? ? ? a HTTP session so as to not be replicated ? It's a long story,
>> ? ? ? but we have some data loaded into a hashtable, more specifically
>> ? ? ? a Properties object, stored in our session. With the hastable
>> ? ? ? already loaded into the HTTP session, weblogic does not detect
>> ? ? ? when we add values to the table, and therefore does not replicate
>> ? ? ? the changes. Which is ok since WLS is working as designed.
>To
>> ? ? ? get around this we load the hashtable back into the session everytime
>> ? ? ? we add a value to the hashtable. Yup, I know that's ugly.
>Anyway,
>> ? ? ? what I'm trying to find out if is there is an attribute that
>we
>> ? ? ? can set to indicate, to not replicate this data or that data.
>> ? ? ? Something along the lines of a attribute on a per hastable value
>> ? ? ? basis. For example, I load value A into my hashtable, then
>I
>> ? ? ? need to put my hashtable into the session to get it replicated.
>> ? ? ? Next I load value B into the hastable, and again to get it replicated
>> ? ? ? I have to load the entire hashtable back into the session. The
>> ? ? ? problem here is that the entire table gets replciated. Does
>anyone
>> ? ? ? know if I can set an attribute on value A, when I'm adding value
>> ? ? ? B, so as to not replicate value A when I reload the table ?
>Of
>> ? ? ? course all goal is to not store so much data in the session,
>but
>> ? ? ? I'm trying to find a work around until that is completed.
>> ? ? ? Thanks,
>> ? ? ? David
>
-
URGENT http session HELP PLEASE
Hello all.
i work in http session...after i redirect in https(login.jsp for example)
in JavaBean for Login.jsp try get connection with all object or JavaBeans from last http session ...but i cannot do it.
Where my problem ?
How i can have access across sessions?
Help me please.i don't understand your meaning exactly,but i think what you mean is maybe to make a bean accessible across the session?is that right?if yes,you can set the scope attribute to session,such as:
<jsp:useBean id="..." scope="session" class="...."/> -
In-memory replication of http session is not working in BEA7 cluster
Hi everyone,
I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
through apache web server. I have given cluster address as URL in httpd.conf of
apache server which sends the client requests for dynamic pages such as JSPs and
servlets to the weblogic cluster.
Load balancing is working fine. I ensured this from the log files of all the 3
servers. All the 3 servers are getting different client requests and thus load
balancing is working.
Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
for this. I feel the cluster itself will handle fail-over provided i make the
http session as memory replicated.
I updated the weblogic.xml with the following entry :
<session-descriptor>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
</session-descriptor>
I guess this is sufficient to make the http session as cluster aware.
But when I shutdown server1, the user connected to server1 will be kicked out
of the session and come to login page through server2 or server3 which are running
fine.
Could anyone help me to achieve http session as cluster aware. Does it indicate
that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
http session ?
BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
the session.
thanks in advance.
Hi Ryan,
Thanks for ur valuable input.
I can see failover working.
But, I can not continue with the same session in my application.
I printed session Ids before and after failover, I found both are different.
I guess session replication is a responsibility of weblogic/apache plugin.
If not please let me know which all settings I should do to make failover working?
Thanks again.
Plad
"ryan upton" <ryanjupton at learningvoyage dot com> wrote:
>Plad,
>
>Are you trying to gracefully shut down the server? If you are then the
>problem that you say you can't identify is simply the server's default
>behavior which is to wait for all non-replicated sessions to be dropped
>or
>timed out before killing the process. Try forcing the shutdown: kill
>-9 the
>PID or CTRL-C if you started the server from the command line. You can
>also
>check the ``Ignore Sessions During Shutdown" checkbox under the server's
>control tab in the admin console, this should allow you to shut down
>gracefully without waiting for session timeout. BTW your sequence is
>off
>in #5 below, the replication doesn't occur upon failure, the replication
>has
>already happened once you created the session object on the first server,
>I
>think maybe you're confusing replication with failover.
>
>~RU
>
>"Plad" <[email protected]> wrote in message
>news:[email protected]...
>>
>> Hi,
>> I have 2 managed servers in a cluster.
>>
>> 1. I have got a DNS name configured which maps to these 2 managed server's
>IP
>> addresses.
>> 2. I can browse my site using this DNS name.
>> In HTTPD.conf I have :
>>
>> ServerName dev.a.b.net
>>
>> <IfModule mod_weblogic.c>
>> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
>> MatchExpression *.*
>> </IfModule>
>>
>> LoadModule weblogic_module modules/mod_wl_20.so
>>
>> 3. I have adeded session descriptor in weblogic.xml , also enabled
>proxy
>plugin
>> in weblogic console.
>>
>> 4. I tested accessing my application using DNS url after shutting down
>alternatively
>> each manaed server. I can access application.
>>
>> 5. Now, problem comes when I access a managed server1 , keeping server2
>down.
>> I am able to access my application.
>> Now, I start the server2.
>> (Here I am supposing that replication should occur)
>> Then I am shutting down server1.
>> But, this time the server log shows me following:
>>
>>
>> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
>non-replicated
>> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
>sessions
>> to finish.
>> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
>non-replicated
>> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
>sessions
>> to finish.
>>
>> I am unable to make out where the problem is?
>> Can it be a problem of Liecense? Is there any specialcluster liecense
>for
>weblogic8?
>>
>> Hoping to get replies.
>> Thanx.
>> Plad
>>
>> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
>> >See my reply to your first post, but I've also added a few comments
>here.
>> >
>> >"jyothi" <[email protected]> wrote in message
>> >news:[email protected]...
>> >>
>> >> I guess someone from bea support team only can answer both your
>question
>> >and mine.
>> >> As per my knowledge, we do not need to do any setup at Apache
>side
>> >regarding
>> >> cluster other than mentioning cluster address as URL while
>contacting
>> >WLS
>> >> from apache.
>> >>
>> >> I hope someone from Bea, will help us. I do not think that we
>> >go for
>> >WLS
>> >> proxy plug-in using HttpClusterServlet for making session replication.
>> > I
>> >strongly
>> >> feel that the cluster itself be able to manage the fail-over of
>> >http
>> >sessions
>> >> provided we put the entry "PersistentStoreType" in weblogic.xml
>> >regarding
>> >> the session replication.
>> >>
>> >
>> >The cluster does handle the management of Sessions. The clustered
>> >applications still create the Session objects and the cluster manages
>> >them
>> >as per your deployment descriptor settings (replicated, JDBC, File)
>however
>> >the proxy has to be aware of which server the client has an affinity
>> >for
>> >(only with replicated sessions) and it does that by reading a cookie
>> >passed
>> >back from the server that handled the initial request and created
>the
>> >primary session object. The proxy has a list of both the primary
>and
>> >secondary server locations from this cookie that it can use to failover
>> >the
>> >request if the primary server fails. Clusters _DO NOT_ failover nor
>> >do they
>> >load balance, that's the job of your proxy, whether you're using the
>> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
>> >balancer like Big IPs F5
>> >
>> >> jyothi
>> >>
>> >
>> >~RU
>> >
>> >
>>
>
>
-
Entity remote in clustered http session ?
we put a entity remote object into a http session which is replicated
across a cluster of 3 linux machines ( each with 1 weblogic 6.1 SP2).
http session replication works fine: the entity is accessible on every
machine in this cluster.
it seems that there is no failover for entity remote object in this
case: i kill the server where the entity was originally created. the
web application just reports an "10.5.1 500 Internal Server Error".
the server log of the machine where the current request was executed
says:
1.
Removing solarium jvmid:-995414765884053603S:192.168.145.41:
[2357,2357,7002,7002,2357,7002,-1]:beacluster.hybris.de:hybr
is:solarium from cluster view due to PeerGone
( solarium is the killed server; beacluster the cluster DNS name )
2.
Removing -995414765884053603S:192.168.145.41:[2357,2357,7002
,7002,2357,7002,-1]:beacluster.hybris.de:hybris:solarium to
the cluster
3.
[WebAppServletContext(729829,dummyweb,/dummyweb)] Servlet fa
iled with IOException
java.rmi.ConnectException: Unable to get direct or routed connection to:
'-995414765884053603S:192.168.145.41:[2357,2357,7002,7002,2357,7002,-1]:beacluster.hybris.de:hybris:solarium'
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at
weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
at
weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy86.getText(Unknown Source)
at jsp_servlet.__dummyEntity._jspService(__dummyEntity.java:148)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
thanks in advance,
axel grossmann.
HTTP session is only replicated to the secondary server, not all servers in
the cluster.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Axel Großmann" <[email protected]> wrote in message
news:[email protected]...
>
> we put a entity remote object into a http session which is replicated
> across a cluster of 3 linux machines ( each with 1 weblogic 6.1 SP2).
>
> http session replication works fine: the entity is accessible on every
> machine in this cluster.
>
> it seems that there is no failover for entity remote object in this
> case: i kill the server where the entity was originally created. the
> web application just reports an "10.5.1 500 Internal Server Error".
>
> the server log of the machine where the current request was executed
> says:
>
> 1.
> Removing solarium jvmid:-995414765884053603S:192.168.145.41:
>
> [2357,2357,7002,7002,2357,7002,-1]:beacluster.hybris.de:hybr
> is:solarium from cluster view due to PeerGone
>
> ( solarium is the killed server; beacluster the cluster DNS name )
>
> 2.
> Removing -995414765884053603S:192.168.145.41:[2357,2357,7002
> ,7002,2357,7002,-1]:beacluster.hybris.de:hybris:solarium to
> the cluster
>
> 3.
> [WebAppServletContext(729829,dummyweb,/dummyweb)] Servlet fa
> iled with IOException
> java.rmi.ConnectException: Unable to get direct or routed connection to:
>
'-995414765884053603S:192.168.145.41:[2357,2357,7002,7002,2357,7002,-1]:beac
luster.hybris.de:hybris:solarium'
> at
>
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
java:85)
> at
>
weblogic.rmi.cluster.EntityRemoteRef.privateInvoke(EntityRemoteRef.java:144)
> at
> weblogic.rmi.cluster.EntityRemoteRef.invoke(EntityRemoteRef.java:115)
> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
> at $Proxy86.getText(Unknown Source)
> at jsp_servlet.__dummyEntity._jspService(__dummyEntity.java:148)
> at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> at
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
> at
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
> at
>
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
> at
>
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
> thanks in advance,
> axel grossmann.
-
Is there anyway to share a HTTP session between 2 web contexts?
Both web contexts are running on the same server.
I wanted to redirect a user from one web context to another and the share
session so that
i don't have ask the user to authenticate again and share the session
content from the
previous web context.
Thanks
/selvan
Captura Software, IncTHanks for the info.
I am using WLS 6.1 version.
/selvan
"Cameron Purdy" <[email protected]> wrote in message
news:3ba0b484$[email protected]..
Look at the J2EE / Servlet specs for "single sign on" discussions. I've
never tried it specifically, and I know from others that various releases
either did it by default or didn't seem to support it at all. What WL
version are you using?
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/download.jsp >>
"Selvan Ramasamy" <[email protected]> wrote in message
news:[email protected]..
Is there anyway to share a HTTP session between 2 web contexts?
Both web contexts are running on the same server.
I wanted to redirect a user from one web context to another and the
share
session so that
i don't have ask the user to authenticate again and share the session
content from the
previous web context.
Thanks
/selvan
Captura Software, Inc -
Create Java bean for a http session
how can i create a java bean for an http session. also is it possible to access it from another java class within that session
Try the following forum (about JSP technology)
http://forum.java.sun.com/forum.jspa?forumID=45 -
Maintaining an HTTP session in SOAP
Is it possible to maintain an HTTP session when using RPC style SOAP services?
If not, how do people maintain conversational state between a client and a SOAP
server?All is not lost though!!! Apache's SOAP implementation supports Stateful session.
Maybe u should take a look at it...
"Kumar Mettu" <[email protected]> wrote:
Naresh,
BEA's webservices implementation is at Stateless Session Bean level .
And
hence you are never working at servlet/jsp level. So there is no way
you can
use HTTP Session.
Also BEA's webservices doesn't support Header Element.
Kumar.
"Naresh Bhatia" <[email protected]> wrote in message
news:3bc72918$[email protected]..
Well, if that is the case, we could maintain state manually by "inventing"our
own session objects. All we would have to do is to maintain a map atthe
server
end that maps a sessionId to a session. The sessionId would have tobe
passed
as a parameter to every method. (Yuck. Or can it be put into the soapheader somehow
- so as to keep the method signatures clean?) Do you see any holeswith
this approach?
"Mullai Murugan" <[email protected]> wrote:
It looks like maintaining state is not possible in the current release.
The documentation
says clearly that only stateless beans are supported.
"Naresh Bhatia" <[email protected]> wrote:
Is it possible to maintain an HTTP session when using RPC style SOAP
services?
If not, how do people maintain conversational state between a client
and a SOAP
server? -
Single admin server and two managed servers in a cluster. Using NES plugin API from three web servers to the cluster. EJB is deployed with PersistenceStore=Memory.
Session data is not replicating. Cluster is configured for Round-robin. One jsp hits server (A) the next hits server (B). Well,
server (B) requires the session data from the first jsp.
Anyone have any idea where I should look next to troubleshoot this.
TIAHi.
You need to make sure you have PersistentStoreType set in your weblogic.xml as follows in order to replicate http session data:
<session-descriptor>
<session-param>
<param-name> PersistentStoreType </param-name>
<param-value> replicated </param-value>
</session-param>
</session-descriptor>
HTH,
Michael
Tim Perkins wrote:
Single admin server and two managed servers in a cluster. Using NES plugin API from three web servers to the cluster. EJB is deployed with PersistenceStore=Memory.
Session data is not replicating. Cluster is configured for Round-robin. One jsp hits server (A) the next hits server (B). Well,
server (B) requires the session data from the first jsp.
Anyone have any idea where I should look next to troubleshoot this.
TIA--
Michael Young
Developer Relations Engineer
BEA Support -
Hi,
I am working on weblogic portal 9.2
I am seeing some weird behavior while handling http session object.
I have a desktop contains 2 page flow portlet and 1 Jsp/Html portlet.
On Portal Admin I have created 2 differennt desktop as below.
1.http://localhost:7001/Test/appmanager/desk/desk1
2.http://localhost:7001/Test/appmanager/desk/desk2
Desktop 1 will put some value in session but when I am running the other desktop i.e. desk2 then desk2 is receiving the same session value that desktop 1 put.. Not sure why?
Generally for every desktop URL new Http Session should be created. But in my Case old session is sharing between 2 desktop.
Java code
HttpSession session = request.getSession(false);
session.getAttribute("");
JSP
<%@ page session="false"%>
In non Portal application, we can have control to all the href but in case of Portal we are getting data from content management that provides href.
Edited by: user11311969 on Oct 9, 2009 4:58 AM
Edited by: user11311969 on Oct 9, 2009 5:23 AMHi,
Thanks for the replay.
You are right If I add desktop name in session then atleast I can insure that correct desktop is fetching the session value.
Ok But while rending both the desktop there is common code that put some values in session.
Let say Desktop1 put "name = Desktop1" and "Value = "MyDesktop" in session.
After that I run Desktop2, that will put "name = Desktop2" and "Value = "OtherDesktop " in session.
i.e when I run Desktop1, then I should get "name = Desktop1" and "Value = "MyDesktop "
when I run Desktop2, then I should get "name = Desktop2" and "Value = "OtherDesktop "
If I click any link on Desktop1 then i will get "name = Desktop2" and "Value = "OtherDesktop " because Desktop2 has already overwrite the session value.
How can I solve this? -
Getting http session attributes
Hello,
Perhaps the question here may sound stupid, but I have real problem with that:
Is it possible to obtain http session attributes from the client side
(and even worse) in other languages like VB or VC++? What i mean is that after creating Http session by servlet, and setting some attributes, is it possible to get them by VC or VB app? Thanks in advance :)What i mean is that after creating Http session by servlet, and >setting some attributes, is it possible to get them by VC or VB app? >Thanks in advance :) What do you mean by "VC or VB app" ?
A desktop app written in VC or VB ? a web app in VBscript/ASP ? (but as far as I know there is no web language based on VC, unless you're talking about executable CGIs that can be written in any language).
Assuming that you talk about VB-ASP, I don't think it possible "out of the box" to retrieve session variables created by a servlet in an ASP page.
That would be possible if HTTP supported sessions.
Sessions are implemented at the application level on top of HTTP; they reside in the application that handles requests. Outside it, they don't exist.
It doesn't mean that you can't do that, but that you have to do that using HTTP constructs like URL rewriting or form submission.
For example you could set session variables in a JSP page, and then forward the request to an ASP page through a GET request with all session variables written in the URL. -
Replicated http sessions : classcastexception
has anyone else seen this with wls6.1 sp1 when trying to run in memory
replicated http session?
-peter
<Oct 18, 2001 12:01:26 PM EDT> <Error> <HTTP>
<[WebAppServletContext(7569280,v21
,/v21)] Servlet failed with Exception
java.lang.ClassCastException:
weblogic.servlet.internal.session.MemorySessionCon
text
Start server side stack trace:
java.lang.ClassCastException:
weblogic.servlet.internal.session.MemorySessionCon
text
at
weblogic.servlet.internal.session.SessionData.getContext(SessionData.
java:270)
at
weblogic.servlet.internal.session.ReplicatedSessionData.becomeSeconda
ry(ReplicatedSessionData.java:178)
at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
at
weblogic.cluster.replication.ReplicationManager$wroManager.create(Rep
licationManager.java:352)
at
weblogic.cluster.replication.ReplicationManager.create(ReplicationMan
ager.java:1073)
at
weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:265)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR
equest.java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy88.create(Unknown Source)
at
weblogic.cluster.replication.ReplicationManager.trySecondary(Replicat
ionManager.java:870)
at
weblogic.cluster.replication.ReplicationManager.createSecondary(Repli
cationManager.java:825)
at
weblogic.cluster.replication.ReplicationManager.register(ReplicationM
anager.java:393)
at
weblogic.servlet.internal.session.ReplicatedSessionData.<init>(Replic
atedSessionData.java:119)
at
weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSess
ion(ReplicatedSessionContext.java:193)
at
weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletReq
uestImpl.java:1948)
at
weblogic.servlet.internal.ServletRequestImpl.getSession(ServletReques
tImpl.java:1729)
at jsp_servlet.__login._jspService(__login.java)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
When do you see this? While shutting down one of the servers?
Make sure your clustered servers are uniform. ie.the webapp
you have deployed is deployed on all servers and PersistentType
is set to "replicated" in all servers.
--Vinod.
Peter Ghosh wrote:
> has anyone else seen this with wls6.1 sp1 when trying to run in memory
> replicated http session?
> -peter
>
> <Oct 18, 2001 12:01:26 PM EDT> <Error> <HTTP>
> <[WebAppServletContext(7569280,v21
> ,/v21)] Servlet failed with Exception
> java.lang.ClassCastException:
> weblogic.servlet.internal.session.MemorySessionCon
> text
>
> Start server side stack trace:
> java.lang.ClassCastException:
> weblogic.servlet.internal.session.MemorySessionCon
> text
> at
> weblogic.servlet.internal.session.SessionData.getContext(SessionData.
> java:270)
> at
> weblogic.servlet.internal.session.ReplicatedSessionData.becomeSeconda
> ry(ReplicatedSessionData.java:178)
> at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
> at
> weblogic.cluster.replication.ReplicationManager$wroManager.create(Rep
> licationManager.java:352)
> at
> weblogic.cluster.replication.ReplicationManager.create(ReplicationMan
> ager.java:1073)
> at
> weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
> Source)
> at
> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
> at
> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
> a:265)
> at
> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
> .java:22)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> at
> weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR
> equest.java:85)
> at
> weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
> at $Proxy88.create(Unknown Source)
> at
> weblogic.cluster.replication.ReplicationManager.trySecondary(Replicat
> ionManager.java:870)
> at
> weblogic.cluster.replication.ReplicationManager.createSecondary(Repli
> cationManager.java:825)
> at
> weblogic.cluster.replication.ReplicationManager.register(ReplicationM
> anager.java:393)
> at
> weblogic.servlet.internal.session.ReplicatedSessionData.<init>(Replic
> atedSessionData.java:119)
> at
> weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSess
> ion(ReplicatedSessionContext.java:193)
> at
> weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletReq
> uestImpl.java:1948)
> at
> weblogic.servlet.internal.ServletRequestImpl.getSession(ServletReques
> tImpl.java:1729)
> at jsp_servlet.__login._jspService(__login.java)
> at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
> pl.java:265)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
> pl.java:200)
> at
> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
> rvletContext.java:2456)
> at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
> pl.java:2039)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
-
How to close a HTTP session when a user closes the window
Hi,
I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
I did implement a logoff function at my web template and this was implimented on the Menu page, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly.
If user navigates to the other pages from the main page... then the logoff function was not implimented in the other pages. So many of the users are closing the windows directly. Eevn if we impliment logoff in all the subpages, As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
Regards,
TonyHi,
And also take a look on the Genral property of the web template. We solved this problem by changing only this property (no extra things).
<b>Property: Value</b>
Automatic Session Management: Active
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma -
Bw web report plugin http session hangs at the server side
Hi,
I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
I did implement a logoff function at my web template, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly. But As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
By the way, we actived our BEX service at the SICF.
Thanks for help!
JAHi
If you want to avoid a blank page with logoff button, add opener=0
<a href="<SAP_BW_URL CMD='LOG_OFF' ~command='logoff'
>" onClick="javascript:window.close(opener=0);">Log off</a>
If you want to close the session via X, use this code:
create a sapscript function
function closeSession()
logoff()
window.unload=CloseSession()
However, the Plugin HTTP session isn't killed.
Regards
Maybe you are looking for
-
Manually trigger PO Creation for a SC
Hi Experts, Due to downtime issue one SC is created but the PO creation did not take place. The SC is stuck in I1111 " Item in Transfer Process" but the PO never got created. Is there anyway I can trigger the PO creation manually. The system is SRM 7
-
When I open Pages and get a blank page, the curser is no longer working. Meaning, I am now unable to type a document as there's no place to begin. Never had this happen before. Interestingly, if I create a text box, I AM able to type, but not with
-
User login records on Hyperion Financial Reporting
Hi all, We understand we can turn on audit to capture the user login (authentication) in Hyperion Planning. Can we have the same option/feature for Financial Reporting to turn on audit so that we know that which reports in one day was generated by en
-
Bad TV video filter won't apply
I can't seem to get the Bad TV and a couple other video effects to apply to a clip. I move the mix button down and can see the video in the canvas, and they render the clip, but there is no change in the video... How do I make these effects work? Tha
-
I set up a file with 147 frames that was supposed to be 7s at 21 fps. When I exported it the swf file ran over 7s. And when you played it in flash and watch it count the seconds it counted to 4 then dropped back to 2 before continuing to count up to