Build and Release Management

Running Multiple Commands with SSHExec ANT Task

admin — Fri, 29 Mar 2013 19:18:07 +0000

Did you have to figure out how to run multiple commands within the Ant’s Optional SSHExec task?

Here’s how to do it:

You just basically chain the commands consecutively with “&&”

Apache2 Proxy Disabled Connection on (localhost)

admin — Tue, 11 Sep 2012 19:59:18 +0000

If you ever tried to set a proxy connection where you’re using Apache to serve as the front-end host for a webapp (via Tomcat) on the same server and you ran into a similar error message:

[error] proxy: HTTP: disabled connection for (localhost)
-or-
[error] ap_proxy_connect_backend disabling worker for (localhost)

You can try this to fix it:

sudo /usr/sbin/setsebool -P httpd_can_network_connect 1

Rookie Gradle Errors I Made

admin — Wed, 13 Jun 2012 18:34:47 +0000

This is just a beginning of a long series of posts documenting the rookie mistakes that I’ve made while getting acquainted with Gradle.

Ever received this error?

* What went wrong:
Could not compile build file ‘/path/to/build.gradle’.
> startup failed:
build file ‘/path/to/build.gradle’: 4: expecting anything but ”\n”; got it anyway @ line 4, column 17.
print “hello, ‘
^

1 error

What happened was that I had a mix of quote and apostrophe on my ‘print’ statement: print “hello, ‘

Set “ulimit” parameters to fix “Too Many Open Files” Error

admin — Thu, 08 Dec 2011 21:16:58 +0000

If you ever run into the following errors with the below stacktrace, there’s a more than likely easy fix for it at the bottom of this article.

java.lang.IllegalStateException: Failed to load ApplicationContext
at org.springframework.test.context.TestContext.get
ApplicationContext(TestContext.java:308)
at org.springframework.test.context.support.DependencyInjection
TestExecutionListener.injectDependencies

(DependencyInjectionTestExecutionListener.java:109)
at org.springframework.test.context.support.DependencyInjection
TestExecutionListener.prepareTestInstance

(DependencyInjectionTestExecutionListener.java:75)
at org.springframework.test.context.TestContextManager.prepareTestInstance
(TestContextManager.java:321)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest
(SpringJUnit4ClassRunner.java:211)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.
runReflectiveCall(SpringJUnit4ClassRunner.java:287)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock
(SpringJUnit4ClassRunner.java:289)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild
(SpringJUnit4ClassRunner.java:231)
at com.fmn.testutil.FmnTestClassRunner.runChild(FmnTestClassRunner.java:10)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.
evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.
evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run
(SpringJUnit4ClassRunner.java:174)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute
(JUnitTestClassExecuter.java:51)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass
(JUnitTestClassProcessor.java:63)
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass
(SuiteTestClassProcessor.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch
(ContextClassLoaderDispatch.java:32)
at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke
(ProxyDispatchAdapter.java:75)
at $Proxy4.processTestClass(Unknown Source)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.messaging.remote.internal.MethodInvocationUnmarshallingDispatch.dispatch
(MethodInvocationUnmarshallingDispatch.java:48)
at org.gradle.messaging.dispatch.DiscardOnFailureDispatch.dispatch

(DiscardOnFailureDispatch.java:31)
at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:129)
at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)
at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:69)
at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run
(DefaultExecutorFactory.java:63)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean

with name ‘hadoopInit’ defined in class path resource [testservices/services-test.xml]:

Instantiation of bean failed; nested exception is org.springframework.beans.

BeanInstantiationException: Could not instantiate bean class [com.fmn.hadoop.testutil.HadoopInit]:

Constructor threw exception; nested exception is java.io.IOException: Cannot run program “bash”:

