openshift – Page 5 – Kev's Development Toolbox

July 25, 2012

DeploymentScanner timeouts on OpenShift JBoss AS7

I haven’t seen this error often on the hosted OpenShift service (only occasionally when there’d been a system update and your app doesn’t redeploy correctly once restarted), but running OpenShift Origin locally I was seeing this consistently trying to deploy a new application:

2012/07/25 15:00:24,158 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
2012/07/25 15:00:24,160 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ROOT.war" was rolled back with failure message Operation cancelled

To increase the deployment scanner’s timeout setting, edit your project’s .openshift/config/standalone.xml, and find the deployment-scanner element:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" />
        </subsystem>

…and then add this attribute to <deployment-scanner> :

deployment-timeout="1200"

The XSD schema for this element says the default value is 600 second, but the error above says it’s timing out after 60 seconds. Assuming the default value is 600, I doubled it, and this fixed my timeout issues.

June 22, 2012March 17, 2024

Presenting at Red Hat Summit 2012 next week: Accenture & Red Hat collaboration to grow OpenShift skills

I’m presenting at the Red Hat Summit 2012 conference next week, Thursday June 28th @ 2:30pm at Campground 1 – I’m going to be talking about some work we recently did at Accenture in collaboration with Red Hat to grow OpenShift skills at Accenture.

Here’s the details of the session from the link above:

Growing OpenShift Skills within Accenture: The J-Prize Coding Contest

June 15th, 2012
by Accenture team

In Spring 2012, Accenture collaborated with Red Hat to run the “J-Prize Coding Contest” for Accenture Java developers. The focus of the contest was to design and develop a Java application and deploy it to OpenShift, Red Hat’s Platform as a Service (PaaS) offering.

“Cloud-related technologies are rapidly maturing and are increasingly being used by our clients to deliver real value,” said Kevin Hooke, Manager, Open Source Initiatives Lead for the Accenture Java Development Program. “The contest helped us grow our Java developers’ knowledge and experience with building and deploying applications to the cloud using PaaS offerings such as OpenShift.”

To learn more, attend the Red Hat campground session hosted by Kevin where he will discuss the success of the contest, the benefits gained for Accenture, and he will showcase the four winning applications.

Thursday, July 28 @ 2:30pm: Campground 1 (Room 301, Hynes)

June 15, 2012

Using OpenShift’s DIY cartridge to add Tomcat support

Grant Shipley at Red Hat has a great post here showing how you can use OpenShift’s DIY cartridge to add Tomcat support to your app, so you can run your app on Tomcat instead of JBoss.

May 17, 2012

In a Nutshell: Deploying a Java webapp to Red Hat’s OpenShift

Deploying a Java webapp to OpenShift couldn’t be any simpler. In as few words as possible to show you how simple it is – here’s a quickstart:

Follow the Quickstart setup guide here: https://openshift.redhat.com/app/express#quickstart
Develop your app
git add .
git commit -m “commit message”
git push

… and that’s it. Your app is pushed to your remote Git repo, built with Maven, and deployed to JBoss 7.

That’s pretty simple, huh?