Can't start cq5 service under windows 7 64bit - service

One year ago I installed successfully CQ5 as a windows service under Windows 7 32bit. After that I've switched to Windows 7 64bit. Currently I have a project using CQ5 so I install again it (under Window 64bit). CQ5 starts fine with crx-quickstart/bin/start.bat using command line. Also I don't see any problem when installing as service with the command instsrv.bat cq5:
Installing service cq5
runs in E:\servers\cq5-server\author\crx-quickstart
uses E:\servers\cq5-server\author\crx-quickstart\opt\helpers\\..\..\app\cq-quickstart-5.5.0-standalone.jar
starts org.apache.sling.launchpad.app.Main
redirects output to: E:\servers\cq5-server\author\crx-quickstart\logs\startup.log
But when I run net start cq5, I get an error as below:
The cq5 service is starting.
The cq5 service could not be started.
A service specific error occurred: 0.
More help is available by typing NET HELPMSG 3547.
And checking log file commons-daemon.2013-09-01.log, I see:
[2013-09-01 23:26:36] [info] Commons Daemon procrun (1.0.8.0 64-bit) started
[2013-09-01 23:26:36] [info] Running 'cq5' Service...
[2013-09-01 23:26:36] [info] Starting service...
[2013-09-01 23:26:36] [error] Failed creating java
[2013-09-01 23:26:36] [error] The system cannot find the file specified.
[2013-09-01 23:26:36] [error] ServiceStart returned 1
[2013-09-01 23:26:36] [error] The system cannot find the file specified.
[2013-09-01 23:26:36] [info] Run service finished.
[2013-09-01 23:26:36] [info] Commons Daemon procrun finished
Could anyone let me know what I'm wrong?
I'm following the instructions at Installing and Starting Adobe Experience Manager as a Windows Service

