Tomcat 6 No Available Handlers

[Dundaur]

We are running GW 12.0.2 on SLES 11 SP1. This particular server holds a secondary domain, a GWIA, and WebAccess. While searching for an answer as to why the WebAccess quits responding I found the following errors in the catalina.out file.

ERROR: No handler is available for the action [Folder.List.Open]
java.lang.NullPointerException
at com.novell.webaccess.providers.soap.SOAP.service(SOAP.java:665)
at com.novell.webaccess.common.BaseServlet.onLogout(BaseServlet.java:1973)
at com.novell.webaccess.common.BaseServlet.service(BaseServlet.java:1077)
at com.novell.webaccess.WebAccessServlet.service(WebAccessServlet.java:273)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.novell.webaccess.common.BaseServlet.service(BaseServlet.java:906)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:438)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:736)
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]
ERROR: No handler is available for the action [Folder.List.Open]

This keeps repeating itself. I'm not too familiar with tomcat but it would appear that something is calling a Folder.List.Open action that is not supported? Anyone have clue as to why I see this?

Phillip
----------
University of Central Arkansas

[KonecnyA]

In article <Dundaur.694o7c@no-mx.forums.novell.com>, Dundaur wrote:
> We are running GW 12.0.2 on SLES 11 SP1.
...
> ERROR: No handler is available for the action [Folder.List.Open]
> java.lang.NullPointerException
...
> ERROR: No handler is available for the action [Folder.List.Open]
> ERROR: No handler is available for the action [Folder.List.Open]
...
> This keeps repeating itself. I'm not too familiar with tomcat but it
> would appear that something is calling a Folder.List.Open action that is
> not supported? Anyone have clue as to why I see this?

Hey Phillip, any particular reason why the running SLES service patch is that far back (2010)
compared to GW (2013) That mismatch might be a part of your issue as GW 2012 was released when
SLES 11 sp2 was current (now sp3 is current). Just patching may fix up those Tomcat files.

Has this ever worked and just recently broke?



Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please show your appreciation by
clicking on the star below. Thanks!

[Dundaur]

We normally prescribe to the "if it's not broke, don't fix it" attitude. I will apply the latest SP and see what happens.

Phillip

[KonecnyA]

In article <Dundaur.69blqn@no-mx.forums.novell.com>, Dundaur wrote:
> We normally prescribe to the "if it's not broke, don't fix it" attitude.
> I will apply the latest SP and see what happens.
>
I understand that approach, and there are many places where that is a very
good practice even though it almost never survives any sort of compliance
audit such as for security.
Given that WebAccess is usually very externally facing, that is a very
high risk to take as there are plenty of automated systems looking for
unsecured systems to take advantage of even if just to add them to their
botnets (and therefor taking them out of your control). We can't exclude
the possibility that this problem is due to an attempt to take over your
server.


Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

[Dundaur]

This is very true. We will be upgrading all of our WebAccess servers SP3 this Friday evening. I'll let you know if the problem persists.

Phillip

[Dundaur]

We've upgraded our SLES 11 SP1 to SP3 and have the same issue. Something just dawned on me though. We are running the FTF file that fixes the Windows 8 Folder List display. Everything seems to be working, even with this error. I think I'll wait until we get the final GW2012 SP3 build.

Phillip

[KonecnyA]

In article <Dundaur.69p8hd@no-mx.forums.novell.com>, Dundaur wrote:
> We are running the FTF file that
> fixes the Windows 8 Folder List display.
>
Was that the entire system this was applied to? Might be worth
confirming what you are actually running on the server with
rpm -qa | grep group
which on a GroupWise 2012 sp2 system shows
novell-groupwise-agents-12.0.2-108211
novell-groupwise-gwha-12.0.2-108211
novell-groupwise-gwia-12.0.2-108211
novell-groupwise-admin-12.0.2-108211
novell-groupwise-gwdva-12.0.2-108211
novell-groupwise-calhost-12.0.2-108211
novell-groupwise-webaccess-12.0.2-108211



Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

[Dundaur]

The patch was applied to WebAccess only as per the instructions I received. My rpm -qa | grep group command displays...

novell-groupwise-gwdva-12.0.2-108211
novell-groupwise-gwia-12.0.2-108211
novell-groupwise-admin-12.0.2-108211
novell-groupwise-webaccess-12.0.2-113525
novell-groupwise-agents-12.0.2-108211
novell-groupwise-gwha-12.0.2-108211

Phillip

[KonecnyA]

In article <Dundaur.69sanz@no-mx.forums.novell.com>, Dundaur wrote:
> The patch was applied to WebAccess only as per the instructions I
> received. My *rpm -qa | grep group* command displays...
> novell-groupwise-webaccess-12.0.2-113525

Was that as a part of an SR? If so is it still open?
Did the problem you have partially described begin at about the same
time as applying that FTF?
Interesting that the FTF was to fix a folder problem and those logs
show "ERROR: No handler is available for the action [Folder.List.Open]"
That sure makes me think they may be related.



Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

[Dundaur]

We have no open SR at the moment. I had not even associated the [Folder.List.Open] error with the folder list problem on Windows 8. I know the FTF was for that problem, but for some reason I didn't relate the two. Your right in so much as the problem didn't exist until I added the FTF file. Thanks for pointing that out. I at least have a direction to go now.

Phillip