Re: [paxweb] Update of Tomcat version

[Stephan Siano]

Hi Achim,

OK, thanks for your feedback. I have merged the pull request.

What needs to be done next? Is there a build job that runs a SNAPSHOT build 
somewhere (so I can push a pull request to Pax-Web that references these 
SNAPSHOTS)? I actually don't understand how any consumable version of this 
will get to Nexus. Who can release this (and how is this done)?

Best regards
Stephan

Am Donnerstag, 31. August 2017 07:48:37 UTC+2 schrieb Achim Nierbeck:
>
> Hi 
>
> looks good to me. 
>
> regards, Achim 
>
> 2017-08-30 12:01 GMT+02:00 Stephan Siano >
> :
>
>> Hi Achim,
>>
>> OK, I created PAXTIPI-47  and 
>> PAXWEB-1128  for the update. 
>> Would you be willing to have a look into the pull requests?
>>
>> Best regards
>> Stephan 
>>
>>
>> Am Dienstag, 29. August 2017 23:23:23 UTC+2 schrieb Achim Nierbeck:
>>>
>>> Hi Stephan, 
>>>
>>> Technically you are correct. Create the pax-tipi projects, a release is 
>>> needed at lease the moment we release the pax-web project referencing that 
>>> version. 
>>> So you could also reference some snapshot versions from pax-web. 
>>> Regarding Jira tasks, yes it's common to create a Jira task in the pax 
>>> tipi project (https://ops4j1.jira.com/projects/PAXTIPI/) and also a 
>>> Jira task in Pax Web. 
>>> If you like you can reference the pax tipi one in pax web. 
>>>
>>> regards, Achim 
>>>
>>>
>>> 2017-08-29 7:54 GMT+02:00 Stephan Siano :
>>>
 Hi Achim,

 No problem, I was also a but busy. I found out that SPDY support was 
 removed from tomcat 8 in the meantime, which makes the tomcat-embed-core 
 bundle easier to build.

 How does this work technically? I need to create two projects in 
 pax-tipi, release it and then create the changes in pax-web. The 
 documentation in pax-tipi seems a bit sparse. Do I create a JIRA task for 
 the Tomcat update under pax-web and also do the pax-tipi updates in there, 
 or do I need to create a different JIRA task for that somewhere?

 Best regards
 Stephan

 Am Samstag, 26. August 2017 08:10:23 UTC+2 schrieb Achim Nierbeck:
>
> Hi Stephan, 
>
> sorry for taking me so long, but my day job actually eats up a lot of 
> time right now. 
> A new tomcat version does require a new folder in the pax-tipi 
> project. 
> Actually the main project is just a "container" holding a bunch of 
> sub-projects. 
>
> regarding the juli logger, what ever works best and doesn't break Pax 
> Web from working. 
> I tried to move around that in the past, but it seemed to be better to 
> just include the juli logger inside the tomcat bundles. 
>
> regards, Achim 
>
> 2017-08-22 9:50 GMT+02:00 Stephan Siano :
>
>> Hi Achim,
>>
>> yes I was aware of the things done in pax-tipi. I will try this out 
>> and then create the required projects in there. As I understand a new 
>> tomcat version would require new folders in pax-tipi for the required 
>> bundles (next to the ones for version 8.0.14), is this correct?
>>
>> One more question: What about the org.apache.juli.logging stuff? 
>> pax-logging-api exports org.apache.juli.logging in version 5.5 and 6.0, 
>> (tipi) tomcat-embed-logging-juli exports org.apache.juli and 
>> org.apache.juli.logging in its own version. tomcat-embed-core and 
>> tomcat-embed-websocket import org.apache.juli.logging in their own 
>> version 
>> (currently 8.0.14), pax-web-jsp imports org.apache.juli.logging without 
>> version (which makes kind of sense, because if the web container is not 
>> tomcat, the tomcat-embed-logging-juli bundle will not be there).
>>
>> Do you have an idea how to straigthen that out? Maybe we can import 
>> org.apache.juli.logging without a version and rely for the pax-logging 
>> implementation (and not have a tomcat-embed-juli bundle in pax-tipi). 
>> The 
>> only class that seems to be used besides the things pax-logging emulates 
>> is 
>> org.apache.juli.ClassLoaderLogManager, which needs to be replaced 
>> somehow. 
>> Has anyone tried that already?
>>
>> Best regards
>> Stephan
>>
>> Am Montag, 21. August 2017 18:33:54 UTC+2 schrieb Achim Nierbeck:
>>>
>>> Hi, 
>>>
>>> the 6.0.x branch should stay with 8.0 version but a newer one if 
>>> available. 
>>> A minor version bump is fine with a 6.1.x (or master branch). 
>>>
>>> regards, Achim 
>>>
>>> P.S. btw. since Tomcat isn't OSGi ready we did some "enhancements" 
>>> in the Pax Tipi Project. 
>>>
>>>
>>> 2017-08-21 15:07 GMT+02:00 Stephan Siano :
>>>
 Hi,

 currently the tomcat support in pax-web references tomcat 8.0.14, 
 which is almost three years old. The current tomcat versions are 
 8.0.46 and 

Re: [paxweb] Update of Tomcat version

['Achim Nierbeck' via OPS4J]

Hi

looks good to me.

regards, Achim

2017-08-30 12:01 GMT+02:00 Stephan Siano :

> Hi Achim,
>
> OK, I created PAXTIPI-47  and
> PAXWEB-1128  for the update.
> Would you be willing to have a look into the pull requests?
>
> Best regards
> Stephan
>
>
> Am Dienstag, 29. August 2017 23:23:23 UTC+2 schrieb Achim Nierbeck:
>>
>> Hi Stephan,
>>
>> Technically you are correct. Create the pax-tipi projects, a release is
>> needed at lease the moment we release the pax-web project referencing that
>> version.
>> So you could also reference some snapshot versions from pax-web.
>> Regarding Jira tasks, yes it's common to create a Jira task in the pax
>> tipi project (https://ops4j1.jira.com/projects/PAXTIPI/) and also a Jira
>> task in Pax Web.
>> If you like you can reference the pax tipi one in pax web.
>>
>> regards, Achim
>>
>>
>> 2017-08-29 7:54 GMT+02:00 Stephan Siano :
>>
>>> Hi Achim,
>>>
>>> No problem, I was also a but busy. I found out that SPDY support was
>>> removed from tomcat 8 in the meantime, which makes the tomcat-embed-core
>>> bundle easier to build.
>>>
>>> How does this work technically? I need to create two projects in
>>> pax-tipi, release it and then create the changes in pax-web. The
>>> documentation in pax-tipi seems a bit sparse. Do I create a JIRA task for
>>> the Tomcat update under pax-web and also do the pax-tipi updates in there,
>>> or do I need to create a different JIRA task for that somewhere?
>>>
>>> Best regards
>>> Stephan
>>>
>>> Am Samstag, 26. August 2017 08:10:23 UTC+2 schrieb Achim Nierbeck:

 Hi Stephan,

 sorry for taking me so long, but my day job actually eats up a lot of
 time right now.
 A new tomcat version does require a new folder in the pax-tipi project.
 Actually the main project is just a "container" holding a bunch of
 sub-projects.

 regarding the juli logger, what ever works best and doesn't break Pax
 Web from working.
 I tried to move around that in the past, but it seemed to be better to
 just include the juli logger inside the tomcat bundles.

 regards, Achim

 2017-08-22 9:50 GMT+02:00 Stephan Siano :

> Hi Achim,
>
> yes I was aware of the things done in pax-tipi. I will try this out
> and then create the required projects in there. As I understand a new
> tomcat version would require new folders in pax-tipi for the required
> bundles (next to the ones for version 8.0.14), is this correct?
>
> One more question: What about the org.apache.juli.logging stuff?
> pax-logging-api exports org.apache.juli.logging in version 5.5 and 6.0,
> (tipi) tomcat-embed-logging-juli exports org.apache.juli and
> org.apache.juli.logging in its own version. tomcat-embed-core and
> tomcat-embed-websocket import org.apache.juli.logging in their own version
> (currently 8.0.14), pax-web-jsp imports org.apache.juli.logging without
> version (which makes kind of sense, because if the web container is not
> tomcat, the tomcat-embed-logging-juli bundle will not be there).
>
> Do you have an idea how to straigthen that out? Maybe we can import
> org.apache.juli.logging without a version and rely for the pax-logging
> implementation (and not have a tomcat-embed-juli bundle in pax-tipi). The
> only class that seems to be used besides the things pax-logging emulates 
> is
> org.apache.juli.ClassLoaderLogManager, which needs to be replaced
> somehow. Has anyone tried that already?
>
> Best regards
> Stephan
>
> Am Montag, 21. August 2017 18:33:54 UTC+2 schrieb Achim Nierbeck:
>>
>> Hi,
>>
>> the 6.0.x branch should stay with 8.0 version but a newer one if
>> available.
>> A minor version bump is fine with a 6.1.x (or master branch).
>>
>> regards, Achim
>>
>> P.S. btw. since Tomcat isn't OSGi ready we did some "enhancements" in
>> the Pax Tipi Project.
>>
>>
>> 2017-08-21 15:07 GMT+02:00 Stephan Siano :
>>
>>> Hi,
>>>
>>> currently the tomcat support in pax-web references tomcat 8.0.14,
>>> which is almost three years old. The current tomcat versions are 8.0.46 
>>> and
>>> 8.5.20. The end of life for tomcat 8.0 is announced for June 30th 2018.
>>>
>>> Would it make sense to upgrade the tomcat version in pax-web-6.0x
>>> branch to tomcat 8.5, or should it remain with a more current 
>>> 8.0-version
>>> and move to 8.5 only in the master branch? What do you think?
>>>
>>> Best regards
>>> Stephan
>>>
>>> --
>>> --
>>> --
>>> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OPS4J" group.
>>> To unsubscribe from this group and stop receiving emails f

Re: ClassNotFoundException: com.vaadin.testbench.TestBenchTestCase not found by PAXEXAM-PROBE

[laeubi.mobile via OPS4J]

And even better: You can open issues for the libs that are not bundles an 
try to convince them to add bundle-manifest headers to their lib for better 
osgi integration :-)

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ClassNotFoundException: com.vaadin.testbench.TestBenchTestCase not found by PAXEXAM-PROBE

[laeubi.mobile via OPS4J]

You use the wrapBundle() option, depending on your setup you have to add 
pax-url and pax-wrap to your bunlde-mix.

Am Freitag, 4. August 2017 06:17:47 UTC+2 schrieb reindheer:
>
> Hi,
>
> I am using Apache Karaf 4.0.8 for our backend and ui web applications, and 
> pax exam 4.10 for module testing. We have have written module tests using 
> pax exam for the backend applications.
>
> In UI application we use vaadin for ui and testbench for ui automation 
> testing. Now we want to integrate both so we could test the whole backend 
> and ui application. 
>
> So we are trying to run testbench using junits in pax exam.The testbench 
> uses selenium and other third party libs which are not bundles. Even 
> testbench is not a bundle. We have added all the third party libs as 
> dependencies to our project which only runs tests on pax exam. It compiles 
> but when run we get the following exception.
>
> java.lang.ClassNotFoundException: com.vaadin.testbench.TestBenchTestCase 
> not found by PAXEXAM-PROBE-19b79a7d-9de8-4bf9-bc34-0d3bdab631d6 [190]
> at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)
> at 
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2370)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2154)
> at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1542)
> at 
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> com.mymoduletest.uitest.LaunchWebApp.(LaunchWebApp.java:14)
>
> For this i tried adding all libraries required for testbench in a bundle( 
> exporting all packages) and added this to pax exam using maven() in pax 
> exam config method. Is this correct or we could do it in a better way?
>
> Thanks & Regards,
> Dheeraj
>

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ClassNotFoundException: com.vaadin.testbench.TestBenchTestCase not found by PAXEXAM-PROBE

