This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ JDK VERSION : 1.6.* ] Some other, possibly related, issue I have is that breakpoints are only being respected after deploying my EAR when a debug session is already in progress. So when I have breapoints and I start debugging, they are not respected. Not in the servlets, not in the WS not in EJBs. But when I deploy my EAR again while the debugging session is in progress, the breakpoints are being respected and the debugging can begin. This I witnessed in NB671 and I think also in the current dev builds for 68. BTW I'm using GF21 Iwan
Reassigning to GF plugin. Also Martin E may have an idea what could be the problem.
I cannot reproduce this, though I may be doing something very different from the work-flow that you have not described in detail. Here is the test that I did. I created an ent app with an ejb module and a web app module I created a simple echo ejb. I created a simple servlet that called that ejb. I set a bp in the ejb. I set a bp in the servlet. I used Run to run the app. it executed correctly. I stopped the server. I started the server in debug mode. I attached the IDE to the server. I reloaded the servlet in the browser... I did not do an operation that would trigger a redeploy. the app stopped at the BP's as expected. I added another bp in the servlet. I reloaded the servlet in the browser window. the server stopped at each of the BP's... 2 in the servlet... one in the ejb. So, I need to get step-by-step instructions from you about your work-flow, so I can reproduce your issue. You must be doing something different and that is what triggers the behavior that you are seeing, but I cannot think of what that work-flow is...
Hi, You're doing a few steps different. Please note that I use the project that I mailed directly to you some time ago. So here's what I do: 1. Start NB 2. Load my EAR project and all related projects. 3. Ensure that my EAR project is the main project 4. Set a bp in a servlet, WS and/or EJB 5. Debug my main project by clicking on the debug button in the toolbar. Selecting debug from the context menu of my EAR project gices the same result though. 6. Witness that none of the bp are hit 7. right-click on my EAR project and select 'deploy' 8. Witness that all of the bp are hit Here's another observation: In the past, but I don't remember which version of NB, when I had in my persistence.xml stated that the db should be dropped and created, it would get dropped and created each time I started the EAR project in either run or debug. I noticed that in the current builds, and I investigated it also happens in NB67, the drop-creae only happens after I deploy the project explicitly. Iwan
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested information and reopen issue. Thanks in advance.
I just seconds ago entered the detailed steps as requested. I find it a bit too aggressive to say I'm not responding to a request for more information while I respond within a day. I am reopening. Please note that I have other responsibilities than checking my email for request for more information on NetBeans issues. Iwan
Sorry for that .. my mistake ;o)
Hmm. what is the state of the server and the app before your step 5... Server: running, running in debug, not running app: already deployed, not deployed Why I ask... I have gone through a number of combination and have not been able to replicate your result. More info will speed up the search
The state of the server before step 5 is that the server is not yet running. Step 5 will also start the server, and as I am starting a debug session, it will be running in debugmode. At least that is what I assume and think I see from the Ant output in NB. The app is already deployed. But my observation is that when the app is not already deployed, the same behavior can be witnessed. Iwan
I have been trying to replicate this again. I am still unsuccessful. Do you... have a large number of bp's in the app/IDE? have a large number of apps on the server? What happens if you 'Debug'... miss the bp's and then 'Debug' again (instead of doing a deploy)?
My laptop died on me (HD failure and Videocard memory problems), so I can't look into it right now. Unfortunately. I'll check on my Mac tonight and see how M2 works on it as well as older builds. I'll keep you updated. Iwan
it does not make sense to check builds older than m2... m2 is basically the trunk as of Sept. 26... which is ancient compared to the trunk (which is ancient compared to the team repositories, like web-main [which is the first place where glassfish plugin changes appear]. The delta between the published dev build and the web-main repository is about 4 days...)