search

wjw465150 / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Undeterminable behavior of RJR depending on Eclipse>run and Eclipse>debug #111

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Besides the problems of issue 87 I had some hard days working on an issue 
related to whether you start RJR with Eclipse>run and Eclipse>debug.

I'm using tapestry5 and the new Eclipse maven plugin together with the latest 
RJR.

When "debugging" my mavenized tapestry5 app everything works as supposed. I can 
send out mails, use my database with hibernate, etc.

But when I start the same tapestry5 app with Eclipse>run then mails arent't 
delivered. The app simply stops without response in the transport.send() method 
of the mail API, or it stops in the UUID.randomUUID(), or it stops before the 
schema of my database is beeing deployed in hibernate.

This is really strange! In "debug-mode" everything works fine. In "real-mode" 
these things show up. 

At the time, the plugin - though I loved and used it for years now - isn't 
usable any more.

Any ideas what I could do?

Regards,
Michael

Original issue reported on code.google.com by michael....@gmail.com on 22 Jan 2012 at 5:37

GoogleCodeExporter commented 9 years ago 
Could you provide your OS information and your plug-in version ? (ex. Win7 , 
32bit , 1.3.2 ) 

---

I have received some user complaining run mode is not working propertly in  Win 
XP/32bit few months ago,and I still looking for reason.

The strange part is not all users in WinXP(32 bit) facing this issue and some 
of them will be fixed after they change their project JRE to JDK,
those issue is starting from 1.3.0 , so it might be a issue for the fix/feature 
in 1.3.0 .

And all those issue is gone after they switch back to 1.2.1.1 version ,
I am not sure if that's same case , and I plan to do some code change.

I am thinking if the Eclipse Listener and Eclise Command feature causing the 
issue , 
but I have to build a reproducible environment to test this.

But I can't really understand the difference between debug mode and run mode. :(

I will try to find a VM to help me test this and reply this issue after Chinese 
New Year.(That means next Monday. )

Maybe you could use debug mode first?

Or if you didn't use any new feautre , you could re-install 1.2.1.1 version in 
our old update-site first.

I am sorry for your inconvenient and will see if I could fix this soon.:-|

Original comment by tonylovejava on 24 Jan 2012 at 6:35

GoogleCodeExporter commented 9 years ago 
Here's our old update-site run.googlecode.com/svn/trunk/updatesite-old

Original comment by tonylovejava on 24 Jan 2012 at 6:35

GoogleCodeExporter commented 9 years ago 
Thank you for the infos. And yes, I also use winXP SP2 (or 3, don't know 
exactly, but always up to date with updates) 32-bit edition. My hardware is 
relatively old - about 7 years. I use JRE 6.0.20 and Eclipse 3.7 SR 1. This is 
also the reason why I upgraded to latest RJR.

I started to develop in debug mode. I also turned off the reload mechanism, 
since working on mail templates tapestry templates doesn't require reloading of 
the whole webapp. This works fine. Thank you anyway for this wonderful plugin!

Another thing might be of interest: tapestry5 is using byte code manipulation. 
And it has build in support for reloading of classes and services in 
development mode. So the simpler RJR is the better for tapestry developers it 
is.

Tell me if you need some extra info.

Original comment by michael....@gmail.com on 26 Jan 2012 at 2:27

GoogleCodeExporter commented 9 years ago 
Yep , I think it's not necessary for source scanner to be default enabled,
I will change the default settings in next version.

About WinXP /32bit issue , let's see if I could fix it next week. :)

Original comment by tonylovejava on 27 Jan 2012 at 3:29

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 19 Feb 2012 at 4:39