Focal Point
[CLOSED] MR Administration gives HTTP 500 Error

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/132108215

August 20, 2010, 02:27 PM
Rocky
[CLOSED] MR Administration gives HTTP 500 Error
Hi All,
Can some one advice on this issue. In my webfocus admin console I am trying to open the MR adminstration tab but it throws 500 error.

Webfocus admin console-->Diagnostics-->Traces-->MR Administration.
This shows 500 Error.
I suspected the ear was corrupted and hence I took the ear from other enivronment and placed here so the issue was resolved but created other errors so I had reverted back.

Can some one advice.

Thank you

This message has been edited. Last edited by: Kerry,


WEBFOCUS 7.6.4
Unix
All output
August 23, 2010, 10:16 AM
Francis Mariani
What's an "ear"?


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
August 24, 2010, 08:33 AM
PBrightwell
check your configuration files, something is missing or not set up correctly. If IBI did the install for you, call your local office for help.


Pat
WF 7.6.8, AIX, AS400, NT
AS400 FOCUS, AIX FOCUS,
Oracle, DB2, JDE, Lotus Notes
August 24, 2010, 08:40 AM
dlogan
Francis,
An EAR is an Enterprise ARchive format. Its used in WebSphere to deploy a collection of WAR files as a single unit (e.g. One might deploy ibi_apps, ibi_html, approot, and rcaster as one webfocus.ear file)

Rocky,
Typically when I've seen HTTP 500 errors on accessing a trace area its either one of two things:

1) Traces were left on for a long time and you now have thousands of traces within your WebFOCUS76\logs directory. The list of these trace files is taking so long to compile it times out and gives the HTTP 500.

2) You have a log4j Jar file in your WebSphere bootstrap. This is causing the first log4j.xml definition file found to be used for all the WebFOCUS web applications. Since typically ibi_html or approot loads in an EAR before ibi_apps this means that all of the log4j definitions required for our tracing facilities to run are not defined and as a result they're not found when you access the log pages. This kicks off the HTTP 500.


In either case above, or some other cause not listed, more details as to why the HTTP 500 is being triggered should be found within your WebSphere logs.


WF 71.x, 76.x, 7701, 8.0 Beta OS: Linux, Win2k3, Win2k, Win2k8, WinXP


August 24, 2010, 11:21 AM
Arif
Check your web server if its up. Also bounce web server, report caster, & webfocus service.


WebFOCUS 7.6.10
Windows
HTML
August 30, 2010, 02:48 PM
Rocky
Hi All,
I have contacted IBI and they are unable to resolve the issue, since an year.
1)One more reason for raising this concern and concluding that the ear is corrupted is the Websphere application logs is not showing the information.Genarally in Prod they are working fine but in INT and STG. they dont work.
2)Multiple recycles of webfocus webserver,app server,RC is done.
3) IBI recomended the change of class loading policy and redeply the ear file. I am in process of the same....Keep you posted
4)@ dlogon....Please advice if you want me to verify the Log4j of STG and PROD. might get a clue.

Thanks allot in advance.

Regards,
Rocky


WEBFOCUS 7.6.4
Unix
All output
August 30, 2010, 03:37 PM
dlogan
Rocky,
What is the error you're seeing in your WebSphere logs? It can't hurt to check out your bootstrap.


WF 71.x, 76.x, 7701, 8.0 Beta OS: Linux, Win2k3, Win2k, Win2k8, WinXP


August 30, 2010, 04:41 PM
Rocky
Class Loaders are as follows:

1) For application(Webfocus)
-->Classes loaded with parent class loader first
-->Calss loader for each WAR file in application

2) In JVM level for webfocus
Classloader policy--> Multiple
Class loading mode--> Parent first.


WEBFOCUS 7.6.4
Unix
All output
August 31, 2010, 12:49 PM
dlogan
I was thinking more along the lines of:

http://publib.boulder.ibm.com/.../tcws_sharedlib.html

And checking to see if log4j was in there.


WF 71.x, 76.x, 7701, 8.0 Beta OS: Linux, Win2k3, Win2k, Win2k8, WinXP