File manager doesn't actually upload files
RoboMWM opened this issue · 7 comments
Using 469cb18
On web-end, JPanel appears to properly show upload progress and a completion message. However, the file does not appear in the web view. Neither does it actually appear when I log into the server.
user:
password: redacted
canEditFiles: true
canChangeGroups: false
canSendCommands: falseOS: Windows 7 (my Windows Server machine is rip at the moment)
It uploads fine to my server, just it doesn't update the web view (as I posted previously).
Make sure your firewall isn't blocking anything, also double check Java has write-access to the folder.
Then again I am running JPanel on a VPS running Linux, thus Windows may have an issue with this.
Sure, but it indicates that he's not using any standard java libraries/environmental variables and the like to figure out the path... hardcoding isn't really a good idea in any circumstance...
Ah, so it is working fine for me simply because I am running my server on Linux.
Yup, he hardcodes a period in the path. Also is strangely using the appdata folder...
[14:09:42] [qtp124656802-219/WARN]: java.io.FileNotFoundException: C:\Users\THISIS~1\AppData\Local\Temp\C:\Users\thisisauser\Documents\serbur\.\Capture.PNG (The filename, directory name, or volume label syntax is incorrect)
[14:09:42] [qtp124656802-219/WARN]: at java.io.FileOutputStream.open0(Native Method)
[14:09:42] [qtp124656802-219/WARN]: at java.io.FileOutputStream.open(Unknown Source)
[14:09:42] [qtp124656802-219/WARN]: at java.io.FileOutputStream.<init>(Unknown Source)
[14:09:42] [qtp124656802-219/WARN]: at java.io.FileOutputStream.<init>(Unknown Source)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.util.MultiPartInputStreamParser$MultiPart.write(MultiPartInputStreamParser.java:262)
[14:09:42] [qtp124656802-219/WARN]: at net.rymate.jpanel.posters.FilePost.getResponse(FilePost.java:44)
[14:09:42] [qtp124656802-219/WARN]: at spark.RouteImpl$1.handle(RouteImpl.java:61)
[14:09:42] [qtp124656802-219/WARN]: at spark.http.matching.Routes.execute(Routes.java:61)
[14:09:42] [qtp124656802-219/WARN]: at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:128)
[14:09:42] [qtp124656802-219/WARN]: at spark.embeddedserver.jetty.JettyHandler.doHandle(JettyHandler.java:50)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.Server.handle(Server.java:517)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
[14:09:42] [qtp124656802-219/WARN]: at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
[14:09:42] [qtp124656802-219/WARN]: at java.lang.Thread.run(Unknown Source)
Yeah, I've seen this issue before as well. Servers with this plugin running on Linux don't have this problem
