I followed quick start steps described in EJBCA documentation (http://www.ejbca.org/docs/installation.html)
'ant deploy' eventually failed with the following error
...
...
set-paths-not-jboss7:
set-paths:
jee:deployServicesJBoss5:
jee:assert-runJBoss7:
[echo] Checking if JBoss 7 is up and running...
[exec] Result: 1
BUILD FAILED
/home/pa/ejbca-setup/ejbca_ce_6_0_3/build.xml:635: The following error occurred while executing this line:
/home/pa/ejbca-setup/ejbca_ce_6_0_3/bin/jboss.xml:380: The requested action requires that JBoss 7 is up and running.
My problem was that JBoss wasn't starting. The documentation did point out that if 'ant deploy' fails, most likely caused is JBoss not running.
Since JBoss did not show any error, I thought it was up, however upon second look I understood that it was stuck in 'starting' state. There were no errors in log files. My Java version was 8. Installing Java 7 fixed the problem. Be sure to recompile EJBCA after switching Java.
Related
I am trying to upgrade to Jira 7 from version 6. I used the rapid upgrade method. It installs fine but I get an error on the browser “There is a problem with your Jira Access”. I went through the logs and I see that 6 plugins are failed to load during the Jira startup. Somehow they are disabled. I replaced couple of these .jar files with latest .jar and re-started the service, but I get the same error.
I also ran this query update pluginstate set pluginenabled='true' in the db but no luck.
Here is the log:
net.customware.plugins.connector.salesforce.salesforce-connector-plugin' - 'ServiceRocket Salesforce.com Connector Plugin - Plugin' failed to load.
Cannot start plugin: net.customware.plugins.connector.salesforce.salesforce-connector-plugin
Unresolved constraint in bundle net.customware.plugins.connector.salesforce.salesforce-connector-plugin [206]: Unable to resolve 206.0: missing requirement [206.0] osgi.wiring.bundle; (osgi.wiring.bundle=net.customware.plugins.connector.atlassian.jira-connector-plugin) [caused by: Unable to resolve 204.0: missing requirement [204.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.rpc)]
It was loaded from C:\JIRA_data\plugins\installed-plugins\salesforce-connector-plugin-6.0.8.jar.
We had the same problem last week, upgrading from 6.4.13 to 7.1.6. There are some incompatible plugins that crash Jira 7 when started, despite an apparently successful upgrade. Please refer to this page for details on the target plugins, as well as a way to solve the problem:
https://confluence.atlassian.com/jirakb/upgrading-to-jira-7-throws-a-nosuchmethoderror-on-com-atlassian-crowd-embedded-api-user-781396615.html
I have developed a working hybrid application in which I am using "phonegap-googlemaps-plugin". This plugin needs as a dependency two other which downloads and installs automatically in the project. The dependencies are:
com.google.playservices and plugin.http.request
Using the Cordova-CLI, installing this plugin with the dependencies will fail building the project the 1st time because of a specific directory in the "playservices" plugin. To overcome this, I have to run "ant clean" in my project and also remove/rename that directory. Now, I am using Intel XDK and uploaded my app and installed most of my plugins successfully and run the application on my device. When I am trying to install the google play services plugin, it fails to build because of the reason I described above (I've run through the logs). How can I overcome this issue now?
I have attached the part of the log that shows the fail error
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[aapt] invalid resource directory name: .../App/platforms/android/com.google.playservices/google-play-services_lib/bin/res/crunch
BUILD FAILED
/Developer/android-sdk-linux/tools/ant/build.xml:653: The following error occurred while executing this line:
/Developer/android-sdk-linux/tools/ant/build.xml:698: null returned: 1
Total time: 5 seconds
Error code 1 for command: ant with args: release,-f,.../App/platforms /android/build.xml,-Dout.dir=ant-build,-Dgen.absolute.dir=ant-gen
Command finished with error code 2: .../App/platforms/android/cordova/build --release
Error: .../App/platforms/android/cordova/build: Command failed with exit code 2
at ChildProcess.whenDone (/Developer/cordova/3.5.0-0.2.7/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
Thanks in advance.
I am new to Eclipse Juno using the Gradle Integration for Eclipse plugin. I am at a loss why gradle works perfectly from the command line and as an external tool; but in Eclipse Juno Package Explorer menu: gradle task it fails constantly with the following stack trace:
Error while initializing classpath container
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.5/userguide/gradle_daemon.html
Please read below process output to find out more:
java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.(File.java:423)
at org.gradle.api.internal.classpath.EffectiveClassPath.findAvailableClasspathFiles(EffectiveClassPath.java:41)
at org.gradle.api.internal.classpath.EffectiveClassPath.(EffectiveClassPath.java:32)
at org.gradle.api.internal.classpath.DefaultModuleRegistry.(DefaultModuleRegistry.java:61)
at org.gradle.api.internal.classpath.DefaultModuleRegistry.(DefaultModuleRegistry.java:55)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:41)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32)
at org.gradle.launcher.daemon.bootstrap.GradleDaemon.main(GradleDaemon.java:22)
Could not fetch model of type 'EclipseProject' using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.5-bin.zip'.
The env variables for GRADLE_HOME, GRADLE_USER_HOME, PATH are all setup correctly. From the command line gradle -v returns:
Gradle 1.6
Gradle build time: Tuesday, May 7, 2013 9:12:14 AM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ivy: 2.2.0
JVM: 1.7.0_45 (Oracle Corporation 24.45-b08)
OS: Windows 7 6.1 amd64
Eclipse version:
Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 2
Build id: 20130225-0426
OS is Win7 64 on amd64 platform with 4GB of system memory so it show not be a memory issue and there are no gradle daemons running when I get the above stack trace in Eclipse Juno.
I have exhausted all means on the web, this site, and my team to resolve the issue. I need some help please.
Windows 7 sets the user.home as a UNC path.
Add -Duser.home=x:\ to your Eclipse INI file where "x" is a local drive name.
That should solve your problem
If you are using the Gradle plugin, ensure it is pointing to the correct Gradle installation. I get the error you show when I use the embedded Gradle that comes with Spring Tools Suite.
I'm using a eclipse 4.2 distribution and have installed the gradle eclipse integration plugin from springsource.
When I initially try to create a quick java project with the wizard I get the following error:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at C:\devtools\gradle-1.4\docs\userguide\gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Could not fetch model of type 'HierarchicalEclipseProject' using Gradle installation 'C:\devtools\gradle-1.4'.
When I run gradle build in the command line everything's fine.
Any ideas how i could get this to work?
Cheers
Since you can run gradle in command line successfully, you would want to try to use that gradle in the eclipse plugin.
Set Preference -> Gradle -> Gradle Distribution -> Folder to your own gradle distribution that runs fine.
I recently update my QtSdk to 1.2 and after that, I am unable to deploy a debian file of more then 6 mb. It gives me the following error:
16:32:02: Preparing SFTP connection...
16:32:02: Starting upload...
16:32:03: Failed to upload package: Failure
16:32:03: Deploy step failed.
Error while building project Animal101SymbianMeegov1 (target: Harmattan)
When executing build step 'Deploy Debian package via SFTP upload'
Has anyone run across this problem?
The workaround I use to deploy is to create a link in /tmp/.deb pointing to /var/tmp/.deb and the run the deploy step in QtCreator.