[laeubi.mobile via OPS4J]

Am Freitag, 4. August 2017 06:17:47 UTC+2 schrieb reindheer:
>
> Hi,
>
> I am using Apache Karaf 4.0.8 for our backend and ui web applications, and 
> pax exam 4.10 for module testing. We have have written module tests using 
> pax exam for the backend applications.
>
> In UI application we use vaadin for ui and testbench for ui automation 
> testing. Now we want to integrate both so we could test the whole backend 
> and ui application. 
>
> So we are trying to run testbench using junits in pax exam.The testbench 
> uses selenium and other third party libs which are not bundles. Even 
> testbench is not a bundle. We have added all the third party libs as 
> dependencies to our project which only runs tests on pax exam. It compiles 
> but when run we get the following exception.
>
> java.lang.ClassNotFoundException: com.vaadin.testbench.TestBenchTestCase 
> not found by PAXEXAM-PROBE-19b79a7d-9de8-4bf9-bc34-0d3bdab631d6 [190]
> at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)
> at 
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2370)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2154)
> at 
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1542)
> at 
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
> at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> com.mymoduletest.uitest.LaunchWebApp.(LaunchWebApp.java:14)
>
> For this i tried adding all libraries required for testbench in a bundle( 
> exporting all packages) and added this to pax exam using maven() in pax 
> exam config method. Is this correct or we could do it in a better way?
>
> Thanks & Regards,
> Dheeraj
>

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: gave up waiting for service org.ops4j.pax.exam.ProbeInvokerFactory

