lem9 Absent Member.
Absent Member.
957 views

Tomcat solid crash

Hi,
I just installed Filr 1.0 on three VMs. It worked for a few days but now, even after restarting the three VMs, trying to visit the main Filr machine on 8443 replies with:

HTTP Status 500 - Filter execution threw an exception

type Exception report

message Filter execution threw an exception

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Filter execution threw an exception
org.kablink.teaming.webdav.servlet.filter.ResourceDispatchFilter.doFilter(ResourceDispatchFilter.java:87)
0 Likes
3 Replies
jmarton2 Absent Member.
Absent Member.

Re: Tomcat solid crash

lem9 wrote:

> I just installed Filr 1.0 on three VMs. It worked for a few days but
> now, even after restarting the three VMs, trying to visit the main
> Filr machine on 8443 replies with:
>
> HTTP Status 500 - Filter execution threw an exception
>
> type Exception report
>
> message Filter execution threw an exception
>
> description The server encountered an internal error that prevented it
> from fulfilling this request.
>
> exception
>
> javax.servlet.ServletException: Filter execution threw an exception
>
> org.kablink.teaming.webdav.servlet.filter.ResourceDispatchFilter.doFil
> ter(ResourceDispatchFilter.java:87)


Is this 1.0 or 1.0.1? If it's 1.0 you may want to scratch the current
environment and start over with 1.0.1. If it's 1.0.1, how much RAM is
allocated to each VM, and how much RAM is the JVM configured on each VM
(especially the Filr & Search VMs)?

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Bob-O-Rama
Visitor.

Re: Tomcat solid crash

Could be anything, but you may want to review this thread also if you are running current code. Generally filr dying a horrible death like that is caused by insufficient memory allocated to the VM host.

-- Bob
0 Likes
Highlighted
lem9 Absent Member.
Absent Member.

Re: Tomcat solid crash

The crash was with 1.0 and 1.0.1. After reinstalling and changing two things, the servers have been stable for eight days. What I changed was:
- no longer define net folders pointing to a Netware server having eDirectory < 8.8
- no longer point the LDAP definition to a Netware server but to a SLES/OES11 server (same tree)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.