[
https://issues.apache.org/jira/browse/CLOUDSTACK-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575640#comment-13575640
]
ASF subversion and git services commented on CLOUDSTACK-1181:
-------------------------------------------------------------
Commit a0341d1ce4a6f869ef3dc0fa759efdd744fdef83 in branch refs/heads/4.1 from
[~bhaisaab]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=a0341d1 ]
CLOUDSTACK-1181: Fix Environment so db.properties is in classpath
We export CATALINA_HOME to utils/ which is the path which a lot of utils class
would
check and read db.properties file. This is exactly what is done in production.
The utils classes (Transaction, Encryption*Checker etc.) would use
PropertiesUtil
which tries to find it in CATALINA_HOME.
The only issue is, even if someone defined an override file, the encryption type
would be still read from the db.properties file. For all other params, the
override
file would be re read and datastores would be reinitialized
BUG-ID: CLOUDSTACK-1181
Signed-off-by: Rohit Yadav <bhais...@apache.org>
(cherry picked from commit 23f7267753c3a1b05e61e04b2e8c3f24c54d6975)
Signed-off-by: Rohit Yadav <bhais...@apache.org>
> mvn deploy db failing with NPE
> ------------------------------
>
> Key: CLOUDSTACK-1181
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1181
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Fresh CS 4.1.0 installation and db deployment
> Reporter: Venkata Siva Vijayendra Bhamidipati
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> The check for the encryption property in the db.properties file in
> Transaction.java calls into check() in EncryptionSecretKeyChecker.java, and
> that fails to find the db.properties file. It looks like the full path of the
> db.properties file (or the db.properties.override file) is not being sent to
> the check() function.
> This is the output (with exception stack) of the deploydb:
> [root@RichActon3-CC2 incubator-cloudstack]# mvn -e -P developer -pl developer
> -Ddeploydb
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
> (default) @ cloud-developer ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
> cloud-developer ---
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
> [INFO] Executing tasks
> main:
> [INFO] Executed tasks
> [INFO]
> [INFO] >>> exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer >>>
> [INFO]
> [INFO] <<< exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer <<<
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer ---
> [WARNING]
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.ExceptionInInitializerError
> at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:159)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at java.io.FileInputStream.<init>(FileInputStream.java:133)
> at
> com.cloud.utils.crypt.EncryptionSecretKeyChecker.check(EncryptionSecretKeyChecker.java:65)
> at com.cloud.utils.db.Transaction.<clinit>(Transaction.java:101)
> ... 7 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 13.052s
> [INFO] Finished at: Wed Feb 06 13:19:28 PST 2013
> [INFO] Final Memory: 19M/47M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java
> (create-schema) on project cloud-developer: An exception occured while
> executing the Java class. null: InvocationTargetException:
> ExceptionInInitializerError: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on
> project cloud-developer: An exception occured while executing the Java class.
> null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An exception
> occured while executing the Java class. null
> at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:352)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.ExceptionInInitializerError
> at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:159)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at java.io.FileInputStream.<init>(FileInputStream.java:133)
> at
> com.cloud.utils.crypt.EncryptionSecretKeyChecker.check(EncryptionSecretKeyChecker.java:65)
> at com.cloud.utils.db.Transaction.<clinit>(Transaction.java:101)
> ... 7 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [root@RichActon3-CC2 incubator-cloudstack]#
> Workaround for now:
> Revert commit# b1d70f7fe340302f180843c01ee6674166d03ee1
> The fix would be to locate the db.properties file correctly in the call to
> enc.check();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