[laeubi.mobile via OPS4J]

Okay, I have created https://ops4j1.jira.com/browse/PAXEXAM-891 I'll try to 
take a look at it the nex days..
It seems the logic has already changed in PaxExam-5 for this, if you want 
you can try our latest snapshot build?


Am Mittwoch, 30. August 2017 12:36:04 UTC+2 schrieb Martin Lichtin:
>
> Thanks, but unfortunately that setting has no effect in this situation.
>
> Parser.createInvoker calls
>
> public static  T getService( BundleContext bc, Class type, 
> Map props )
> {
> return getService( bc, type, DEFAULT_TIMEOUT, props );
> }
>
> and that DEFAULT_TIMEOUT is set to 10 seconds.
>
> On Tuesday, August 29, 2017 at 3:42:01 PM UTC+2, laeubi...@googlemail.com 
> wrote:
>>
>> This can happen when your test-container is under stress e.g init several 
>> things after startup. You can define a system-property 
>> 'pax.exam.service.timeout' with a value of e.g. 3 to wait longer.  
>> using systemProperty() option.
>>
>> Am Sonntag, 27. August 2017 17:17:08 UTC+2 schrieb Martin Lichtin:
>>>
>>> Actually no, the @Injects are all ok, also they all have a 60s timeout 
>>> on it.
>>>
>>> From the stacktrace you can see it's hitting an pax-exam internal 10s 
>>> timeout.
>>>
>>> Parser.createInvoker calls ServiceLookup.getService(ctx, 
>>> org.ops4j.pax.exam.ProbeInvokerFactory.class)
>>> That getService method waits up to 10 seconds for the 
>>> "ProbeInvokerFactory" service.
>>>
>>> Would you understand what could cause a delay for that service to become 
>>> registered?
>>>
>>> - Martin
>>>
>>> On Saturday, August 26, 2017 at 8:15:49 AM UTC+2, Achim Nierbeck wrote:

 Hi, 

 is your test failing because an @Inject of your service fails?
 I think you can add a timeout to the @Inject, in case you have a rather 
 big setup where the service does take a bit longer to be available after 
 start. 

 regards, Achim

 2017-08-24 10:51 GMT+02:00 Martin Lichtin :

