Hello,

Please share your knowledge about Java Callable Exit in WebFOCUS 5.2.5 (Specific Java class used for application level security)

I got Exception and unable to find that causes it:
ibi.webfoc.wfutil.WFErrorException: 6 at

ibi.webfoc.wfutil.WFRunScript.runScript(WFRunScript.java:584) at ibi.webfoc.wfutil.WFRunScript.runScript(WFRunScript.java:559) at ibi.webfoc.wfutil.WFContext.runScript

WFContext.java:563) at ibi.webfoc.wfutil.WFContext.(WFContext.java:547) at ibi.webfoc.WFWorkerUtil.processRequest(WFWorkerUtil.java:98) at ibi.webfoc.WFWorkerUtil.processRequest(WFWorkerUtil.java:68) at ibi.webfoc.WFServlet.processRequest

(WFServlet.java:546) at ibi.webfoc.WFServlet.doGet(WFServlet.java:465) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at ibi.srv.util.IBIHttpServlet.service(IBIHttpServlet.java:87) at javax.servlet.http.HttpServlet.service

(HttpServlet.java:853) at ibi.srv.util.IBIHttpServlet.service(IBIHttpServlet.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247) at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter
Chain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at

org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at

org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(
StandardPipeline.java:643) at

org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:553) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:641) at

org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416) at

org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:643) at

org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(
StandardPipeline.java:641) at

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext
(StandardPipeline.java:641) at

org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext

(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service

(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
(Http11Protocol.java:392) at

org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:619) at java.lang.Thread.run(Thread.java:534)
Thanks,
Pranas

This message has been edited. Last edited by: <Mabel>,

Did you remember to jar the user exit into the war file and add the init param to the servlet?

WFUser,

Sure Callable Exit class is in Jar file.
It works on production environment (separete machines for client & server, Win2003 Srv., WebFOCUS 5.2.4) very well.

I don't know why, but it seems WFServlet unable to parse correct site.wfs file on test environment (Single machine, Wind2000 Srv. adv.,WebFOCUS 5.2.5)

Thanks,
Pranas

If that's the case, it's easy enough to test. Remove your custom code from site.wfs. It might not produce the desired results from your app, but you can see if you get the java error. If that works, post your site.wfs.

Thanks WFUser,

It seems a problem is not in site.wfs file but in modified IBI jar file. I still can not figure out why it behaves so differently on similar platforms

Pranas

Just another supposition:
Do you have the same code pages (windows cmd command: chcp), on the test environment and on the production web server ?

Hello Grzegorz,

Code Page the same on test and prod env.
Some WFClient configuration files may be different.
Test Environment uses default parameters from installation. Production was tuned.

Thanks folks for ideas!

Regards from Lithuania

Pranas,

The last resort you can use to diagnose the problem is to turn on the traces, and spend some hours reading it.
The convenient tool to see the WF Client traces is: http://the_host/ibi_apps/tracing.jsp, or you can turn on the "normal tracing" setting in the %IBI_HOME%\client52\wfc\web\cgi\ibiweb.cfg:

TRACE=on<br />TRACE_LOCATION=path_where_the_traces_will_be_written

Tomcat "Request Dumper Valve" is a good diagnostic tool, as well.

Regards
Grzegorz

Grzegorz,

THANK YOU! It was realy helpful.

Pranas