Adobe Community: CRXDE 1.0.1 issues with CQ5.5

Currently Being Moderated

1. Davide G,

Mar 14, 2012 8:53 AM in reply to Murali Vusthipalli

Report

Hi Murali,

Try deleting your .~/.crxde directory before starting it up.

I simply started CRX101 with CQ55 without incurring in major issues.

HTH

Davide

|

Mark as:

Currently Being Moderated

2. Murali Vusthipalli,

Mar 14, 2012 10:27 AM in reply to Davide G

Report

I have done that many times to fix the issues with CRXDE, but forgot this time some how Thaks for the information, Davide.

|

Mark as:

Currently Being Moderated

3. Murali Vusthipalli,

Mar 15, 2012 7:45 PM in reply to Murali Vusthipalli

Report

I started CQ5.5 in debug mode using the command: java -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=30303,suspend=n -jar cq-author-4502.jar. Then I opened CRXDE to start debugging. But it shows "Attach Debugger" as disabled still. Usually, I used to see this is enabled after starting the earlier versios of CQ-5.4, 5.3 in debug mode. Can any one help with this?

Also, are there any steps available to start debugger with Eclipse, RAD, netbeans etc.,?

|

Mark as:

252 posts
Nov 24, 2010

Currently Being Moderated

4. Justin Edelson,

Mar 15, 2012 7:51 PM in reply to Murali Vusthipalli

Report

Murali-

If you take a look of the console output of that java command, does it say "Will fork a JVM to get enough memory"? If so, the forked Java process will not get your debug parameters.

Debugging in Eclipse, RAD, NetBeans, etc. is just a matter of starting a remote debugger pointing to port 30303.

HTH,

Justin

|

Mark as:

Currently Being Moderated

5. Murali Vusthipalli,

Mar 15, 2012 8:01 PM in reply to Justin Edelson

Report

Hi Justin,

Here is the below output of the command. Though I provided -Xmx1024m, it is still complaining the same, could you please help? Thank you so much!

|

Mark as:

252 posts
Nov 24, 2010

Currently Being Moderated

6. Justin Edelson,

Mar 15, 2012 8:05 PM in reply to Murali Vusthipalli

Report

Murali-

Something's fishy here. You're passing -Xmx1024m, but the JVM is reporting a heap size of 910 MB and, as a result, forking. I don't know why that would be. You could either give the JVM more memory or pass -nofork to suppress the forking behavior.

Also, I see you are running on Java 7. That is not supported. See http://dev.day.com/docs/en/cq/current/deploying/technical_requirements .html

Maybe this is why it isn't supported

Justin

|

Mark as:

Currently Being Moderated

7. Murali Vusthipalli,

Mar 15, 2012 8:16 PM in reply to Justin Edelson

Report

Justin, the documentation says that "JRE or JDK 1.5 (or higher)". So I thought JDK 1.7 would work. I have tried with -nofork option, but it is still reporting the same error. I will also give a try with JDK1.5 and see if that works.

Thank you very much for your help

|

Mark as:

252 posts
Nov 24, 2010

Currently Being Moderated

8. Justin Edelson,

Mar 15, 2012 8:19 PM in reply to Murali Vusthipalli

Report

If you scroll further down, you'll see where Oracle JRE 1.7 isn't supported.

Justin

|

Mark as:

Currently Being Moderated

9. Murali Vusthipalli,

CQ5

CRXDE 1.0.1 issues with CQ5.5

Mar 14, 2012 7:29 AM

More Like This

Bookmarked By (0)

Answers + Points = Status