You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Charles Moulliard <cm...@gmail.com> on 2011/04/22 11:02:41 UTC
Issue with config:admin and modification made in pax-web-jetty
Hi,
I have modified the project pax-web-jetty and pax-web-runtime
(1.1.0-SNAPSHOT) to add new variables to be able to configure NCSA Log
with Jetty (http://issues.ops4j.org/browse/PAXWEB-269)
My keys are well registered in config admin
Pid: org.ops4j.pax.web
BundleLocation: mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
Properties:
org.ops4j.pax.web.log.ncsa.format = yyyy_mm_dd.request.log
service.pid = org.ops4j.pax.web
org.ops4j.pax.web.log.ncsa.append = true
org.ops4j.pax.web.log.ncsa.extended = true
org.ops4j.pax.web.log.ncsa.timezone = GMT
org.ops4j.pax.web.log.ncsa.retaindays = 90
felix.fileinstall.filename =
file:/Users/charlesmoulliard/Applications/apache-karaf-2.2.0/etc/org.ops4j.pax.web.cfg
But when I try to deploy features:install webconsole which will use
pax-web-jetty to instantiate a new Jetty instance, I get this error
Error executing command: Could not start bundle
mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
[405].
10:45:27,004 | ERROR | g.ops4j.pax.web) | configadmin
| ? ? | 5 -
org.apache.felix.configadmin - 1.2.8 | Cannot use configuration
org.ops4j.pax.web for [org.osgi.service.cm.ManagedService, id=198,
bundle=405]: Configuration bound to bundle
mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
10:50:10,088 | INFO | l Console Thread | Console
| araf.shell.console.jline.Console 236 | 22 -
org.apache.karaf.shell.console - 2.2.0 | Exception caught while
executing command
java.lang.Exception: Could not start bundle
mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
[405].
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[23:org.apache.karaf.features.core:2.2.0]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[23:org.apache.karaf.features.core:2.2.0]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[23:org.apache.karaf.features.core:2.2.0]
at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[19:org.apache.karaf.features.command:2.2.0]
at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[19:org.apache.karaf.features.command:2.2.0]
at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:79)[22:org.apache.karaf.shell.console:2.2.0]
at org.apache.karaf.shell.console.jline.Console.run(Console.java:218)[22:org.apache.karaf.shell.console:2.2.0]
at java.lang.Thread.run(Thread.java:680)[:1.6.0_24]
Caused by: org.osgi.framework.BundleException: Activator start error
in bundle org.ops4j.pax.web.pax-web-runtime [405].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)[org.apache.felix.framework-3.0.8.jar:]
at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)[org.apache.felix.framework-3.0.8.jar:]
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)[org.apache.felix.framework-3.0.8.jar:]
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)[org.apache.felix.framework-3.0.8.jar:]
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:350)[23:org.apache.karaf.features.core:2.2.0]
... 15 more
Caused by: java.lang.AbstractMethodError
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:357)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:67)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:514)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:84)
at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:150)
at org.ops4j.pax.web.service.internal.Activator.createManagedService(Activator.java:172)
at org.ops4j.pax.web.service.internal.Activator.access$800(Activator.java:70)
at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:331)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)[karaf.jar:]
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)[karaf.jar:]
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)[karaf.jar:]
at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
... 19 more
In debug mode, I see that NCSA keys are not present in the object
org.ops4j.pax.web.service.internal.ConfigurationImpl.m_properties.
Question : Why when we install webconsole of karaf, pax-web-jetty does
not use org.ops4j.pax.web.cfg and config admin keys created ?
Help is welcome ?
Regards,
Charles Moulliard
Sr. Principal Solution Architect - FuseSource
Apache Committer
Blog : http://cmoulliard.blogspot.com
Twitter : http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard
Skype: cmoulliard
Re: Issue with config:admin and modification made in pax-web-jetty
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Charles,
basically as I described in http://issues.ops4j.org/browse/PAXWEB-269
I added an additional flag for disabling the specialized logger, it's
the default case.
right now on my windows machine I wasn't able to turn the logging on
since I did receive IOExceptions regarding the folder logs, looks
like the folder isn't created or is not allowed to be created. Will
check later today.
regards, Achim
2011/4/27 Charles Moulliard <cm...@gmail.com>:
> Great. Can you tell me which minor modification you have made ?
>
> Regards,
>
> Charles
>
> On Wed, Apr 27, 2011 at 12:23 AM, Achim Nierbeck
> <bc...@googlemail.com> wrote:
>> After applying the patch and doing some minor enhancements, I'm able to
>> start karaf with a disabled version of the ncsa logger
>> on my system ( it's running under windows ) it's not able to create a
>> log directory or a file.
>> I'll check in the changes on the 1.1.0-SNAPSHOT version of pax web since
>> the default behaviour does work now with a disabled
>> version of it :)
>>
>> Regards, Achim
>>
>>> Hi Charles,
>>>
>>> I can take a look at it later today.
>>>
>>> Regards, Achim
>>>
>>> 2011/4/22 Charles Moulliard <cm...@gmail.com>:
>>>> Hi,
>>>>
>>>> I have modified the project pax-web-jetty and pax-web-runtime
>>>> (1.1.0-SNAPSHOT) to add new variables to be able to configure NCSA Log
>>>> with Jetty (http://issues.ops4j.org/browse/PAXWEB-269)
>>>>
>>>> My keys are well registered in config admin
>>>>
>>>> Pid: org.ops4j.pax.web
>>>> BundleLocation: mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>>>> Properties:
>>>> org.ops4j.pax.web.log.ncsa.format = yyyy_mm_dd.request.log
>>>> service.pid = org.ops4j.pax.web
>>>> org.ops4j.pax.web.log.ncsa.append = true
>>>> org.ops4j.pax.web.log.ncsa.extended = true
>>>> org.ops4j.pax.web.log.ncsa.timezone = GMT
>>>> org.ops4j.pax.web.log.ncsa.retaindays = 90
>>>> felix.fileinstall.filename =
>>>> file:/Users/charlesmoulliard/Applications/apache-karaf-2.2.0/etc/org.ops4j.pax.web.cfg
>>>>
>>>>
>>>> But when I try to deploy features:install webconsole which will use
>>>> pax-web-jetty to instantiate a new Jetty instance, I get this error
>>>>
>>>> Error executing command: Could not start bundle
>>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>>>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>>>> [405].
>>>>
>>>> 10:45:27,004 | ERROR | g.ops4j.pax.web) | configadmin
>>>> | ? ? | 5 -
>>>> org.apache.felix.configadmin - 1.2.8 | Cannot use configuration
>>>> org.ops4j.pax.web for [org.osgi.service.cm.ManagedService, id=198,
>>>> bundle=405]: Configuration bound to bundle
>>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>>>> 10:50:10,088 | INFO | l Console Thread | Console
>>>> | araf.shell.console.jline.Console 236 | 22 -
>>>> org.apache.karaf.shell.console - 2.2.0 | Exception caught while
>>>> executing command
>>>> java.lang.Exception: Could not start bundle
>>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>>>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>>>> [405].
>>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[23:org.apache.karaf.features.core:2.2.0]
>>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[23:org.apache.karaf.features.core:2.2.0]
>>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[23:org.apache.karaf.features.core:2.2.0]
>>>> at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[19:org.apache.karaf.features.command:2.2.0]
>>>> at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[19:org.apache.karaf.features.command:2.2.0]
>>>> at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:79)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at org.apache.karaf.shell.console.jline.Console.run(Console.java:218)[22:org.apache.karaf.shell.console:2.2.0]
>>>> at java.lang.Thread.run(Thread.java:680)[:1.6.0_24]
>>>> Caused by: org.osgi.framework.BundleException: Activator start error
>>>> in bundle org.ops4j.pax.web.pax-web-runtime [405].
>>>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)[org.apache.felix.framework-3.0.8.jar:]
>>>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)[org.apache.felix.framework-3.0.8.jar:]
>>>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)[org.apache.felix.framework-3.0.8.jar:]
>>>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)[org.apache.felix.framework-3.0.8.jar:]
>>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:350)[23:org.apache.karaf.features.core:2.2.0]
>>>> ... 15 more
>>>> Caused by: java.lang.AbstractMethodError
>>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:357)
>>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:67)
>>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:514)
>>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:84)
>>>> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:150)
>>>> at org.ops4j.pax.web.service.internal.Activator.createManagedService(Activator.java:172)
>>>> at org.ops4j.pax.web.service.internal.Activator.access$800(Activator.java:70)
>>>> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:331)
>>>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
>>>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
>>>> at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)[karaf.jar:]
>>>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)[karaf.jar:]
>>>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)[karaf.jar:]
>>>> at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
>>>> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
>>>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
>>>> ... 19 more
>>>>
>>>> In debug mode, I see that NCSA keys are not present in the object
>>>> org.ops4j.pax.web.service.internal.ConfigurationImpl.m_properties.
>>>>
>>>> Question : Why when we install webconsole of karaf, pax-web-jetty does
>>>> not use org.ops4j.pax.web.cfg and config admin keys created ?
>>>>
>>>> Help is welcome ?
>>>>
>>>> Regards,
>>>>
>>>> Charles Moulliard
>>>>
>>>> Sr. Principal Solution Architect - FuseSource
>>>> Apache Committer
>>>>
>>>> Blog : http://cmoulliard.blogspot.com
>>>> Twitter : http://twitter.com/cmoulliard
>>>> Linkedin : http://www.linkedin.com/in/charlesmoulliard
>>>> Skype: cmoulliard
>>>>
>>
>>
>
--
--
*Achim Nierbeck*
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
Re: Issue with config:admin and modification made in pax-web-jetty
Posted by Charles Moulliard <cm...@gmail.com>.
Great. Can you tell me which minor modification you have made ?
Regards,
Charles
On Wed, Apr 27, 2011 at 12:23 AM, Achim Nierbeck
<bc...@googlemail.com> wrote:
> After applying the patch and doing some minor enhancements, I'm able to
> start karaf with a disabled version of the ncsa logger
> on my system ( it's running under windows ) it's not able to create a
> log directory or a file.
> I'll check in the changes on the 1.1.0-SNAPSHOT version of pax web since
> the default behaviour does work now with a disabled
> version of it :)
>
> Regards, Achim
>
>> Hi Charles,
>>
>> I can take a look at it later today.
>>
>> Regards, Achim
>>
>> 2011/4/22 Charles Moulliard <cm...@gmail.com>:
>>> Hi,
>>>
>>> I have modified the project pax-web-jetty and pax-web-runtime
>>> (1.1.0-SNAPSHOT) to add new variables to be able to configure NCSA Log
>>> with Jetty (http://issues.ops4j.org/browse/PAXWEB-269)
>>>
>>> My keys are well registered in config admin
>>>
>>> Pid: org.ops4j.pax.web
>>> BundleLocation: mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>>> Properties:
>>> org.ops4j.pax.web.log.ncsa.format = yyyy_mm_dd.request.log
>>> service.pid = org.ops4j.pax.web
>>> org.ops4j.pax.web.log.ncsa.append = true
>>> org.ops4j.pax.web.log.ncsa.extended = true
>>> org.ops4j.pax.web.log.ncsa.timezone = GMT
>>> org.ops4j.pax.web.log.ncsa.retaindays = 90
>>> felix.fileinstall.filename =
>>> file:/Users/charlesmoulliard/Applications/apache-karaf-2.2.0/etc/org.ops4j.pax.web.cfg
>>>
>>>
>>> But when I try to deploy features:install webconsole which will use
>>> pax-web-jetty to instantiate a new Jetty instance, I get this error
>>>
>>> Error executing command: Could not start bundle
>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>>> [405].
>>>
>>> 10:45:27,004 | ERROR | g.ops4j.pax.web) | configadmin
>>> | ? ? | 5 -
>>> org.apache.felix.configadmin - 1.2.8 | Cannot use configuration
>>> org.ops4j.pax.web for [org.osgi.service.cm.ManagedService, id=198,
>>> bundle=405]: Configuration bound to bundle
>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>>> 10:50:10,088 | INFO | l Console Thread | Console
>>> | araf.shell.console.jline.Console 236 | 22 -
>>> org.apache.karaf.shell.console - 2.2.0 | Exception caught while
>>> executing command
>>> java.lang.Exception: Could not start bundle
>>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>>> [405].
>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[23:org.apache.karaf.features.core:2.2.0]
>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[23:org.apache.karaf.features.core:2.2.0]
>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[23:org.apache.karaf.features.core:2.2.0]
>>> at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[19:org.apache.karaf.features.command:2.2.0]
>>> at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[19:org.apache.karaf.features.command:2.2.0]
>>> at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:79)[22:org.apache.karaf.shell.console:2.2.0]
>>> at org.apache.karaf.shell.console.jline.Console.run(Console.java:218)[22:org.apache.karaf.shell.console:2.2.0]
>>> at java.lang.Thread.run(Thread.java:680)[:1.6.0_24]
>>> Caused by: org.osgi.framework.BundleException: Activator start error
>>> in bundle org.ops4j.pax.web.pax-web-runtime [405].
>>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)[org.apache.felix.framework-3.0.8.jar:]
>>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)[org.apache.felix.framework-3.0.8.jar:]
>>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)[org.apache.felix.framework-3.0.8.jar:]
>>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)[org.apache.felix.framework-3.0.8.jar:]
>>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:350)[23:org.apache.karaf.features.core:2.2.0]
>>> ... 15 more
>>> Caused by: java.lang.AbstractMethodError
>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:357)
>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:67)
>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:514)
>>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:84)
>>> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:150)
>>> at org.ops4j.pax.web.service.internal.Activator.createManagedService(Activator.java:172)
>>> at org.ops4j.pax.web.service.internal.Activator.access$800(Activator.java:70)
>>> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:331)
>>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
>>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
>>> at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)[karaf.jar:]
>>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)[karaf.jar:]
>>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)[karaf.jar:]
>>> at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
>>> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
>>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
>>> ... 19 more
>>>
>>> In debug mode, I see that NCSA keys are not present in the object
>>> org.ops4j.pax.web.service.internal.ConfigurationImpl.m_properties.
>>>
>>> Question : Why when we install webconsole of karaf, pax-web-jetty does
>>> not use org.ops4j.pax.web.cfg and config admin keys created ?
>>>
>>> Help is welcome ?
>>>
>>> Regards,
>>>
>>> Charles Moulliard
>>>
>>> Sr. Principal Solution Architect - FuseSource
>>> Apache Committer
>>>
>>> Blog : http://cmoulliard.blogspot.com
>>> Twitter : http://twitter.com/cmoulliard
>>> Linkedin : http://www.linkedin.com/in/charlesmoulliard
>>> Skype: cmoulliard
>>>
>
>
Re: Issue with config:admin and modification made in pax-web-jetty
Posted by Achim Nierbeck <bc...@googlemail.com>.
After applying the patch and doing some minor enhancements, I'm able to
start karaf with a disabled version of the ncsa logger
on my system ( it's running under windows ) it's not able to create a
log directory or a file.
I'll check in the changes on the 1.1.0-SNAPSHOT version of pax web since
the default behaviour does work now with a disabled
version of it :)
Regards, Achim
> Hi Charles,
>
> I can take a look at it later today.
>
> Regards, Achim
>
> 2011/4/22 Charles Moulliard <cm...@gmail.com>:
>> Hi,
>>
>> I have modified the project pax-web-jetty and pax-web-runtime
>> (1.1.0-SNAPSHOT) to add new variables to be able to configure NCSA Log
>> with Jetty (http://issues.ops4j.org/browse/PAXWEB-269)
>>
>> My keys are well registered in config admin
>>
>> Pid: org.ops4j.pax.web
>> BundleLocation: mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>> Properties:
>> org.ops4j.pax.web.log.ncsa.format = yyyy_mm_dd.request.log
>> service.pid = org.ops4j.pax.web
>> org.ops4j.pax.web.log.ncsa.append = true
>> org.ops4j.pax.web.log.ncsa.extended = true
>> org.ops4j.pax.web.log.ncsa.timezone = GMT
>> org.ops4j.pax.web.log.ncsa.retaindays = 90
>> felix.fileinstall.filename =
>> file:/Users/charlesmoulliard/Applications/apache-karaf-2.2.0/etc/org.ops4j.pax.web.cfg
>>
>>
>> But when I try to deploy features:install webconsole which will use
>> pax-web-jetty to instantiate a new Jetty instance, I get this error
>>
>> Error executing command: Could not start bundle
>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>> [405].
>>
>> 10:45:27,004 | ERROR | g.ops4j.pax.web) | configadmin
>> | ? ? | 5 -
>> org.apache.felix.configadmin - 1.2.8 | Cannot use configuration
>> org.ops4j.pax.web for [org.osgi.service.cm.ManagedService, id=198,
>> bundle=405]: Configuration bound to bundle
>> mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
>> 10:50:10,088 | INFO | l Console Thread | Console
>> | araf.shell.console.jline.Console 236 | 22 -
>> org.apache.karaf.shell.console - 2.2.0 | Exception caught while
>> executing command
>> java.lang.Exception: Could not start bundle
>> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
>> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
>> [405].
>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[23:org.apache.karaf.features.core:2.2.0]
>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[23:org.apache.karaf.features.core:2.2.0]
>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[23:org.apache.karaf.features.core:2.2.0]
>> at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[19:org.apache.karaf.features.command:2.2.0]
>> at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[19:org.apache.karaf.features.command:2.2.0]
>> at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:79)[22:org.apache.karaf.shell.console:2.2.0]
>> at org.apache.karaf.shell.console.jline.Console.run(Console.java:218)[22:org.apache.karaf.shell.console:2.2.0]
>> at java.lang.Thread.run(Thread.java:680)[:1.6.0_24]
>> Caused by: org.osgi.framework.BundleException: Activator start error
>> in bundle org.ops4j.pax.web.pax-web-runtime [405].
>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)[org.apache.felix.framework-3.0.8.jar:]
>> at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)[org.apache.felix.framework-3.0.8.jar:]
>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)[org.apache.felix.framework-3.0.8.jar:]
>> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)[org.apache.felix.framework-3.0.8.jar:]
>> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:350)[23:org.apache.karaf.features.core:2.2.0]
>> ... 15 more
>> Caused by: java.lang.AbstractMethodError
>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:357)
>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:67)
>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:514)
>> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:84)
>> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:150)
>> at org.ops4j.pax.web.service.internal.Activator.createManagedService(Activator.java:172)
>> at org.ops4j.pax.web.service.internal.Activator.access$800(Activator.java:70)
>> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:331)
>> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
>> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
>> at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)[karaf.jar:]
>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)[karaf.jar:]
>> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)[karaf.jar:]
>> at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
>> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
>> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
>> ... 19 more
>>
>> In debug mode, I see that NCSA keys are not present in the object
>> org.ops4j.pax.web.service.internal.ConfigurationImpl.m_properties.
>>
>> Question : Why when we install webconsole of karaf, pax-web-jetty does
>> not use org.ops4j.pax.web.cfg and config admin keys created ?
>>
>> Help is welcome ?
>>
>> Regards,
>>
>> Charles Moulliard
>>
>> Sr. Principal Solution Architect - FuseSource
>> Apache Committer
>>
>> Blog : http://cmoulliard.blogspot.com
>> Twitter : http://twitter.com/cmoulliard
>> Linkedin : http://www.linkedin.com/in/charlesmoulliard
>> Skype: cmoulliard
>>
Re: Issue with config:admin and modification made in pax-web-jetty
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Charles,
I can take a look at it later today.
Regards, Achim
2011/4/22 Charles Moulliard <cm...@gmail.com>:
> Hi,
>
> I have modified the project pax-web-jetty and pax-web-runtime
> (1.1.0-SNAPSHOT) to add new variables to be able to configure NCSA Log
> with Jetty (http://issues.ops4j.org/browse/PAXWEB-269)
>
> My keys are well registered in config admin
>
> Pid: org.ops4j.pax.web
> BundleLocation: mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
> Properties:
> org.ops4j.pax.web.log.ncsa.format = yyyy_mm_dd.request.log
> service.pid = org.ops4j.pax.web
> org.ops4j.pax.web.log.ncsa.append = true
> org.ops4j.pax.web.log.ncsa.extended = true
> org.ops4j.pax.web.log.ncsa.timezone = GMT
> org.ops4j.pax.web.log.ncsa.retaindays = 90
> felix.fileinstall.filename =
> file:/Users/charlesmoulliard/Applications/apache-karaf-2.2.0/etc/org.ops4j.pax.web.cfg
>
>
> But when I try to deploy features:install webconsole which will use
> pax-web-jetty to instantiate a new Jetty instance, I get this error
>
> Error executing command: Could not start bundle
> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
> [405].
>
> 10:45:27,004 | ERROR | g.ops4j.pax.web) | configadmin
> | ? ? | 5 -
> org.apache.felix.configadmin - 1.2.8 | Cannot use configuration
> org.ops4j.pax.web for [org.osgi.service.cm.ManagedService, id=198,
> bundle=405]: Configuration bound to bundle
> mvn:org.ops4j.pax.web/pax-web-runtime/1.1.0-SNAPSHOT
> 10:50:10,088 | INFO | l Console Thread | Console
> | araf.shell.console.jline.Console 236 | 22 -
> org.apache.karaf.shell.console - 2.2.0 | Exception caught while
> executing command
> java.lang.Exception: Could not start bundle
> mvn:org.ops4j.pax.web/pax-web-runtime/1.0.1 in feature(s) http-2.2.0:
> Activator start error in bundle org.ops4j.pax.web.pax-web-runtime
> [405].
> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:353)[23:org.apache.karaf.features.core:2.2.0]
> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:280)[23:org.apache.karaf.features.core:2.2.0]
> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)[23:org.apache.karaf.features.core:2.2.0]
> at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[19:org.apache.karaf.features.command:2.2.0]
> at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[19:org.apache.karaf.features.command:2.2.0]
> at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:79)[22:org.apache.karaf.shell.console:2.2.0]
> at org.apache.karaf.shell.console.jline.Console.run(Console.java:218)[22:org.apache.karaf.shell.console:2.2.0]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_24]
> Caused by: org.osgi.framework.BundleException: Activator start error
> in bundle org.ops4j.pax.web.pax-web-runtime [405].
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)[org.apache.felix.framework-3.0.8.jar:]
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)[org.apache.felix.framework-3.0.8.jar:]
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)[org.apache.felix.framework-3.0.8.jar:]
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:909)[org.apache.felix.framework-3.0.8.jar:]
> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:350)[23:org.apache.karaf.features.core:2.2.0]
> ... 15 more
> Caused by: java.lang.AbstractMethodError
> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:357)
> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.start(ServerControllerImpl.java:67)
> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Unconfigured.configure(ServerControllerImpl.java:514)
> at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.configure(ServerControllerImpl.java:84)
> at org.ops4j.pax.web.service.internal.Activator$2.updated(Activator.java:150)
> at org.ops4j.pax.web.service.internal.Activator.createManagedService(Activator.java:172)
> at org.ops4j.pax.web.service.internal.Activator.access$800(Activator.java:70)
> at org.ops4j.pax.web.service.internal.Activator$DynamicsServiceTrackerCustomizer.addingService(Activator.java:331)
> at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
> at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
> at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:184)[karaf.jar:]
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:339)[karaf.jar:]
> at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:273)[karaf.jar:]
> at org.ops4j.pax.web.service.internal.Activator.start(Activator.java:95)
> at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835)
> ... 19 more
>
> In debug mode, I see that NCSA keys are not present in the object
> org.ops4j.pax.web.service.internal.ConfigurationImpl.m_properties.
>
> Question : Why when we install webconsole of karaf, pax-web-jetty does
> not use org.ops4j.pax.web.cfg and config admin keys created ?
>
> Help is welcome ?
>
> Regards,
>
> Charles Moulliard
>
> Sr. Principal Solution Architect - FuseSource
> Apache Committer
>
> Blog : http://cmoulliard.blogspot.com
> Twitter : http://twitter.com/cmoulliard
> Linkedin : http://www.linkedin.com/in/charlesmoulliard
> Skype: cmoulliard
>