Shalini Komarla

Ranch Hand
+ Follow
since Aug 28, 2002
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Shalini Komarla

My guess is that it might have something to do with enabling global security in websphere.
20 years ago
what fixpak are you on? I have seen this problem happen on was 4.0.1/4.0.2 I think If you upgrade to 4.0.4, your problem might go away.
20 years ago
what about the afpa setting in the httpd.conf file? I did not see any entries for that in the conf file. Generally we keep all afpa related entries commented out, cause that has proven to be quite notorious and has caused us problems in the past.
20 years ago
YES I agree, you need to first move upto WAS 4.0.4
This is not only my recommendation, but that is what IBM will tell you as well.
20 years ago
Hey Guys,
Hopefully I am posting this in the right forum.
I was wondering, what are all the different member levels at JavaRanch and how are they determined.
I used to be a green horn, then I think when I completed 50 posts, I got 'upgraded' to Ranch Hand. But that's about all I know...
What is the significance of these levels?
Thank You in advance for your replies.
20 years ago
It's been a while since I worked with 3.5, but I think that for the app in question, you will need to create the servlet using the admin console. You can check the load at startup option, to make sure it is loaded when your application starts.
20 years ago
The best option is to use the JDK that IBM provides with Websphere. In that case, you do not need any external JDK. It comes with websphere. However, If you wish to use another JDK, then you will need to download the appropriate files.
20 years ago
I'm glad I can help....don't loose heart. On both occasions I spent almost 2 months working back and forth with the JIT development team in Toronto to help them identify exactly where the problem was and to help them test the modified JIT compiler!!!
for your production environment you can work around this problem by setting the JITC_COMPILEOPT variable in the environment variable section through the admin console...
JITC_COMPILEOPT=SKIP{fully qualified class name}{method name}
This should have almost no impact on performance (skipping compilation of one method rarely affects performance) and is much better than using
JAVA_COMPILER=NONE.
Good Luck!
20 years ago
Have you verified that your war file does indeed contain the .class files? If so, then you might have something to think about.
20 years ago
actually IBM recommends you be on WAS 4.0.4
If you are upgrading anyways, I would suggest going to 4.0.4, rahter then 4.0.3
You can download fixpak 4 from IBM's website itself.
20 years ago
The JIT compiler is invoked when a determination is made that a method or a class is being called more than x number of times. The JIT compiler then pre-compiles the method, thus allowing better performance. If the JIT is turned off, then there is no pre-compilation.
Sometimes the JIT complier incorrectly compiles the code, thus leading to problems that you are experiencing. Are you getting any dr watason dumps or user dumps? Generally these files will help identify where the problem might be.
Another thing would be to first identify the method where the JIT compiler is failing. Once this is done, you can skip the compilation of just this method, rather than turning off the JIT compiler, thus not having to compromise on the performance of your application.
I have in the past worked extensively with IBM on two different occasions with regards to JIT compiler problems and have a learnt a lot from that. Feel free to shoot me any more questions you might have with regards to this issue.
Your best bet would be to open a PMR with IBM.
20 years ago
This is interesting. I have never worked on Win 2003, but would be interested to know what you find out. Can you please post your findings?
Thanks,
20 years ago
I work with WAS 4.0 and I have tried to use another version of IBM's jdk. All I do is replace the Websphere\appserver\java folder with the other version andrestart websphere.
I know that we can use any other jdk as well (other than IBM's), but I don't know how that is done.....never tried it.
20 years ago
IBM recommends you to be on 4.0.4...they have fixed numerous issues with fixpak 4. Probably you should do that ans see if your problem goes away.
20 years ago
There is a good redbook on IBM 's website : http://redbooks.ibm.com
It will help you install and deploy apps on WAS.
20 years ago