Weblogic.httpd.session.cookies.enable not working in WLS4.5 sp 11 ?
I want to disable the use of cookies in WLS 4.5, and set the following
weblogic.httpd.session.cookies.enable=false
In WLS 4.5 sp7, this correctly prevents the server from using cookies
for session-tracking, forcing the extraction of the session id from a
rewritten URL.
However, for WLS 4.5 sp11 cookies are still sent from the server
Is this a known issue ?
jo
I want to disable the use of cookies in WLS 4.5, and set the following
weblogic.httpd.session.cookies.enable=false
In WLS 4.5 sp7, this correctly prevents the server from using cookies
for session-tracking, forcing the extraction of the session id from a
rewritten URL.
However, for WLS 4.5 sp11 cookies are still sent from the server
Is this a known issue ?
jo
Similar Messages
-
Session-failover-enabled not working in iWS6 with a FileStore
I'm trying to use a FileStore to implement session persistence using IWSSessionManager. I have the following in my web-apps.xml:
<web-app uri="/Banking" dir="c:/java/online">
<session-manager class='com.iplanet.server.http.session.IWSSessionManager'>
<init-param>
<param-name>session-data-store</param-name>
<param-value>com.iplanet.server.http.session.FileStore</param-value>
</init-param>
<init-param>
<param-name>session-data-dir</param-name>
<param-value>c:/iplanet/servers/SessionData</param-value>
</init-param>
<init-param>
<param-name>session-failover-enabled</param-name>
<param-value>false</param-value>
</init-param>
</session-manager>
</web-app>
I'm seeing the following exception in my log:
[12/Jun/2002:10:10:56] info ( 320): java.io.NotSerializableException: com.iplanet.server.http.servlet.WebApplication
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.util.Hashtable.writeObject(Hashtable.java:764)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at com.iplanet.server.http.session.IWSHttpSession.writeObject(IWSHttpSession.java:764)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at com.iplanet.server.http.session.FileStore.save(FileStore.java:167)
at com.iplanet.server.http.session.IWSSessionManager.update(IWSSessionManager.java:499)
at com.iplanet.server.http.servlet.NSHttpServletRequest.closeInputStream (NSHttpServletRequest.java:612)
at com.iplanet.server.http.servlet.NSServletRunner.servicePostProcess(NSServletRunner.java:857)
at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:942)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
Any ideas what's wrong?
I should note that I don't think it is because I am storing non-serializable things in the session attributes. I think this because originally I was getting an exception that said that a specific attribute wasn't serializable. I changed the class definition of the class I was storing in that attribute to include "implements java.io.Serializable" and that problem went away.Hi Sija,
Can i have detailed scenario in your cluster configuration.
Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
Regards
Nick Loy -
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 -
WAR cookie example not working. Please help!
Hi,
The cookie example worked fine if I put everything unpackaged under the
public_html/cookie directory. However, when I jarred this directory as
cookie.war and registered it with WLS, I got this exception when trying
to access CookieCounter servlet.
javax.servlet.ServletException: Servlet class: servlets.CookieCounter
could not
be loaded - the requested class wasn't found in the classpath
Also, I was able to get to the hello.html page (my welcome-file) when I
put in this request
http://127.0.0.1:7001/cookie
That means the server was able to extract the cookie.war file and parse
web.xml correctly.
The structure of my cookie.war file is exactly the same as the cookie
directory's.
This is what my cookie.war file looks like
error.jsp
WEB-INF/classes/servlets/CookieCounter.class
WEB-INF/classes/CookieCounter.class
WEB-INF/CookieCounter.java
WEB-INF/web.xml
images/cookie.jpg
hello.html
This is the entry in weblogic.properties
weblogic.httpd.webApp.cookie=c:/weblogic/myserver/public_html/cookie.war
my web.xml is
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<!--
<context-param>
<param-name>weblogic.servlet.reloadCheckSecs</param-name>
<param-value>0</param-value>
</context-param>
-->
<servlet>
<servlet-name>CookieCounter</servlet-name>
<servlet-class>servlets.CookieCounter</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>CookieCounter</servlet-name>
<url-pattern>monster</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>hello.html</welcome-file>
</welcome-file-list>
<error-page>
<error-code>404</error-code>
<location>/error.jsp</location>
</error-page>
</web-app>
The problem seems to be that weblogic was able to find
CookieCounter.class under the unpackaged cookie directory but not inside
cookie.war
Please help.
Thanks a lot.
By the way, if you have a war file that works, please send it to me at
[email protected]
I would greatly appreciate it.
Try resetting it:
Press and hold the On/Off Sleep/Wake button and the Home
button at the same time for at least ten seconds, until the Apple logo appears.
Next try restoring via itunes. -
How to get the weblogic.httpd.session.timeoutSecs value in a JSP file
Hi,
We are using Weblogic 5.1 SP8. We set weblogic.httpd.session.timeoutSecs=900 in the weblogic.properties file. How can I get this value in a JSP file if I don't use java.util.Properties to parse the properties file?
Can I use session.getValue(sessionName) to get it? If so, what is the session name for this property?
Thanks.
Frank
I think something like this should work:
T3ServicesDef services = T3Services.getT3Services();
services.config().getProperty("weblogic.httpd.session.timeoutSecs");
Frank Yu <[email protected]> wrote:
> Hi,
> We are using Weblogic 5.1 SP8. We set weblogic.httpd.session.timeoutSecs=900 in the weblogic.properties file. How can I get this value in a JSP file if I don't use java.util.Properties to parse the properties file?
> Can I use session.getValue(sessionName) to get it? If so, what is the session name for this property?
> Thanks.
> Frank
Dimitri
-
Sun Access Manager 2005Q1 session failover is not working
Hi All
I m using Sun access manager 2005Q1,message queue 2005Q1, Sun Directory server 5.2 ,BerkelyDb 4.2.52 and radware hardware load balancer with sticky session.
I m have configured message queue and BerkeleyDB and both are running with any error.
I m using http://docs.sun.com/source/817-7644/ch5_scenarios.html#wp41008 doc for session failover.
Simple failover is working fine but the Session failover is not working.
Any body has done session failover with Sun Access manager 2005 Q1 I m trying to resolve this issue last two month.
Please it is urgent.It works fine in 2005Q4, after applying a patch 120954 if I am not mistaken. But 2005Q4 and 2005Q1 are probably different in terms of session failover (site configuration etc.)
1. Stop both AM servers
2. Set logging to debug mode in AMConfig.properties.
3. Delete / move everything in /var/opt/SUNWam/debug
4. tail -f /var/opt/SUNWam/debug/amSession
5. Post that file here... you should be able to see if session failover is enabled etc....
hope this helps. -
BI Administrator error: Session Management will not work
Hi!
I am about to set up BI Administrator Addon in SAP Portal. All the configuration steps seems to be ok.
Unfortunately when I try to start some of applications of BI Administrator I get the following error:
Session Management will not work.
Please check the DSM log file for details
Question:
How can I solve this problem?
Thank you very much!
regardsHi
This error means--Please notify us of this problem by submitting an IT Service Request (Please Note: In order to log into the Infra system, you will need to preface your NKU account with nku\. For example, if your user name is smithj7, the "User Name" field would need to be populated with nku\smithj7.)
under the problem type "SAP BW/Portal.
Much of EP / BASIS issue.
Hope it helps -
Save-sessions-enabled not working
WLS 8.1SP4
EAR file with WAR file.
CLuster of 2 managed servers.
In-Memory Replication.
save-sessions-enabled set to true in weblogic.xml
save-sessions-enmabled doesnt seem to work. I log into the web app, do work, redeploy the webapp, and the next click in teh web app forces me to log-in again, i.e. my session is lost.
Sam Pullara had a comment in 2003 about it not working with replicated sessions until SP2. I'm on SP4.
Any ideas before I raise a case?
Many Thanks,
Graham.I have checked the support site and this is still a problem in SP3. A pach was available for SP3.
Apparently, you get the problem if you deploy the app with context-root = '/'.
I have raised a case to see if a patch is available for SP4. -
Enabled cookies, but not working for this specific site...
I was trying to log in to milwaukeejobs.com, but then it takes me to a page which says, "If you have tried to log in, but are being redirected to this page. It may be because cookies are not enabled on your computer." I made sure my cookies were enabled (I have "accept cookies from sites" and "accept third-party cookies"), but I still can't log in. I tried logging into my milwaukeejobs.com account from another browser (Safari) and that worked so it's not a problem with my account. It is firefox. I didn't have a problem with this until I upgraded to firefox 4. Please help! Thanks so much.
Had the same problem with a different website. Solved by doing this:
# Clean browsers cookies and cache
# Go to the specific login/registration page that didn't work. Make sure it is http://'''www'''.site.com and NOT just http://site.com
# Login/register -
I have a desktop at work, and a desktop and laptop at home and just recently the "restore previous session" button that comes up when I use the desktop icon to start a Firefox Web browser session does not work. It is there and I click it but nothing happens. I have Windows 7 on the two computers at home and thought that is what I had on this computer at work, but it may be Vista. It's not XP.
Had this trouble myself, just did some research and solved it!
Go to the '''Help''' menu, go to "'''Troubleshooting Information'''"
On the new window, click "'''Open Containing folder'''" next to ''Profile Directory'' (This opens the folder on your PC where Mozilla stores some settings, like a tab history)
In the new Windows Explorer window, Find the file "'''chromeappsstore.sqlite'''"
You'll want to close Firefox and then '''delete''' that file (don't worry, Firefox will create a new one, and you won't even lose the open tabs)
Start Firefox again and the button should work!
(For completeness's sake, the profile folder for windows7 is: C:\Users\Tiberion\AppData\Roaming\Mozilla\Firefox\Profiles\c6xu23fh.default\
where you replace Tiberion with your own username, and the random characters in the final folder will be different.) -
Function to get session variable is not working
I created a report based on the following sql query:
SELECT EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO FROM SCOTT.EMP
WHERE DEPTNO = empcust.current_deptno
empcust.current_deptno is a function which returns the value of the session variable. However, nothing gets returned. The value of the session variable is not found.
I know that the session variable is being set b/c i have a procedure that sets it and prints out the assigned.
This is my code for the current_deptno function. If anyone can help, i'd greatly appreciate it!
procedure current_deptno
return VARCHAR2
as
v_Session portal.wwsto_api_session;
v_Return VARCHAR2(20); --DEPT.DEPTNO%TYPE;
begin
v_Session := portal.wwsto_api_session.load_session('PORTAL','SESS_EMP');
v_Return := v_Session.get_attribute_as_varchar2('DEPTNO');
htp.p('Return session var'||v_Return);
RETURN(v_Return);
end;Hi Imtiaz,
Could you verify that the variable has indeed a value? You could check via the Session Manager in the Admin Tool. You could also check the Query Log to verify whether the Initialization Block is working like expected.
Thanks.
Daan Bakboord
http://obibb.wordpress.com -
How to disable 'Hello'tried about loop:enabled -not working
I have the new version of Mozilla Firefox and it starts up with 'Hello' that allows video talking. I have tried to amend about:config, loop:enabled to disable it but this does not work, each time I start up my machine 'Hello' is back.
Any suggestions? Could the fact that my History clears daily mean the change to Hello is not being saved?hello DivaDiva, are you referring to the current hello promotion on the firefox start page? this is different from the actual feature itself which you can disable through the loop.enabled preference & will be featured on the homepage for just a few days...
-
HELP SESSION RESTORE WILL NOT WORK
please can some one help me i am trying to copy session restore file from a previous back up - but it will not work - please help - thnx
Could you describe what you have tried?
To make sure you are copying the old sessionstore.js file to your currently active Firefox profile folder, you can open that folder from inside Firefox as follows (either):
* "3-bar" menu button > "?" button > Troubleshooting Information
* Help menu > Troubleshooting Information
* type or paste about:support in the address bar and press Enter
In the first table on the page, click the "Show Folder" button
Please note that before touching the existing sessionstore.js file, you should exit Firefox and allow time for it to close files. Either:
* "3-bar" menu button > "power" button
* File menu > Exit
Then rename it to sessionstore.old before copying in the file you want to use.
Note: if Windows does not show .js extensions on file, please see the steps in this article to show them so you can work with files as accurately as possible: http://support.microsoft.com/kb/865219 -
WebLogic 9.0 - HTC files not working when specified as a part of cascading
Same problem as described in:
http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls/S-10511.htm
but resolution does not work for me.
I have created a mimemappings.properties file in BEA directory BEA\user_projects\domains\myDomain\config\mimemappings.properties with following content:
htm=text/html
gif=image/gif
jpg=image/jpeg
htc=text/plain
png=image/png
CSS file:
.calendarClass {behavior:url(calendar.htc)}
Web.xml:
<mime-mapping>
<extension>htc</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
I also tried htc=text/x-component.
Stop / Start of server, Redeploy of War, this does not work.
Any idea ?Thanks Ben!
That helped. I also was using that
from the examples, and it did not play well in the HTMLPanel.
I appreciate the quick assistance, as I am pretty new to Spry. I have been creating version 2 of my website code, and one of the conversions has beenfrom JQuery to Spry for almost everything. Spry is a lot easier to conceptualize, except I completely missed the setting you gave me.
One of my problems is lack of knowledge on how to see what is happening, or not ahppening with javascript on a page. I have firebug, and that seems to give me some info. But when I tried to look at stuff with scripts running on the HTMLPanel, I was unable to see anything.
Thanks again,
Jamie -
Core/examples/sessions/Broker example not working
Guys
I am trying the example with Oracle database instead of the HSQL database. I replaced the driver & url strings and put the classes12.jar in the classpath
But I continue to get the following error. Can someone please tell me what I am missing.
D:\toplink\examples\core\examples\sessions\broker>D:\JDev9i\jdk\bin\java.exe -classpath ""D:\JDev9i\jdk\lib\tools.jar";"d:\to
plink\ant\lib\jaxp.jar";"d:\toplink\ant\lib\jakarta-ant-1.4.1-optional.jar";"d:\toplink\ant\lib\crimson.jar";"d:\toplink\ant\
lib\ant.jar";.;d:\toplink\core\lib\toplink.jar;D:\JDev9i\jdbc\lib\classes12.jar;d:\toplink\core\lib\toplink.
jar;D:\JDev9i\jdbc\lib\classes12.jar" -Dant.home=d:\toplink\ant -Dtl.home=d:\toplink -Dwls61.home= -Dwls70.home= -Dwas.home=
-Doracle.home=D:\JDev9i\OC4J903 -Dexamples.home=d:\toplink\examples -Dtoplink.dir=d:\toplink\core\lib -Dtoplink.library=topli
nk.jar,xerces.jar -Dtoplink.weblogic.path=d:\toplink\wls_cmp\lib\tl_wlsx.jar -Dtoplink.was.path=d:\toplink\was_cmp\lib\tl_wa
sx.jar -Dhsql.path=d:\toplink\HSQL\lib\hsqldb.jar -DDEBUG=on org.apache.tools.ant.Main runExample -DtestClass=examples.sessions.broker.Demo
Buildfile: build.xml
init:
verify.build.done:
runExample:
[java] 2003.05.19 03:54:35.625--DatabaseSession(11)--Thread[main,5,main]--Connection(12)--TopLink, version:TopLink - 9.0
.3 (Build 423)
[java] 2003.05.19 03:54:35.685--DatabaseSession(11)--Thread[main,5,main]--Connection(12)--connecting(DatabaseLogin(
[java] platform => OraclePlatform
[java] user name => "asdfbf"
[java] datasource URL => "jdbc:oracle:thin:@localhost:fims"
[java] ))
[java] 2003.05.19 03:54:35.705--DatabaseSession(11)--Thread[main,5,main]--EXCEPTION [TOPLINK-4003] (TopLink - 9.0.3 (Bui
ld 423)): oracle.toplink.exceptions.DatabaseException
[java] EXCEPTION DESCRIPTION: Configuration error. Class [oracle.jdbc.driver.OracleDriver] not found.LOCAL EXCEPTION ST
ACK:One more thing to add:
I am not able to get any of the examples to work with Oracle database. Again the only thing I suppose I need to change are the folloowing lines in the EmployeeProject.java
login.usePlatform(new oracle.toplink.internal.databaseaccess.OraclePlatform());
login.setDriverClassName("oracle.jdbc.driver.OracleDriver");
login.setConnectionString("jdbc:oracle:thin:@localhost:1522:fims");
login.setUserName("kumarv");
login.setEncryptedPassword("7AD96CD575D1A7FCAA504BA7E4FC");
Also one line change in the sessions.xml file to use the OraclePlatform instead of the HSQLPlatform.
Has any one got these to work with Oracle, Any help is really appreciated.
classes12.jar is in the classpath so I don;t understand why I get the execption that:
[java] EXCEPTION DESCRIPTION: Configuration error. Class [oracle.jdbc.driver.OracleDriver] not found.
[java] oracle.toplink.exceptions.DatabaseException oracle.toplink.exceptions.DatabaseException.configurationErrorCla
ssNotFound(java.lang.String)
Thanks
Maybe you are looking for
-
Why can't I access the Store from my iTunes
Why can't I access the Store from my iTunes on my PC?
-
I wonder if somebody can help me. I am not able to use my internet bank anymore, since Java launched their latest update (7.51) a few days ago. Appearently this one is not compatible with my hardware. I am using Mac OSX version 10.6.8, and Java versi
-
Having connection problems with Zen Touch...Please h
I haven't used my Touch in a while but I went to install everything last night on my XP machine and when I load MediaSource it says there is no player attached. Windows recognizes the player is there and I can see all the songs in Explorer and I even
-
Using Fifefox 3.6.15 (no prob w/IE8) - at AOL Homescreen & trying to use Left-Click button on mouse to select Fwd/Back arrows on news articles - AOL screen does not recognize mouse clicks on the fwd/back arrows.
-
Hi all, I'm trying to resize a pic to 10 k file size for use as an online avatar. Ideally I'd like to keep it around 100 by 135 pixels. In Windows this is very easy but in the amazingly overhyped and under-featured iphoto it appears to be well nigh i