I am trying to deploy a simple Camel route to my local instance of JBoss Fuse 6.1 (GA release). I am trying to use the fabric8-maven-plugin to do so, but everytime I run fabric8:deploy, I receive the following error
Failed to execute goal io.fabric8:fabric8-maven-plugin:1.0.0.redhat-379:deploy (default-cli) on project filemover: Error executing: IO-Error while contacting the server: org.apache.http.NoHttpResponseException: The target server failed to respond
Here is my current plugin-definition from my pom file
<plugin>
<groupId>io.fabric8</groupId>
<artifactId>fabric8-maven-plugin</artifactId>
<version>1.0.0.redhat-379</version>
<configuration>
<profile>sample-filemover</profile>
<parentProfiles>feature-camel</parentProfiles>
<features>mq-fabric-camel</features>
</configuration>
</plugin>
My ~/.m2/user/settings.xml file contains the following server definition
<server>
<id>fabric8.upload.repo</id>
<username>admin</username>
<password>admin</password>
</server>
And I am executing the following mvn command
mvn fabric8:deploy -Dmaven.test.skip=true
(I realize I am skipping the tests, but I am trying to just deploy a profile at this time)
I can log onto the management console just fine and can see the root container no problem. Have I missed something in the configuration of Fuse to enable this?
I just spend some hours in the same problem.
Just change the version to 1.1.0.CR5 and you can deploy using mvn fabric8:deploy
Best Regards
are you sure you are trying on the correct server? Just put the fabric URL server where you want to deploy. I'm using that plugin version and it works correctly.
I know may be it's too late, but just for let you know, you can deploy in any server with
mvn clean fabric8:deploy -Dfabric8.jolokiaUrl=http://localhost:8181/jolokia
Cheers
Related
Managed VM's require in your appengine-web.xml or it's app.yaml equivalent:
<beta-settings>
<setting name="java_quickstart" value="true" />
</beta-settings>
And you use try to deploy you get this RuntimeException, what's going on?
As part of the deployment process, both the gcloud preview app deploy and mvn gcloud:deploy commands will launch jetty locally as part of the discovery of your annotations. If there is an error in your code it will crash. For example, in your contextedDestroyed or contextInitialized methods they will crash.
If you are using Maven, it is possible to debug this issue by:
For Java SDK 1.9.32:
java -jar ~/.m2/repository/com/google/appengine/appengine-java-sdk/1.9.32/appengine-java-sdk/appengine-java-sdk-1.9.32/lib/java-managed-vm/appengine-java-vmruntime/quickstartgenerator.jar target/myExplodedWar-1.0-SNAPSHOT
For Java SDK 1.9.33:
java -jar ~/.m2/repository/com/google/appengine/appengine-java-sdk/1.9.33/appengine-java-sdk/appengine-java-sdk-1.9.33/lib/java-managed-vm/appengine-java-vmruntime/quickstartgenerator.jar target/myExplodedWar-1.0-SNAPSHOT ~/.m2/repository/com/google/appengine/appengine-java-sdk/1.9.33/appengine-java-sdk/appengine-java-sdk-1.9.33/lib/jetty-base-sdk/etc/webdefault.xml
We expect this to be fixed in Java SDK 1.9.35
I followed this tutorial
to get a Bigtable client up and running in Google Managed VMs. But is there a way to run this locally? Reason is that deploying the code remotely in development is a pain.
Normally I can use dev_appserver.sh to run GAE app locally. But when I run it, I'm getting this error:
Caused by: java.lang.IllegalStateException: Jetty ALPN has not been
properly configured.
Which means we need to include ALPN library? Since our codebase is in Java 7, I used this ALPN version: 7.1.3.v20150130.
I then tried again with this:
dev_appserver.sh --jvm_flag=-Xbootclasspath/p:/Users/shouguoli/tmp/alpn-boot-7.1.3.v20150130.jar
still getting this error:
Caused by: com.google.apphosting.api.ApiProxy$CallNotFoundException:
The API package 'urlfetch' or call 'Fetch()' was not found.
How do you get it to work locally?
The sample was updated last week. It's based on the java 8 compat runtime, which means that you have access to most of the App Engine API's including Users, Task Queues, and Datastore.
There is a new Netty TCNative module that uses Boring SSL.
To use it with the pom.xml in the sample, do:
mvn clean -Pmac jetty:run -Dbigtable.projectID=<your-project> -Dbigtable.clusterID=<your-cluster> -Dbigtable.zone=<your-zone>
To use on Windows, use -Pwindows instead of -Pmac. For linux, omit the Profile -P as it's the default.
To deploy:
mvn clean gcloud:deploy -Dbigtable.projectID=<your-project> -Dbigtable.clusterID=<your-cluster> -Dbigtable.zone=<your-zone>
NOTE - it is advisable to do the clean between running locally and running remotely as the TCNative module is currently specific to the platform the code runs on.
We are in the process of updating all of our samples to use TCNative, we hope to have this by 3/10/16.
I am building Jenkins Maven Job. When I run Jenkins Job,I am getting following Dependencies error.
Failed to execute goal on project rabbitmq-build-trigger: Could not resolve dependencies for project org.jenkins-ci.plugins:rabbitmq-build-trigger:hpi:2.3.4: Failed to collect dependencies at **org.jenkins-ci.plugins:xunit:jar:1.90 -> org.jenkins-ci.lib.dtkit:dtkit-metrics-model:jar:2.0.0:** Failed to read artifact descriptor for org.jenkins-ci.lib.dtkit:dtkit-metrics-model:jar:2.0.0: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.34 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): Connect to repo.jenkins-ci.org:80 [repo.jenkins-ci.org/*.*.*.*, repo.jenkins-ci.org/*.*.*.*, repo.jenkins-ci.org/*.*.*.*] failed: Connection timed out -> [Help 1]
I have uploaded all required dependencies into our employer specific remote repo. and employer do not want to download any artifact from Central repo. Hence, accessing or calling external URL from slave box is restricted.
I do not know how dependencies work through a POM file. From the above message, "->" is travelling along with dependencies file
Can someone explain me what is wrong and how I supposed to resolve this issue? You answer is really matters to me
Are you sure you successfully uploaded specifically 'org.jenkins-ci:jenkins:pom:1.34' to the remote repository?
Also, ensure the remote repository is added as a repository element in your project's pom, like so:
<project>
...
<repositories>
<repository>
<id>my-internal-site</id>
<url>http://myserver/repo</url>
</repository>
</repositories>
...
</project>
(more information on repositories here: http://maven.apache.org/guides/introduction/introduction-to-repositories.html)
You might see if you can retrieve the artifacts by using each one's URL in a browser. If so, there's something amiss with your maven project repo configuration.
I have Jboss 7 running in Linux system. and I had deployed Solr 3.5 in it. It was working fine before.
After some days, Today when I started jboss 7 , it does not start my solr 3.5 . my sorl.war file exist at jboss-as-web-7.0.2.Final/standalone/deployments/
such issue also occured some times before, when my war deployment shows solr.war.failed in deployments. and i was able to resolve it by just moving / renaming that file.
But currently I am unable to deploy my was file and not showing as running when I start Jboss.
Below is response when i start jboss
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-as-web-7.0.2.Final
JAVA: /usr/lib/jvm/jdk1.7.0_40/bin/java
JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
I also tried by creating war file again and again deploy it.
Please help me to resolve this issue. how can i make it running??
Thanks
Make sure your solr.war is placed in jboss-as-web-7.0.2.Final/standalone/deployments/ and add an empty file named solr.war.dodeploy right next to the war.. If the deploy fails, copy the full stacktrace of the error.
does anyone know a way to configure a maven goal to deploy to a tomcat server after a build is run? I know that this is possible using the maven-tomcat-plugin but it looks as though as this only works for Maven 2 whereas I'm using Maven 1.1
I'm currently trying to set up Hudson so this would be part of my continuous intergration phase which I hope will run like this:
Build all necessary components
Build war and deploy to (local) server
Run selenium tests
Any help with this would be much appreciated.
Thanks.
Honestly I would refactor your project to use Maven 2, there are several guides that can help ease migration pain (google maven 2 migration), and there is even the maven-one-plugin to convert your project.xml or package your Maven 1 plugins for Maven 2.
If you can't do that, you could use the Maven 1 ant plugin to copy the war to tomcat's webapps directory after it has been packaged. Tomcat will detect the new war and should hot-deploy it.
I have to admit, I don't know much about the plugin for maven, but I do everything in a simple script that cleans the work directories as well (don't know if the maven plugin cleans the work directories).
CALL mvn clean install
CALL rm C:\apps\tomcat\webapps\Foo.war
CALL rm -rdf C:\apps\tomcat\webapps\foo
CALL rm -rdf C:\apps\tomcat\work\Catalina
CALL copy C:\webapps\workspace\Foo\target\Foo.war C:\apps\tomcat\webapps\Foo.war /y
(I know, -1 for MS scripting)
The point is you generally want to clean the work directory and the webapps directory and the Maven 1 ant plugin does not do this (as far as I know if, and read from the link provided). Tomcat is "supposed" to recreate the class files in these directories when it explodes the war file, but anybody who has worked with it long enough knows: this isn't always the case.
Therefore, if the plugin does not clean these directories, it's useless as far as I am concerned. Write yourself a cheap little script like the one provided. It takes 2 minutes.
I've figured out that best way to do this - its actually pretty easy to write a maven goal to transfer the war. The goal could be written as follows:
<goal name="deployWar" prereqs="buildWar">
<echo message="+---------------------------------------------------+" />
<echo message="installing war file to server" />
<echo message="+---------------------------------------------------+" />
<j:set var="deploy.dir" value="${server}/webapps" />
<copy file="${maven.build.dir}/${pom.artifactId}.war"
todir="${deploy.dir}" overwrite="true" />
</goal>
The server variable can be determined in your project.properties file. Also be sure to specify that a pre-requisite to build the WAR before you try to deploy it. Hope this helps someone!
webappDirectory can be configured for maven-war-plugin to deploy exploded war. Nothing special is needed, just run maven install.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<webappDirectory>path/to/server/deploy/dir</webappDirectory>
</configuration>
</plugin>