[Logo] JForum - Powering Communities
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Top Downloads] Top Downloads   [Groups] Back to home page 
[Register] Register /  [Login] Login 


JForum 2.6.2, which fixes a few bugs in 2.6.0, has been released. Download it from here
installing on jetty RSS feed
Forum Index » User Forum
Author Message
philfrei


Joined: 2019/7/24
Messages: 13
Offline
I am using Windows 10, with Java 11 (OpenJDK) and MySQL 8.0.

I installed Jetty (9.4.19.v20190610) a couple days ago. AFAIK the installation went smoothly. I am able to run their examples. I was able to configure a "base" directory for .war files, and to drop an example .war file in, and the browser is able to find and run it.

The installation instructions for JForum say the following:
"It is assumed that you have some knowledge on how to install/configure a Java servlet container (or already have one up and running), and the database is properly configured. "

My inexperience with this makes me wonder if there is something I've missed. For example, the MySQL program I installed works fine. But is there some aspect that has to be specifically configured to work with JForum prior to installation?

There is another instruction that gives me pause. After unpacking the .war, we have this:
"The next step you should do is register the JForum application within your Servlet Container, like Tomcat."
I do not see any mention in Jetty about a registration process.

Since I am doing this on my own PC as the owner, and not as part of a network, I am assuming all the required directories will have full write permissions.

When starting Jetty, the following is generated.

C:\Users\Genie\jetty\base>java -jar %JETTY_HOME%/start.jar
2019-07-23 16:07:21.155:INFO::main: Logging initialized @2562ms to org.eclipse.jetty.util.log.StdErrLog
2019-07-23 16:07:21.403:WARN:oejx.XmlConfiguration:main: Deprecated method public void org.eclipse.jetty.server.HttpConfiguration.setBlockingTimeout(long) in file:///C:/Users/Genie/jetty/jetty-distribution-9.4.19.v20190610/etc/jetty.xml
2019-07-23 16:07:21.544:INFO:oejs.Server:main: jetty-9.4.19.v20190610; built: 2019-06-10T16:30:51.723Z; git: afcf563148970e98786327af5e07c261fda175d3; jvm 11.0.1+13
2019-07-23 16:07:21.569:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:///C:/Users/Genie/jetty/base/webapps/] at interval 1
2019-07-23 16:07:24.378:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /jforum-2.6.0, did not find org.eclipse.jetty.jsp.JettyJspServlet
2019-07-23 16:07:24.468:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
2019-07-23 16:07:24.468:INFO:oejs.session:main: No SessionScavenger set, using defaults
2019-07-23 16:07:24.471:INFO:oejs.session:main: node0 Scavenging every 660000ms
JForum: problems initializing the logger: template not found: "C:\Users\Genie\jetty\base\webapps\WEB-INF\log4j_template.xml"
java.lang.Exception: template not found: "C:\Users\Genie\jetty\base\webapps\WEB-INF\log4j_template.xml"
        at net.jforum.util.log.LoggerHelper.checkTemplate(LoggerHelper.java:161)
        at net.jforum.util.log.LoggerHelper.provideJForumLogConfig(LoggerHelper.java:119)
        at net.jforum.util.log.LoggerHelper.checkLoggerInitialization(LoggerHelper.java:94)
        at net.jforum.ContextListener.contextInitialized(ContextListener.java:76)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:959)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:553)
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:924)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:365)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:854)
        at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:278)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46)
        at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192)
        at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:510)
        at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:153)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:172)
        at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:430)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:65)
        at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
        at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
        at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
        at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:145)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:598)
        at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:240)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167)
        at org.eclipse.jetty.server.Server.start(Server.java:418)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:119)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
        at org.eclipse.jetty.server.Server.doStart(Server.java:382)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$0(XmlConfiguration.java:1797)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1746)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:220)
        at org.eclipse.jetty.start.Main.start(Main.java:490)
        at org.eclipse.jetty.start.Main.main(Main.java:77)
