You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by jochenw <jo...@googlemail.com> on 2014/11/07 16:22:45 UTC
pax-web: war stays in deploying state
Dear all,
I'm trying to deploy a normal .war with "bundle:install -s
webbundle:....war?Bundle-SymbolicName=testwar&Web-ContextPath=/testwar". The
war contains a Vaadin-based Web application, and it runs on a standalone
jetty or tomcat without problems.
When deploying in Karaf (war feature installed), the command mentioned above
returns without an error, and the bundle is shown as active. However,
web:list continues showing the Web-State as "Deploying", and http:list shows
no servlet. Of course, trying to access the Web UI fails.
Any idea what I'm doing wrong? Below you can see the relevant lines from the
log.
Best Regards,
Jochen
2014-11-07 15:05:28,022 | DEBUG | h for user karaf | testwar
| 145 - testwar - 0.0.0 | BundleEvent INSTALLED - testwar
2014-11-07 15:05:28,022 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting BlueprintContainer
destruction process for bundle testwar
2014-11-07 15:05:28,022 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for testwar.
2014-11-07 15:05:28,028 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting BlueprintContainer
destruction process for bundle testwar
2014-11-07 15:05:28,028 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for testwar.
2014-11-07 15:05:28,028 | DEBUG | h for user karaf | Activator
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Starting
destruction process for bundle testwar
2014-11-07 15:05:28,028 | DEBUG | h for user karaf | Activator
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Not an extended
bundle or destruction of extension already finished for testwar.
2014-11-07 15:05:28,829 | DEBUG | h for user karaf | testwar
| 145 - testwar - 0.0.0 | BundleEvent RESOLVED - testwar
2014-11-07 15:05:28,829 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting BlueprintContainer
destruction process for bundle testwar
2014-11-07 15:05:28,829 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for testwar.
2014-11-07 15:05:28,832 | DEBUG | h for user karaf | testwar
| 145 - testwar - 0.0.0 | BundleEvent STARTING - testwar
2014-11-07 15:05:28,832 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | Scanning bundle testwar for
blueprint application
2014-11-07 15:05:28,834 | DEBUG | h for user karaf | BlueprintExtender
| 15 - org.apache.aries.blueprint.core - 1.4.1 | No blueprint application
found in bundle testwar
2014-11-07 15:05:28,885 | DEBUG | h for user karaf | WebEventDispatcher
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Sending web event
WebEvent [replay=false, type=DEPLOYING, bundle=testwar [145],
extenderBundle=org.ops4j.pax.web.pax-web-extender-war [133], cause=null,
timestamp=1415372728885, contextPath=/testwar, collisionIds=null,
httpService=null, httpContext=null] for bundle testwar
2014-11-07 15:05:28,894 | DEBUG | EventExecutor: 1 | pax-web-extender-war
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 |
org/osgi/service/web/DEPLOYING
2014-11-07 15:05:28,894 | DEBUG | h for user karaf | WebAppParser
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | version found in
web.xml - 3.0
2014-11-07 15:05:28,894 | DEBUG | h for user karaf | WebAppParser
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | metadata-complete
is: false
2014-11-07 15:05:28,895 | DEBUG | h for user karaf | WebAppParser
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | scanning for
ServletContainerInitializers
2014-11-07 15:05:28,897 | DEBUG | h for user karaf | WebAppParser
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | found container
initializers by SafeServiceLoader ... skip the old impl.
2014-11-07 15:05:29,615 | DEBUG | h for user karaf | Activator
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Scheduling start of
extension for bundle testwar asynchronously
2014-11-07 15:05:29,622 | DEBUG | h for user karaf | testwar
| 145 - testwar - 0.0.0 | BundleEvent STARTED - testwar
2014-11-07 15:05:29,622 | DEBUG | h for user karaf | ChannelSession
| 28 - org.apache.sshd.core - 0.12.0 | Send SSH_MSG_CHANNEL_DATA on channel
0
2014-11-07 15:05:29,622 | DEBUG | pool-7-thread-1 | WebAppPublisher
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Publishing web
application
[WebApp{displayName=testwar,contextName=testwar,m_httpContext=null}]
2014-11-07 15:05:29,622 | DEBUG | h for user karaf | Nio2Session
| 28 - org.apache.sshd.core - 0.12.0 | Writing 68 bytes
2014-11-07 15:05:29,624 | DEBUG | h for user karaf | ChannelSession
| 28 - org.apache.sshd.core - 0.12.0 | Send SSH_MSG_CHANNEL_DATA on channel
0
2014-11-07 15:05:29,624 | DEBUG | 5]-nio2-thread-1 | Nio2Session
| 28 - org.apache.sshd.core - 0.12.0 | Finished writing
2014-11-07 15:05:29,624 | DEBUG | h for user karaf | Nio2Session
| 28 - org.apache.sshd.core - 0.12.0 | Writing 52 bytes
2014-11-07 15:05:29,624 | DEBUG | 5]-nio2-thread-2 | Nio2Session
| 28 - org.apache.sshd.core - 0.12.0 | Finished writing
2014-11-07 15:05:29,625 | DEBUG | h for user karaf |
LoggingCommandSessionListener | 25 - org.apache.karaf.shell.console -
3.0.2 | Command: 'bundle:install -s
"webbundle:file:/opt/testwar-1.0.0.1.war?Bundle-SymbolicName=testwar&Web-ContextPath=/testwar"'
returned 'null'
--
View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: pax-web: war stays in deploying state
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Jochen,
... AND if javax.servlet.annotation is imported . Annotation scanning works
> now. That's why we use OSGi - to have more control, don't we?
yes, and that's why I alway use the maven-bundle-plugin to build all my
bundles (including war).
In that case those imports aren't forgotten :D
regards, Achim
2014-11-14 15:55 GMT+01:00 jochenw <jo...@googlemail.com>:
> Hi Achim,
>
> ... AND if javax.servlet.annotation is imported . Annotation scanning works
> now. That's why we use OSGi - to have more control, don't we?
>
> Servlet as inner class - I don't know whether the scanner should support
> that, one can solve this easily. It's just a bit tricky to find out that it
> doesn't work that way.
>
> Regarding the resources: yes, there we need to do some refactoring.
> Starting
> with a "normal" war, one easily uses things like getBaseDirectory() to
> access images etc.
>
> Again thanks for the help - you brought me on the right track.
>
> Regards,
> Jochen
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036427.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: pax-web: war stays in deploying state
Posted by jochenw <jo...@googlemail.com>.
Hi Achim,
... AND if javax.servlet.annotation is imported . Annotation scanning works
now. That's why we use OSGi - to have more control, don't we?
Servlet as inner class - I don't know whether the scanner should support
that, one can solve this easily. It's just a bit tricky to find out that it
doesn't work that way.
Regarding the resources: yes, there we need to do some refactoring. Starting
with a "normal" war, one easily uses things like getBaseDirectory() to
access images etc.
Again thanks for the help - you brought me on the right track.
Regards,
Jochen
--
View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036427.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: pax-web: war stays in deploying state
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Jochen,
ok a couple of different issues here.
I'll try to address those.
First of all if you have a WAB, it's only a valid WAB if the
Web-ContextPath attribute is inside it.
The Annotated Classes only work if this is set AND if you have also a
web.xml inside the war/jar if this web.xml is defined to be a version 3
web.xml. Either that or remove the corresponding web.xml :)
Since it seems to work with the webbundle I guess you are missing the
first, the Web-ContextPath attribute.
For resources don't - please don't - rely on extracted Jars it doesn't work
this way in an OSGi container. Make sure you're able to address the
resources via a standard classpath way. If it's accessible from within the
bundle it will work. Take a look at a couple of different samples available
at the pax-web project you'll find the correct way there.
The servlet as inner class ... well Never expected that to happen. I guess
I'd need to alter the scanner for that.
regards, Achim
2014-11-14 9:26 GMT+01:00 jochenw <jo...@googlemail.com>:
> Thanks for the hints, Achim!
>
> Now it works - basically. The trick was to move out the servlet class from
> the Vaadin main UI class. It looks like pax-web cannot deal with the
> servlet
> defined as inner class (TestwarUI$Servlet.class).
>
> I still have some problems: when installing the bundle as a wab (just with
> install file:..., manifest of course filled accordingly), the WebAppParser
> in org.ops4j.pax.web.pax-web-extender-war does not scan for annotated
> classes. So this deployment does not work if I use the @WebServlet
> annotation, but I have to include the respective definitions in the
> web.xml.
> When I install the bundle as plain war (install webbundle:file:...), it
> scans for annotated classes and uses the @WebServlet annotation correctly.
> Any idea what I have to do to trigger the scanning also for wab deployment?
>
> I also receive a "java.lang.AssertionError: Not a File:
> /org/atmosphere/annotation" and it is not possible to access some resources
> since the war is not extracted. Maybe I just have to find where to set
> extractWars to true for jetty running in Karaf.
>
> Regards,
> Jochen
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036414.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: pax-web: war stays in deploying state
Posted by jochenw <jo...@googlemail.com>.
Thanks for the hints, Achim!
Now it works - basically. The trick was to move out the servlet class from
the Vaadin main UI class. It looks like pax-web cannot deal with the servlet
defined as inner class (TestwarUI$Servlet.class).
I still have some problems: when installing the bundle as a wab (just with
install file:..., manifest of course filled accordingly), the WebAppParser
in org.ops4j.pax.web.pax-web-extender-war does not scan for annotated
classes. So this deployment does not work if I use the @WebServlet
annotation, but I have to include the respective definitions in the web.xml.
When I install the bundle as plain war (install webbundle:file:...), it
scans for annotated classes and uses the @WebServlet annotation correctly.
Any idea what I have to do to trigger the scanning also for wab deployment?
I also receive a "java.lang.AssertionError: Not a File:
/org/atmosphere/annotation" and it is not possible to access some resources
since the war is not extracted. Maybe I just have to find where to set
extractWars to true for jetty running in Karaf.
Regards,
Jochen
--
View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036414.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: pax-web: war stays in deploying state
Posted by Achim Nierbeck <bc...@googlemail.com>.
If you work with larger maven projects make sure you do use test, compile
and provided scopes on your dependencies.
Usually this will help filter out lot's of your issues already as only
compile dependencies are included if you use the maven-bundle-plugin.
Right now I wouldn't know of any restrictions about your dependencies, but
that doesn't mean there are non :)
First you might want to check the correct setting of he ClassPath in the
Manifes. It should not only contain the lib/jar (hell you got there) but
also the WEB-INF/classses as path.
regards, Achim
2014-11-12 12:56 GMT+01:00 jochenw <jo...@googlemail.com>:
> Better check from time to time what Maven does in a complex project .
>
> We'll have to check how to get rid of all the jars needed for testing. In
> the meantime, I have removed at least the toxic items from the lib folder
> (osgi jars, javax.servlet, and, to be sure, also the jetty jars). Already
> after removal of the osgi jars, the deployment worked, and web:list and
> http:list look reasonable.
>
> However, I still receive a 404 when calling the usual URL for the UI
> (myserver:8181/testwar). When checking the log, I found
> org.ops4j.pax.web.pax-web-extender-war throwing a warning that the class
> for
> which the WebServlet annotation was found could not be "created", and the
> class ....MyUI.Servlet wasn't loaded (the servlet class - extending
> VaadinServlet - is an inner class of the main UI class - extending the
> Vaadin framework class UI). The class exists in WEB-INF/classes as
> MyUI$Servlet.class. Should this combination still be supported by pax-web,
> or is this the point where my experiments to simply deploy the war in Karaf
> have to come to an end, and we have to go for a full OSGi integration of
> our
> Vaadin-based Web UI?
>
> Best Regards,
> Jochen
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036363.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: pax-web: war stays in deploying state
Posted by jochenw <jo...@googlemail.com>.
Better check from time to time what Maven does in a complex project .
We'll have to check how to get rid of all the jars needed for testing. In
the meantime, I have removed at least the toxic items from the lib folder
(osgi jars, javax.servlet, and, to be sure, also the jetty jars). Already
after removal of the osgi jars, the deployment worked, and web:list and
http:list look reasonable.
However, I still receive a 404 when calling the usual URL for the UI
(myserver:8181/testwar). When checking the log, I found
org.ops4j.pax.web.pax-web-extender-war throwing a warning that the class for
which the WebServlet annotation was found could not be "created", and the
class ....MyUI.Servlet wasn't loaded (the servlet class - extending
VaadinServlet - is an inner class of the main UI class - extending the
Vaadin framework class UI). The class exists in WEB-INF/classes as
MyUI$Servlet.class. Should this combination still be supported by pax-web,
or is this the point where my experiments to simply deploy the war in Karaf
have to come to an end, and we have to go for a full OSGi integration of our
Vaadin-based Web UI?
Best Regards,
Jochen
--
View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036363.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: pax-web: war stays in deploying state
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Jochen
yep these imports are evil as hell.
and
though shall not import
WEB-INF/lib/javax.servlet-3.0.0.v201112011016.jar
in a web application bundle, neither for a standard web container nor for a
OSGi one, where it actually will hit you hard in the face :D
and those jetty libs aren't any good either.
If you really want to keep those in the war (where the Jetty Server jars
shouldn't be in either) make sure you don't put them in the classpath.
regards, Achim
2014-11-12 8:27 GMT+01:00 jochenw <jo...@googlemail.com>:
> Hi Achim,
>
> thanks for the reply!
>
> web:stop and web:start on the bundle changes the Web-State - from Deploying
> to Waiting. The debug-output says:
>
> 2014-11-12 06:52:03,199 | DEBUG | l for user karaf | WebEventDispatcher
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Sending web event
> WebEvent [replay=false, type=WAITING, bundle=testwar [145],
> extenderBundle=org.ops4j.pax.web.pax-web-extender-war [133], cause=null,
> timestamp=1415775123199, contextPath=/testwar, collisionIds=[145, 145],
> httpService=null, httpContext=null] for bundle testwar
> 2014-11-12 06:52:03,199 | DEBUG | EventExecutor: 1 | pax-web-extender-war
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 |
> org/osgi/service/web/FAILED
> 2014-11-12 06:52:03,199 | DEBUG | l for user karaf |
> LoggingCommandSessionListener | 25 - org.apache.karaf.shell.console -
> 3.0.2 | Command: 'web:start 145' returned 'null'
>
> Apart from Vaadin and some Vaadin plugins, we use Eclipselink for JPA with
> access to a PostgreSQL DB, Shiro for authentication/authorization.
>
> I just saw that in WEB-INF/lib, we have included some jars which are
> required for UI unit testing (jetty, selenium, phantomjs driver, Vaadin
> testbench), and interestingly there are also some Equinox osgi jars. Could
> the latter cause some problems, since all the jars are included in the
> bundle class path on installation of the plain (non-OSGi) war?
>
> These jars are most probably there, since we currently re-use some of our
> OSGi-backend functionality as non-OSGi libs for the UI, and the mvn
> dependency resolution then adds those jars to the lib folder. If those
> things cause the problem, we might need to clean up first. But there is no
> clear hint in the debug output.
>
> Our final goal is to OSGi-ify the UI, and then it will of course no longer
> internalize such OSGi libs, but properly import the needed packages. As a
> first step, I just want to have the war running in the OSGi container
> as-is.
> Maybe this approach is bit too simple.
>
> Best Regards,
>
> Jochen
>
> P.S.: here the output of "headers 145":
>
> Bundle-Name = testwar
> Bundle-SymbolicName = testwar
> Bundle-Version = 0
> Bundle-ManifestVersion = 2
> Bundle-ClassPath =
>
> WEB-INF/classes,WEB-INF/lib/activemq-all-5.9.0.jar,WEB-INF/lib/animator-1.7.3.jar,WEB-INF/lib/atmosphere-runtime-2.1.2.vaadin6.jar,WEB-INF/lib/authorizationbundle-1.0.0.1.jar,WEB-INF/lib/bcpkix-jdk15on-1.48.jar,WEB-INF/lib/bcprov-jdk15on-1.48.jar,WEB-INF/lib/cglib-nodep-2.1_3.jar,WEB-INF/lib/commonj.sdo-2.1.1.jar,WEB-INF/lib/commons-beanutils-1.8.3.jar,WEB-INF/lib/commons-codec-1.8.jar,WEB-INF/lib/commons-collections-3.2.1.jar,WEB-INF/lib/commons-exec-1.1.jar,WEB-INF/lib/commons-io-2.4.jar,WEB-INF/lib/commons-lang3-3.1.jar,WEB-INF/lib/commons-logging-1.1.3.jar,WEB-INF/lib/cssparser-0.9.11.jar,WEB-INF/lib/dbbundle-1.0.0.1.jar,WEB-INF/lib/easymock-3.1.jar,WEB-INF/lib/eclipselink-2.5.1.jar,WEB-INF/lib/flute-1.3.0.gg2.jar,WEB-INF/lib/framebundle-1.0.0.1.jar,WEB-INF/lib/g-leaflet-0.4.6.jar,WEB-INF/lib/g-leaflet-draw-0.4.6.jar,WEB-INF/lib/g-leaflet-markercluster-0.4.5.jar,WEB-INF/lib/gson-2.2.jar,WEB-INF/lib/guava-15.0.jar,WEB-INF/lib/guava-16.0.1.vaadin1.jar,WEB-INF/lib/h2-1.3.174.jar,WEB-INF/lib/htmlunit-2.15.jar,WEB-INF/lib/htmlunit-core-js-2.15.jar,WEB-INF/lib/httpclient-4.3.1.jar,WEB-INF/lib/httpcore-4.3.jar,WEB-INF/lib/httpmime-4.3.1.jar,WEB-INF/lib/jackson-annotations-2.3.0.jar,WEB-INF/lib/jackson-core-2.3.2.jar,WEB-INF/lib/jackson-databind-2.3.2.jar,WEB-INF/lib/javassist-3.18.1-GA.jar,WEB-INF/lib/javax.persistence-2.1.0.jar,WEB-INF/lib/javax.servlet-3.0.0.v201112011016.jar,WEB-INF/lib/javax.servlet.jsp-2.2.0.v201112011158.jar,WEB-INF/lib/jcip-annotations-1.0.jar,WEB-INF/lib/jetty-http-8.1.12.v20130726.jar,WEB-INF/lib/jetty-io-8.1.12.v20130726.jar,WEB-INF/lib/jetty-rc-repacked-5.jar,WEB-INF/lib/jetty-repacked-7.6.1.jar,WEB-INF/lib/jetty-util-8.1.12.v20130726.jar,WEB-INF/lib/jetty-websocket-8.1.15.v20140411.jar,WEB-INF/lib/jna-3.4.0.jar,WEB-INF/lib/json-0.0.20080701.jar,WEB-INF/lib/json-20080701.jar,WEB-INF/lib/jsoup-1.6.3.jar,WEB-INF/lib/jts-1.13.jar,WEB-INF/lib/libbundle-1.0.0.1.jar,WEB-INF/lib/log4j-1.2.17.jar,WEB-INF/lib/messagesbundle-1.0.0.1.jar,WEB-INF/lib/mx4j-tools-3.0.1.jar,WEB-INF/lib/nekohtml-1.9.19.jar,WEB-INF/lib/netty-3.5.5.Final.jar,WEB-INF/lib/objenesis-1.2.jar,WEB-INF/lib/org.apache.felix.dependencymanager-3.2.0.jar,WEB-INF/lib/org.eclipse.osgi-3.7.1.jar,WEB-INF/lib/org.eclipse.persistence.antlr-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.asm-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.core-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa.jpql-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa.modelgen.processor-2.5.1.jar,WEB-INF/lib/org.osgi.compendium-4.3.0.jar,WEB-INF/lib/org.osgi.core-4.2.0.jar,WEB-INF/lib/osgi-3.1.1.jar,WEB-INF/lib/phantomjsdriver-1.2.0.jar,WEB-INF/lib/platform-3.4.0.jar,WEB-INF/lib/postgresql-9.3-1100-jdbc41.jar,WEB-INF/lib/refresher-1.2.3.7.jar,WEB-INF/lib/sac-1.3.jar,WEB-INF/lib/selenium-api-2.43.1.jar,WEB-INF/lib/selenium-chrome-driver-2.43.1.jar,WEB-INF/lib/selenium-firefox-driver-2.43.1.jar,WEB-INF/lib/selenium-htmlunit-driver-2.43.1.jar,WEB-INF/lib/selenium-ie-driver-2.43.1.jar,WEB-INF/lib/selenium-java-2.43.1.jar,WEB-INF/lib/selenium-remote-driver-2.43.1.jar,WEB-INF/lib/selenium-safari-driver-2.43.1.jar,WEB-INF/lib/selenium-server-2.43.1.jar,WEB-INF/lib/selenium-support-2.43.1.jar,WEB-INF/lib/serializer-2.7.1.jar,WEB-INF/lib/servlet-api-2.5-6.1.9.jar,WEB-INF/lib/shiro-core-1.2.3.jar,WEB-INF/lib/sizereporter-0.1.1.jar,WEB-INF/lib/slf4j-api-1.6.4.jar,WEB-INF/lib/slf4j-simple-1.7.2.jar,WEB-INF/lib/snakeyaml-1.8.jar,WEB-INF/lib/streamhtmlparser-jsilver-0.0.10.vaadin1.jar,WEB-INF/lib/v-leaflet-0.5.6.jar,WEB-INF/lib/v-leaflet-markercluster-0.4.5.jar,WEB-INF/lib/vaadin-charts-1.1.7.jar,WEB-INF/lib/vaadin-client-compiled-7.3.3.jar,WEB-INF/lib/vaadin-push-7.3.3.jar,WEB-INF/lib/vaadin-sass-compiler-0.9.10.jar,WEB-INF/lib/vaadin-server-7.3.3.jar,WEB-INF/lib/vaadin-shared-7.3.3.jar,WEB-INF/lib/vaadin-slf4j-jdk14-1.6.1.jar,WEB-INF/lib/vaadin-testbench-4.0.0.rc2.jar,WEB-INF/lib/vaadin-testbench-api-7.3.0.rc2.jar,WEB-INF/lib/vaadin-testbench-core-4.0.0.rc2.jar,WEB-INF/lib/vaadin-themes-7.3.3.jar,WEB-INF/lib/validation-api-1.0.0.GA-sources.jar,WEB-INF/lib/validation-api-1.0.0.GA.jar,WEB-INF/lib/webbit-0.4.15.jar,WEB-INF/lib/xalan-2.7.1.jar,WEB-INF/lib/xercesImpl-2.11.0.jar,WEB-INF/lib/xml-apis-1.4.01.jar
>
> Import-Package =
> javax.activation;resolution:=optional,
> javax.annotation.processing;resolution:=optional,
> javax.crypto;resolution:=optional,
> javax.crypto.interfaces;resolution:=optional,
> javax.crypto.spec;resolution:=optional,
> javax.ejb;resolution:=optional,
> javax.el;resolution:=optional,
> javax.enterprise.context.spi;resolution:=optional,
> javax.enterprise.inject.spi;resolution:=optional,
> javax.imageio;resolution:=optional,
> javax.imageio.stream;resolution:=optional,
> javax.inject;resolution:=optional,
> javax.jmdns;resolution:=optional,
> javax.lang.model;resolution:=optional,
> javax.lang.model.element;resolution:=optional,
> javax.lang.model.type;resolution:=optional,
> javax.lang.model.util;resolution:=optional,
> javax.mail;resolution:=optional,
> javax.mail.internet;resolution:=optional,
> javax.management;resolution:=optional,
> javax.management.loading;resolution:=optional,
> javax.management.modelmbean;resolution:=optional,
> javax.management.monitor;resolution:=optional,
> javax.management.openmbean;resolution:=optional,
> javax.management.relation;resolution:=optional,
> javax.management.remote;resolution:=optional,
> javax.management.timer;resolution:=optional,
> javax.microedition.io;resolution:=optional,
> javax.naming;resolution:=optional,
> javax.naming.directory;resolution:=optional,
> javax.naming.event;resolution:=optional,
> javax.naming.ldap;resolution:=optional,
> javax.naming.spi;resolution:=optional,
> javax.net;resolution:=optional,
> javax.net.ssl;resolution:=optional,
> javax.portlet;resolution:=optional,
> javax.portlet.filter;resolution:=optional,
> javax.resource;resolution:=optional,
> javax.resource.cci;resolution:=optional,
> javax.rmi;resolution:=optional,
> javax.rmi.CORBA;resolution:=optional,
> javax.security.auth;resolution:=optional,
> javax.security.auth.callback;resolution:=optional,
> javax.security.auth.login;resolution:=optional,
> javax.security.auth.x500;resolution:=optional,
> javax.security.cert;resolution:=optional,
> javax.sql;resolution:=optional,
> javax.swing;resolution:=optional,
> javax.swing.border;resolution:=optional,
> javax.swing.event;resolution:=optional,
> javax.swing.filechooser;resolution:=optional,
> javax.swing.table;resolution:=optional,
> javax.swing.text;resolution:=optional,
> javax.swing.text.html;resolution:=optional,
> javax.swing.tree;resolution:=optional,
> javax.tools;resolution:=optional,
> javax.websocket;resolution:=optional,
> javax.websocket.server;resolution:=optional,
> javax.ws.rs;resolution:=optional,
> javax.ws.rs.core;resolution:=optional,
> javax.ws.rs.ext;resolution:=optional,
> javax.xml.bind;resolution:=optional,
> javax.xml.bind.annotation;resolution:=optional,
> javax.xml.bind.annotation.adapters;resolution:=optional,
> javax.xml.bind.attachment;resolution:=optional,
> javax.xml.bind.helpers;resolution:=optional,
> javax.xml.rpc;resolution:=optional,
> javax.xml.soap;resolution:=optional,
> javax.xml.ws;resolution:=optional,
> javax.xml.ws.handler;resolution:=optional,
> javax.xml.ws.soap;resolution:=optional,
> org.slf4j.spi;resolution:=optional;provider=paxlogging,
> org.apache.log4j.xml;resolution:=optional;provider=paxlogging,
> javax.servlet.jsp;resolution:=optional,
> javax.servlet.jsp.el;resolution:=optional,
> org.slf4j.helpers;resolution:=optional;provider=paxlogging,
> javax.servlet,
>
> org.apache.commons.logging.impl;resolution:=optional;provider=paxlogging,
> org.slf4j;resolution:=optional;provider=paxlogging,
> org.apache.log4j;resolution:=optional;provider=paxlogging,
>
> org.apache.commons.logging;resolution:=optional;provider=paxlogging,
> org.apache.log4j.spi;resolution:=optional;provider=paxlogging,
> javax.servlet.http
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036359.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: pax-web: war stays in deploying state
Posted by jochenw <jo...@googlemail.com>.
Hi Achim,
thanks for the reply!
web:stop and web:start on the bundle changes the Web-State - from Deploying
to Waiting. The debug-output says:
2014-11-12 06:52:03,199 | DEBUG | l for user karaf | WebEventDispatcher
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Sending web event
WebEvent [replay=false, type=WAITING, bundle=testwar [145],
extenderBundle=org.ops4j.pax.web.pax-web-extender-war [133], cause=null,
timestamp=1415775123199, contextPath=/testwar, collisionIds=[145, 145],
httpService=null, httpContext=null] for bundle testwar
2014-11-12 06:52:03,199 | DEBUG | EventExecutor: 1 | pax-web-extender-war
| 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 |
org/osgi/service/web/FAILED
2014-11-12 06:52:03,199 | DEBUG | l for user karaf |
LoggingCommandSessionListener | 25 - org.apache.karaf.shell.console -
3.0.2 | Command: 'web:start 145' returned 'null'
Apart from Vaadin and some Vaadin plugins, we use Eclipselink for JPA with
access to a PostgreSQL DB, Shiro for authentication/authorization.
I just saw that in WEB-INF/lib, we have included some jars which are
required for UI unit testing (jetty, selenium, phantomjs driver, Vaadin
testbench), and interestingly there are also some Equinox osgi jars. Could
the latter cause some problems, since all the jars are included in the
bundle class path on installation of the plain (non-OSGi) war?
These jars are most probably there, since we currently re-use some of our
OSGi-backend functionality as non-OSGi libs for the UI, and the mvn
dependency resolution then adds those jars to the lib folder. If those
things cause the problem, we might need to clean up first. But there is no
clear hint in the debug output.
Our final goal is to OSGi-ify the UI, and then it will of course no longer
internalize such OSGi libs, but properly import the needed packages. As a
first step, I just want to have the war running in the OSGi container as-is.
Maybe this approach is bit too simple.
Best Regards,
Jochen
P.S.: here the output of "headers 145":
Bundle-Name = testwar
Bundle-SymbolicName = testwar
Bundle-Version = 0
Bundle-ManifestVersion = 2
Bundle-ClassPath =
WEB-INF/classes,WEB-INF/lib/activemq-all-5.9.0.jar,WEB-INF/lib/animator-1.7.3.jar,WEB-INF/lib/atmosphere-runtime-2.1.2.vaadin6.jar,WEB-INF/lib/authorizationbundle-1.0.0.1.jar,WEB-INF/lib/bcpkix-jdk15on-1.48.jar,WEB-INF/lib/bcprov-jdk15on-1.48.jar,WEB-INF/lib/cglib-nodep-2.1_3.jar,WEB-INF/lib/commonj.sdo-2.1.1.jar,WEB-INF/lib/commons-beanutils-1.8.3.jar,WEB-INF/lib/commons-codec-1.8.jar,WEB-INF/lib/commons-collections-3.2.1.jar,WEB-INF/lib/commons-exec-1.1.jar,WEB-INF/lib/commons-io-2.4.jar,WEB-INF/lib/commons-lang3-3.1.jar,WEB-INF/lib/commons-logging-1.1.3.jar,WEB-INF/lib/cssparser-0.9.11.jar,WEB-INF/lib/dbbundle-1.0.0.1.jar,WEB-INF/lib/easymock-3.1.jar,WEB-INF/lib/eclipselink-2.5.1.jar,WEB-INF/lib/flute-1.3.0.gg2.jar,WEB-INF/lib/framebundle-1.0.0.1.jar,WEB-INF/lib/g-leaflet-0.4.6.jar,WEB-INF/lib/g-leaflet-draw-0.4.6.jar,WEB-INF/lib/g-leaflet-markercluster-0.4.5.jar,WEB-INF/lib/gson-2.2.jar,WEB-INF/lib/guava-15.0.jar,WEB-INF/lib/guava-16.0.1.vaadin1.jar,WEB-INF/lib/h2-1.3.174.jar,WEB-INF/lib/htmlunit-2.15.jar,WEB-INF/lib/htmlunit-core-js-2.15.jar,WEB-INF/lib/httpclient-4.3.1.jar,WEB-INF/lib/httpcore-4.3.jar,WEB-INF/lib/httpmime-4.3.1.jar,WEB-INF/lib/jackson-annotations-2.3.0.jar,WEB-INF/lib/jackson-core-2.3.2.jar,WEB-INF/lib/jackson-databind-2.3.2.jar,WEB-INF/lib/javassist-3.18.1-GA.jar,WEB-INF/lib/javax.persistence-2.1.0.jar,WEB-INF/lib/javax.servlet-3.0.0.v201112011016.jar,WEB-INF/lib/javax.servlet.jsp-2.2.0.v201112011158.jar,WEB-INF/lib/jcip-annotations-1.0.jar,WEB-INF/lib/jetty-http-8.1.12.v20130726.jar,WEB-INF/lib/jetty-io-8.1.12.v20130726.jar,WEB-INF/lib/jetty-rc-repacked-5.jar,WEB-INF/lib/jetty-repacked-7.6.1.jar,WEB-INF/lib/jetty-util-8.1.12.v20130726.jar,WEB-INF/lib/jetty-websocket-8.1.15.v20140411.jar,WEB-INF/lib/jna-3.4.0.jar,WEB-INF/lib/json-0.0.20080701.jar,WEB-INF/lib/json-20080701.jar,WEB-INF/lib/jsoup-1.6.3.jar,WEB-INF/lib/jts-1.13.jar,WEB-INF/lib/libbundle-1.0.0.1.jar,WEB-INF/lib/log4j-1.2.17.jar,WEB-INF/lib/messagesbundle-1.0.0.1.jar,WEB-INF/lib/mx4j-tools-3.0.1.jar,WEB-INF/lib/nekohtml-1.9.19.jar,WEB-INF/lib/netty-3.5.5.Final.jar,WEB-INF/lib/objenesis-1.2.jar,WEB-INF/lib/org.apache.felix.dependencymanager-3.2.0.jar,WEB-INF/lib/org.eclipse.osgi-3.7.1.jar,WEB-INF/lib/org.eclipse.persistence.antlr-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.asm-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.core-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa.jpql-2.5.1.jar,WEB-INF/lib/org.eclipse.persistence.jpa.modelgen.processor-2.5.1.jar,WEB-INF/lib/org.osgi.compendium-4.3.0.jar,WEB-INF/lib/org.osgi.core-4.2.0.jar,WEB-INF/lib/osgi-3.1.1.jar,WEB-INF/lib/phantomjsdriver-1.2.0.jar,WEB-INF/lib/platform-3.4.0.jar,WEB-INF/lib/postgresql-9.3-1100-jdbc41.jar,WEB-INF/lib/refresher-1.2.3.7.jar,WEB-INF/lib/sac-1.3.jar,WEB-INF/lib/selenium-api-2.43.1.jar,WEB-INF/lib/selenium-chrome-driver-2.43.1.jar,WEB-INF/lib/selenium-firefox-driver-2.43.1.jar,WEB-INF/lib/selenium-htmlunit-driver-2.43.1.jar,WEB-INF/lib/selenium-ie-driver-2.43.1.jar,WEB-INF/lib/selenium-java-2.43.1.jar,WEB-INF/lib/selenium-remote-driver-2.43.1.jar,WEB-INF/lib/selenium-safari-driver-2.43.1.jar,WEB-INF/lib/selenium-server-2.43.1.jar,WEB-INF/lib/selenium-support-2.43.1.jar,WEB-INF/lib/serializer-2.7.1.jar,WEB-INF/lib/servlet-api-2.5-6.1.9.jar,WEB-INF/lib/shiro-core-1.2.3.jar,WEB-INF/lib/sizereporter-0.1.1.jar,WEB-INF/lib/slf4j-api-1.6.4.jar,WEB-INF/lib/slf4j-simple-1.7.2.jar,WEB-INF/lib/snakeyaml-1.8.jar,WEB-INF/lib/streamhtmlparser-jsilver-0.0.10.vaadin1.jar,WEB-INF/lib/v-leaflet-0.5.6.jar,WEB-INF/lib/v-leaflet-markercluster-0.4.5.jar,WEB-INF/lib/vaadin-charts-1.1.7.jar,WEB-INF/lib/vaadin-client-compiled-7.3.3.jar,WEB-INF/lib/vaadin-push-7.3.3.jar,WEB-INF/lib/vaadin-sass-compiler-0.9.10.jar,WEB-INF/lib/vaadin-server-7.3.3.jar,WEB-INF/lib/vaadin-shared-7.3.3.jar,WEB-INF/lib/vaadin-slf4j-jdk14-1.6.1.jar,WEB-INF/lib/vaadin-testbench-4.0.0.rc2.jar,WEB-INF/lib/vaadin-testbench-api-7.3.0.rc2.jar,WEB-INF/lib/vaadin-testbench-core-4.0.0.rc2.jar,WEB-INF/lib/vaadin-themes-7.3.3.jar,WEB-INF/lib/validation-api-1.0.0.GA-sources.jar,WEB-INF/lib/validation-api-1.0.0.GA.jar,WEB-INF/lib/webbit-0.4.15.jar,WEB-INF/lib/xalan-2.7.1.jar,WEB-INF/lib/xercesImpl-2.11.0.jar,WEB-INF/lib/xml-apis-1.4.01.jar
Import-Package =
javax.activation;resolution:=optional,
javax.annotation.processing;resolution:=optional,
javax.crypto;resolution:=optional,
javax.crypto.interfaces;resolution:=optional,
javax.crypto.spec;resolution:=optional,
javax.ejb;resolution:=optional,
javax.el;resolution:=optional,
javax.enterprise.context.spi;resolution:=optional,
javax.enterprise.inject.spi;resolution:=optional,
javax.imageio;resolution:=optional,
javax.imageio.stream;resolution:=optional,
javax.inject;resolution:=optional,
javax.jmdns;resolution:=optional,
javax.lang.model;resolution:=optional,
javax.lang.model.element;resolution:=optional,
javax.lang.model.type;resolution:=optional,
javax.lang.model.util;resolution:=optional,
javax.mail;resolution:=optional,
javax.mail.internet;resolution:=optional,
javax.management;resolution:=optional,
javax.management.loading;resolution:=optional,
javax.management.modelmbean;resolution:=optional,
javax.management.monitor;resolution:=optional,
javax.management.openmbean;resolution:=optional,
javax.management.relation;resolution:=optional,
javax.management.remote;resolution:=optional,
javax.management.timer;resolution:=optional,
javax.microedition.io;resolution:=optional,
javax.naming;resolution:=optional,
javax.naming.directory;resolution:=optional,
javax.naming.event;resolution:=optional,
javax.naming.ldap;resolution:=optional,
javax.naming.spi;resolution:=optional,
javax.net;resolution:=optional,
javax.net.ssl;resolution:=optional,
javax.portlet;resolution:=optional,
javax.portlet.filter;resolution:=optional,
javax.resource;resolution:=optional,
javax.resource.cci;resolution:=optional,
javax.rmi;resolution:=optional,
javax.rmi.CORBA;resolution:=optional,
javax.security.auth;resolution:=optional,
javax.security.auth.callback;resolution:=optional,
javax.security.auth.login;resolution:=optional,
javax.security.auth.x500;resolution:=optional,
javax.security.cert;resolution:=optional,
javax.sql;resolution:=optional,
javax.swing;resolution:=optional,
javax.swing.border;resolution:=optional,
javax.swing.event;resolution:=optional,
javax.swing.filechooser;resolution:=optional,
javax.swing.table;resolution:=optional,
javax.swing.text;resolution:=optional,
javax.swing.text.html;resolution:=optional,
javax.swing.tree;resolution:=optional,
javax.tools;resolution:=optional,
javax.websocket;resolution:=optional,
javax.websocket.server;resolution:=optional,
javax.ws.rs;resolution:=optional,
javax.ws.rs.core;resolution:=optional,
javax.ws.rs.ext;resolution:=optional,
javax.xml.bind;resolution:=optional,
javax.xml.bind.annotation;resolution:=optional,
javax.xml.bind.annotation.adapters;resolution:=optional,
javax.xml.bind.attachment;resolution:=optional,
javax.xml.bind.helpers;resolution:=optional,
javax.xml.rpc;resolution:=optional,
javax.xml.soap;resolution:=optional,
javax.xml.ws;resolution:=optional,
javax.xml.ws.handler;resolution:=optional,
javax.xml.ws.soap;resolution:=optional,
org.slf4j.spi;resolution:=optional;provider=paxlogging,
org.apache.log4j.xml;resolution:=optional;provider=paxlogging,
javax.servlet.jsp;resolution:=optional,
javax.servlet.jsp.el;resolution:=optional,
org.slf4j.helpers;resolution:=optional;provider=paxlogging,
javax.servlet,
org.apache.commons.logging.impl;resolution:=optional;provider=paxlogging,
org.slf4j;resolution:=optional;provider=paxlogging,
org.apache.log4j;resolution:=optional;provider=paxlogging,
org.apache.commons.logging;resolution:=optional;provider=paxlogging,
org.apache.log4j.spi;resolution:=optional;provider=paxlogging,
javax.servlet.http
--
View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036359.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: pax-web: war stays in deploying state
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
try a web:stop and web:start on that bundle ID.
Maybe that works.
Besides using Vaadin anything else special about the war?
regards, Achim
2014-11-07 16:22 GMT+01:00 jochenw <jo...@googlemail.com>:
> Dear all,
>
> I'm trying to deploy a normal .war with "bundle:install -s
> webbundle:....war?Bundle-SymbolicName=testwar&Web-ContextPath=/testwar".
> The
> war contains a Vaadin-based Web application, and it runs on a standalone
> jetty or tomcat without problems.
>
> When deploying in Karaf (war feature installed), the command mentioned
> above
> returns without an error, and the bundle is shown as active. However,
> web:list continues showing the Web-State as "Deploying", and http:list
> shows
> no servlet. Of course, trying to access the Web UI fails.
>
> Any idea what I'm doing wrong? Below you can see the relevant lines from
> the
> log.
>
> Best Regards,
> Jochen
>
> 2014-11-07 15:05:28,022 | DEBUG | h for user karaf | testwar
> | 145 - testwar - 0.0.0 | BundleEvent INSTALLED - testwar
> 2014-11-07 15:05:28,022 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting
> BlueprintContainer
> destruction process for bundle testwar
> 2014-11-07 15:05:28,022 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for testwar.
> 2014-11-07 15:05:28,028 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting
> BlueprintContainer
> destruction process for bundle testwar
> 2014-11-07 15:05:28,028 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for testwar.
> 2014-11-07 15:05:28,028 | DEBUG | h for user karaf | Activator
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Starting
> destruction process for bundle testwar
> 2014-11-07 15:05:28,028 | DEBUG | h for user karaf | Activator
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Not an extended
> bundle or destruction of extension already finished for testwar.
> 2014-11-07 15:05:28,829 | DEBUG | h for user karaf | testwar
> | 145 - testwar - 0.0.0 | BundleEvent RESOLVED - testwar
> 2014-11-07 15:05:28,829 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Starting
> BlueprintContainer
> destruction process for bundle testwar
> 2014-11-07 15:05:28,829 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for testwar.
> 2014-11-07 15:05:28,832 | DEBUG | h for user karaf | testwar
> | 145 - testwar - 0.0.0 | BundleEvent STARTING - testwar
> 2014-11-07 15:05:28,832 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | Scanning bundle testwar
> for
> blueprint application
> 2014-11-07 15:05:28,834 | DEBUG | h for user karaf | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.1 | No blueprint application
> found in bundle testwar
> 2014-11-07 15:05:28,885 | DEBUG | h for user karaf | WebEventDispatcher
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Sending web event
> WebEvent [replay=false, type=DEPLOYING, bundle=testwar [145],
> extenderBundle=org.ops4j.pax.web.pax-web-extender-war [133], cause=null,
> timestamp=1415372728885, contextPath=/testwar, collisionIds=null,
> httpService=null, httpContext=null] for bundle testwar
> 2014-11-07 15:05:28,894 | DEBUG | EventExecutor: 1 | pax-web-extender-war
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 |
> org/osgi/service/web/DEPLOYING
> 2014-11-07 15:05:28,894 | DEBUG | h for user karaf | WebAppParser
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | version found in
> web.xml - 3.0
> 2014-11-07 15:05:28,894 | DEBUG | h for user karaf | WebAppParser
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | metadata-complete
> is: false
> 2014-11-07 15:05:28,895 | DEBUG | h for user karaf | WebAppParser
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | scanning for
> ServletContainerInitializers
> 2014-11-07 15:05:28,897 | DEBUG | h for user karaf | WebAppParser
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | found container
> initializers by SafeServiceLoader ... skip the old impl.
> 2014-11-07 15:05:29,615 | DEBUG | h for user karaf | Activator
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Scheduling start
> of
> extension for bundle testwar asynchronously
> 2014-11-07 15:05:29,622 | DEBUG | h for user karaf | testwar
> | 145 - testwar - 0.0.0 | BundleEvent STARTED - testwar
> 2014-11-07 15:05:29,622 | DEBUG | h for user karaf | ChannelSession
> | 28 - org.apache.sshd.core - 0.12.0 | Send SSH_MSG_CHANNEL_DATA on channel
> 0
> 2014-11-07 15:05:29,622 | DEBUG | pool-7-thread-1 | WebAppPublisher
> | 133 - org.ops4j.pax.web.pax-web-extender-war - 3.1.2 | Publishing web
> application
> [WebApp{displayName=testwar,contextName=testwar,m_httpContext=null}]
> 2014-11-07 15:05:29,622 | DEBUG | h for user karaf | Nio2Session
> | 28 - org.apache.sshd.core - 0.12.0 | Writing 68 bytes
> 2014-11-07 15:05:29,624 | DEBUG | h for user karaf | ChannelSession
> | 28 - org.apache.sshd.core - 0.12.0 | Send SSH_MSG_CHANNEL_DATA on channel
> 0
> 2014-11-07 15:05:29,624 | DEBUG | 5]-nio2-thread-1 | Nio2Session
> | 28 - org.apache.sshd.core - 0.12.0 | Finished writing
> 2014-11-07 15:05:29,624 | DEBUG | h for user karaf | Nio2Session
> | 28 - org.apache.sshd.core - 0.12.0 | Writing 52 bytes
> 2014-11-07 15:05:29,624 | DEBUG | 5]-nio2-thread-2 | Nio2Session
> | 28 - org.apache.sshd.core - 0.12.0 | Finished writing
> 2014-11-07 15:05:29,625 | DEBUG | h for user karaf |
> LoggingCommandSessionListener | 25 - org.apache.karaf.shell.console -
> 3.0.2 | Command: 'bundle:install -s
>
> "webbundle:file:/opt/testwar-1.0.0.1.war?Bundle-SymbolicName=testwar&Web-ContextPath=/testwar"'
> returned 'null'
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master