> Sometimes, not always, a Pax test fails with
>
> org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting 
> for service org.ops4j.pax.exam.ProbeInvokerFactory
> at 
> org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:161)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
> at 
> org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:104)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
> at 
> org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:87)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
> at 
> org.ops4j.pax.exam.raw.extender.intern.Parser.createInvoker(Parser.java:79)[296:org.ops4j.pax.exam.extender.service:4.11.0]
> at 
> org.ops4j.pax.exam.raw.extender.intern.Parser.make(Parser.java:68)[296:org.ops4j.pax.exam.extender.service:4.11.0]
> at 
> org.ops4j.pax.exam.raw.extender.intern.Parser.(Parser.java:54)[296:org.ops4j.pax.exam.extender.service:4.11.0]
> at 
> org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver.addingEntries(TestBundleObserver.java:69)[296:org.ops4j.pax.exam.extender.service:4.11.0]
> at 
> org.ops4j.pax.swissbox.extender.BundleWatcher$3.run(BundleWatcher.java:226)[301:org.ops4j.pax.swissbox.extender:1.8.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_141]
> at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_141]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_141]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_141]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748)[:1.8.0_141]
>
> Any ideas what could be wrong? In case it is a timing issue, which 
> timeout parameter would that be?
>
> - Martin
>
> -- 
> -- 
> --
> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>
> --- 
> You received this message because you are subscribed to the Google 
> Groups "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to ops4j+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



 -- 

 Apache Member
 Apache Karaf  Committer & PMC
 OPS4J Pax Web  
 Committer & Project Lead
 blog 
 Co-Author of Apache Karaf Cookbook 

 Software Architect / Project Manager / Scrum M

Re: Setup database structure before bundle under test is started with pax exam + karaf

['Christoph Läubrich' via OPS4J]

From the log it seems your blueprint starts up before the service is 
registered. Since Camel does not know directly about the dependency you 
might try the following:
Let your blueprint import a javax.sql.DataSource service, then it won't 
start up before one is avaiable e.g. with


  

that will make your bundle wait for at least one DatasourceService (you 
might want to adjust the interface if pax-jdbc registers a different 
one, havent checked that...).


Beside that you should check if camel can even use those fetched service 
as a datasource instead of JNDI because that might create issues if the 
service changes while blueprint keeps track of those changes.


Am 30.08.2017 11:46, schrieb karsten.bl...@hermes-ottoint.com:

full Stack Trace for exception and log excerpt
datasources.osgi includes the pax-jdbc config files in live, for test 
the additional pax-jdbc bundles for derby and config files are added 
in the PaxExam configure() method
The only strange thing i see now is that the "Creating DataSource" log 
message is after the JNDI search by "org.apache.aries.jpa.container".

Might this be the cause? And how to change?

...
2017-08-30 11:26:42,770 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature datasources.osgi 
17.32.2-SNAPSHOT | bcid:  
exchange:  msgid:
2017-08-30 11:26:42,770 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature camel-jdbc 
2.16.3 | bcid:  exchange:  msgid:
2017-08-30 11:26:42,772 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-config 
0.9.0 | bcid:  exchange:  msgid:
2017-08-30 11:26:42,772 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-spec 
0.9.0 | bcid:  exchange:  msgid:
2017-08-30 11:26:42,776 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature 
pax-jdbc-postgresql 0.9.0 | bcid:  
exchange:  msgid:
2017-08-30 11:26:42,777 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature 
pax-jdbc-pool-dbcp2 0.9.0 | bcid:  
exchange:  msgid:




2017-08-30 11:26:44,968 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-derby 
0.9.0 | bcid:  exchange:  msgid:
2017-08-30 11:26:44,968 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-spec 
0.9.0 | bcid:  exchange:  msgid:


2017-08-30 11:27:04,677 | INFO  | Factory Update: 
factoryPid=[org.ops4j.datasource]) | nfig.impl.DataSourceRegistration 
| Detected config for DataSource jdbc/scv. Tracking DSF with filter 
(&(objectClass=org.osgi.service.jdbc.DataSourceFactory)(osgi.jdbc.driver.name=derby-pool)) 
| bcid:  exchange:  msgid:
2017-08-30 11:27:05,343 | INFO  | Factory Update: 
factoryPid=[org.ops4j.datasource]) | nfig.impl.DataSourceRegistration 
| Detected config for DataSource jdbc/scv_xa. Tracking DSF with filter 
(&(objectClass=org.osgi.service.jdbc.DataSourceFactory)(osgi.jdbc.driver.name=derby-pool-xa)) 
| bcid:  exchange:  msgid:

...

2017-08-30 11:27:27,421 | INFO  | 
FelixStartLevel| 
openjpa.Runtime  | Starting OpenJPA 2.2.2 | 
bcid:  exchange:  msgid:
2017-08-30 11:27:27,482 | ERROR | 
FelixStartLevel| 
org.apache.aries.jpa.container   | The DataSource 
osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/scv_xa) 
required by bundle UNDERTEST/17.32.2.SNAPSHOT could not be found. | 
bcid:  exchange:  msgid:
javax.naming.NameNotFoundException: 
osgi:service/javax.sql.DataSource/"(osgi.jndi.service.name=jdbc/scv_xa)"
at 
org.apache.aries.jndi.url.ServiceRegistryContext.lookup(ServiceRegistryContext.java:113)
at 
org.apache.aries.jndi.url.ServiceRegistryContext.lookup(ServiceRegistryContext.java:138)
at 
org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)

at javax.naming.InitialContext.lookup(InitialContext.java:417)
at 
org.apache.aries.jpa.container.unit.impl.JndiDataSource.getDs(JndiDataSource.java:66)
at 
org.apache.aries.jpa.container.unit.impl.DelayedLookupDataSource.getConnection(DelayedLookupDataSource.java:36)
at 
org.apac

