Tomcat 5.0.25 persisting session data by default ?!?

This is, I imagine, a dumb question, but I can't quite figure out what is happening by looking at past postings.
When I start Tomcat I get an error : "IOException while loading persisted sessions" because some classes we use are not serializable. That makes sense - we didn't design them to be serialized.
I understand that Tomcat CAN try to persist session data across restarts. However, I do not want it to do this. I thought this was something we had to configure, but it looks like it happens by default (?)
Anyway ... any advice about how to prevent this behavior, at least for our app, would be appreciated ... really puzzled ... !
Thanks in advance for any help you can give !!
ethan

Well, thanks ... I have been there actually, but it only tells me how to set up the 'Experimental" Persistent Manager and not how to turn this off. Here is an interesting blurb from that site :
<<<<<
Whenver Catalina is shut down normally and restarted, or when an application reload is triggered, the standard Manager implementation will attempt to serialize all currently active sessions to a disk file located via the pathname attribute. All such saved sessions will then be deserialized and activated (assuming they have not expired in the mean time) when the application reload is completed.
In order to successfully restore the state of session attributes, all such attributes MUST implement the java.io.Serializable interface. You MAY cause the Manager to enforce this restriction by including the <distributable> element in your web application deployment descriptor (/WEB-INF/web.xml).
>>>>>>>
I THINK this means that persitence is on by default. I'm not certain because - if that is true - then what is the Persisistent Manager for ? I have found thi ssnippet of config in conf/server.xml :
<<<<<<
<Context path="/myApp" reloadable="true" docBase="myApp" workDir="C:\myApp\\work\org\apache\jsp" >
<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>
</Context>
>>>>>>
which tells Tomcat to use the Persistent Manager for my app and then ... tells it not to store session data. And this seems to work ... at least the error messages go away. Now, though, I get a new and different error message :
<<<<<<
SEVERE: no store configured, persistence disabled
>>>>>>
So I am still doing something wrong ... I think ... and still looking for help ... B-)
Thanks again, black_lotus ... maybe we'll learn about this together ;-)

Similar Messages

Unable to create/cleanup persistent session data cache

Hi all
After the iPlanet Webserver 4.1 SP12 starts up the following entries appears in the error log file:
[14/Oct/2003:09:24:48] info ( 5999): successful server startup
[14/Oct/2003:09:24:48] info ( 5999): iPlanet-WebServer-Enterprise/4.1SP12 BB1-12/18/2002 14:18
14/Oct/2003:09:24:49] catastrophe ( 5999): Unable to create/cleanup persistent session data cache
What does the last entry mean?
Thanks for any help :-}
Best regards,
Jean-Claude

Check permissions, disk space of following dirs:
server_root/https-instance/ClassCache/
server_root/https-instance/SessionData/
Try to:
Clear Session Data
Delete JSP Class Cache Files
using the Session Data link under Admin Server GUI Java tab
Hope it helps!

Error at tomcat starting :IOException while loading persisted session. : j

I am gettin error when tomact starts.error is like this "IOException while loading persisted session. : java.io.writeabortedexception.;writing aborted;java.io.Notserializable exception.
what is this error .I think it is due to session scope of bean.what care shold be taken if you are using session scope.please help me;
thanks

To where are you persisting your sessions? If you don't care about session persistance, try making this change in your server.xml.
<Context path="/myApp" reloadable="true" docBase="myApp" workDir="C:\myApp\\work\org\apache\jsp" >
<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>
</Context>I got this from http://forum.java.sun.com/thread.jspa?threadID=575302&messageID=2871444
Check it! Bo!

How to replicate session data at the user level?

Hi all,
my client has users who use laptop/tablet computers in the field with wireless connections. The application requires the users to complete long multi-page forms where the data is only submitted to the EIS layer at the end of the process. The connections regularly drop out which understandably is a cause of some grief. In addition, the users want to be able to switch to another machine in order to complete their session.
The 'switching machine' requirement kills the idea of using persistent cookies and session replication unfortunately. So I am faced with the idea of storing the session data (keyed by user id), in serialized form, either on a stand-alone disk which is accessible by each webserver in the cluster or is the database. The problem with the database idea is the performance hit of traversing the EJB and JDBC layers.
Can anyone suggest the best practice in this case? Or point to an article or tool that covers the problem?
BTW, the app serves a small (<50) and stable base of authenticated users so scalability is not really an issue whereas failover is.
Regards,
Dave.