java.io.IOException: error=24, Too many open files
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
instantiateBean(AbstractAutowireCapableBeanFactory.java:965)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
createBeanInstance(AbstractAutowireCapableBeanFactory.java:911)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject
(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean
(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
(DefaultListableBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization
(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh
(AbstractApplicationContext.java:425)
at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext
(AbstractGenericContextLoader.java:84)
at org.springframework.test.context.support.AbstractGenericContextLoader.loadContext
(AbstractGenericContextLoader.java:1)
at org.springframework.test.context.TestContext.loadApplicationContext(TestContext.java:280)
at org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:304)
… 47 more
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class
[com.fmn.hadoop.testutil.HadoopInit]: Constructor threw exception; nested exception is java.io.

IOException: Cannot run program “bash”: java.io.IOException: error=24, Too many open files
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:141)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate
(SimpleInstantiationStrategy.java:74)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean
(AbstractAutowireCapableBeanFactory.java:958)
… 61 more
Caused by: java.io.IOException: Cannot run program “bash”: java.io.IOException: error=24, Too many open files
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at org.apache.hadoop.util.Shell.runCommand(Shell.java:200)
at org.apache.hadoop.util.Shell.run(Shell.java:182)
at org.apache.hadoop.fs.DF.getFilesystem(DF.java:63)
at org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker.addDirsToCheck

(NameNodeResourceChecker.java:93)
at org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker

.(NameNodeResourceChecker.java:73)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:348)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:327)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:271)
at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:465)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1239)
at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:278)
at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:225)
at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:347)
at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:292)
at com.fmn.hadoop.testutil.HadoopInit.(HadoopInit.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance

(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
… 63 more
Caused by: java.io.IOException: java.io.IOException: error=24, Too many open files
at java.lang.UNIXProcess.(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
… 83 more

More often than not this has to do with the default limitation your OS has for concurrent file handles being opened.

Prior to making the changes permanent, you can issue this command:

ulimit -n

The number it gives you is the system’s default. Chances are you’ll need to bump it significantly upward.

You can simply bump this limit by editing the file /etc/security/limits.conf and adding the following lines:

* soft nofile 10000
* hard nofile 10000

Restart your system then issue this command again to ensure the new limit is correct:

ulimit -n

modprobe loop FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory

admin — Fri, 12 Aug 2011 17:16:24 +0000

Ever run into an error message like this?

modprobe loop FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory

If you take a peek into the /lib/modules, what do you see? Do you just see this?

2.6.21-1.3194.fc7

You can just simply create a symlink of 2.6.16-xenU to that to stop the error messages:

cd /lib/modules
ln -s 2.6.16-xenU 2.6.21-1.3194.fc7

/sbin/mingetty[1823]: tty2: No such file or directory

admin — Fri, 12 Aug 2011 17:10:09 +0000

Did you ever get this similar error messages?

Aug 12 12:46:39 ip-10-10-10-99 /sbin/mingetty[1736]: tty2: No such file or directory
Aug 12 12:46:39 ip-10-10-10-99 /sbin/mingetty[1737]: tty3: No such file or directory
Aug 12 12:46:39 ip-10-10-10-99 /sbin/mingetty[1738]: tty4: No such file or directory
Aug 12 12:46:39 ip-10-10-10-99 /sbin/mingetty[1739]: tty5: No such file or directory
Aug 12 12:46:39 ip-10-10-10-99 /sbin/mingetty[1740]: tty6: No such file or directory
Aug 12 12:46:44 ip-10-10-10-99 init: Id “2″ respawning too fast: disabled for 5 minutes
Aug 12 12:46:44 ip-10-10-10-99 init: Id “3″ respawning too fast: disabled for 5 minutes
Aug 12 12:46:44 ip-10-10-10-99 init: Id “4″ respawning too fast: disabled for 5 minutes
Aug 12 12:46:44 ip-10-10-10-99 init: Id “5″ respawning too fast: disabled for 5 minutes
Aug 12 12:46:44 ip-10-10-10-99 init: Id “6″ respawning too fast: disabled for 5 minutes

What I had to do to resolve this was to edit the /etc/inittab file, more specifically this section:

# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

And change that to the following:

# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:off:/sbin/mingetty tty2
3:2345:off:/sbin/mingetty tty3
4:2345:off:/sbin/mingetty tty4
5:2345:off:/sbin/mingetty tty5
6:2345:off:/sbin/mingetty tty6

After making the changes, the cleanest way is to reboot but if you prefer not to then you can run this command:

kill -HUP 1

svn: The repository at ‘‘ has uuid ‘‘, but the WC has ‘‘

admin — Thu, 04 Aug 2011 19:03:16 +0000

If you’ve ever tried to switch your current working copy to a new SVN URL with ‘svn switch –relocate [old_repo] [new_repo]‘ command you may run into an error message similar to this:

svn: The repository at ‘[new_repo]‘ has uuid ‘[new_uuid]‘, but the WC has ‘[old_uuid]‘

The reason for this is that Subversion expects the same repository from the svn switch command and you wouldn’t run into this problem if you had done an svnsync on it.

At any rate, to solve the above error, you must do an svnadmin setuuid [path/to/new/repo] ‘[old_uuid]‘ on your new repo so that the uuid matches. Hope that solves your problem.

Could not find com.google.gwt.dev.Compiler. Make sure you have it in your classpath

admin — Wed, 13 Jul 2011 21:01:32 +0000

If you ever run into an exception similar to the following:

Execution failed for task ‘:common:gwt-utils:gwtCompile’.
at org.gradle.api.internal.tasks.DefaultTaskExecuter.executeActions

(DefaultTaskExecuter.java:66)
at org.gradle.api.internal.tasks.DefaultTaskExecuter.execute(DefaultTaskExecuter.java:43)
at org.gradle.api.internal.project.taskfactory.PostExecutionAnalysisTaskExecuter.execute

(PostExecutionAnalysisTaskExecuter.java:32)
at org.gradle.api.internal.project.taskfactory.ExecutionShortCircuitTaskExecuter.execute

(ExecutionShortCircuitTaskExecuter.java:50)
at org.gradle.api.internal.tasks.SkipTaskExecuter.doExecute(SkipTaskExecuter.java:57)
at org.gradle.api.internal.tasks.SkipTaskExecuter.execute(SkipTaskExecuter.java:35)
at org.gradle.api.internal.tasks.ExecuteAtMostOnceTaskExecuter.execute

(ExecuteAtMostOnceTaskExecuter.java:32)
at org.gradle.api.internal.AbstractTask.execute(AbstractTask.java:231)
at org.gradle.execution.DefaultTaskGraphExecuter.executeTask

(DefaultTaskGraphExecuter.java:167)
at org.gradle.execution.DefaultTaskGraphExecuter.doExecute

(DefaultTaskGraphExecuter.java:160)
at org.gradle.execution.DefaultTaskGraphExecuter.execute

(DefaultTaskGraphExecuter.java:78)
at org.gradle.execution.TaskNameResolvingBuildExecuter.execute

(TaskNameResolvingBuildExecuter.java:113)
at org.gradle.execution.DelegatingBuildExecuter.execute

(DelegatingBuildExecuter.java:54)
at org.gradle.execution.DelegatingBuildExecuter.execute

(DelegatingBuildExecuter.java:54)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages

(DefaultGradleLauncher.java:153)
at org.gradle.initialization.DefaultGradleLauncher.doBuild

(DefaultGradleLauncher.java:107)
at org.gradle.initialization.DefaultGradleLauncher.run

(DefaultGradleLauncher.java:75)
at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:41)
at org.gradle.launcher.RunBuildAction.execute(RunBuildAction.java:27)
at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute

(CommandLineActionFactory.java:209)
at org.gradle.launcher.CommandLineActionFactory$WithLoggingAction.execute

(CommandLineActionFactory.java:193)
at org.gradle.launcher.Main.execute(Main.java:55)
at org.gradle.launcher.Main.main(Main.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke

(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke

(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:46)
at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:28)
at org.gradle.launcher.GradleMain.main(GradleMain.java:24)
Caused by: : Java returned: 1

-or-

Could not find com.google.gwt.dev.Compiler. Make sure you have it in your classpath

..and you’ve explored all options/fixes with no luck, perhaps you may be overlooking one elementary item. Is the project you’re trying to compile sitting in a directory path with spaces? If so, that’s your problem. It’s the age old Unix dislike for spaces in directory.

svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists

admin — Sat, 18 Sep 2010 00:42:46 +0000

Ever gotten this Subversion checkout/update operation error message?

svn: Failed to add directory ‘foo/foo’: an unversioned directory of the same name already exists

You can fix this problem by applying an extra option of “–force” to the SVN’s checkout/update command. This will mark the folder in question as updated and the subfolder files as versioned but will not overwrite any of YOUR files in there.

p4:// “no permission for operation on files(s)” Problem?

admin — Mon, 13 Sep 2010 23:04:33 +0000

If you ever tried to do an integration activity in Perforce and have gotten a similar error message such as “no permission for operation on files(s)” then these are the steps you can do to resolve the problem:

Check to make sure your branch spec or the source/target does not have any typo.
Check to make sure you are branching within a source tree such as //softwareX/branches/1.0/… //softwareX/branches/1.1/… and NOT //softwareX/branches/1.0/… to //softwareY/branches/1.1/…
Check p4 protect to make sure your account has write permission within that code line.