Re: gave up waiting for service org.ops4j.pax.exam.ProbeInvokerFactory

[Martin Lichtin]

Thanks, but unfortunately that setting has no effect in this situation.

Parser.createInvoker calls

public static  T getService( BundleContext bc, Class type, 
Map props )
{
return getService( bc, type, DEFAULT_TIMEOUT, props );
}

and that DEFAULT_TIMEOUT is set to 10 seconds.

On Tuesday, August 29, 2017 at 3:42:01 PM UTC+2, laeubi...@googlemail.com 
wrote:
>
> This can happen when your test-container is under stress e.g init several 
> things after startup. You can define a system-property 
> 'pax.exam.service.timeout' with a value of e.g. 3 to wait longer.  
> using systemProperty() option.
>
> Am Sonntag, 27. August 2017 17:17:08 UTC+2 schrieb Martin Lichtin:
>>
>> Actually no, the @Injects are all ok, also they all have a 60s timeout on 
>> it.
>>
>> From the stacktrace you can see it's hitting an pax-exam internal 10s 
>> timeout.
>>
>> Parser.createInvoker calls ServiceLookup.getService(ctx, 
>> org.ops4j.pax.exam.ProbeInvokerFactory.class)
>> That getService method waits up to 10 seconds for the 
>> "ProbeInvokerFactory" service.
>>
>> Would you understand what could cause a delay for that service to become 
>> registered?
>>
>> - Martin
>>
>> On Saturday, August 26, 2017 at 8:15:49 AM UTC+2, Achim Nierbeck wrote:
>>>
>>> Hi, 
>>>
>>> is your test failing because an @Inject of your service fails?
>>> I think you can add a timeout to the @Inject, in case you have a rather 
>>> big setup where the service does take a bit longer to be available after 
>>> start. 
>>>
>>> regards, Achim
>>>
>>> 2017-08-24 10:51 GMT+02:00 Martin Lichtin :
>>>
 Sometimes, not always, a Pax test fails with

 org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting 
 for service org.ops4j.pax.exam.ProbeInvokerFactory
 at 
 org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:161)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
 at 
 org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:104)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
 at 
 org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:87)[304:org.ops4j.pax.swissbox.tracker:1.8.2]
 at 
 org.ops4j.pax.exam.raw.extender.intern.Parser.createInvoker(Parser.java:79)[296:org.ops4j.pax.exam.extender.service:4.11.0]
 at 
 org.ops4j.pax.exam.raw.extender.intern.Parser.make(Parser.java:68)[296:org.ops4j.pax.exam.extender.service:4.11.0]
 at 
 org.ops4j.pax.exam.raw.extender.intern.Parser.(Parser.java:54)[296:org.ops4j.pax.exam.extender.service:4.11.0]
 at 
 org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver.addingEntries(TestBundleObserver.java:69)[296:org.ops4j.pax.exam.extender.service:4.11.0]
 at 
 org.ops4j.pax.swissbox.extender.BundleWatcher$3.run(BundleWatcher.java:226)[301:org.ops4j.pax.swissbox.extender:1.8.2]
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_141]
 at 
 java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_141]
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_141]
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_141]
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_141]
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_141]
 at java.lang.Thread.run(Thread.java:748)[:1.8.0_141]

 Any ideas what could be wrong? In case it is a timing issue, which 
 timeout parameter would that be?

 - Martin

 -- 
 -- 
 --
 OPS4J - http://www.ops4j.org - op...@googlegroups.com

 --- 
 You received this message because you are subscribed to the Google 
 Groups "OPS4J" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to ops4j+un...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>>
>>> Apache Member
>>> Apache Karaf  Committer & PMC
>>> OPS4J Pax Web  Committer 
>>> & Project Lead
>>> blog 
>>> Co-Author of Apache Karaf Cookbook 
>>>
>>> Software Architect / Project Manager / Scrum Master 
>>>
>>>

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [paxweb] Does anybody know the rationale for building pax-web-jsp as it is?

[Stephan Siano]

Hi Achim,

OK, I willl try to clean that up when I do the update. I'd probably do that 
in an extra commit.

Best regards
Stephan

Am Dienstag, 29. August 2017 17:11:27 UTC+2 schrieb Achim Nierbeck:
>
> Hi Stephan, 
>
> I'd say that the sources are included has been an accident. 
> The build should re-build everything needed with the special adapted 
> classes for OSGi classloaders. 
>
> hope that helps already :) 
>
> regards, Achim 
>
>
> 2017-08-29 10:02 GMT+02:00 Stephan Siano >
> :
>
>> Hi,
>>
>> During my attempt to update the tomcat version in pax-web, I stumbled 
>> about the pax-web-jsp bundle.
>>
>> pax-web-jsp unpacks the source bundle of tomcat-embed-jasper with the 
>> maven-resources-plugin (exluding some of the java files which are in the 
>> source tree of the pax-web-jsp bundle). As a consequence the resulting 
>> bundle contains both the java files and the class files. What's the reason 
>> for that? It seems really odd to me to mix java and class files in a single 
>> archive. Can anyone remember why the build for pax-web-jsp is as it is?
>>
>> Best regards
>> Stephan
>>
>> -- 
>> -- 
>> --
>> OPS4J - http://www.ops4j.org - op...@googlegroups.com 
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "OPS4J" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ops4j+un...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Apache Member
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer & 
> Project Lead
> blog 
> Co-Author of Apache Karaf Cookbook 
>
> Software Architect / Project Manager / Scrum Master 
>
>

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [paxweb] Update of Tomcat version