log4j:WARN No appenders could be found for logger (net.jforum.util.preferences.SystemGlobals).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2019-07-23 16:07:24.560:WARN:oejw.WebAppContext:main: Failed startup of context o.e.j.w.WebAppContext@53045c6c{JForum - Powering Communities,/jforum-2.6.0,file:///C:/Users/Genie/jetty/base/webapps/jforum-2.6.0/,UNAVAILABLE}{C:\Users\Genie\jetty\base\webapps\jforum-2.6.0.war}
net.jforum.exceptions.ForumException: java.io.FileNotFoundException: C:\Users\Genie\jetty\base\webapps\WEB-INF\config\SystemGlobals.properties (The system cannot find the path specified)
        at java.base/java.io.FileInputStream.open0(Native Method)
        at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
        at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
        at net.jforum.util.preferences.SystemGlobals.loadProps(SystemGlobals.java:448)
        at net.jforum.util.preferences.SystemGlobals.loadDefaults(SystemGlobals.java:194)
        at net.jforum.util.preferences.SystemGlobals.buildSystem(SystemGlobals.java:131)
        at net.jforum.util.preferences.SystemGlobals.initGlobals(SystemGlobals.java:107)
        at net.jforum.ConfigLoader.startSystemglobals(ConfigLoader.java:92)
        at net.jforum.ContextListener.contextInitialized(ContextListener.java:78)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:959)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:553)
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:924)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:365)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:854)
        at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:278)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46)
        at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192)
        at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:510)
        at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:153)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:172)
        at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:430)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:65)
        at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
        at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
        at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
        at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:145)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:598)
        at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:240)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167)
        at org.eclipse.jetty.server.Server.start(Server.java:418)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:119)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
        at org.eclipse.jetty.server.Server.doStart(Server.java:382)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$0(XmlConfiguration.java:1797)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1746)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:220)
        at org.eclipse.jetty.start.Main.start(Main.java:490)
        at org.eclipse.jetty.start.Main.main(Main.java:77)
Caused by:
java.io.FileNotFoundException: C:\Users\Genie\jetty\base\webapps\WEB-INF\config\SystemGlobals.properties (The system cannot find the path specified)
        at java.base/java.io.FileInputStream.open0(Native Method)
        at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
        at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
        at net.jforum.util.preferences.SystemGlobals.loadProps(SystemGlobals.java:448)
        at net.jforum.util.preferences.SystemGlobals.loadDefaults(SystemGlobals.java:194)
        at net.jforum.util.preferences.SystemGlobals.buildSystem(SystemGlobals.java:131)
        at net.jforum.util.preferences.SystemGlobals.initGlobals(SystemGlobals.java:107)
        at net.jforum.ConfigLoader.startSystemglobals(ConfigLoader.java:92)
        at net.jforum.ContextListener.contextInitialized(ContextListener.java:78)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:959)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:553)
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:924)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:365)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:854)
        at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:278)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46)
        at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192)
        at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:510)
        at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:153)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:172)
        at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:430)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:65)
        at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
        at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
        at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
        at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:145)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:598)
        at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:240)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167)
        at org.eclipse.jetty.server.Server.start(Server.java:418)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:119)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
        at org.eclipse.jetty.server.Server.doStart(Server.java:382)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$0(XmlConfiguration.java:1797)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1746)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:220)
        at org.eclipse.jetty.start.Main.start(Main.java:490)
        at org.eclipse.jetty.start.Main.main(Main.java:77)
