Upgrade to 5.3.2 search failing within help

Post any questions regarding Installing or Upgrading Ebase, including problems starting up the Ebase Xi Server or Designer

Moderators: Dave, Jon, Steve, Ian

neilnewman
Ebase User
Posts: 183
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Upgrade to 5.3.2 search failing within help

#1

Postby neilnewman » Tue Sep 25, 2018 8:43 am

We have just noticed that the search.jsp used when we search the help does not appear to work:

Any ideas please

The log file returns:

Stacktrace:] with root cause
org.apache.jasper.JasperException: Unable to compile class for JSP:

An error occurred at line: [45] in the jsp file: [/search.jsp]
The method open(Path) is undefined for the type FSDirectory
42: {
43: String indexDir = getServletConfig().getServletContext().getRealPath("/WEB-INF/docidx");
44:
45: directory = FSDirectory.open(java.nio.file.Paths.get(indexDir));
46: reader = DirectoryReader.open(directory);
47: searcher = new IndexSearcher(reader);
48:


An error occurred at line: [67] in the jsp file: [/search.jsp]
The method search(Query, Filter) in the type Searcher is not applicable for the arguments (Query, int)
64:
65:
66:
67: TopDocs results = searcher.search(qQuery, java.lang.Integer.MAX_VALUE);
68: ScoreDoc[] hHits = results.scoreDocs;
69: hitCount = hHits.length;
70:


Stacktrace:
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:102)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:212)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:495)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:350)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:595)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:382)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:800)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
0 x

Jon
Moderator
Moderator
Posts: 1295
Joined: Wed Sep 12, 2007 12:49 pm

Re: Upgrade to 5.3.2 search failing within help

#2

Postby Jon » Tue Sep 25, 2018 10:24 am

Can you please check the level of the lucene jars in the WEB-INF/lib directory of the webapp on the server. For the integrated server this will be something like VerjioStudio\UfsClient\IntegratedServer\ebasetest\WEB-INF\lib. You should see five (and only five) lucene jars at level 6.2.1 as follows:

lucene-analyzers-common-6.2.1.jar
lucene-core-6.2.1.jar
lucene-highlighter-6.2.1.jar
lucene-memory-6.2.1.jar
lucene-queryparser-6.2.1.jar

If these look OK then delete the files in VerjioStudio\UfsClient\IntegratedServer\work\Tomcat\localhost\ebasetest\org\apache\jsp to force re-compilation of the search JSP.
0 x

neilnewman
Ebase User
Posts: 183
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Re: Upgrade to 5.3.2 search failing within help

#3

Postby neilnewman » Tue Sep 25, 2018 10:34 am

Hi Jon,
I have checked the lib folder and there are only five lucene jar files all at 6.2.1.
I went to remove the UfsClient\IntegratedServer\work\Tomcat\localhost\ebasetest\org\apache\jsp folder but it does not exist in the installation, all I have is a path to: D:\Ebase\dbc-ebase-test\UfsClient\IntegratedServer\work\Tomcat\localhost\ebasetest with nothing beneath this.
0 x

Jon
Moderator
Moderator
Posts: 1295
Joined: Wed Sep 12, 2007 12:49 pm

Re: Upgrade to 5.3.2 search failing within help

#4

Postby Jon » Tue Sep 25, 2018 11:38 am

Silly question: are you actually using the Integrated Server?
0 x

neilnewman
Ebase User
Posts: 183
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Re: Upgrade to 5.3.2 search failing within help

#5

Postby neilnewman » Tue Sep 25, 2018 11:45 am

might not be a silly question!

Because there are only two of us doing the Ebase forms work and we don't generally edit each others Projects, we have setup the system thus:
On the server we have the installation software and we file share out the Workspace file system which we refer to at the Ebase PC client end when we select the workspace.
Therefore we don't deploy any of our work to the server as such, we are editing it directly.

Why would this impact the search in the help system?
0 x

Jon
Moderator
Moderator
Posts: 1295
Joined: Wed Sep 12, 2007 12:49 pm

Re: Upgrade to 5.3.2 search failing within help

#6

Postby Jon » Tue Sep 25, 2018 12:01 pm

I think that means you are using the Integrated Server but we should check - in the studio click File > Preferences > Test Server. Which option do you have checked?

It matters which server you are using - that's where the search JSP is running.
0 x

neilnewman
Ebase User
Posts: 183
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Re: Upgrade to 5.3.2 search failing within help

#7

Postby neilnewman » Tue Sep 25, 2018 12:12 pm

OK we are setup thus:
We refer to the main servers Workspace from the client PC's via the Windows share and use the "External server" which points to the main Ebase server/instance.

Could we run with the "Intergrated Server" locally on the client PC's and keep the main servers Workspace mapped?
I presume if we did this we would still not have to deploy anything as we are working from the man servers Workspace.

Is that a supported way to configure things?

Not sure I entirely understand all this!
0 x

Jon
Moderator
Moderator
Posts: 1295
Joined: Wed Sep 12, 2007 12:49 pm

Re: Upgrade to 5.3.2 search failing within help

#8

Postby Jon » Tue Sep 25, 2018 1:01 pm

You're using an external server so you should check the lucene jar files on that (in WEB-INF/lib) and similarly delete any content in tomcat/work.

The way you've configured your server and workspace is not what we intended, but I can't see anything wrong with it so you don't need to change anything. I don't much like the sound of running multiple Integrated Servers against one remote workspace - it might lead to problems.
0 x

neilnewman
Ebase User
Posts: 183
Joined: Fri Dec 20, 2013 1:29 pm
Location: Dartford Borough Council
Contact:

Re: Upgrade to 5.3.2 search failing within help

#9

Postby neilnewman » Tue Sep 25, 2018 1:52 pm

Thanks Jon,
There was a lucene-1.4.3.jar file in our D:\Ebase\dbc-ebase-live\UfsServer\tomcat\webapps\ufs\WEB-INF\lib folder.
Removed the file and now the Search within Help is working fine, and thanks for confirming that our setup is OK even if it is not standard
0 x


Who is online

Users browsing this forum: Google [Bot] and 1 guest