[Stephan Siano]

Hi Achim,

OK, I created PAXTIPI-47  and 
PAXWEB-1128  for the update. 
Would you be willing to have a look into the pull requests?

Best regards
Stephan 


Am Dienstag, 29. August 2017 23:23:23 UTC+2 schrieb Achim Nierbeck:
>
> Hi Stephan, 
>
> Technically you are correct. Create the pax-tipi projects, a release is 
> needed at lease the moment we release the pax-web project referencing that 
> version. 
> So you could also reference some snapshot versions from pax-web. 
> Regarding Jira tasks, yes it's common to create a Jira task in the pax 
> tipi project (https://ops4j1.jira.com/projects/PAXTIPI/) and also a Jira 
> task in Pax Web. 
> If you like you can reference the pax tipi one in pax web. 
>
> regards, Achim 
>
>
> 2017-08-29 7:54 GMT+02:00 Stephan Siano >:
>
>> Hi Achim,
>>
>> No problem, I was also a but busy. I found out that SPDY support was 
>> removed from tomcat 8 in the meantime, which makes the tomcat-embed-core 
>> bundle easier to build.
>>
>> How does this work technically? I need to create two projects in 
>> pax-tipi, release it and then create the changes in pax-web. The 
>> documentation in pax-tipi seems a bit sparse. Do I create a JIRA task for 
>> the Tomcat update under pax-web and also do the pax-tipi updates in there, 
>> or do I need to create a different JIRA task for that somewhere?
>>
>> Best regards
>> Stephan
>>
>> Am Samstag, 26. August 2017 08:10:23 UTC+2 schrieb Achim Nierbeck:
>>>
>>> Hi Stephan, 
>>>
>>> sorry for taking me so long, but my day job actually eats up a lot of 
>>> time right now. 
>>> A new tomcat version does require a new folder in the pax-tipi project. 
>>> Actually the main project is just a "container" holding a bunch of 
>>> sub-projects. 
>>>
>>> regarding the juli logger, what ever works best and doesn't break Pax 
>>> Web from working. 
>>> I tried to move around that in the past, but it seemed to be better to 
>>> just include the juli logger inside the tomcat bundles. 
>>>
>>> regards, Achim 
>>>
>>> 2017-08-22 9:50 GMT+02:00 Stephan Siano :
>>>
 Hi Achim,

 yes I was aware of the things done in pax-tipi. I will try this out and 
 then create the required projects in there. As I understand a new tomcat 
 version would require new folders in pax-tipi for the required bundles 
 (next to the ones for version 8.0.14), is this correct?

 One more question: What about the org.apache.juli.logging stuff? 
 pax-logging-api exports org.apache.juli.logging in version 5.5 and 6.0, 
 (tipi) tomcat-embed-logging-juli exports org.apache.juli and 
 org.apache.juli.logging in its own version. tomcat-embed-core and 
 tomcat-embed-websocket import org.apache.juli.logging in their own version 
 (currently 8.0.14), pax-web-jsp imports org.apache.juli.logging without 
 version (which makes kind of sense, because if the web container is not 
 tomcat, the tomcat-embed-logging-juli bundle will not be there).

 Do you have an idea how to straigthen that out? Maybe we can import 
 org.apache.juli.logging without a version and rely for the pax-logging 
 implementation (and not have a tomcat-embed-juli bundle in pax-tipi). The 
 only class that seems to be used besides the things pax-logging emulates 
 is 
 org.apache.juli.ClassLoaderLogManager, which needs to be replaced somehow. 
 Has anyone tried that already?

 Best regards
 Stephan

 Am Montag, 21. August 2017 18:33:54 UTC+2 schrieb Achim Nierbeck:
>
> Hi, 
>
> the 6.0.x branch should stay with 8.0 version but a newer one if 
> available. 
> A minor version bump is fine with a 6.1.x (or master branch). 
>
> regards, Achim 
>
> P.S. btw. since Tomcat isn't OSGi ready we did some "enhancements" in 
> the Pax Tipi Project. 
>
>
> 2017-08-21 15:07 GMT+02:00 Stephan Siano :
>
>> Hi,
>>
>> currently the tomcat support in pax-web references tomcat 8.0.14, 
>> which is almost three years old. The current tomcat versions are 8.0.46 
>> and 
>> 8.5.20. The end of life for tomcat 8.0 is announced for June 30th 2018.
>>
>> Would it make sense to upgrade the tomcat version in pax-web-6.0x 
>> branch to tomcat 8.5, or should it remain with a more current 
>> 8.0-version 
>> and move to 8.5 only in the master branch? What do you think?
>>
>> Best regards
>> Stephan
>>
>> -- 
>> -- 
>> --
>> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>>
>> --- 
>> You received this message because you are subscribed to the Google 
>> Groups "OPS4J" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to ops4j+un...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
>>>

Re: Setup database structure before bundle under test is started with pax exam + karaf

[karsten . blume]

How is your test triggered? By timer? 

The test is started automatically by PaxExam.

>
> Can you create a simpler test-case you can publish on github that shows 
> your problem?
>

Not really, because there are several additional dependencies (db 
unrelated) involved.

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setup database structure before bundle under test is started with pax exam + karaf

[karsten . blume]

full Stack Trace for exception and log excerpt
datasources.osgi includes the pax-jdbc config files in live, for test the 
additional pax-jdbc bundles for derby and config files are added in the 
PaxExam configure() method
The only strange thing i see now is that the "Creating DataSource" log 
message is after the JNDI search by "org.apache.aries.jpa.container".
Might this be the cause? And how to change?

...
2017-08-30 11:26:42,770 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature datasources.osgi 
17.32.2-SNAPSHOT | bcid:  
exchange:  msgid: 
2017-08-30 11:26:42,770 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature camel-jdbc 2.16.3 | 
bcid:  exchange:  
msgid: 
2017-08-30 11:26:42,772 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-config 0.9.0 
| bcid:  exchange:  
msgid: 
2017-08-30 11:26:42,772 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-spec 0.9.0 | 
bcid:  exchange:  
msgid: 
2017-08-30 11:26:42,776 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-postgresql 
0.9.0 | bcid:  exchange:  
msgid: 
2017-08-30 11:26:42,777 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-pool-dbcp2 
0.9.0 | bcid:  exchange:  
msgid: 



2017-08-30 11:26:44,968 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-derby 0.9.0 
| bcid:  exchange:  
msgid: 
2017-08-30 11:26:44,968 | INFO  | 
FelixStartLevel| 
res.internal.FeaturesServiceImpl | Installing feature pax-jdbc-spec 0.9.0 | 
bcid:  exchange:  
msgid: 

2017-08-30 11:27:04,677 | INFO  | Factory Update: 
factoryPid=[org.ops4j.datasource]) | nfig.impl.DataSourceRegistration | 
Detected config for DataSource jdbc/scv. Tracking DSF with filter 
(&(objectClass=org.osgi.service.jdbc.DataSourceFactory)(osgi.jdbc.driver.name=derby-pool))
 