2019-07-23 16:07:28.094:WARN::main: async-rest webapp is deployed. DO NOT USE IN PRODUCTION!
2019-07-23 16:07:28.101:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /async-rest, did not find org.eclipse.jetty.jsp.JettyJspServlet
2019-07-23 16:07:28.130:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@41709512{Async REST Webservice Example,/async-rest,[file:///C:/Users/Genie/AppData/Local/Temp/jetty-0.0.0.0-8080-async-rest.war-_async-rest-any-11406813050755376179.dir/webapp/, jar:file:///C:/Users/Genie/AppData/Local/Temp/jetty-0.0.0.0-8080-async-rest.war-_async-rest-any-11406813050755376179.dir/webapp/WEB-INF/lib/example-async-rest-jar-9.4.19.v20190610.jar!/META-INF/resources],AVAILABLE}{C:\Users\Genie\jetty\base\webapps\async-rest.war}
2019-07-23 16:07:31.184:INFO:oejs.AbstractConnector:main: Started ServerConnector@df6a84a{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2019-07-23 16:07:31.188:INFO:oejs.Server:main: Started @12595ms


When viewing localhost:8008, the following shows:

image

Note that jforum is "not available". Clicking on the link elicits the message "Error 503 Service Unavailable".
The program "async-rest.war" is an example file provided by Jetty and runs as expected.

In the above error printout, two things seem concerning. The first is the following line:

2019-07-23 16:07:24.378:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /jforum-2.6.0, did not find org.eclipse.jetty.jsp.JettyJspServlet


I noticed under "System Requirements" that only Apache Tomcat is mentioned as a server. Previously Jetty was also supported, was it not? Is it no longer supported?

The second thing is an error that shows up repeatedly, a filed is searched for and not found, and the error in the address is always that the folder for the project is not included.

JForum: problems initializing the logger: template not found: "C:\Users\Genie\jetty\base\webapps\WEB-INF\log4j_template.xml"


The file does exist, but it is at the following location: "C:\Users\Genie\jetty\base\webapps\jforum-2.6.0\WEB-INF\log4j_template.xml"

I'm wondering if the missing "jforum-2.6.0" somehow pertains to the project not being "registered" as was specified in the instruction: "The next step you should do is register the JForum application within your Servlet Container, like Tomcat."

Your assistance is much appreciated! The end goal is to provide a new forum for java-gaming.org. As a coder I'm a bit stronger on initiative than skill, and am attempting to put forth JForum as a candidate for consideration. We are currently using SMF.

[WWW]
udittmer


Joined: 2013/2/21
Messages: 273
Offline
Welcome to these parts. I haven't used Jetty before, but installing it and getting a demo web app to run was simple, so I'll try and see what's involved in getting JForum to run on it.

For example, the MySQL program I installed works fine. But is there some aspect that has to be specifically configured to work with JForum prior to installation?

No, the required information will be asked of you during installation.

"The next step you should do is register the JForum application within your Servlet Container, like Tomcat." I do not see any mention in Jetty about a registration process.

"Registration" is a rather fancy word for this - Jetty seems configured by default to start all war files it finds in the webapps directory; there is no need to tell it about additional web apps if that's where you intend to keep it.

2019-07-23 16:07:24.378:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /jforum-2.6.0, did not find org.eclipse.jetty.jsp.JettyJspServlet

This isn't good - JForum needs JSP, and it should be enabled by default. Check the start.ini file for "--module=jsp". Are you starting Jetty as described in https://www.eclipse.org/jetty/documentation/9.4.19.v20190610/quickstart-running-jetty.html, using the demo base?


java.lang.Exception: template not found: "C:\Users\Genie\jetty\base\webapps\WEB-INF\log4j_template.xml"

java.io.FileNotFoundException: C:\Users\Genie\jetty\base\webapps\WEB-INF\config\SystemGlobals.properties

That's odd, it should be looking in C:\Users\Genie\jetty\base\webapps\jforum-2.6.0\WEB-INF instead. I'm running into the very same problem (using Java 8), so apparently Jetty works differently than Tomcat. (As an aside, I note that Jetty doesn't create an exploded directory from the war file in the way Tomcat does - I'm fairly certain that will be a problem later on, as JForum expects to be able to write into that directory.) But even unpacking the war file manually and running the web app that way results in this error.

Note that jforum is "not available". Clicking on the link elicits the message "Error 503 Service Unavailable".

Given the error messages, that's not surprising. SystemGlobals.properties is positively required.

I noticed under "System Requirements" that only Apache Tomcat is mentioned as a server. Previously Jetty was also supported, was it not? Is it no longer supported?

The requirement is a Servlet 3.1 container (which Jetty is). Only Tomcat is listed under "Tested" because that's what we use to test JForum. We haven't done anything to make it incompatible with other servlet containers, though, but there may be snags.

The end goal is to provide a new forum for java-gaming.org. As a coder I'm a bit stronger on initiative than skill, and am attempting to put forth JForum as a candidate for consideration. We are currently using SMF.

Cool. I remember perusing those forums WAY back when when I was learning JOGL. Hopefully we can persuade you to choose JForum. In my obviously biased opinion JForum is the best Java open source forum web app.

I'll update this topic with what I find.

Ping & Net - my free Android app for TCP/IP network diagnostics
[WWW]
udittmer


Joined: 2013/2/21
Messages: 273
Offline
I'm running into the very same problem, so apparently Jetty works differently than Tomcat.

It does, and it's an area where the Servlet specification is unclear which behavior is correct. (For the technically inclined, it doesn't specify what ServletContext.getRealPath should return if an empty string is passed as a parameter). That's an easy fix, which I'll check in shortly. As a bonus, this also seems to work when deploying the unexploded war file (well, I've gotten as far as the first install page, which admittedly isn't very far).

Ping & Net - my free Android app for TCP/IP network diagnostics
[WWW]
udittmer


Joined: 2013/2/21
Messages: 273
Offline
I've uploaded a JForum 2.6 war file that includes the fix, specifically for use with Jetty. Give that a try and let us know how it goes.

Ping & Net - my free Android app for TCP/IP network diagnostics
[WWW]
philfrei


Joined: 2019/7/24
Messages: 13
Offline
Thanks! The new file runs without the missing file folder error.

As for the "JSP not found" error, I have a solution.

The line "--module=jsp" appears in a file named "start.ini" at the JETTY_HOME location. But I think that file is NOT being referenced. Instead, .ini parameters are taken from a directory named "start.d". When I added a file "jsp.ini" with that line as contents (copied from \demo-base\start.d\jsp.ini), the JSP not found error went away.

The configuration page now comes up as expected.
[WWW]
udittmer


Joined: 2013/2/21
Messages: 273
Offline
How are you making out? I'm curious to see if we can persuade you and your community to switch to JForum2 smilie

We've released version 2.6.1 recently, which addresses the Jetty issue, and also fixes a bug that messed up the moderation log.

Ping & Net - my free Android app for TCP/IP network diagnostics
[WWW]
philfrei


Joined: 2019/7/24
Messages: 13
Offline
I'm not in my area of expertise, and the installation is going slowly as I have to work very carefully to fill in the gaps in my knowledge.

On my laptop test install, I was able to find and do some editing of /default to customize a couple aspects of JForum2. Again, not that strong with HTML/CSS/JS, so having to read unfamiliar code and get oriented has been slow. I was wondering, though: is there a place where we specify the subdirectory for the html? Or do we just make use of /templates/default? It seems like there would be a place to specify a file folder name other than "default" but I am not seeing it.

For the new server (which will eventually be the live host), I've managed to install Java 12 and PostgreSQL 11 (both available via apt-get) and just set up the required database for JForum2. Next up, installing Jetty and JForum2 (which I assume is a matter of FTP-ing the code and unpacking) will not be too difficult to figure out. Looks like WinSCP will handle the file transfer. Just have to identify the commands for file-folder creation and for unpacking the .war/.tar or whatever.
[WWW]
udittmer


Joined: 2013/2/21
Messages: 273
Offline
I was wondering, though: is there a place where we specify the subdirectory for the html? Or do we just make use of /templates/default? It seems like there would be a place to specify a file folder name other than "default" but I am not seeing it.

That is the place to make changes. Way back when there was the idea to allow different themes in order to be able to customize the look and feel without having to change the default templates, but that feel by the wayside a long time ago. The "default" directory hierarchy is a remnant of that.

Let us know if you hit any JForum-specific issues and we may be able to help.

Ping & Net - my free Android app for TCP/IP network diagnostics
[WWW]
 
Forum Index » User Forum
Go to:   
Mobile view
Powered by JForum 2.6.0 © 2019 JForum Team • Maintained by Andowson Chang and Ulf Dittmer
Website Security Test