The popular word- Change.

 

Zhu ask me to wait and he think I am not ready. I told him I am ready now.

Things are changing and new world is coming.

Chief description:

 

BEA-100028
Error: Could not deserialize session data.

Description
Could not deserialize session data.
Cause
Failed to deserialize session data.
Action
Make sure the object you are putting into the session is serializable and also the non-transient object it aggregates are also serializable. If any of the non-transient objects in the entire object graph are not serializable, you will receive this error message.

 

 

Further research :

 

From: Martin Gainty
Subject: Re: "could not deserialize the context attribute .. " (configuration: struts 1.1 + web logic 8.1), is it a known bug ?
Date: Sun, 19 Oct 2003 07:23:41 -0700

--------------------------------------------------------------------------------

This is a WL specific issue
"servlet 2.3 spec disallow non serialized objects in the PageContext so
built this into the current
release of Weblogic."

Later on Matt Heaton remarks:
"Struts source and it's trying to use objects which aren't serializable as
JSP page context attributes"

Craig McClanahan replies:
"Yep.  Looking more closely at the error message, it is complaining about a
non-Serializable *context* attribute, not a *session* attribute.  I, like
others, jumped to the wrong conclusion there. The spec provides no
prohibitions on this -- only a warning that you cannot
use a context attribute to share information globally in your application
(the
way that the example app does with its pseudo-database) in a distributed
nvironment.
Is there by chance some WebLogic specific configuration property you have
set that makes it think this (or maybe all) applications should be treated
as distributable?"

A Later comment by Craig:
"I'm afraid that I see no such requirement in the servlet 2.3 spec (and I'm
on
the expert group that came up with it .  The only restrictions on
Serializable attributes in the spec itself relate to *session* attributes,
not
*context* attributes.  And that restriction only applies when you mark your
app
as <distributable/>;.

Note also that the WebLogic response quoted in the message from Ruslan gave
an
entirely different reasoning (their application server requires all
attributes
to be Serializable if you use the "reload on modify" feature).  That's an
entirely reasonable restriction for WebLogic to place, based on their
container's internal architecture.  It's not, however, a spec compliance
issue.

That all being said, I'm looking at ways to make MessageResources a
Serializable
object.  Unfortunately, java.util.ResourceBundle (which it relies on) is
*not*
Serializable, so a different solution to that is going to be required.

The pseudo-database in the Struts example application (which has nothing to
do
with the framework itself) is not Serializable, and will *not* operate
correctly
in a distributed environment.  I'm NOT planning on changing that in the
short
term, because it's only there to give you a quick "proof of concept" that
Struts
is working, plus some examples of some Struts-related development
techniques."

http://www.mail-archive.com/[EMAIL PROTECTED]/msg01017.html

Weblogic Solution:
"WLS comes with reload-on-modify turned on out of the box. You can turn it
off by setting reload periods to -1 (never check). There are two separate
params for JSP and servlets.
The one for JSPs is set in weblogic.xml descriptor,
the one for servlets is set in the console."

i.e. Turn off reload-on-modify

Sorry for the long-winded response!

-Martin
----- Original Message -----
From: "Marc Dugger" <[EMAIL PROTECTED]>;
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>;
Sent: Sunday, October 19, 2003 8:36 AM
Subject: RE: "could not deserialize the context attribute .. "
(configuration: struts 1.1 + web logic 8.1), is it a known bug ?