| bcid:  exchange:  
msgid: 
2017-08-30 11:27:05,343 | INFO  | Factory Update: 
factoryPid=[org.ops4j.datasource]) | nfig.impl.DataSourceRegistration | 
Detected config for DataSource jdbc/scv_xa. Tracking DSF with filter 
(&(objectClass=org.osgi.service.jdbc.DataSourceFactory)(osgi.jdbc.driver.name=derby-pool-xa))
 
| bcid:  exchange:  
msgid: 
...

2017-08-30 11:27:27,421 | INFO  | 
FelixStartLevel| 
openjpa.Runtime  | Starting OpenJPA 2.2.2 | 
bcid:  exchange:  
msgid: 
2017-08-30 11:27:27,482 | ERROR | 
FelixStartLevel| 
org.apache.aries.jpa.container   | The DataSource 
osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/scv_xa) 
required by bundle UNDERTEST/17.32.2.SNAPSHOT could not be found. | 
bcid:  exchange:  
msgid: 
javax.naming.NameNotFoundException: 
osgi:service/javax.sql.DataSource/"(osgi.jndi.service.name=jdbc/scv_xa)"
at 
org.apache.aries.jndi.url.ServiceRegistryContext.lookup(ServiceRegistryContext.java:113)
at 
org.apache.aries.jndi.url.ServiceRegistryContext.lookup(ServiceRegistryContext.java:138)
at 
org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at 
org.apache.aries.jpa.container.unit.impl.JndiDataSource.getDs(JndiDataSource.java:66)
at 
org.apache.aries.jpa.container.unit.impl.DelayedLookupDataSource.getConnection(DelayedLookupDataSource.java:36)
at 
org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:110)
at 
org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:87)
at 
org.apache.openjpa.jdbc.sql.DBDictionaryFactory.newDBDictionary(DBDictionaryFactory.java:91)
at 
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:603)
at 
org.apache.openjpa.jdbc.meta.MappingRepository.endConfiguration(Mappin

Re: Setup database structure before bundle under test is started with pax exam + karaf

['Christoph Läubrich' via OPS4J]

Can you explain what error do you get? Database not found? are the 
tables not created?


How is your test triggered? By timer?


Can you create a simpler test-case you can publish on github that shows 
your problem?



Am 30.08.2017 um 09:29 schrieb Blume, Karsten:


Hello,

yes this might help.

Bundle under test is a blueprint bundle with a camel jpa 
endpoint/component










and a persistence.xml



osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=_jdbc_/scv_xa)

a running live pax-jdbc configuration

this works also for the pax exam test

osgi.jdbc.driver.name = PostgreSQL JDBC Driver-pool-xa

databaseName=scv

dataSourceName=jdbc/scv_xa

user=xxx

password=xxx

url = jdbc:postgresql:// 155:155:155:155:5432/scv

What does not work:

A pax exam pax-jdbc configuration which I expect starts up the db 
before starting the test like:


osgi.jdbc.driver.name=derby-pool-xa

databaseName=scv

dataSourceName=jdbc/scv_xa

user=xxx

password=xxx

url=jdbc:derby:target/scvdev;create=true;user=xxx;password=xxx

or similar with H2

For the different test methods I need different test data inserted 
into the db. So a single startup script is not sufficient.


For the pax exam tests

How can a startup the db, modify it per test method and publish it so 
that the probe and the bundle under test can access it?


Regards

Karsten

*From:*laeubi.mobile via OPS4J [mailto:ops4j@googlegroups.com]
*Sent:* Dienstag, 29. August 2017 15:37
*To:* OPS4J
*Subject:* Re: Setup database structure before bundle under test is 
started with pax exam + karaf