> Is it possible to close a PO at the header level
Po can be closed at Item level and not Header level. You can set Deletion Indicator and further can be archived thru SARA MM_EKKO
or a way to deactivate the PO so that no new items can be added?
You can activate Release strategy and Choose a Proper Release indicatory so that no new changes to be carried out.
Else go for User Exits

Persisted Sessions Count in Tomcat5.0

I am using Tomcat5.0. I want to find the exact number of sessions associated with application running in the server. By using HttpSessionListener i wrote my logic.So that i can count the number of sessions.My Problem is, Suposse if i stop my tomcat server, the sessions in the server will be persisted. When i restart the tomcat those sessions (*which were pesisted when i stop the tomcat*) will be loaded again. I am unble to find the number of sessions which are loaded. Newly created sessions i can track and i can count. but those persisted session which are loaded when i restart the tomcat are out my count . How can i find the exact number?

Dorababu wrote:
I am using Tomcat5.0. I want to find the exact number of sessions associated with application running in the server. By using HttpSessionListener i wrote my logic.So that i can count the number of sessions.My Problem is, Suposse if i stop my tomcat server, the sessions in the server will be persisted. When i restart the tomcat those sessions (*which were pesisted when i stop the tomcat*) will be loaded again.Is that a requirement? Else you should just turn it off. Its configurable in the server.xml.
I am unble to find the number of sessions which are loaded. Newly created sessions i can track and i can count. but those persisted session which are loaded when i restart the tomcat are out my count . How can i find the exact number?If you have to have sessions persisted, you will have to subclass the PersistentManager class (which is responsible for persisting & reviving sessions across restarts). The only additional functionality that you would add is to register lifecycle Listeners that will be notified of session revivals. Happy googling :)
cheers,
ram.

Apache2.x and Tomcat5.0.x & Session' data