>; I had a somewhat similar issue with Tomcat when it came to serializing a
>; FormFile.  I got around this by extending the MultipartRequestHandler and
>; implementing Serializable.  It appears that you could do the same with the
>; RequestProcessor.  Be sure to add this to your struts-config.xml:
>;
>; <controller contentType="text/html;charset=UTF-8" locale="true"
>; nocache="true" processorClass="your.package.CustomRequestProcessor"
>; debug="9" />;
>;
>;
>; >; -----Original Message-----
>; >; From: Shay Cohen [mailto:[EMAIL PROTECTED]
>; >; Sent: Sunday, October 19, 2003 3:17 AM
>; >; To: '[EMAIL PROTECTED]'
>; >; Subject: "could not deserialize the context attribute .. "
>; >; (configuration: struts 1.1 + web logic 8.1), is it a known bug ?
>; >;
>; >;
>; >; Hi,
>; >;
>; >; I've encountered lately the following exception "Could not deserialize
>; >; context attribute....". Reported on the following attribute:
>; >;
>; >;
>; >;             Attribute: org.apache.struts.action.REQUEST_PROCESSOR
(object:
>; >; org.apache.struts.tiles.TilesRequestProcessor)
>; >;
>; >; After reading old emails concerning the subject, I've learned that this
is
>; >; due to weblogic restrictions that require context attributes to be
>; >; serializable.
>; >;
>; >;
>; >; Is there any workaround to this problem? will it be solved  ?
>; >;
>; >; ---------------------------------------------------------------------
>; >; To unsubscribe, e-mail: [EMAIL PROTECTED]
>; >; For additional commands, e-mail: [EMAIL PROTECTED]
>;
>;
>; ---------------------------------------------------------------------
>; To unsubscribe, e-mail: [EMAIL PROTECTED]
>; For additional commands, e-mail: [EMAIL PROTECTED]
>;
>;

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 

    最近几个月试用了好几个新的软件，IBM RSA,MyEclipse 5.5 or above,Loadrunner,Weblogic9 and 10 和一些Code generator 。经历了好几次J2EE app server版本和JVM的切换。

    整体的感觉确定今后的发展，别说太虚的，在工业级的项目不同于学术研究，要不断寻找并利用好的code generator来减少团队的代码量(我已经找到一些成果，可以将7 or above 人天的代码量在一定前提下缩短到 5min 人)，

1.团队中经验缺乏的成员可以通过这些代码去学习，

2.稍有经验的成员应将精力放在app server的tuning和deploy上，

3.有专门的测试人员去利用loadrunner这个很重要的工具，如果说代码只是为了implement functions,那么LR就是让我们的成果更完美，最终要实现LR和weblogic, OS之间的监控关系。

4.更有经验的成员应该使用RSA建立整个系统从Use Case到数据库ER的关系，统领全局，

5.而最后说到的是PM，调配资源和团队建设，为团队利益争取最大化（这世界还是很现实的，没有物资基础何来说精神）。

希望自己能在有限的时间实现这个架构，on the way now。

Installation Overview

LoadRunner provides two different ways to monitor a WebLogic server depending upon the WebLogic version, i.e. SNMP-based monitor, or JMX monitor.

WebLogic Monitor (SNMP-based monitor)

WebLogic monitor (SNMP- based) gathers measurement based on information returned by the WebLogic SNMP agent. 

·        Availability: LoadRunner 6.0

·        Supported Server Version: WebLogic 5.x

·        Supported Server Platform: Windows NT, Windows 2000

 

WebLogic Monitor (JMX monitor)

WebLogic monitor (JMX) gathers measurement based on Java API. It uses the JMX interface, (which is a Sun extension to Java.

·        Availability: LoadRunner7.02 or above

·        Supported Server Version: WebLogic 6.x –7.x. For WebLogic8.x, please refer to the additional setup information below .

·        Supported Server Platform: Windows NT, Windows 2000, Solaris 2.6, AIX 5.1, HP-UX 11

WebLogic Monitor (SNMP-based monitor)

Installation guide

The WebLogic (SNMP) monitor uses SNMP to retrieve server statistics. To use this monitor, you must make sure that a version prior to WebLogic 6.0 is installed on your server, and that the SNMP agent is installed and activated on the server.

How to start the Bea Web Server

1.      Go to the WebLogic directory.

2.      Save the startWebLogic.cmd file as startWebLogic.bat.

3.      Open startWebLogic.bat and set the JDK_HOME parameter to <JDK installation>.

4.        Run startWebLogic.bat from the Command Prompt and wait a couple of minutes – if it starts OK, you will receive a “WebLogic started” notification.

How to start the SNMP agent on the server

1.      Make sure that the standard SNMP agent is not running – to verify this, go to Control Panel ® Services and check the status of SNMP and SNMP Trap or consult the UNIX admin for the SNMP daemon on the Unix machine.

2.      For the Windows platform, Open startSnmpAgent.cmd or startSnmpAgent.bat and set the JDK_HOME parameter to <JDK_installation_directory>.

 For the UNIX platform, the batch file is startSnmpAgent.sh.

3.     In the same file (startSnmpAgent.bat or startSnmpAgent.sh), search for the following line (usually the last line in file):

“%JDK_HOME%\bin\java -classpath %JAVACLASSPATH% weblogic.SNMPAgent -password ServerSystemPassword -serverURLs t3://localhost:7001 -trapDestinations localhost:162”

·        This is the command use to startup the WebLogic SNMP agent.

·        It requires a Java Virtual Machine for execution.

·        The classpath must contain weblogicaaux.jar and \weblogic\classes. For Weblogic 5.1 with SP, you would need to add the sp jar file (usually named weblogic510spxxx.jar)to the CLASSPATH of the agent startup scrīpt.

4.      Replace ServerSystemPassword with the password defined during server installation.

5.      If you do not know your password, it is in the “weblogic.properties” file under the property “weblogic.password.system=???.”

6.      You will probably need to change “localhost” to the name of your machine.

7.      Run startSnmpAgent.bat from the Command Prompt.  If it starts OK, you will receive a “Agent Initialization Complete” message.

 

NOTE:

1.      For detailed instructions on installing the WebLogic SNMP agent and the utilities to test the agent, see http://www.weblogic.com/docs51/admindocs/snmpagent.html.

2.      If you intend to run the WebLogic Server SNMP agent as the only agent on the system, you may not be able to start it if any other agent is already running and is bound to the SNMP port (161).

How to configure the SNMP-based monitor in LoadRunner

 

1.      Click the WebLogic (SNMP) graph in the graph tree, and drag it into the right pane of the Run view.

2.      Right-click the graph and choose Add Measurement(s), or choose Monitors à Add Online Measurement.

3.      In the Monitored Server Machines section of the WebLogic (SNMP) ( or WebLogic) dialog box, click Add to enter the server name or IP address of the machine you want to monitor. Select the platform on which the machine runs, and click OK.

4.      In the Resource Measurements section of the WebLogic (SNMP) dialog box, click Add to select the measurements that you want to monitor. The WebLogic SNMP Resources dialog box displays the available measurements.

5.      Browse the WebLogic SNMP Objects tree.

6.        To measure an object, select it, and click Add. The following tables describe the measurements and server properties that can be monitored

 

 

 

Known Issues and limitations

 

1.      The SNMP-based monitor can only monitor up to 25 measurements.

 

2.      Some network devices between the LoadRunner Controller machine and the SNMP agent machine might be configured to block or reroute the SNMP traffic. 

Tips and Tricks

Q.   LoadRunner 6.51 Controller crashes if the SNMP agent is unavailable

R.     This is a known issue in LoadRunner 65 SP1.  To resolve the issue, please download and apply Patch LR651P34 from Support’s Download à Patches à LoadRunner à 6.5 SP1 à LR651P34 - LoadRunner 6.51 Fixed Controller crashes caused by unavailability of the SNMP or WebLogic server

 

Q.   How to monitor a non- Community String

R.     To do so, please modify the snmp.cfg located in <LoadRunnner >\dat\monitors:

1.      Look for the appropriate monitor.

2.      Uncomment the "SNMP_community_name=" line by removing the semi-colon (";").

3.      Add the community string setup by the SNMP agent, to the end of “SNMP_community_name=;”. Please note that this is case-sensitive.

4.      Save the snmp.cfg file and restart the LoadRunner Controller.

 

Q.   How to change the port number

R.     To do so, you need to modify the snmp.cfg file in <LoadRunner>\dat\monitors.

1.         Look for the appropriate monitor.

2.         Uncomment the  "port=" line by removing the semi-colon (";").

3.           Add the port number to the end of “port=”. For example, port=1234

 

Q.   What to do if there is a firewall between Controller and Host

For monitoring over firewall, please refer to Knowledge Base Article 3678

 

 

Q.   Error: “Not a scalar MIB object”

R.     You receive this error because you are trying to access a private/ proprietary MIB file.  LoadRunner does not recognize this file, as it is not in LoadRunner’s MIB definition file.

 

 WebLogic Monitor (JMX monitor)

Installation Requirement

1.      WebLogic 6.0 or above on the server

2.      JDK 1.3.x or above installed on the Controller machine. For WebLogic8.x, you need JDK1.4.

3.      Copy WebLogic.jar from <server installation>\lib folder to <LoadRunner>\classes

4.      LoadRunner 7.02 or above:

a.       No patches is required for LoadRunner 7.5 or above

b.      For LoadRunner 7.02:

·  Contact Mercury Customer Support for patch LR702P34 - LoadRunner 7.02 WebLogic JMX monitor for versions 6.0 & 6.1

·  To install:

 

i.         Exit LoadRunner Controller.

ii.       Unzip weblogic60_702.zip in the LoadRunner installation directory.

iii.      Terminate the Java Web server by entering the URL 

http://localhost:1112/?id=exit&type=0 in a browser.

iv.     Run patch_monitors_v702.bat in <LoadRunner>\bin

v.       Install Java Runtime by executing j2re-1_3_1-win.exe.

 

How to configure the WebLogic (JMX) Monitor in LoadRunner

1.      Click the WebLogic (JMX) graph in the graph tree, and drag it into the right pane of the Run view.

2.      Right-click the graph and choose Add Measurement(s), or choose Monitors à Add Online Measurement.

3.      In the Monitored Server Machines section of the WebLogic (JMX) dialog box, click Add to enter the server name or IP address of the machine you want to monitor. Enter the server name or IP address according to the following format:

<server name>:<port number>  

For example: mercury:8111. Select the platform on which the machine runs, and click OK.

4.      Click Add in the Resource Measurements section of the WebLogic (JMX) dialog box. In the Enter Login Information dialog box, enter the username and password of a user with administrative privileges to the WebLogic server. The BEA WebLogic Monitor Configuration dialog box opens. For details on creating user permissions, see

5.      Browse the Measured Components tree.

6.      Check the required performance counters in the BEA WebLogic Monitor Configuration window's right pane.

7.        Click OK in the BEA WebLogic Monitor Configuration dialog box, and in the WebLogic (JMX) dialog box, to activate the WebLogic (JMX) monitor.

Today, I browsed the friend list in msn. suddenly, some strange feeling comes when I saw the group named "HKU". Open it and found many old friends. Gai, Fenado and Jolin, my dear friends who lived with me, miss the days with you. nights we struggle with homework ,went to have meals together, and discuss many topics. all of you are irreplaceable cauz' you are so sincere to me. Autumn Sea and Sheng , you two guys are rather interested. I own you one meal and drink together. Autumn Sea, I am so sorry to waste those beers you bought last time. whenever you like, come here and find me to make it true. Mei, remember your attitude as the tutor and classmates, you are a consciencious ppl. Thank you for your guide and effort.Well, last one is Charles, I am glad to know you before graduate, I just feel sorry that moment is so late that I even don't have many times to learnt from you.

 

 

In the past two months, I went back the this old office and worked with those guys, feels so far so good. Lots of work, including projects and new function modules. I prefer to cheat them as the chances to implement my new skill and idea , show off my power rather than the burden. Well, that makes me feel more comfortable and happy. The damn disaster in Si Chuan let numerous childen lost their parents, house , even life. If possible, I want to be their teacher in one day , that is all I can do except for the donation. What is more, I finished the evaluation and am qualified.It is my turn to make the decision whether to apply for it.Em...., that is difficult. Maybe I should cheat it easy, things are changing.

Finally, Lakers won the western champion and return to the final. God bless Kobe.