[ODLPARENT-157] failed to parse and instantiate of javax.servlet.ServletContainerInitializer in classpath Created: 02/Aug/18  Updated: 12/Mar/19  Resolved: 12/Mar/19

Status: Resolved
Project: odlparent
Component/s: Karaf
Affects Version/s: 3.1.3
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Michael Vorburger Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The following messages appears in logs (e.g. here and here) :

2018-08-02T01:44:05,980 | WARN  | paxweb-extender-1-thread-1 | ServletContainerInitializerScanner | 440 - org.ops4j.pax.web.pax-web-api - 6.0.9 | failed to parse and instantiate of javax.servlet.ServletContainerInitializer in classpath

My current understanding is that this is completely harmless; this message does NOT mean that all web related functionality (like /diagstatus and all RESTCONF URLs) is broken, it works - there are no real functional problems (related to this message).

It's just a possibly mildly confusing, and thus perhaps something to figure out how to supress, some time (low priority, given overall situation of things).

This WARN log also appears in older ODLPARENT-74 and ODLPARENT-82, but those used to contains full stack trace showing a RuntimeException from ASM as root cause of this message. That does not show up here - unclear whether that just got removed following a (Karaf / Pax Web) upgrade, or if this is something else. More likely the former, so this message is less scary now - but, in an ideal world, shouldn't show up at all.

 Comments   
Comment by Robert Varga [ 05/Sep/18 ]

vorburger is this still happening (with karaf-4.2.1?)

Comment by Michael Vorburger [ 05/Sep/18 ]

I'm not seeing this exact message anymore (on today's master Neon), but there's this now:

2018-09-04T23:39:55,023 | WARN | Blueprint Extender: 2 | ServletContainerInitializerScanner | 426 - org.ops4j.pax.web.pax-web-api - 6.0.9 | Failed to find annotated classes for ServletContainerInitializer

It's not a real problem though, just a possibly mildly confusing, and thus perhaps something to figure out how to supress, some time (low priority, given overall situation of things). I'm also OK if we just close this issue as WONTDO.

Comment by Robert Varga [ 12/Mar/19 ]

This is completely in hands of upstream, as far as I can tell. Let's see when they clean it up.

Generated at Wed Feb 07 20:27:47 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.