- This topic has 8 replies, 2 voices, and was last updated 11 years, 9 months ago by
.
-
Posts
-
I’ve just finished upgrading from MyEclipseBlue v8.6 to v10.7. My reason for upgrading was that I could not get v8.6 to recognize my breakpoints set in EJBs. I would always get the attached error. So now I’m in the upgraded version, and am still getting the error. Will someone please help me get past this? I absolutely need to be able to set breakpoints in my EJBs! The attachment shows 2 screenshots. The first is the error that I get while the server is starting. The second is the error I get when I’m stepping through the code and it gets to an EJB.
I have tried unchecking the “Add line number attributes” option in the EJB project Java Compiler settings. Then I rebuilt the project. Then I rechecked “Add line number attributes” and rebuilt again. Still the same error. I am running a 6.0 JDK and I’ve also verified that the org.eclipse.jdt.core.prefs file has the .lineNumber=generate line in it.
I’ve also noticed that the server is incredibly slow in Debug mode. The speed is normal in the Run mode. Any suggestions there? Redeploying is incredibly slow, as well. I’m using a WebSphere v6.0 server. It did not run unusually slow in Debug mode when using v8.6 of MyEclipseBlue.
Joyce,
Apologies for the delay.
1) Can you please move to later version of WAS(6.1 or above) and try setting breakpoints in EJB ?
2) If you are still seeing this issue, can you please right click on the EAR > Properties > MyEclipse > EAR. Uncheck the option ‘Run EJBDeploy Tool’. If the EAR project has EJB 2.x as well, then you need to manually run the MyEclipse EJB Deploy tool. Right click on the EJB 2.x module > MyEclipse > Run EJB Deploy. Now try debugging.
3) If you have any issues moving to WAS 6.1 or above version, can you please attach the sample project which exhibits the issue to help us investigate further ?
My production server for this application is WebSphere v6.0, so no I can’t move to 6.1. I have unchecked “Run EJBDeploy Tool”. My EJB module is v3.1. Should I still try running the MyEclipse EJB Deploy tool?
Can someone please help me troubleshoot this using WebSphere v6.0? I will work on trying to get a sample project that displays the issue so I can send it. I can’t send the code I”m working with now.
Thanks for any help you can give me.
My production server for this application is WebSphere v6.0, so no I can’t move to 6.1. I have unchecked “Run EJBDeploy Tool”. My EJB module is v3.1. Should I still try running the MyEclipse EJB Deploy tool?
Can someone please help me troubleshoot this using WebSphere v6.0? I will work on trying to get a sample project that displays the issue so I can send it. I can’t send the code I”m working with now.
Thanks for any help you can give me.
Pradeep,
I found this solution on an Eclipse Help forum, but I’m having trouble transposing it to a WebSphere environment. The solution is for a WebLogic environment. Can you please help? If I wanted to try this, where would I put the workspace in a WebSphere environment? I am desperate enough to try anything…
Thanks,
JoyceHi,
I found the answer for this question. I have set the WORKSPACE of my Eclipse to point to Weblogic – applications directory.
Further I have copied the SRC folder of my application to
D:\bea\user_projects\domains\xyzdomain\applications\XYZ directory.
Where my XYZ directory is the root directory of my applications containing all HTML / JSP / JS files.
Let me know if you need any further information.
Regards
RangaA few interesting things I’ve learned since yesterday. Breakpoints in the Home_Stub and _Stub files work, and these files are located in the ejbModule alongside each Bean file that DOESN’T recognize breakpoints. I also ran the javap -verbose command on my Bean files and see that they DO contain Line Number tables, so they have their line numbers. It must be that MyEclipseBlue is just not recognizing the line numbers in my Bean files. I wonder if it has something to do with the EJB container? Maybe somehow that is blocking the tool from seeing the breakpoints?
Looks to be a glitch with MyEclipseBlue. Can anyone else step through their EJBs with this tool?
Joyce,
1) As far as my knowledge goes, WAS 6.0 doesn’t support EJB 3.1. WAS 6.0 does work with at most 2.1. Can you please clarify how are you running EJB 3.1 with WAS 6.0 ?
2) Can you please try “Run EJB Deploy tool” option which was mentioned in my previous reply ?
3) The solution for WebLogic won’t work for WAS 6.0. As, we support in-workspace mode only for WAS 6.1 and above.
4) Can you please clarify whether you are using any postprocessing stuff like AspectJ or anything which can alter class file after deployment ?
5) Can you please check if classes in WAS deployment location contain line info ?
It would be more helpful for us if we have the example project to help us investigate further.
I have attached the solution to my problem. I don’t completely understand it, but I got it to work. The short version is…my EJB module was deploying as a .jar file, and that was hanging up MyEclipseBlue. I went to the deployed app location and unzipped the EJB.jar file into a folder with the same name. At this point there were still no line numbers in my EJB class files. Then, through MyEclipseBlue, I cleaned and rebuilt JUST the EJB part of my application. After I did that, poof, line numbers. So apparently it is the fact that my app standard deploy wants to have the EJB module as a .jar file. Once I manually expand it out and recompile just that part, it’s ok and it runs fine for development.
I did look at the deployed app on my “real” servers and the EJB is just a .jar file, so when I’m done playing with it I suppose I’ll need to recompile with the standard build and let it go back to a .jar.
Hope this helps someone else. Glad I got it!!!
