Counterclockwise 0.12.4 Progress

[Laurent PETIT]

Hello,

Recent progress on Counterclockwise:

https://github.com/laurentpetit/ccw/blob/master/ChangeLog.md

You can test these changes by referencing and upgrading from the
Software Update Site created by build 73 of Travis of Git Commit
f07af4521ba502b54f3156dc195aba803da9c618 , namely:

http://updatesite.ccw-ide.org/branch/master/master-travis000073-gitf07af4521ba502b54f3156dc195aba803da9c618/

Yes, there's a pattern here. Refer to the ChangeLog to learn more.

Cheers,

--
Laurent

[Laurent PETIT]

Hello Anand,

2013/6/30 Anand Prakash <anand....@gmail.com>:
> Thx Lauren.
>
> Needed your help with something. We are currently running 0.12.3.STABLE001.
> Its been working great for me, except one of my friends gets DestroyJVM and
> the process doesn't start and he need to clean multiple times before it
> starts.

What do you mean by "gets DestroyJVM"?

>
> I was wondering if there is any setup more stable than 0.12.3.STABLE001. If
> yes, then is it on selfcontained ccw-ide or using the new update-site.

I'm not sure the issue your friends is getting will get more stable
support in the current selfcontained ccw-ide.

Would it be possible for you to send his .workspace/.metadata/.log log
file after such a problem occurs ? I'd like to check the symptoms, to
see it those are the same that have been reported from time to time
during the first semester?

(If so, I may have a fix within reach, btw).

Cheers,

--
Laurent


>
> Thanks
> Anand

> --
> You received this message because you are subscribed to the Google Groups
> "counterclockwise-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojuredev-use...@googlegroups.com.
> To post to this group, send email to clojured...@googlegroups.com.
> Visit this group at http://groups.google.com/group/clojuredev-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Laurent PETIT]

Hmm, there is a timeout after which CCW will kill the process,
considering something was wrong. On 0.12.3, it is set to 30sec. It's
been increased to 60sec on the leiningen branch, and will be available
tomorrow in the master branch when I have cherry-picked it.

Could this explain that it sometimes works, sometimes does not work?

2013/7/3 Anand Prakash <anand....@gmail.com>:
> Hi Lauren
> Thanks for the reply.
>
> When I start REPL from eclipse and look at the debug window, I see following
> processes.
> 1. Thread [main] (Running)
> 2. Thread [clojure-agent-send-off-pool-*] - 6 instances
>
> When it's not going to work I see a thread called DestroyVM. If it's going
> to work I see threads nREPL-worker-* and others.
>
> Whenever I see the DestoryVM thread, the server doesn't start. However if I
> do Project->Leiningen->Update Dependencies - it works every single time. I
> am starting to see this issue on my machine too.
>
> Does this help. I will try to send relevant snippet from .log, once I face
> this problem again.
>
>
> Thanks
> Anand

[Laurent PETIT]

Le mercredi 3 juillet 2013, Anand Prakash a écrit :

Hi Lauren

Thanks. This makes sense. The weird problem here is that the same jetty server starts within 2-3 seconds from commandline with 'lein run', however sometimes it takes more than 30 seconds to start on eclipse through counter-clockwise. Any theories.

I agree that the difference is weird. I have no theory yet to explain it. But should definitely take some time to reproduce and think about it. 

Anyway, this seems to confirm the timeout explanation ? And that a quick fix would be to increase to 60 secs fwiw?

 

Thanks

Anand