Liferay ant deploy failed - deployment

I am trying to deploy my first "hello-world"-portlet for Liferay
but I get a "BUILD FAILED" when deploying it.
My folders look like this:
D:\[Code Home]\bundles\liferay-portal-6.2-ce-ga2
and
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\portlets
My build.[username].properties file contains this:
app.server.portal.dir = D:\\[Code Home]\\bundles\\liferay-portal-6.2-ce-ga2\\tomcat- 7.0.42\\webapps\\ROOT
app.server.lib.global.dir = D:\\[Code Home]\\bundles\\liferay-portal-6.2-ce-ga2\\lib\\ext
app.server.deploy.dir = D:\\[Code Home]\\bundles\\liferay-portal-6.2-ce-ga2\\tomcat-7.0.42\\webapps
app.server.type = tomcat
app.server.dir = D:\\[Code Home]\\bundles\\liferay-portal-6.2-ce-ga2\\tomcat-7.0.42
When deploying the portlet I get this:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\portlets>ant deploy
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; sup
port was removed in 8.0
Buildfile: D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\portlets\build.xml
deploy:
BUILD FAILED
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common-plugins.xml:57: The
following error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:1387: The follow
ing error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:1392: The follow
ing error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:235: The followi
ng error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:993: The followi
ng error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:299: The followi
ng error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:1766: The follow
ing error occurred while executing this line:
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\build-common.xml:175: D:\[Code Ho
me]\bundles\liferay-portal-6.2-ce-ga2\lib\ext does not exist.
Total time: 0 seconds
D:\[Code Home]\plugins\liferay-plugins-sdk-6.2\portlets>
any idea where the problem is?

Seems you are missing auto.deploy.dir value.
Here is my build.properties values.
app.server.type=tomcat
app.server.parent.dir=/home/maleen/workspace/liferay
app.server.tomcat.dir=${app.server.parent.dir}/tomcat-7.0.40
app.server.tomcat.deploy.dir=${app.server.tomcat.dir}/webapps
app.server.tomcat.lib.global.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.portal.dir=${app.server.tomcat.dir}/webapps/ROOT
auto.deploy.dir=${app.server.parent.dir}/deploy
Hope this helps.

The error message says
D:\[Code Home]\bundles\liferay-portal-6.2-ce-ga2\lib\ext does not exist.
Does it? If not: You need to either create it (e.g. unzip a bundle at that location) or configure your build.username.properties - what's this?
Look at build.properties - you'll find many values configured in there. Just like with other property files in Liferay, you should identify the value that you want to change from the default, create a file named build.username.properties (replace with your actual username) and override the value that you'd like to change - e.g. app.server.parent.dir is a good candidate to point to your unzipped bundle.
Note that Java8 is not yet officially supported by Liferay: This is a portal that runs on so many existing application server that it's a bit slower in adopting new environments. That's not to say that it won't work - only if you run into Java8 related problems, you might want to try Java7, and be slow to adopt the new features so that you can easily backport.

Related

Error runing mftf in Magento 2.3.5 I get an error on build:project

First time eveer runing mftf I installed with composer with in a m2 2.3.5 and when I run the build I get this message:
mftf build:project
mftf files removed from filesystem.
codeception.yml applied to /var/www/html/dev/tests/acceptance/codeception.yml
functional.suite.yml configuration successfully applied.
functional.suite.yml applied to /var/www/html/dev/tests/acceptance/tests/functional.suite.yml
command.php copied to /var/www/html/dev/tests/acceptance/utils/command.php
.credentials.example successfully applied.
.env configuration successfully applied.
In Configuration.php line 212:
Output path is not defined by key "paths: output"
In BuildProjectCommand.php line 105:
The codecept build command failed unexpectedly. Please see the above output for more details.
Any ideas what can be ?

Error upgrading Jasperreports server from 7.2 to 7.5 (keystore problem)

