RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I hope the latest version(8.0.13) should solve the issue.
Thank you for taking up the issue and being supportive, your responses are
deeply appreciated.
Regards,
Prashanth
From: Prashanth Ettaboina
Sent: 16 November 2022 15:33
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 16 November 2022 14:02
To: 'iss...@karaf.apache.org'
mailto:iss...@karaf.apache.org>>;
'dev@karaf.apache.org' mailto:dev@karaf.apache.org>>;
'u...@karaf.apache.org' mailto:u...@karaf.apache.org>>
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 15 November 2022 20:03
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm generating a WAR file of the bundle(which will have the web application).
Adding the war file in the feature.xml and installing it in the karaf as a kar
file.
mvn:com.server.console/helloboard/${project.version}/war
karaf@root()> kar: install file :filepath*** snapshot.kar
below are the logs from karaf which are generated while I installed the kar
file.
2022-11-15T19:19:11.401+0530 CEF:1 | org.apache.karaf.kar.core | 4.4.1 | INFO
| ID=168 THR=0.0-SNAPSHOT.kar CAT=KarServiceImpl MSG=Added
feature repository
'mvn:com.server.kars/example-console/51.0.0-SNAPSHOT/xml/features'
2022-11-15T19:19:11.403+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=0.0-SNAPSHOT.kar CAT=FeaturesServiceImpl
MSG=Adding features: example-console/[51.0.0.SNAPSHOT,51.0.0.SNAPSHOT]
2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
MSG=Changes to perform:
2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
Region: root
2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
Bundles to install:
2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
mvn:com.server.console/helloboard/51.0.0-SNAPSHOT/war
2022-11-15T19:19:20.621+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
helloboard/51.0.0.SNAPSHOT
2022-11-15T19:19:20.634+0530 CEF:1 | org.ops4j.pax.web.pax-web-extender-war |
8.0.6 | INFO | ID=269 THR=ender-1-thread-1 CAT=BundleWebApplication
MSG=Configuring Web Application "/helloboard" for bundle
helloboard/51.0.0.SNAPSHOT
2022-11-15T19:19:20.635+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
MSG=Done.
2022-11-15T19:19:32.512+0530 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| INFO | ID=272 THR=ender-1-thread-1 CAT=StoppableHttpServiceFactory
MSG=Binding HTTP Service for bundle: [helloboard [318]]
2022-11-15T19:19:32.514+0530 CEF:1 | org.ops4j.pax.web.pax-web-extender-war |
8.0.6 | INFO | ID=269 THR=ender-1-thread-1 CAT=BundleWebApplication
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 16 November 2022 14:02
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 15 November 2022 20:03
To: 'iss...@karaf.apache.org'
mailto:iss...@karaf.apache.org>>;
'dev@karaf.apache.org' mailto:dev@karaf.apache.org>>;
'u...@karaf.apache.org' mailto:u...@karaf.apache.org>>
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm generating a WAR file of the bundle(which will hav
RE: Unable to create default RequestDispatcher
2-11-15T19:19:32.640+0530 CEF:1 | org.ops4j.pax.web.pax-web-jsp | 8.0.6 |
INFO | ID=271 THR=ploy /helloboard) CAT=PaxWebTldScanner
MSG=Searching for TLDs in bundle helloboard [318]
2022-11-15T19:19:32.828+0530 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| INFO | ID=272 THR=ploy /helloboard) CAT=HttpServiceEnabled
MSG=Registering
EventListenerModel{id=EventListenerModel-252,listener='ch.qos.logback.classic.servlet.LogbackServletContextListener@70476be6',contexts=[{WAB,OCM-233,/helloboard,/helloboard}]}
2022-11-15T19:19:32.828+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerController
MSG=Receiving Batch{"Registration of
EventListenerModel{id=EventListenerModel-252,listener='ch.qos.logback.classic.servlet.LogbackServletContextListener@70476be6',contexts=[{WAB,OCM-233,/helloboard,/helloboard}]}",
size=1}
2022-11-15T19:19:32.830+0530 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| INFO | ID=272 THR=ploy /helloboard) CAT=HttpServiceEnabled
MSG=Registering
EventListenerModel{id=EventListenerModel-251,listener='org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer$ContextDestroyListener@526531fa',contexts=[{WAB,OCM-233,/helloboard,/helloboard}]}
2022-11-15T19:19:32.831+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerController
MSG=Receiving Batch{"Registration of
EventListenerModel{id=EventListenerModel-251,listener='org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer$ContextDestroyListener@526531fa',contexts=[{WAB,OCM-233,/helloboard,/helloboard}]}",
size=1}
2022-11-15T19:19:32.834+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| INFO | ID=243 THR=ploy /helloboard) CAT=ContextHandler
MSG=Started
o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd{ServerHelloboard,/helloboard,null,AVAILABLE}<mailto:o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd%7bServerDashboard,/dashboard,null,AVAILABLE%7d>
From: Prashanth Ettaboina
Sent: 15 November 2022 16:28
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm not registering the ExampleServlet anywhere, I'm configuring them in
web.xml.
In the web.xml we are giving the servlet and servlet mapping with url-pattern
and class path.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 14 November 2022 19:11
To: iss...@karaf.apache.org<mailto:iss...@karaf.apache.org>;
dev@karaf.apache.org<mailto:dev@karaf.apache.org>;
u...@karaf.apache.org<mailto:u...@karaf.apache.org>
Subject: Unable to create default RequestDispatcher
Hi Team,
I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to 11 in
my application.
Gone through the official Release notes and updated some dependencies as well.
Upgraded OSGI-Core from 6.0.0 to 8.0.0.
Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
Upgraded pax-web-spi from 4.3.4 to 7.2.11.
I'm using javax.servlet-api 3.1.0 version in my application.
I'm unable to create default RequestDispatcher.
Please check the below code lines.
public class ExampleServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
RequestDispatcher requestDispatcher =
getServletContext().getNamedDispatcher("default"); // get getServletContext()
is calling the method in GenericServlet.
requestDispatcher.include(request, response);
}
}
the above code used to work fine before the version upgrades but now I'm
getting the requestDispatcher as null.
Can anyone please look at it, let me know if I'm missing something.
Thanks,
Prashanth Ettaboina
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm not registering the ExampleServlet anywhere, I'm configuring them in
web.xml.
In the web.xml we are giving the servlet and servlet mapping with url-pattern
and class path.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 14 November 2022 19:11
To: iss...@karaf.apache.org; dev@karaf.apache.org; u...@karaf.apache.org
Subject: Unable to create default RequestDispatcher
Hi Team,
I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to 11 in
my application.
Gone through the official Release notes and updated some dependencies as well.
Upgraded OSGI-Core from 6.0.0 to 8.0.0.
Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
Upgraded pax-web-spi from 4.3.4 to 7.2.11.
I'm using javax.servlet-api 3.1.0 version in my application.
I'm unable to create default RequestDispatcher.
Please check the below code lines.
public class ExampleServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
RequestDispatcher requestDispatcher =
getServletContext().getNamedDispatcher("default"); // get getServletContext()
is calling the method in GenericServlet.
requestDispatcher.include(request, response);
}
}
the above code used to work fine before the version upgrades but now I'm
getting the requestDispatcher as null.
Can anyone please look at it, let me know if I'm missing something.
Thanks,
Prashanth Ettaboina
Unable to create default RequestDispatcher
Hi Team,
I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to 11 in
my application.
Gone through the official Release notes and updated some dependencies as well.
Upgraded OSGI-Core from 6.0.0 to 8.0.0.
Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
Upgraded pax-web-spi from 4.3.4 to 7.2.11.
I'm using javax.servlet-api 3.1.0 version in my application.
I'm unable to create default RequestDispatcher.
Please check the below code lines.
public class ExampleServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
RequestDispatcher requestDispatcher =
getServletContext().getNamedDispatcher("default"); // get getServletContext()
is calling the method in GenericServlet.
requestDispatcher.include(request, response);
}
}
the above code used to work fine before the version upgrades but now I'm
getting the requestDispatcher as null.
Can anyone please look at it, let me know if I'm missing something.
Thanks,
Prashanth Ettaboina
RE: Unable to load custom web.xml for Pax Web in Karaf (4.4.1)
Hi,
Thank you Grzegorz for your response. It helped me.
Thanks,
Prashanth.
From: Prashanth Ettaboina
Sent: 10 November 2022 19:49
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to load custom web.xml for Pax Web in Karaf (4.4.1)
Hi Grzybek,
Thank you for your response.
I do not have any jars in my /WEB-INF/lib, I do not have lib folder in my
WEB-INF folder.
In my module I have a web.xml (/src/main/webapp/WEB-INF/web.xml) I'm building
this module as a kar file and installing it into the karaf console.
I'm able to see my bundle getting started and getting active without any issue.
But I'm able to see the below log lines after installing the kar file.
2022-11-10T19:09:05.486+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
helloboard/51.0.0.SNAPSHOT
2022-11-10T19:09:05.506+0530 CEF:1 | org.ops4j.pax.web.pax-web-extender-war |
8.0.6 | WARN | ID=269 THR=tures-3-thread-1 CAT=WarExtenderContext
MSG=Web-ContextPath manifest header of helloboard [312] specifies invalid
context path: helloboard. This bundle will not be processed.
2022-11-10T19:09:05.506+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
MSG=Done.
When I try to access https://localhost:8443/helloboard/ server responded back
with 404.
Below are the jetty logs when I try to access the above endpoint.
2022-11-10T19:39:46.391+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=REQUEST for //localhost:8443/helloboard on
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=IDLE rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=true
al=0},r=2,c=false/false,a=IDLE,uri=//localhost:8443/helloboard,age=0}
GET //localhost:8443/helloboard HTTP/1.1
Host: localhost:8443
2022-11-10T19:39:46.392+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=handle //localhost:8443/helloboard
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=IDLE rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=true
al=0},r=2,c=false/false,a=IDLE,uri=//localhost:8443/helloboard,age=0}
2022-11-10T19:39:46.392+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=action DISPATCH
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=true
al=0},r=2,c=false/false,a=HANDLING,uri=//localhost:8443/helloboard,age=1}
2022-11-10T19:39:46.392+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=SecureRequestCustomizer
MSG=Host localhost with SNI null
2022-11-10T19:39:46.392+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=Server
MSG=REQUEST GET /helloboard on
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=true
al=0},r=2,c=false/false,a=HANDLING,uri=https://localhost:8443/helloboard,age=1}
2022-11-10T19:39:46.393+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=ContextHandler
MSG=scope null||/helloboard @
o.o.p.w.s.j.i.PaxWebServletContextHandler@52ee63a5{/,null,AVAILABLE}<mailto:o.o.p.w.s.j.i.PaxWebServletContextHandler@52ee63a5%7b/,null,AVAILABLE%7d>
2022-11-10T19:39:46.393+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=ContextHandler
MSG=context=||/helloboard @
o.o.p.w.s.j.i.PaxWebServletContextHandler@52ee63a5{/,null,AVAILABLE}<mailto:o.o.p.w.s.j.i.PaxWebServletContextHandler@52ee63a5%7b/,null,AVAILABLE%7d>
2022-11-10T19:39:46.393+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=session
MSG=Entering scope
org.ops4j.pax.web.service.jetty.internal.PaxWebSessionHandler1209060588==dftMaxIdleSec=1800,
dispatch=REQUEST asyncstarted=false
2022-11-10T19:39:46.393+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=session
MSG=Got Session ID node0153ccberdksh618rs5jxv328kq22.node0 from cookie
JSESSIONID
2022-11-10T19:39:46.393+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=session
MSG=Session node0153ccberdksh618rs5jxv328kq22 not found locally in
org.eclipse.jetty.server.session.DefaultSessionCache@3daaf5f7[evict=-1,removeUnloadable=false,saveOnCreate=false,saveOnInactiveEvict=false<mailto:org.eclipse.jetty.server.se
RE: Unable to load custom web.xml for Pax Web in Karaf (4.4.1)
20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=action SEND_ERROR
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=false
al=0},r=2,c=false/false,a=HANDLING,uri=https://localhost:8443/helloboard,age=11}
2022-11-10T19:39:46.402+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=onContentComplete
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=false
al=0},r=2,c=false/false,a=HANDLING,uri=https://localhost:8443/helloboard,age=11}
2022-11-10T19:39:46.403+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=onRequestComplete
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING rs=BLOCKING
os=OPEN is=IDLE awp=false se=false i=false
al=0},r=2,c=false/false,a=HANDLING,uri=https://localhost:8443/helloboard,age=12}
2022-11-10T19:39:46.403+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=ErrorPageErrorHandler
MSG=getErrorPage(GET /helloboard) => error_page=null (from global default)
2022-11-10T19:39:46.404+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=sendResponse info=null
content=HeapByteBuffer@6fd24ba[p=0,l=372,c=32768,r=372]={<<<\n\n\n\n\n\n>>>\ne link,
...\x00\x00\x00\x00\x00\x00\x00} complete=true committing=true
callback=org.eclipse.jetty.util.Callback$3@46bbe7e6<mailto:callback=org.eclipse.jetty.util.Callback$3@46bbe7e6>
2022-11-10T19:39:46.404+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=COMMIT for /helloboard on
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=HANDLING
rs=COMPLETING os=COMMITTED is=IDLE awp=false se=false i=false
al=0},r=2,c=false/false,a=HANDLING,uri=https://localhost:8443/helloboard,age=13}
404 null HTTP/1.1
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
2022-11-10T19:39:46.405+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpGenerator
MSG=generateHeaders HTTP/1.1{s=404,h=2,cl=-1} last=true
content=HeapByteBuffer@6fd24ba[p=0,l=372,c=32768,r=372]={<<<\n\n\n\n\n\n>>>\ne link,
...\x00\x00\x00\x00\x00\x00\x00}
2022-11-10T19:39:46.405+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpGenerator
MSG=Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
2022-11-10T19:39:46.406+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpGenerator
MSG=CONTENT_LENGTH
2022-11-10T19:39:46.407+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=action TERMINATED
HttpChannelOverHttp@62fa25b0{s=HttpChannelState@2f46c6d1{s=IDLE rs=COMPLETED
os=COMPLETED is=IDLE awp=false se=false i=false
al=0},r=2,c=true/true,a=IDLE,uri=https://localhost:8443/helloboard,age=15}
2022-11-10T19:39:46.407+0530 CEF:1 | org.eclipse.jetty.util | 9.4.48.v20220622
| DEBUG | ID=243 THR=qtp501056700-863 CAT=HttpChannel
MSG=onCompleted for /helloboard written=372
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 10 November 2022 15:56
To: iss...@karaf.apache.org; dev@karaf.apache.org; u...@karaf.apache.org
Subject: Unable to load custom web.xml for Pax Web in Karaf (4.4.1)
Hi Team,
I have upgraded my Application from Karaf 4.2.15 to 4.4.1 version.
As per release notes (4.4.0 and 4.4.1) I have updated Pax Web dependency to
8.0.6 along with Jetty to 9.4.46.v20220331
The issue is Pax web is unable to load my web.xml, I have tried to find the end
points (list of servlets) which are running in the karaf using the karaf
commands (http:list & web:list) both commands are not supported by latest karaf.
Can anyone please look at it.
Thanks,
Prashanth Ettaboina,
Unable to load custom web.xml for Pax Web in Karaf (4.4.1)
Hi Team, I have upgraded my Application from Karaf 4.2.15 to 4.4.1 version. As per release notes (4.4.0 and 4.4.1) I have updated Pax Web dependency to 8.0.6 along with Jetty to 9.4.46.v20220331 The issue is Pax web is unable to load my web.xml, I have tried to find the end points (list of servlets) which are running in the karaf using the karaf commands (http:list & web:list) both commands are not supported by latest karaf. Can anyone please look at it. Thanks, Prashanth Ettaboina,