hi everyone,
i was just wondering how i can pass user's session data from Apache to Tomcat and visversa:
an examples
im restricting access to a directory secret/* with Apache Authentication on Mysql (AAOM)
Inside that directory ther is a link to one of my servlets
what i want is to pass the user's data already collected after the log in against AAOM (username, etc ...) to that servlet
ill be glade for any ideas how i can perform this
ps im using mod_jk which mean im using tomcat only as a servlet container behind apache since the most data iam serving is a static data
Thanks in Advance
YEL

Hi,
I believe that this must have been discussed somewhere but as you are saying that you could not get clear answers, please find the answers.
In 3.x, we had Infopackages loading the data to infoproviders. In the infopackage itself, there was an option which asked you the way to update. i.e. Only to PSA, To PSA and subsequently to infoproviders, To infoproviders only. Thus, PSA was optional.
In 7.x, PSA are mandatory and Infopackages can load the data only to PSA. DTP loads the data from PSA to infoproviders.
DTP also provides many new options to us in BI. e.g. You can carry out delta load from PSA to infoprovider.
Edited by: Rahul K Rai on Sep 6, 2010 3:56 PM

Do you know where session data store on server?

hi I have a problem colud you help me? I created a servlet which includes a session and it takes two parameters and write them into html page. Now i want to know how i can see session data .I mean session doesn't create cookie so it doesn't set cookie on client.It must keep data on server. I use tomcat and I couldn't see any file which contain data.

It is stored in memory. Some servers may serialize the sessions to a file when the server shuts down but the session is mantained in memory when the server is running.
If you want to track data added to a session you could use the HttpSessionAttributeListener to record when data is put in a session.

How to persist a data in request scope

Hi All...
I am using JDeveloper Studio Edition Version 11.1.1.0.2.In my managed bean (backing bean scope), I have a variable say " private loginname;" with a global scope and corresponding getter and setter methods inside the backing bean.How can I persist my data in request scope not using a session variable.
Thanks in advance
Dinil Mithra

Hi all,
I need to access the data in the request scope( Not in session scope ). ie, after the command button's action or action listener ,I loose the persistence of my variable.But the same time persistence of the textfield exists.I need to implement the persistence like textbox or ADF component
Thanks for your response
Dinil Mithra
Edited by: Dinil Mithra on May 21, 2009 1:25 AM

Shared Session Data

Hello Everyone,
I have a problem that I could not seem to find a solution or best methods and practices for.
I have session level data abstracted by a package API and accessed query-inline via a table function. All this works fine; however, there is one caveat that does not. The query SQL is passed to a jobs table and executed by a scheduled job. So the job session can not see the user session data.
Is there a way to:
1) Share Session data?
2) define a table as containing Session temporary data, but public scope?
3) Group Sessions or grant session privileges (to share scope)?
4) Run a process/job under a different Session ID, or with specific Session privileges?
5) Call a procedure or function from one session, but have it Execute under a different session?
As it stands, I can either copy the data out to a permanent table (and manually implement Session ID, and Session level cleanup), change the current API and underlying global temporary table to a permanent table (and again manually implement Session ID, and Session level cleanup), or before job scheduling parse the SQL, and expand the function table data into the SQL statically.
None of these are solutions I like. I am looking for something more elegant. Any suggestions would be appreciated.
*EDIT: sorry, I forgot to add; I'm using Oracle 10g.
Thank you for your time.
Edited by: user10921261 on Mar 20, 2009 11:57 AM

Aequitas wrote:
I have session level data abstracted by a package API and accessed query-inline via a table function. All this works fine; however, there is one caveat that does not. The query SQL is passed to a jobs table and executed by a scheduled job. So the job session can not see the user session data.Correct. As a job is a brand new session that is created to execute the supplied PL/SQL code. This process does not create the session by inheriting the environment (name space details, temp tables, transactions) of the session that submitted the job.
Imagine the complexities of this when the session that created the job, terminated 24 hours ago.... would it session state (if kept persistent) still apply? And what about the complexities dealing with the overheads to somehow and somewhere store this session data for the job to re-use.
Nope.. this is not a workable solution (and nor a sensible one), so Oracle does not support it. When a job is executed, a brand new session is created for that job. (not entirely correct at a technical level as the job queue process may already exist and already have a session - but conceptually, think of a brand new session for a job).
Is there a way to:
1) Share Session data?What session data specifically? And what about a session that long since ceased to exist? What about session data that is dynamic and changing? Should then job see the version of that data at the time it was submiited? At the time is started execution? Or the data as it is currently within that session?
2) define a table as containing Session temporary data, but public scope?Does not need to have a "public scope". It can be managed via an API (PL/SQL), using the job number as unique reference number. It is even possible to create low level access control on such a table that only the job and no-one else can even see the data in that table, except for the job.
3) Group Sessions or grant session privileges (to share scope)?Nope.
4) Run a process/job under a different Session ID, or with specific Session privileges?Which session privileges? Remember that each session has two basic memory areas - the PGA (Process Global Area) and UGA (User Global Area). Both are private and non-sharable.
5) Call a procedure or function from one session, but have it Execute under a different session?Nope.
As it stands, I can either copy the data out to a permanent table (and manually implement Session ID, and Session level cleanup), change the current API and underlying global temporary table to a permanent table (and again manually implement Session ID, and Session level cleanup), or before job scheduling parse the SQL, and expand the function table data into the SQL statically.Still not sure what you imply with session data.
In my case I have a process API (running on top of DBMS_JOB ) that developers use to schedule jobs (it manages external processes, mostly used for collecting data from other non-db servers). In some cases, the caller is a Virtual Private Database (VPDB) session - with a name space that contains the keys and tokens and what not that is required for access control and security. The name space cannot be copied across to the job.
So as part of the process API that creates the job, a logon/authentication/authorisation call is added. With the calling session username. This is the same call that would have been made when the user session was created at logon time. And this call creates the name space that contains the keys and tokens required. Thus creating that batch (job) session in the background, uses the same initialisation processing that an interactive session (created from the app server) would use. The code running in that job is oblivious to the fact that the session was not created via an interactive logon from the app server.
None of these are solutions I like. I am looking for something more elegant. Any suggestions would be appreciated.If you truly want an IPC mechanism between two sessions in Oracle, two methods come to mind. Database pipes. Advance Queuing.
This is not really that complex to implement. IPC itself is not difficult. The difficult part is designing the code around cross-session communication and have that work effectively and efficiently. And within the database session context, this can be not only quite difficult to do, but also not always the very sensible thing to do.

Lost session data on jsps

I run a jsp on Tomcat. But the Tomcat says that the session is lost and returns a null pointer. There is no session clear statement in my jsp except its pointing out a null session data.
It works well when I go to a jsp that comes from a servlet processing. But when I click on link that directly calls on a jsp page, the page doesn't finish loading/errs out.
What to do with this? This works fine in single-serevr instance. But when it's run on a cluster/shared environment, it doesn't.
Message was edited by:
rachehernandez

I'm new to tomcat itself and to this job :) I'm using tomcat 5.0.28.
I'm not sure how they do clustering in their setup though.
It's working fine by in a test standalone mode. I do think there's something wrong with the setup. But how would I know?
The jsp sometimes work , and most of the times not. It works when you try to refresh the page. It also works when it comes from a servlet call. But when its just an href link, it doesn't. JSP is using an object from the session. It throws an exception when it can't find this object in the session. But when I click on a link that calls a servlet to load a jsp that's using the same session object, how come it can load up.
What's happening with the session?
Thanks!

"Could not deserialize session data" error during sign out

Hello,
I have an application deployed on WLS 8.1, one instance, no clustering. The application EAR contains 1 web module and 2 ejb modules. When I try to sign out(I use Single Sign-On for Multiple Applications - a sign out application deployed separately) I receive the attached error.
Notes: my session is serializable - I did a test that serialize and deserialize the session and I have no errors.
Q: Why does WLS try to deserialize the session data during sign out? I don't use any session persistance/replication.
The error ClassNotFoundException from my point of view is normal: UsersTableModel(from web modile) is not visible from the Application Classloader.
Here is the error:
<> <BEA-100028> <Could not deserialize session data.
java.lang.ClassNotFoundException: xxx.controller.actions.UsersTableModel: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;Z)Ljava.lang.Class;(ApplicationManager.java:344)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;)Ljava.lang.Class;(ApplicationManager.java:258)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:253)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:216)
     at weblogic.common.internal.WLObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(WLObjectInputStream.java:48)
     at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
     at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
     at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
     at weblogic.servlet.internal.AttributeWrapper.convertBytesToObject([B)Ljava.lang.Object;(AttributeWrapper.java:173)
     at weblogic.servlet.internal.AttributeWrapper.getObject(Z)Ljava.lang.Object;(AttributeWrapper.java:114)
     at weblogic.servlet.internal.AttributeWrapper.getObject()Ljava.lang.Object;(AttributeWrapper.java:69)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;Z)Ljava.lang.Object;(SessionData.java:614)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;)V(SessionData.java:596)
     at weblogic.servlet.internal.session.SessionData.remove()V(SessionData.java:808)
     at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Lweblogic.servlet.internal.session.SessionData;)Z(MemorySessionContext.java:69)
     at weblogic.servlet.internal.session.SessionData.invalidate()V(SessionData.java:750)
     at weblogic.servlet.security.ServletAuthentication.invalidateAll(Ljavax.servlet.http.HttpServletRequest;)Z(ServletAuthentication.java:184)
     at xxx.framework.authentication.WebAuthenticationHelper.invalidateSessions(Ljavax.servlet.http.HttpServletRequest;)V(WebAuthenticationHelper.java:574)
     at xxx.framework.authentication.WebAuthenticationHelper.closeSession(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:523)
     at xxx.framework.authentication.WebAuthenticationHelper.logout(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:250)
     at xxx.yyy.ViewDispatcher.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:75)
     at xxx.yyy.ViewDispatcher.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:42)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
Edited by: user11291053 on 22-Jun-2009 02:52
Edited by: user11291053 on 22-Jun-2009 03:01
Edited by: user11291053 on 23-Jun-2009 01:42

When OptimisticSerialization is turned on, WebLogic server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to Web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two Web applications do not belong to the same application.
When OptimisticSerialization is turned off (which is the default) WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific Web applications by setting the optimistic-serialization value in weblogic.xml.
[http://edocs.bea.com/wls/docs100/ConsoleHelp/pagehelp/Corecoredomaindomainconfigwebapptitle.html]
[http://e-docs.bea.com/wls/docs90/webapp/weblogic_xml.html#1067857]
I hope this helps :)

"Could not deserialize session data" error during shutdown WLS 6.0SP2

          Hello all,
          I get this Error ("Could not deserialize session data") when shutting down WLS
          6.0 SP2.
          I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to use memory-based
          storage for session data. So WLS should not try to serialize the session and save
          it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          methods and realized that WLS calls writeObject on all in the session saved objects
          and readObject directly afterwards. Here's the stackTrace:
          ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          AttributeWrapper.getObject()
          SessionData.removeAttribute()
          SessionData.removeValue()
          SessionData.remove()
          MemorySessionContext.invalidateSession()
          MemorySessionContext.shutDown()
          WebAppServletContext.destroyServlets()
          HttpServer.destroyServlets()
          HttpServer.shutDown()
          WebService.shutDown()
          ServerServiceList.shutDown()
          T3srvr.die()
          T3srvr.waitForDeath()
          T3srvr.run()
          Server.main()
          I do save some objects which are not Serializable in the session. I understand
          that session data can be made persistent in a file/jdbc and then the objects must
          be Serializable but not when saving the session data in memory.
          Why is WLS trying to Serialize the Session Data and how can I switch it off ?
          The Documentation says that it is allowed to store any object in the sessio, as
          long as it is not persistet.
          Thanks for your help,
          Oliver
          [weblogic.xml]


          Hello Oliver & All-
          Did anyone ever make any progress with this question, or come up with an answer?
          I've found similar behavior when properly shuting down a WLS server with this command:
          java -classpath $CLASSPATH weblogic.Admin -url t3://localhost:7001 -username <user>
          -password <passwd> SHUTDOWN
          TIA.
          --oliver.
          "Oliver Seiler" <[email protected]> wrote:
          >
          >Hello all,
          >
          >I get this Error ("Could not deserialize session data") when shutting down
          >WLS
          >6.0 SP2.
          >I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to
          >use memory-based
          >storage for session data. So WLS should not try to serialize the session
          >and save
          >it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          >methods and realized that WLS calls writeObject on all in the session saved
          >objects
          >and readObject directly afterwards. Here's the stackTrace:
          >
          >ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          >AttributeWrapper.getObject()
          >SessionData.removeAttribute()
          >SessionData.removeValue()
          >SessionData.remove()
          >MemorySessionContext.invalidateSession()
          >MemorySessionContext.shutDown()
          >WebAppServletContext.destroyServlets()
          >HttpServer.destroyServlets()
          >HttpServer.shutDown()
          >WebService.shutDown()
          >ServerServiceList.shutDown()
          >T3srvr.die()
          >T3srvr.waitForDeath()
          >T3srvr.run()
          >Server.main()
          >
          >I do save some objects which are not Serializable in the session. I understand
          >that session data can be made persistent in a file/jdbc and then the objects
          >must
          >be Serializable but not when saving the session data in memory.
          >Why is WLS trying to Serialize the Session Data and how can I switch it
          >off ?
          >The Documentation says that it is allowed to store any object in the sessio,
          >as
          >long as it is not persistet.
          >
          >Thanks for your help,
          > Oliver
          >

How do I access session data through an EJB?

Hi
How do I access session data through an EJB?
I am currantly developing a Web service (using ejb's, JBoss.net and Apache Axis). A client making a call to this Web service, is expecting a bussiness-object in return. My problem is that this bussiness-object i stored in a users session data. How do I retrieve this bussiness-object from the users session.
I have read that this does not work with httpsessions, is this true? If this is true, is it possible to store the bussiness object in a JavaBean e.g:
<jsp:useBean id="userContextWebImpl" scope="session" class="com.ac.march.client.UserContextWebImpl">
<%
String key = "test";
String value = "This is the value";
userContextWebImpl.setValue( key, value1 );
%>
</jsp:useBean>
and then retrieve this information through the EJB? Or is it possible to do this by using Statfull JavaBeans? Or can this be done through a nother solution?
Please help!

I have created a JavaBean with scope="application" to store some data. The data is stored when a user prefomes a spesific task.
A different person then makes a call to a Web-Service on the server. The Web-Service then asks an EJB to retrieve the data stored in the JavaBean (servlet cotext). In other words: How do I retrieve this data from the EJB?
I have tried with this code, but with no luck.
(ApplicationContextWebImpl is the JavaBean)
public static String getBookingResult( String key )
     String myResult = null;
     String myKey = key;
     ApplicationContextWebImpl applicationContextWebImpl = null;
     try
          applicationContextWebImpl = new ApplicationContextWebImpl();
          myResult = (String)applicationContextWebImpl.getValue( key );
     catch ( java.rmi.RemoteException e )
     return myResult;
}

Waveburner; a few Questions regarding track files and Session Data

After a bit of negotiating, I'm almost ready to burn. Was having problems with file locations and discovered that i had multiple files in different locations. Those have been eliminated and all relative track files are in one place now with the Song Data File as well.
I then re-imported the individual aif tracks only to find that all of my fades and edits are GONE. It appears that I may have to DO THEM ALL OVER AGAIN! Please tell me that there is a work around.
Is it possible to import only the Session Data related to the fades and edits(everything but the actual audio files), so as to avoid all this "do-again" work?
I was also wonder if it is necessary, or perhaps a good idea, to change the File INFO for each of the individual audio track files from "OpenWith" iTunes (default setting) to "Open With": WAVEBURNER ?. (selectable on the aiff files, "Show More Info" window
Currently the aif files are set to "OpenWith" iTunes (default)
One last question please.
Is Waveburner really up to snuff? How many people are using this for Mastering and Burning CD's? I'm about to start inserting some AU Mastering Plug Ins and I'm hoping for the best. Any other suggestions are greatly appreciated.
G5 Dual 2.0/PBook G41.5Ghz/LogicPro7 Live5 Reason3.0 PansncDA7 TascamFW1804 Mac OS X (10.4.7)

You're grammer isn't bad jord, it was I who asked a plethora of questions under one Subject heading.
When i open the project file(.wb3),
The prompt says;
"Please choose a replacement from the list below:"
/Volumes/320GB HD/Users/ahuihou/.Trash/1 Track 01.aiff
/Volumes/320GB HD/Users/ahuihou/.Trash/2 Track 02.aiff
/Volumes/320GB HD/Users/ahuihou/.Trash/3 Track 03.aiff
/Volumes/320GB HD/Users/ahuihou/.Trash/4 Track 04.aiff
/Volumes/320GB HD/Users/ahuihou/.Trash/6 Track 06.aiff
As you can see the files are in the trash.
The first problem is that there are no actual files in the trash. Just an icon of a CD Disc which was dragged there to eject it, It is no longer in the disc drive/tray. Perhaps i should put the disc back in the drive and then update/replace the files afterwords. (The CD is scratched.)
The strange thing is that i can still preview the track that's in the trash by selecting More Info and playing it on the little Quicktime player bar. I guess the file is in a cache somewhere?
I've looked everywhere on all drives for the specific files but can not find them anywhere.
In the Replacement prompt there is a place that I can check to "Search in the same folder for subsequent files" button on the "Replacement" prompt.
which "same folder" is it refering to?
The Trash folder where the old files are or the Folder where the actual .wb3 project file is? I do have all of the correctly named song files/regions in the same folder with the project file.
maybe i should just start again. i'm not one to give up easy though and would much prefer to "beat" the computer at the game.

How can we reset the session data in SAP ISA B2B application.

com.sap.isa.isacore.action.IsaCoreInitAction$StartupParameter this action class providing the special feature to store all data passed to it in the request as parameters into the session context and make them available for all other actions.
1. But in the inner class they had defined private parametrized constructor.
2. Action class is defined as final.(there is no chance to override the method)
3. There is no setter method (only getter() is available).
4. Creating a new Z_ class that is reflecting in entire application.
5.They had hard coded the Session attribute name in Action class.
6. Application is expecting a session object with the same attributes.
Is there any chance to create a new object for this class or any where any chance to reset the session data. Am using the Multiple_SoldTO concept in my application. My back end ECC .Please help me.
Advanced Thanks
PC.M
Edited by: pmudigonda on Jul 6, 2011 1:21 PM

I am not sure about your requirement, but yet.. Did you check UserSessionData object? It encompasses all the session variables.

Tomcat 5.0.25 persisting session data by default ?!?

Similar Messages

Maybe you are looking for