I am using Fuse 7.7 on Apache Karaf.
I am getting this error
2020-09-28 18:08:57,689 | ERROR | lueprint Extender: 2 | o.a.a.b.c.BlueprintContainerImpl | 51 - org.apache.aries.blueprint.core - 1.10.2 |
Unable to start container for blueprint bundle com.esb.iis-to-rm-vr/1.0.0 due to unresolved dependencies [(&(component=http)(objectClass=org.apache.camel.spi.ComponentResolver))]
java.util.concurrent.TimeoutException: null
I did the below steps. camel-http is not installed.
karaf#root()> features:install camel-http
karaf#root()> features:list | grep camel-http
camel-http4
karaf#root()> list | grep camel-http
67 | Active | 50 | 2.21.0.fuse-770013-redhat-00001 | camel-http-common
255 | Active | 50 | 2.21.0.fuse-770013-redhat-00001 | camel-http4
Please let me know apart from the below step, what are the steps i need to follow to install camel-http.
karaf#root()> features:install camel-http
Be careful that camel-http is only meant to be a producer. You won't be able to do from("http://...") only with him. To be able to do it, you need to add a camel component that will allow your route to bind itself to the karaf's jetty. You can try to install camel-jetty.
Moreover, you're feature:list | grep camel-http seemed to have only returned camel-http4. I'm note sure camel-http feature has been dropped, but you could always install http4 component
Related
i'm trying to generate an Ios Build on AppFlow but i'm getting the follow issue:
▸ Compiling CDVIonicKeyboard.m
▸ Compiling CDVInAppBrowserOptions.m
▸ Compiling CDVInAppBrowserNavigationController.m
▸ Compiling CDVDevice.m
▸ Compiling AppDelegate.m
▸ Compiling AppDelegate+FirebasePlugin.m
▸ Linking Doação do Bem
❌ ld: framework not found Pods_Doac_a_o_do_Bem
❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)
** ARCHIVE FAILED **
The following build commands failed:
Ld /Users/ionic/Library/Developer/Xcode/DerivedData/Doação-beqnnqghtsgeefgbqzrcwiwhvhex/Build/Intermediates.noindex/ArchiveIntermediates/Doação do Bem/InstallationBuildProductsLocation/Applications/Doação.app/Doação normal
(1 failure)
[15:00:46]: Exit status: 65
+---------------+-------------------------+
| Build environment |
+---------------+-------------------------+
| xcode_path | /Applications/Xcode.app |
| gym_version | 2.185.0 |
| export_method | development |
| sdk | iPhoneOS14.5.sdk |
+---------------+-------------------------+
[15:00:46]: ▸ /Users/ionic/builds/inovacao/doacao/platforms/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'FBSDKShareKit' from project 'Pods')
[15:00:46]: ▸ /Users/ionic/builds/inovacao/doacao/platforms/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'FBSDKLoginKit' from project 'Pods')
[15:00:46]: ▸ /Users/ionic/builds/inovacao/doacao/platforms/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'FirebaseCoreDiagnostics' from project 'Pods')
[15:00:46]: ▸ /Users/ionic/builds/inovacao/doacao/platforms/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'FirebaseMessaging' from project 'Pods')
[15:00:46]: ▸ /Users/ionic/builds/inovacao/doacao/platforms/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'FirebaseRemoteConfig' from project 'Pods')
[15:00:46]:
[15:00:46]: ⬆️ Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[15:00:46]: 📋 For the complete and more detailed error log, check the full log at:
[15:00:46]: 📋 /Users/ionic/Library/Logs/gym/Doação-Doação.log
[15:00:46]:
[15:00:46]: Your `export_method` in gym is defined as `development`
[15:00:46]: which might cause problems when signing your application
[15:00:46]: Are you sure want to build and export for development?
[15:00:46]: Please make sure to define the correct export methods when calling
[15:00:46]: gym in your Fastfile or from the command line
[15:00:46]:
[15:00:46]:
[15:00:46]: Looks like fastlane ran into a build/archive error with your project
[15:00:46]: It's hard to tell what's causing the error, so we wrote some guides on how
[15:00:46]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[15:00:46]: Before submitting an issue on GitHub, please follow the guide above and make
[15:00:46]: sure your project is set up correctly.
[15:00:46]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[15:00:46]: the full commands printed out in yellow in the above log.
[15:00:46]: Make sure to inspect the output above, as usually you'll find more error information there
[15:00:46]:
[15:00:46]: -------------------------
[15:00:46]: --- Step: upload_logs ---
[15:00:46]: -------------------------
[15:00:58]: Unable to upload package list log. Skipping.
[15:01:07]: ---------------------------
[15:01:07]: --- Step: shell command ---
[15:01:07]: ---------------------------
[15:01:07]: -----------------------------
[15:01:07]: --- Step: delete_keychain ---
[15:01:07]: -----------------------------
[15:01:07]: Error building the application - see the log above
+-------------------------------------+-----------------------------------------------------------------------------------------------------------------+
| Lane Context |
+-------------------------------------+-----------------------------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM | ios |
| PLATFORM_NAME | ios |
| LANE_NAME | ios build_ionic |
| NODE_PACKAGE_MANAGER | npm |
| PROJECT_WEB_DIR | www |
| KEYCHAIN_PATH | ~/Library/Keychains/IonicKeychain |
| DOWNLOAD_CERTS_PROVISION_FILE_UUID | 5be2531f-1aa3-4edf-b681-f04bc2e9e92e |
| DOWNLOAD_CERTS_CODESIGNING_IDENTITY | iPhone Developer: Vinicius Gomes (42QSQ9W96V) |
| DOWNLOAD_CERTS_TEAM_ID | 8PZLTG83YY |
| DOWNLOAD_CERTS_CERT_PATH | /Users/ionic/builds/inovacao/doacao/cert_file.p12 |
| SIGH_PROFILE_PATHS | ["/Users/ionic/builds/inovacao/doacao/5be2531f-1aa3-4edf-b681-f04bc2e9e92e.mobileprovision"] |
| XCODE_PROJECT_NAME | Doação |
| XCODE_PROJECT_PATH | /Users/ionic/builds/inovacao/doacao/platforms/ios/Doação.xcodeproj |
| XCODE_WORKSPACE_PATH | /Users/ionic/builds/inovacao/doacao/platforms/ios/Doação do Bem.xcworkspace
|
+-------------------------------------+-----------------------------------------------------------------------------------------------------------------+
[15:01:07]: Error building the application - see the log above
[!] Error building the application - see the log above
+------+----------------------------------+-------------+
| fastlane summary |
+------+----------------------------------+-------------+
| Step | Action | Time (in s) |
+------+----------------------------------+-------------+
| 1 | add_extra_platforms | 0 |
| 2 | default_platform | 0 |
| 3 | build_summary | 5 |
| 4 | detect_native_type | 0 |
| 5 | Switch to ios build_cordova lane | 0 |
| 6 | detect_package_manager | 0 |
| 7 | add_git_credentials | 0 |
| 8 | get_appflow_config | 0 |
| 9 | dependency_install | 48 |
| 10 | get_web_dir | 0 |
| 11 | modify_config_xml | 0 |
| 12 | create_keychain | 0 |
| 13 | download_certs | 1 |
| 14 | import_certificate | 0 |
| 15 | build_pro_app | 32 |
| 16 | add_cordova_to_index | 0 |
| 17 | cordova platform add ios | 242 |
| 18 | get_xcode_project_paths | 0 |
| 19 | update_code_signing_settings | 0 |
| 💥 | gym | 361 |
| 21 | upload_logs | 21 |
| 22 | shell command | 0 |
| 23 | delete_keychain | 0 |
+------+----------------------------------+-------------+
[15:01:07]: fastlane finished with errors
Running after script...
$ clean-up
ERROR: Job failed: Process exited with: 1. Reason was: ()
Infos:
Ionic:
Ionic CLI : 5.4.16 (C:\Users\guilh\AppData\Roaming\nvm\v18.12.1\node_modules\ionic)
Ionic Framework : ionic-angular 3.9.5
#ionic/app-scripts : 3.2.2
Cordova:
Cordova CLI : 11.0.0 (cordova-lib#11.1.0)
Cordova Platforms : android 8.1.0, browser 6.0.0
Cordova Plugins : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 5.0.0, (and 13 other plugins)
Utility:
cordova-res : 0.15.4
native-run : not installed
System:
Android SDK Tools : 26.1.1 (C:\Users\guilh\AppData\Local\Android\Sdk)
NodeJS : v18.12.1 (C:\Users\guilh\AppData\Roaming\nvm\v18.12.1\node.exe)
npm : 9.2.0
OS : Windows 10
plugins:
cordova-plugin-androidx-adapter 1.1.3 "cordova-plugin-androidx-adapter"
cordova-plugin-androidx 1.0.2 "cordova-plugin-androidx"
cordova-plugin-device 2.1.0 "Device"
cordova-plugin-facebook4 6.4.0 "Facebook Connect"
cordova-plugin-firebasex 7.0.2 "Google Firebase Plugin"
cordova-plugin-geolocation 4.0.2 "Geolocation"
cordova-plugin-inappbrowser 4.1.0 "InAppBrowser"
cordova-plugin-ionic-keyboard 2.2.0 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 5.0.0 "cordova-plugin-ionic-webview"
cordova-plugin-request-location-accuracy 2.3.0 "Request Location Accuracy"
cordova-plugin-sign-in-with-apple 0.1.2 "cordova-plugin-sign-in-with-apple"
cordova-plugin-splashscreen 5.0.4 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-whitelist 1.3.5 "Whitelist"
cordova-plugin-x-socialsharing 5.6.8 "SocialSharing"
cordova-sqlite-storage 5.1.0 "Cordova sqlite storage plugin - cordova-sqlite-storage plugin version"
es6-promise-plugin 4.2.2 "Promise"
i've tried to change versions of plugins and a lot of thing, but nothing resolved this. Also i tried to remove some os plugins buth none of all worked
Overview:
When I attempt to run VSCode with the instructions given in the contributions page to download all the packages, build the source code, and then run it all on the terminal, an error message pops up saying that I don't have the electron app in the vscode directory. Shouldn't have the electron app been installed when I ran the yarn command to install and build all the dependencies?
Steps to reproduce the bug:
$ yarn //building and installing all dependencies
$ yarn watchd //building vscode
$ ./scripts/code.sh //running vscode
Error Message:
Error launching app
Unable to find Electron app at /home/juan/Desktop/Projects/vscode
Cannot find module '/home/juan/Desktop/Projects/vscode/out/main'. Please verify that the package.json has a valid "main" entry
System Details:
CPUs | Intel(R) Core(TM) i7-6600U CPU # 2.60GHz (4 x 3200)
-- | --
GPU Status | 2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software
Load (avg) | 1, 1, 1
Memory (System) | 7.63GB (0.12GB free)
Process Argv | . --no-sandbox
Screen Reader | no
VM | 0%
OS|Ubuntu 18.04 LTS
Extensions:
Extension | Author (truncated) | Version
-- | -- | --
Bookmarks | ale | 11.2.0
vscode-sqlite | ale | 0.8.2
code-gnu-global | aus | 0.2.2
npm-intellisense | chr | 1.3.0
vscode-svgviewer | css | 2.0.0
vscode-markdownlint | Dav | 0.36.0
jshint | dba | 0.10.21
vscode-eslint | dba | 2.1.5
vscode-html-css | ecm | 0.2.3
EditorConfig | Edi | 0.15.1
vscode-npm-script | eg2 | 0.3.12
vscode-firefox-debug | fir | 2.8.0
beautify | Hoo | 1.5.0
vscode-emacs-friendly | lfs | 0.9.0
rainbow-csv | mec | 1.7.0
python | ms- | 2020.5.80290
cpptools | ms- | 0.28.2
debugger-for-chrome | msj | 4.12.8
sqltools | mtx | 0.22.5
material-icon-theme | PKi | 4.1.0
rust | rus | 0.7.8
lc2k | vio | 1.1.1
Here is the bug report I filled in the vscode github page: https://github.com/microsoft/vscode/issues/99537
I got this same error myself when the code did not build correctly.
In your second step you do:
yarn watchd
I tried this command myself, but ran into the same issue that you have stated here. Although the official wiki suggests this as a tip, I would just ignore it.
Instead, do either of these instead (this is what the official wiki originally suggest to do):
Type: Ctrl + Shift + B
Or alternatively use the Command Palette:
Type: Ctrl + Shift + P
Search for the option called: Tasks: Run Build Task and select it.
Once you start the build task you'll see a couple of things:
Firstly, at the bottom of VS Code (on your status line), VS Code will let you know the code is building.
Secondly, The build command will open two terminals:
Task - Build VS Code
Task - Build VS Code Extensions
Watch the output for both of terminals, make sure:
Task - Build VS Code terminal outputs: [some time] Finished compilation ...
and
Task - Build VS Code Extensions terminal outputs: [some time] Finished compilation extensions ...
If not and the build fails, you'll probably get a notification from VS code saying so (You'll probably get the error twice, one for each task):
yarn ... exited with code [some non-zero integer]
A common error that may occur is the ENOSPC error from inotify (also documented well in a medium blog). You'll want to issue this command:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Arch users would issue:
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system
After fixing this, trying to build again should work. Start the build task again and make sure both tasks succeed. (You'll notice that the tasks do not end after they succeed. This is because they will watch for changes you make in the code while developing and automatically recompile for you).
If successful you may finally issue:
./scripts/code.sh
A new instance of VS Code should open called: Code - OSS dev. This is the version of VS Code you just built.
I'm upgrading some libraries within a Play! project. During the process I'm trying to resolve errors like this:
java.lang.ClassNotFoundException: akka.event.slf4j.Slf4jLoggingFilter
Which I am assuming comes from incompatible transitive dependencies?
But I'm struggling to effectively use sbt-dependency-graph to help me track down the problem.
[info] +-ch.qos.logback:logback-classic:1.1.3
[info] | +-ch.qos.logback:logback-core:1.1.3
[info] | +-org.slf4j:slf4j-api:1.7.21
[info] | +-org.slf4j:slf4j-api:1.7.7 (evicted by: 1.7.21)
Why are there 2 versions of slf4j-api listed 👆🏻
I'm assuming, the newer version (1.7.21) is taking precedence over 1.7.7 But then, why in some instances, do I see as many as 5 different versions of the same dependency (all but 1 evicted):
| | | | +-org.slf4j:slf4j-ext:1.7.12
| | | | +-ch.qos.cal10n:cal10n-api:0.8.1
| | | | +-org.slf4j:slf4j-api:1.6.2 (evicted by: 1.7.21)
| | | | +-org.slf4j:slf4j-api:1.6.4 (evicted by: 1.7.21)
| | | | +-org.slf4j:slf4j-api:1.7.12 (evicted by: 1.7.21)
| | | | +-org.slf4j:slf4j-api:1.7.2 (evicted by: 1.7.21)
| | | | +-org.slf4j:slf4j-api:1.7.21
Once the conflict is found -- do I need to upgrade all dependencies to be using the same version?
Is there another approach I should be taking?
Discovered that "the SLF4J API is backward compatible for all versions". Despite java.lang.ClassNotFoundException being called from an slf4j. So digging a little deeper:
Akka Kindly provides binary compatibility rules which show that backwards compatibility is violated between major versions.
Looking at the dependency tree we were seeing different major versions of akka dependencies (2.3.x and 2.4.x): com.typesafe.akka:akka-actor_2.11:2.3.13 (evicted by: 2.4.11) and com.typesafe.akka:akka-slf4j_2.11:2.3.13
Standardizing all akka dependencies around a major version fixed it:
Our original dependencies only provided the "com.typesafe.akka" %% "akka-actor" % "2.4.11" and play was providing "akka-slf4j" % "2.3.13" transitively which was breaking binary compatibility.
+-com.typesafe.akka:akka-slf4j_2.11:2.3.13 [S]
| +-com.typesafe.akka:akka-actor_2.11:2.3.13 (evicted by: 2.4.11)
Providing both akka-slf4j and akka-actor with the same major version solved this issue.
I have installed apache archiva stand alone in my system.But when i try to start it,itshows the error apache archiva failed to start.My codes are given below
D:\apache-archiva-1.3.5>java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin;D:\apache-archiva-1.3.5\bin
D:\apache-archiva-1.3.5>archiva.bat install
wrapper | Apache Archiva installed.
D:\apache-archiva-1.3.5>archiva.bat start
wrapper | Starting the Apache Archiva service...
wrapper | The Apache Archiva service was launched, but failed to start.
Press any key to continue . . .
Instead of using
C:\apache-archiva-2.2.1\bin>archiva start
if you use console it will work.
C:\apache-archiva-2.2.1\bin>archiva console
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.ContextDeployer:ContextDeployer is deprecated. Use ContextProvider
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.WebAppDeployer:WebAppDeployer is deprecated. Use WebAppProvider
jvm 1 | 2016-06-05 01:11:49.147:INFO:oejs.Server:jetty-8.1.14.v20131031
jvm 1 | 2016-06-05 01:11:49.178:INFO:oejs.NCSARequestLog:Opened C:\apache-archiva-2.2.1\logs\request-20160604.log
jvm 1 | 2016-06-05 01:11:49.225:INFO:oejd.ContextDeployer:Deploy C:\apache-archiva-2.2.1\contexts\archiva.xml -> o.e.j.w.WebAppContext{/,null},C:\apache-archiva-2.2.1/apps/archiva
jvm 1 | 2016-06-05 01:11:53.149:INFO:oejpw.PlusConfiguration:No Transaction manager found - if your webapp requires one, please configure one.
jvm 1 | 2016-06-05 01:11:53.453:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
jvm 1 | 2016-06-05 01:11:54.755:INFO:/:Initializing Spring root WebApplicationContext
jvm 1 | Jun 05, 2016 1:12:09 AM org.apache.tomcat.jdbc.pool.ConnectionPool init
jvm 1 | WARNING: maxIdle is larger than maxActive, setting maxIdle to: 20
jvm 1 | 2016-06-05 01:12:25.275:INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080
How do I determine if my Jetty6-service run with administrative rights?
I need to setup Jetty on my XP dev box to run as a service.
http://docs.codehaus.org/display/JETTY/Win32Wrapper
It installs OK and I can see the Jetty6 Service in windows services manager.
But when I try to start it I get this error in the log file:
STATUS | wrapper | 2010/02/26 10:17:10 | Launching a JVM...
INFO | jvm 2 | 2010/02/26 10:17:10 | Error occurred during initialization of VM
INFO | jvm 2 | 2010/02/26 10:17:10 | Too small initial heap for new size specified
ERROR | wrapper | 2010/02/26 10:17:10 | JVM exited while loading the application.
from above link:
Note: The above application (Jetty-Service.exe) must execute with administrator rights otherwise, it fails.
I do have local administrative access to my XP dev box.
And when I run the jetty server as standalone from cmd.exe then it works fine.
(java -jar start.jar etc/jetty.xml)
Does anyone know how to solve this problem / where to look?
/Thanks.