I'm running a Java server and it works fine by now but recently it stops sometimes when I'm debugging my code. I don't know if the problem is due to java class is using many request/response API or it can be something else.
Have you got any ideas or met this issue before?
Best regards
Related
Here is the problem. I have a Spring web application which I develop on two computers: one with Windows another in Linux, and I share the code via github.
So far I did not have any problems until recently. I can't run in on linux. I get 404 error. At the same time it's working perfectly fine on Windows. I even managed to run it on a completely different computer (fitted with Windows).
Both laptops were switched to Java 8 and that was my primary suspect but so far I couldn't find anything that would cause this issue..
I would appreciate if somebody pointed me the way to fix it.
I'm not asking how to do it. I'm asking what it is. I asked my coworkers if we could setup remote debugging on our smoke-testing server and step through the code in eclipse from our developer PCs, and they looked at me funny.
Does remote debugging mean something other than "debug just like always, but remotely, with an IDE on your computer and the application running on a different machine"?
I've never done it and it looks like something that will take me hours to setup, and I doubt I could get permission to research it just to find out if it is what I hoped it was, so I'm asking you all if it is what I hope it is.
Yes, you can start the server in debug mode and connect to it from another machine using Eclipse. It is not hard to setup, read here: http://wiki.apache.org/tomcat/FAQ/Developing
It works exactly as you describe, using JPDA: http://en.wikipedia.org/wiki/Java_Platform_Debugger_Architecture
I've recently had my app moved from Websphere Application Server 6.1 to WAS 7.5, due to end-of-life for 6.1. Consequently, I needed to update my debugging server. I found this to be an opportune time to move my application from an IBM RAD IDE to Eclipse (already had Indigo installed). Or so I thought.
Anyway, the powers that be, here, have recommended taking my debugger all the way to WAS 8.5, since I'm only using it to debug.
But the issue that I'm encountering is that I cannot get the debugger to stop on my breakpoints. I've got approx. 10 breakpoints in my opening page, all in JSP/Java code.
I'm running Java 1.6.0_32 and Java SE Runtime Environment build 1.6.0_32-b05. I really don't know how to check which JDK I've got loaded. I've seen recommendations to "go back" to JDK 1.5, but I can't be certain that's not what I'm running.
And to cover a few other bases, I have JUST started my system for the day, opened the IDE, started the server in debug (says "Debugging, Synchronized"), put focus on the opening page of the application and clicked "Debug on server". The front page opens without stopping at any of the breakpoints.
Does anyone have ideas or suggestions?
If you use eclipse's debugger and running the application outside eclipse environment , we have to configure it as remote java application.
Also check if the code deployed in server is in sync with the one present in workspace.
anything wrong of the ecplise's site.
Run->Skip all breakpoints
Well, I had recently faced this problem, where the code did not use to stop at breakpoints while I was in debugging mode and was sure that the particular piece of code is executing. In order to solve the problem, I did a clean-build-republish but it did not work, recreated the profile and readded the server with new profile, still did not work then finally re-installed RAD and web-sphere but It still did not work. Then I found the below article
https://www-304.ibm.com/support/docview.wss?uid=swg21240896
and realized it could be a problem due to some other OS process interfering with debug process/port so I performed a system restore. After restore when I deployed the application, debugger started working properly.
I'd like to say I found the answer to this, but I never did. I ended up dropping RAD and moving to debugging on Jetty. My local testing isn't EXACTLY as it would be on the test server, but it works. Not sure if this should be flagged as "answered" or not.
UPDATE: I have left this project but before I did, the entire development platform was moved to IDEA and debugging was no longer an issue. I don't know if I should find a way to mark this question as inactive or closed or whatever so that it's not just sitting out here getting views and responses when it's no longer an issue for me.
We are seeing this very generic error pop up in some circumstances, but we can't seem to track down what is generating it and I'm hoping someone has some insight into where to begin. We have multiple client machines all running the same version of our software, build with SWT, and all hitting the same server, but not everyone gets this error. Nothing is showing up in our client or server logs and I have no idea what log file this error may be referring to, so it's not an error that we are catching anywhere and we have no details about this. Since it's a pop-up message that leads me to think it may be an SWT error. I've seen people mention this error when using Eclipse, but I haven't found where anyone mentioned it in an application they built.
I know this is vague, but I don't have much more to go on. Does anyone have an idea where to start looking for culprits?
Thanks
You're building an RCP application? In that case, this error is talking about the Eclipse platform log.
There should be a .metadata\.log file in your program's instance location. If you do not know your instance location, you can query it by calling:
Platform.getInstanceLocation();
I have problems in production mode. While developing my application I am using development mode and while testing everything is working right. When I compile my application to deploy on server there are some features that does not work. For example I have problems with some ComboBox or not all textfields save it state to database, or data is not populated to tables. It seems like not all code was compiled for production mode and I do not know why.I do not have any errors in logs on server. Probably it is some problem with cross-compilation. Of course when I switch back to development mode, everything is working.
I am using ExtGWT(GXT) with Spring.
Any one had similar problem?
Thanks for help.
In some schenario's it happens. Especially when you work with regex it works well in hosted mode and not in compiled mode.
1) Have you debugged the values coming in the client side service layer? All the values are appearing?
2) After compilation while testing are you sure that you have latest javascript downloaded into your browser? Sometimes due to browser cache you may have old code.
Can you please try find the place where the data is exactly missing? If you are sure the problem is happening from gxt side then you can post your queries in gxt forum.