In the traces you should find something like “Bundle XXX is waiting for 
dependencies [(objectClass=YYY), …]” as INFO

This might give you a hint on what’s going on. Another hint would be after 
timeout (graceperiod) “Unable to start blueprint container for bundle XXX due 
to unresolved dependencies [(objectClass=YYY), …]” as ERROR

I guess one of your bundles is waiting for a service which is not present for 
some reason (bundle missing…).

JP

[@@ OPEN @@]

De : Kevin Carr [mailto:[email protected]]
Envoyé : mercredi 16 octobre 2013 22:05
À : [email protected]
Objet : Re: Blueprint XML Never Starts

It appears that the 2 files start correctly after one of the bundles that use 
the service times out.  Which seems to take about 15 minutes.  I have tried 
setting the bundle-level for the config and datasource to 40, and it still 
fails the same way.
Thanks

On Wed, Oct 16, 2013 at 1:57 PM, Kevin Carr 
<[email protected]<mailto:[email protected]>> wrote:
Here is a sample of the logs, this shows up for the past 10 minutes on the 
server:
I have tried it on 2.3.3 as well, with the same result.  Eventually, it will 
work.

2013-10-16 13:55:50,666 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/config.xml
2013-10-16 13:55:50,667 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/datasource.xml
2013-10-16 13:55:51,669 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/config.xml
2013-10-16 13:55:51,670 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/datasource.xml
2013-10-16 13:55:52,672 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/config.xml
2013-10-16 13:55:52,673 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/datasource.xml
2013-10-16 13:55:53,675 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/config.xml
2013-10-16 13:55:53,676 | INFO  | raf-2.3.2/deploy | fileinstall                
      | ?                                   ? | 6 - 
org.apache.felix.fileinstall - 3.2.6 | Started bundle: 
blueprint:file:/home/ipwsuser/apache-karaf-2.3.2/deploy/datasource.xml


On Wed, Oct 16, 2013 at 1:50 PM, Kevin Carr 
<[email protected]<mailto:[email protected]>> wrote:
I am still seeing a problem with deployed Blueprint XML files.  They do not 
start for about 15+ minutes, then they work.
Everything is in the environment for these to work.  They use BoneCP and a 
configuration tool that I wrote, but they are started directly from blueprint 
files in the deploy is the only difference.

I am thinking about converting to a plain activator instead of using blueprint, 
to see if this fixes the issue.

If anyone has any ideas, I would be happy to hear from you.

On Fri, Oct 11, 2013 at 12:38 AM, Kevin Carr 
<[email protected]<mailto:[email protected]>> wrote:

Yes everything is installed.

I let it run for about 15 minutes and it started working,  but it throws the 
errors every second.  Then there is a timeout for the bundle that uses those 
services.  Then it starts correctly.

Really strange behavior.
On Oct 10, 2013 11:58 PM, "Freeman Fang" 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Did you already install postgresql and commons-dbcp bundles which is needed by 
this blueprint file?
-------------
Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋



On 2013-10-11, at 下午12:02, Kevin Carr wrote:


Here is the file that is being used.  Usernames and passwords changed to 
protect the innocent.

On Thu, Oct 10, 2013 at 10:53 PM, Freeman Fang 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Could you please post your blueprint file here?
-------------
Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com<http://fusesource.com/> | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com<http://freemanfang.blogspot.com/>
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋



On 2013-10-11, at 上午11:39, Scott Carr wrote:


I have a blueprint xml file in the deploy folder in apache karaf 2.3.3.  The 
blueprint has worked before fine.  For some reason, now I see:

Started bundle: blueprint:file:....xml  over and over in the log. It is like it 
keeps trying to create the bundle but there is no other information about an 
error or anything.

Does anyone else see this?  Putting blueprint files directly in the deploy 
folder has worked in the past.

Thanks

Scott Carr




--
Scott Carr
<db_file.xml>



--
Scott Carr


--
Scott Carr



--
Scott Carr

Reply via email to