What steps will reproduce the problem? 1. build sample app 2. run sample app from commandline, samples work 2a. (presently doing so) run maven dependencies:path in shell script to link together a commandline into a shell script to execute the same maven subproject that is called from within servlet, still works. 3. call sample code from servlet, initialization fails.

What is the expected output? What do you see instead?

exepcted output is the stack initialization message. failure output is a BluezDBus and bluecovebluez api failure

What BlueCove version are you using (include build number for SNAPSHOT)? On what operating system and jvm? Is this 64-bit or 32-bit OS and jvm? tested on fedoracore 12 386, ubuntu 9.04, 9.10 386+amd64

Please provide any additional information below. Please use "Attach a file" when uploading stack traces or other big files!

sorry i have no actual sourcecode or stacktraces to provide.

i am reporting based on a proprietary codebase which uses the discovery loop sample code + ~10 lines of code to hand off the discoverable data to other threads. this code is robust against 2.1.0 and 2.1.1-SNAPSHOT and in every previous bluecove initialization failure scenario it was user or usb errors preventing loop #1 completion. performs identically with bluecove 3.21 and 3.4x builds, distribution and home-built

Not enough information provided to even understand what is the problem.

The last time I tired to run it in Tomcat it was working fine.

in any case place bluecove outside the container: e.g. on the same class path as jetty start.jar