You should provide a little more info about your setup, e.g. "working" 
vs "not working" configs, how you run the camel bundle (bluprint? 
spring? Routebuilders?)


I assume you want to test the route itself not the pax-jdbc setup, 
then you should configure your datasource that way that it can either 
run from JNDI or or a local jdbc-url to make testing easier.
You can the provide a config for test and one for deployment that 
contains either jndi or plain jdbc with e.g. inmemory db of h2 (which 
can be configured to init the db from a file).


Am Donnerstag, 24. August 2017 09:36:05 UTC+2 schrieb 
karste...@hermes-ottoint.com :


Hello everybody,
i am running pax exam 4 with a karaf 3 container.
The bundle under test is a camel 2.16.3 bundle.
The bundle uses a time triggered camel jpa component and pax-jdbc
with (XA and pooling) to instantiate the datasource.
For the test i need some table and some test data in a schema.
If i run the test with an existing postgres database everything is
fine. If i try to instantiate and setup the database first (H2 or
Derby) the bundle under test does not
find the database with the jndi name:
javax.naming.NameNotFoundException:
osgi:service/javax.sql.DataSource/"(osgi.jndi.service.name
=jdbc/scv_xa)"

How can i startup and setup the temporary db before the bundle
under test is started?

Thanks and best regards
Karsten

--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com 



---
You received this message because you are subscribed to a topic in the 
Google Groups "OPS4J" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/ops4j/F1YhX1Fvq_Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
ops4j+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.

--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

---
You received this message because you are subscribed to the Google 
Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ops4j+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups "OPS4J" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[infra] ci.ops4j.org over https problem

[Grzegorz Grzybek]

Hello

I'm trying to access ops4j Jenkins instance, but looks like there's some 
Apache/2.2.22 config problem:

$ telnet ci.ops4j.org 443
Trying 5.9.73.199...
Connected to ci.ops4j.org.
Escape character is '^]'.
GET / HTTP/1.0
Connection: close

HTTP/1.1 404 Not Found
Date: Wed, 30 Aug 2017 08:03:22 GMT
Server: Apache/2.2.22 (Ubuntu)
Vary: Accept-Encoding
Content-Length: 284
Connection: close
Content-Type: text/html; charset=iso-8859-1



404 Not Found

Not Found
The requested URL / was not found on this server.

Apache/2.2.22 (Ubuntu) Server at pumpkincay.rebaze.io Port 
80

Connection closed by foreign host.

I don't know whom to ask about proper configuration...

best regards
Grzegorz Grzybek

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Setup database structure before bundle under test is started with pax exam + karaf

[Blume, Karsten]

Hello,
yes this might help.
Bundle under test is a blueprint bundle with a camel jpa endpoint/component
   
  
  
   

and a persistence.xml
   
  
osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/scv_xa)

a running live pax-jdbc configuration
this works also for the pax exam test
osgi.jdbc.driver.name = PostgreSQL JDBC Driver-pool-xa
databaseName=scv
dataSourceName=jdbc/scv_xa
user=xxx
password=xxx
url = jdbc:postgresql:// 155:155:155:155:5432/scv

What does not work:
A pax exam pax-jdbc configuration which I expect starts up the db before 
starting the test like:
osgi.jdbc.driver.name=derby-pool-xa
databaseName=scv
dataSourceName=jdbc/scv_xa
user=xxx
password=xxx
url=jdbc:derby:target/scvdev;create=true;user=xxx;password=xxx
or similar with H2

For the different test methods I need different test data inserted into the db. 
So a single startup script is not sufficient.

For the pax exam tests
How can a startup the db, modify it per test method and publish it so that the 
probe and the bundle under test can access it?

Regards
Karsten



From: laeubi.mobile via OPS4J [mailto:ops4j@googlegroups.com]
Sent: Dienstag, 29. August 2017 15:37
To: OPS4J
Subject: Re: Setup database structure before bundle under test is started with 
pax exam + karaf

You should provide a little more info about your setup, e.g. "working" vs "not 
working" configs, how you run the camel bundle (bluprint? spring? 
Routebuilders?)

I assume you want to test the route itself not the pax-jdbc setup, then you 
should configure your datasource that way that it can either run from JNDI or 
or a local jdbc-url to make testing easier.
You can the provide a config for test and one for deployment that contains 
either jndi or plain jdbc with e.g. inmemory db of h2 (which can be configured 
to init the db from a file).

Am Donnerstag, 24. August 2017 09:36:05 UTC+2 schrieb 
karste...@hermes-ottoint.com:
Hello everybody,
i am running pax exam 4 with a karaf 3 container.
The bundle under test is a camel 2.16.3 bundle.
The bundle uses a time triggered camel jpa component and pax-jdbc with (XA and 
pooling) to instantiate the datasource.
For the test i need some table and some test data in a schema.
If i run the test with an existing postgres database everything is fine. If i 
try to instantiate and setup the database first (H2 or Derby) the bundle under 
test does not
find the database with the jndi name:
javax.naming.NameNotFoundException: 
osgi:service/javax.sql.DataSource/"(osgi.jndi.service.name=jdbc/scv_xa)"

How can i startup and setup the temporary db before the bundle under test is 
started?

Thanks and best regards
Karsten
--
--
--
OPS4J - http://www.ops4j.org - 
ops4j@googlegroups.com

---
You received this message because you are subscribed to a topic in the Google 
Groups "OPS4J" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/ops4j/F1YhX1Fvq_Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.