I've set up JDK by copying java folder from another computer and setting the environment variable JAVA_HOME. So maybe something is missing in registry.
Below is how to fix the problem:
First follow correctly the first 3 steps in the instructions at Installing and Starting Adobe Experience Manager as a Windows Service. (In my case, I used prunsrv_amd64 to replace prunsrv)
Edit again the bat file instsrv.bat by changing
:: path to a jvm.dll or "auto"
set jvm_path="auto"
to
:: path to a jvm.dll or "auto"
set jvm_path="%JAVA_HOME%\jre\bin\server\jvm.dll"
Finally run instsrv.bat CQ5 under \crx-quickstart\opt\helpers
P/S: This way also does help in case of Windows XP 32bit (I've tested)!

You need to modify the instsrv script to use the 64 bit prunsrv.exe. You'll just want to open up the script and change all prunsrv commands to prunsrv_amd64 or prunsrv_ia64.

Related

Jrebel not initializing for embedded tomcat

I have been unable to get Jrebel to run. I am running a Hippo Java project on mac with the Eclipse plugin. I run the project using mvn from a command line (not through the eclipse IDE). I have followed these instructions for Hippo and JRebel
I have located the JRebel Eclipse plugin files here:
/Applications/Eclipse.app/Contents/Eclipse/plugins
From here I copied the contents of
org.zeroturnaround.eclipse.embedder_6.5.0.RELEASE/jrebel/
which contains 2 files: jrebel.jar and jrebel.plugininfo
I put these copies into a created directory ~/Tools/jrebel and pointed the environment variable REBEL_HOME to it.
export REBEL_HOME=~/Tools/jrebel
When I echo $REBEL_HOME I get the correct path. When I cd to that path and ls I get the 2 files.
In my hippo project, from the command line I run
mvn clean verify -Djrebel
I get build success. Then I run
mvn -Pcargo.run -Djrebel
This gives the error:
[INFO] [talledLocalContainer] Error opening zip file or JAR manifest missing : ${env.REBEL_HOME}/jrebel.jar
[INFO] [talledLocalContainer] Error occurred during initialization of VM
[INFO] [talledLocalContainer] agent library failed to init: instrument
I have read here to specify the path of jrebel.jar to -javaagent , but I don't know what this means or how to do it?
Hippo has built in JRebel configurations in the pom.xml. These should be activated with the -Djrebel flag. Why isn't this working?
The error shows that in that process REBEL_HOME isn't defined. I don't see anything wrong with what you did here so there may be some peculiarity to your local setup or to MacOS (I'm not a mac user). In any case your environment variable is not being passed to the process.
Everything you said works for me on Linux (Mint).
You can try setting the property in the cargo profile.
Or you could set the variable in your global environment.

Error while Deploying WAR in WebSphere using ANT

We are trying to checkout, build and deploy EAR files ( IBM Integration Designer developed Mediation Modules.. but mostly similar to Java EAR files ). While deploying to WAS ND I am getting the below error...
[wsadmin] WASX7017E: Exception received while running file "C:\Users\INSTAL~2\AppData\Local\Temp\wsant1588202279705404612jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7132E: Application install for C:\Ant_Automation\ESB\MMCheckout\KY_SF1520_CPRServices_MMApplication\KY_SF1520_CPRServices_MM.ear failed: see previous messages for details.
[wsadmin] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
BUILD FAILED
C:\Ant_Automation\ESB\build.xml:124: Java returned: 105
Total time: 1 minute 53 seconds
I think we have to save the configuration after deployment in a ND deployment, but I am not sure how we can save using ANT.
DMGR System log
[28-06-16 16:43:13:572 CEST] 000003ef InstallSchedu I ADMA5016I: Installation of KY_SF1520_CPRServices_MMApp started.
[28-06-16 16:43:14:384 CEST] 000003ef Configuration I com.ibm.bpm.config.spi.ConfigurationSpi getDeploymentEnvironment Effective deployment target is WebSphere:cell=KYDevBMP02Cell01,node=KYDevBMP02CellManager01,server=dmgr
[28-06-16 16:43:14:400 CEST] 000003ef Configuration I com.ibm.bpm.config.spi.ConfigurationSpi getDeploymentEnvironment Effective deployment target is WebSphere:cell=KYDevBMP02Cell01,node=KYDevBMP02CellManager01,server=dmgr
[28-06-16 16:43:14:493 CEST] 000003ef WBIAAbstractT I com.ibm.ws.wbia.deployment.WBIAAbstractTask performTask CWLRD0101I: No WebSphere Business Integration Adapter files are found in the application KY_SF1520_CPRServices_MMApp.
[28-06-16 16:43:15:134 CEST] 000003ef Configuration I com.ibm.bpm.config.spi.ConfigurationSpi getDeploymentEnvironment Effective deployment target is WebSphere:cell=KYDevBMP02Cell01,node=KYDevBMP02CellManager01,server=dmgr
[28-06-16 16:43:15:149 CEST] 000003ef InstallSchedu I ADMA5014E: The installation of application KY_SF1520_CPRServices_MMApp failed.
You don't need to save if you are using , check this link for Ant script example Using Ant scripts for testing in headless WebSphere Business Process Manager
You have to look for error details either in the Ant console output or server SystemOut.log.
Look at your messages:
Effective deployment target is WebSphere:cell=KYDevBMP02Cell01,node=KYDevBMP02CellManager01,server=dmgr
This is not correct, you are installing application to either Cluster of some server, but for sure not DeploymentManager.
You have to provide options to your wsInstallApp task that will define target. See AdminApp.install command for details.

Issues with installing of plugins for Jenkins

SOLUTION
After I defined the proxy settings, it started working. See the documentation: Jenkins Behind Proxy->How Jenkins handles Proxy Servers.
I want to set up my CI environment (hosted on a Windows 2008 Server) with Jenkins. I installed Jenkins from a binary using the Jenkins Installer and can call it in the browser with localhost:8080.
Now I want to install some plugins, but there are multiple issues:
When I try it via the Jenkins CLI (e.g. java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin git):
$ java -jar jenkins-cli.jar -s http://localhost:8080 install-plugin crap4j
crap4j is neither a valid file, URL, nor a plugin artifact name in the update center
No update center data is retrieved yet from: http://updates.jenkins-ci.org/update-center.json
crap4j looks like a short plugin name. Did you mean ▒null▒?
Apr 04, 2016 3:32:46 PM hudson.remoting.RemoteInvocationHandler$Unexporter run
WARNING: Couldn't clean up oid=3 from null
hudson.remoting.ChannelClosedException: channel is already closed
at hudson.remoting.Channel.send(Channel.java:578)
at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.cleanup(RemoteInvocationHandler.java:360)
at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.access$700(RemoteInvocationHandler.java:319)
at hudson.remoting.RemoteInvocationHandler$Unexporter.run(RemoteInvocationHandler.java:420)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException
at hudson.remoting.Channel.close(Channel.java:1163)
at hudson.remoting.Channel.close(Channel.java:1138)
at hudson.cli.CLI.close(CLI.java:329)
at hudson.cli.CLI._main(CLI.java:511)
at hudson.cli.CLI.main(CLI.java:390)
Since I could not resolve this
Well, I tried to install the plugins via the Jenkins GUI -- but the content of the tab "Available" in "Manage Pligins" is empty.
OK, last chance: manual installation. So I did it as in the docu shown: Went to the list of the plugins on wiki.jenkins-ci.org, downloaded the plugins, put them to $JENKINS_HOME/plugins, and restarted Jenkins (java -jar jenkins-cli.jar -s http://localhost:8080/ restart).
Totally there are 11 plugins I instaled (or tried to). For all the plugins have been plugin folders automatically created in $JENKINS_HOME/plugins (e.g. $JENKINS_HOME/plugins/git). But: Some of the plugins (Clover PHP, Crap4J, JDepend, Plot, Violations, and xUnit) are shown now in the liste ot the installed plugins -- and the other (Git, HTML Publisher, DRY, PMD) not.
Is it possible, that these plugins are installed and just not displayed? Why? How to check this?
How to get the plugins installed?

Activator from guest OS

I'm working on a project that is being converted from Groovy and Grails to Play Framework using Scala.
The app includes integration with native windows libraries, but I do my primary development on OSX only switching over to a Windows guest when I run the full app or tests that are dependent on the native libraries.
Using this setup the project files exist on the host file system and are shared with the Windows guest as a shared folder. This setup worked flawlessly for Grails development, but with the switch to Play Framework and Activator I'm encountering a java.io.IOException: incorrect function error when attempting to execute run via activator.
I can successfully compile and run tests. Additionally, I can successfully create and run new play projects from the guest, just can't run the project from the hosts shared folder. Any ideas how to resolve this?
I'm using the latest play framework download as of yesterday. So Play v2.4.3 with Activator v1.3.6. The project was created by running "activator new" and selecting the play-scala template. No changes were made to the template. The host OS is OSX and the guest OS is Windows 7. Java SDK 1.8.0_65
The activator run stacktrace:
[freshproject] $ run
java.io.IOException: Incorrect function.
at sun.nio.fs.WindowsWatchService$Poller.implRegister(WindowsWatchService.java:407)
at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260)
at sun.nio.fs.WindowsWatchService$Poller.run(WindowsWatchService.java:533)
at java.lang.Thread.run(Thread.java:745)
[trace] Stack trace suppressed: run last compile:run for the full output.
[error] (compile:run) java.io.IOException: Incorrect function.
[error] Total time: 0 s, completed Oct 28, 2015 6:30:56 AM
[freshproject] $ last compile:run
java.io.IOException: Incorrect function.
at sun.nio.fs.WindowsWatchService$Poller.implRegister(WindowsWatchService.java:407)
at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260)
at sun.nio.fs.WindowsWatchService$Poller.run(WindowsWatchService.java:533)
at java.lang.Thread.run(Thread.java:745)
[error] (compile:run) java.io.IOException: Incorrect function.

Jboss log manager error

I am trying to start up JBoss with parameters in Windows but getting some errors. If I remove parameters than JBoss startup iwht no errors. Could some one please take a look.
environment variables:
JAVA_HOME=C:\Java\jdk1.6.0_45
JBOSS_HOME=C:\bin\jboss-eap-6.1
Path=C:\Java\jdk1.6.0_45\bin;C:\WINDOWS\system32;
start up jboss with following parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
"
Error:
WARNING: failed to load the specified log manager class org.jboss.logmanager.LogManager
Error: Operation <"parallel-extension-add"> failed - address:<[]>
java.lang.RuntimeException: failed initializing module org.jboss.as.logging
==========================================================================
so to fix the error above. I have added logmanager parameter below.
start up jboss using parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
​"
ERROR:
Could not load Logmanager "org.jboss.logmanager.LogManager"
java.lang.ClassNotFoundException: org.jboss.logmanager.logManager
==========================================================================
so to fix error above. I have added -xbootclasspath parameter.
start up jboss using parameters:
set "JAVA_OPTS=%JAVA_OPTS%
-Djava.util.logging.manager=org.jboss.logmanager.LogManager"
-Xbootclasspath:C:\bin\jboss-eap-6.1\modules\system\layers\base\org\jboss\logmanager\main\jboss-logmanager-1.4.0.Final-redhat-1.jar
-Djava.rmi.server.hostname=myhost
-Dcom.sun.management.jmxremote.port=myport
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=C:\Java\jdk\jre\lib\management\jmx.password
-Dcom.sun.management.jmxremote.access.file=C:\Java\jdk\jre\lib\management\jmx.access
​"
ERROR:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
and now I have no idea what to do. I have tried reinstalling jdk but no luck.
when I enter "java -version" in CMD. Than I get result: "1.6.0_45". So I know jdk is set up. but when I start Jboss than jdk is not initialization.
To resolve this, do the following:
Go to the JBOSS_HOME location on the file system e.g. c:\jboss\appserver\jboss-eap-6.3, look in the bin folder and open the configuration file named, standalone.conf, in a text editor.
At the top of the file, add the following line - JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager".
Scroll-down the file, to where JVM options are specified and add the following two options:
JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.5.2.Final-redhat-1.jar"
Note: You may need to modify the exact path to the logmanager jar file, as the one on your jboss installation may differ from what applies here. The JBoss EAP version being used in this case was 6.3.0GA. A different version may have a different path to the logmanager jar file.
Simply save the modified 'standalone.conf' file, with these couple of changes, and re-attempt starting up of the JBoss App server (either on the CLI or within Eclipse).
Note: For fixing the issue for a JBoss EAP appserver instance running just within Eclipse, simply open the server's launch configuration and add the 2 JVM options to the VM arguments of the launch configuration, as shown in the screenshot below:
Voila! The startup issue with regards to failure to load the LogManager, should be resolved.
Check this blogpost for details and screenshots - http://obinnakalu.blogspot.com/2014/10/jboss-enterprise-application-platform.html
Although this is an old post, but if someone is still facing the issue:
-Xbootclasspath:C:\bin\jboss-eap-......
Above line replaces bootclasspath and now jvm will use only the specified jar to boot.
Use -Xbootclasspath\a:C:\bin\jboss-eap-......
instead. This will append the mentioned jar to existing bootclasspath.
For Jboss 7.1.1 I have solved this issue by adding following lines in standalone.conf.bat. All the jars are taken from JBoss 7.1.1 modules folder
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:E:/jboss-logmanager-1.2.2.GA.jar;E:/jboss-logmanager-log4j-1.0.0.GA.jar;E:/log4j-1.2.16.jar"