Posts in Category "Startup"

CQ5.5 SP2.1: First deployment of system bundle fragment leads to server shutdown

Issue

If you are deploying a system bundle fragment for the 1st time to CQ, you may notice that the CQ server shuts down.

Solution

This issue is fixed in later CQ versions.  If you have an M&S contract and require an urgent hotfix for this in CQ5.5 SP2.1 you should contact Daycare support.

Workaround

Restart the CQ instance manually and everything should work as normal.

reference: (44186/NPR-2555)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

CQ5.5: javax.jcr.RepositoryException: Unable to register data store in cluster

Issue

If you are installing and starting a new CQ instance you may experience the following exception:

*ERROR* [FelixStartLevel] org.apache.jackrabbit.core.RepositoryImpl failed to start Repository: Unable to register data store in cluster.
javax.jcr.RepositoryException: Unable to register data store in cluster.

Caused by: java.net.UnknownHostException: <server_hostname>: <server_hostname>
at java.net.InetAddress.getLocalHost(InetAddress.java:1360)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:211)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:218)
… 56 more

Reason

This typically happens if the name returned by the “hostname” command cannot be resolved.

Solution

Add the following entry to /etc/hosts (replacing <server_hostname> with the hostname of the server where the CQ instance is running):

127.0.0.1 <server_hostname>

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.8/10 (5 votes cast)

CQ5.5: NullPointerException for wcm-mobile-core after installing SP1 or SP2.1

Issue

If you have installed CQ 5.5 SP1 or SP2.1 and restarted the instance you may notice the following exception in the logs on startup:

ERROR [Background Update com.day.cq.wcm.cq-wcm-mobile-core (219)] com.day.cq.wcm.cq-wcm-mobile-core [com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter]
The bindStats method has thrown an exception (java.lang.NullPointerException) java.lang.NullPointerException
at com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter.bindStats(RedirectFilter.java:173)
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.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:227)
at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:38)
at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:591)
at org.apache.felix.scr.impl.helper.BaseMethod$NotResolved.invoke(BaseMethod.java:548)
at org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:472)

Reason

This error is caused by an issue in the mobile redirect servlet in SP1 and SP2.1.  It will only affect this servlet, which gathers usage statistics on various categories of mobile devices.

Solution

If you do not require a fix for this servlet you can ignore this error.  The issue is currently scheduled to be fixed in the next service pack for CQ5.5.  If you require an urgent solution to this issue you can contact support through Daycare.

reference: (CQ5-18788/NPR-2071)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

CQ5.5: how to start the server in debug mode

Issue

In CQ5.4 you could start the server in debug mode using the [CQ_HOME]/crx-quickstart/server/server.bat file.  The server folder is no longer there in CQ5.5 on Windows.

Solution

To start the server in debug mode you can edit the [CQ_HOME]/crx-quickstart/bin/start.bat file and add the same debug parameters from a server.bat in an existing CQ5.4 installation, or you can use the command line below:

java -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=30303,suspend=n -jar cq-author-4502.jar

Notes

You may notice that the “Attach Debugger” entry in the CRXDE menu is still disabled even after starting the server in debug mode.  You should analyse the console output on server startup to check for issues related to heap/memory problems which may result in a new process being forked.  The debug options used to start the parent JVM are not passed on to the forked process by default.

You can resolve this by adding more heap to the JVM, and/or by specifying the -nofork command line option to prevent forking.  You can also force the forked process to use the parent JVM parameters by specifying the -forkargs [<arg>...] command line option.

You can find more information on the options mentioned above, and other server startup options under the following link:

http://dev.day.com/docs/en/cq/current/deploying/installing_cq.html#Further%20options%20available%20from%20the%20Quickstart%20file

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.7/10 (7 votes cast)