The upgrade procedure is pretty simple and well documented. I have been upgrading jasperreports server since version 4 always using the same procedure (buildomatic).
Now, in 7.5 version I get
java.lang.RuntimeException: KeystoreManager was never initialized or
there are errors while instantiating the instance.
Failed to instantiate
[com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure
that create-keystore was executed;
Error creating bean with name 'keystoreManager': Invocation of init
method failed;
Error creating bean with name 'passwordEncoder': Unsatisfied
dependency expressed through field 'keystoreManager';
The keystore is in /root folder, as it should.
Have you tried the process mentioned in this link https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75
"If the JasperReports Server cannot find the keystore files - maybe because of permissions as noted above, you will get an exception on server start like:
Failed to instantiate [com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure that create-keystore was executed; nested exception is java.lang.RuntimeException: KeystoreManager was never initialized or there are errors while instantiating the instance.
To fix this, you need to move the keystore files into a directory that is accessible by the user running the web app process. See Updating keystore files below."

Could not find or load main class Files.Microsoft while starting GlassFish 4.0

I am trying to start glassfish, but all the time get this error
PS C:\glassfish4\bin> ./asadmin start-domain mydomain
Waiting for mydomain to start .Error starting domain mydomain.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:
Error: Could not find or load main class Files.Microsoft
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=192m; support was removed in 8.0
Command start-domain failed.
Maybe you have any ideas how to solve this issue? I have found nothing about such an error in the internet.
Thank you in advance!

Endeca baseline update is failing: SEVERE: Utility 'rmdir_dgraph-input-old' failed

Baseline update on endeca is failing. Please find the logs below:
INFO: Finished pushing content to dgraph.
INFO: [AuthoringMDEXHost] Starting shell utility 'rmdir_dgraph-input-old'.
INFO: [LiveMDEXHostA] Starting shell utility 'cleanDir_local-dgraph-input'.
INFO: [LiveMDEXHostA] Starting shell utility 'rmdir_dgraph-input-old'.
SEVERE: Utility 'rmdir_dgraph-input-old' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host LiveMDEXHostA.
Occurred while executing line 7 of valid BeanShell script:
AuthoringDgraphCluster.copyIndexToDgraphServers();
AuthoringDgraphCluster.applyIndex();
LiveDgraphCluster.cleanDirs();
LiveDgraphCluster.copyIndexToDgraphServers();
LiveDgraphCluster.applyIndex();
SEVERE: Error executing valid BeanShell script.
Occurred while executing line 19 of valid BeanShell script:
Dgidx.run();
// distribute index, update Dgraphs
DistributeIndexAndApply.run();
// Upload the generated dimension values to Workbench
WorkbenchManager.cleanDirs();
SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.utility.Utility run - Utility 'rmdir_dgraph-input-old' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host LiveMDEXHostA.
INFO: Released lock 'update_lock'.
Has anyone seen this type of error before? Please let me know the potential solution. Also Baseline update is taking 2 to 3 hours and then it's failing, it's annoying.
Thanks!
Check logs under
endeca/PlatformServices/workspace/logs/shell
There should be a log named like appName.rmdir_dgraph-input-old.log
with more info about the error.
Probably a non existing folder is trying to be removed or something like that.
If this is the case just create the folder that the utility is trying to remove and execute baseline again.

forgerock openam ssoadm STS configuration error while running create-sub-cfg

I am getting the following exception while running ssoadm's create-sub-cfg on forgerock openam13 version. I would appreciate any leads or hints to resolve this. Thanks
Command:
create-sub-cfg --servicename RestSecurityTokenService --subconfigname "test" --realm myrealm --datafile mydir1/my_realm_sts_attrs.properties
Exception:
Executing class, com.sun.identity.cli.schema.AddSubConfiguration.
com.sun.identity.cli.CLIException: Message:Unable to add subConfig test
at com.sun.identity.cli.schema.AddSubConfiguration.addSubConfigToRealm(AddSubConfiguration.java:150)
at com.sun.identity.cli.schema.AddSubConfiguration.handleRequest(AddSubConfiguration.java:103)
at com.sun.identity.cli.SubCommand.execute(SubCommand.java:296)
at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:217)
at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:139)
at com.sun.identity.cli.CommandManager.serviceRequestQueue(CommandManager.java:576)
at com.sun.identity.cli.CommandManager.<init>(CommandManager.java:173)
at com.sun.identity.cli.CommandManager.main(CommandManager.java:150)
Caused by: Message:Unable to add subConfig test
at com.sun.identity.sm.ServiceConfig.addSubConfig(ServiceConfig.java:343)
at com.sun.identity.cli.schema.AddSubConfiguration.addSubConfig(AddSubConfiguration.java:228)
at com.sun.identity.cli.schema.AddSubConfiguration.addSubConfigToRealm(AddSubConfiguration.java:131)
... 7 more
Unable to add subConfig test
Command process exited with value 127
You might want to have a look at OPENAM-8006
You probably need to replace:
--subconfigname "test"
with
--subconfigid "test"