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.
Created attachment 91003 [details] log file Build 200911091156 Trying to start an application via jws creates a Stack Overflow. The application worked just fine until built from a recent build of the IDE. See attached file. Might be related to https://netbeans.org/bugzilla/show_bug.cgi?id=153265
I suggest making it atleast P2 since it renders applications unusable via jws
duplicate of Issue 175853 ?
Not related.
Reproducible. Very similar to issue #175853, will probably need similar fix.
core-main #30fb5b4c0279
Integrated into 'main-golden', will be available in build *200911190201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/30fb5b4c0279 User: Jesse Glick <jglick@netbeans.org> Log: #176798: stack overflow fix in RecognizeInstanceFiles needed to be generalized to work in JNLP mode.
Created attachment 92397 [details] Logs I got the same error in Build 200912100200. Sorry I noticed after releasing 6.8 FCS. I'll retry on 6.8 Final and update this bug with my results.
See attachment comment.
Sadly it also happens in 6.8 FCS as I expected.
I can't tell for sure without a test case to reproduce, but I'm guessing it's hitting an nbresloc URL in one of your layers, rather than an nbres URL. Need to generalize again: core-main #6a39244a4fb5 Let me know if this seems to fix it (after the patch makes it into the next daily build), and if so this can go into 6.8.1.
Created attachment 92451 [details] Log Sorry to give feedback so late, was a crazy day at work. Anyways it still happens. I'll try to load the project as well since you mentioned something about my layer files.
Still happening.
Project is way too big to attach. I'll attach the layer files. Looks like that's what you want to see.
Created attachment 92452 [details] CMAIS module layer
Created attachment 92453 [details] HIMS module layer
Created attachment 92454 [details] PCEIS module layer
Integrated into 'main-golden', will be available in build *200912111937* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/6a39244a4fb5 User: Jesse Glick <jglick@netbeans.org> Log: Yet another attempt to fix stack overflow #176798.
This is fixed in build 200912130200. Great work!
(In reply to comment #18) > This is fixed in build 200912130200. Noting, thank you.
The fix has been ported into the release68_fixes repository. http://hg.netbeans.org/release68_fixes/rev/1d17f23fb222
*** Bug 179152 has been marked as a duplicate of this bug. ***
*** Bug 179725 has been marked as a duplicate of this bug. ***
any reproducible testcase to be able to verify in 68 patch 1? Thanks in advance.
javydreamercsw is the only person I know was able to reproduce. Are there dev builds from release68_fixes he could test against?
Created attachment 93567 [details] The NBM with fix for testing. Could javydreamercsw test the NBM from the attachment? Please, use Tools -> Plugins -> Downloaded Tab -> Add Plugins to NBM installation.
Hopefully tomorrow I can give it a try.
I get the following message: Plugin "Utilities API" is already installed. I couldn't find it to uninstall and install new one. Maybe forgot to increase the version?
The attached NBM has spec. version 7.31.2.1. The org.openide.util module in the official NetBeans IDE 6.8 has spec. version 7.31.1.1. Please, check your version of org.openide.util before update. I have tested the update of org.openide.util from 7.31.1.1 to 7.31.2.1 via the Downloaded tab on the vanilla IDE and everything worked smoothly.
I tried on Netbeans with latest Dev. Build. Should I try with 6.8? If so, is there a way to go back (unistall it). 6.8 is used for development and I shouldn't update it like that unless I can get it back to current state.
>Should I try with 6.8? Yes, the NBM is for NetBeans IDE 6.8. > If so, is there a way to go back (unistall it). Please, backup your IDE install directory, install and check the attached NBM, restore the IDE from the backup thereafter.
Still didn't work. I have NB + the latest updates (50+ updates that were available not long ago). I had to make a new install in a different dir to try it out. That said the version is not valid anyways for a NB + latest updates available via Update Center. Sadly my project dependencies are already beyond the ones in vanilla NB 6.8. I tried to make it work but it needs a huge amount of changes to even attempt a conpile that are not worth the try (playing with NB xml config files is too risky IMO)
>I have NB + the latest updates (50+ updates that were available not long ago). I'm sorry but I don't understand what 50+ updates you mean. The NetBeans team hasn't published any update for the NetBeans IDE 6.8. Sounds like you have updated your IDE by something what isn't intended for the IDE 6.8. Anyway, could you please do following steps: 1. Backup your NETBEANS_INSTALL_DIR (just rename it) 2. Backup your NETBEANS_HOME_DIR (just rename it) 3. Download the NetBenas IDE 6.8 from http://netbeans.org/downloads/index.html and install it 4. Install the attached NBM via Tools -> Plugins -> Downloaded Tab -> Add Plugins 5. Test whether the NBM fix the issue #176798 6. Delete newly created NETBEANS_INSTALL_DIR and NETBEANS_HOME_DIR 7. Restore back NETBEANS_INSTALL_DIR and NETBEANS_HOME_DIR from step 1. and 2. I believe that it will work.
That's weird because I remember seeing the message from the IDE about the new updates available (were initially 2 that then turned to 50+ after the restart) Any ways I'll do as you say and give it a try. Also I'll check if I see those updates pop up again.
I'm glad to agree that the issue is fixed! I had to clean the project of wrong version numbers (somehow I got mixed the dev stuff with released stuff). I'm cleaning that now.
That's great! Thank you for your help. I have marked the issue as 68patch1-verified.
*** Bug 178554 has been marked as a duplicate of this bug. ***
*** Bug 191868 has been marked as a duplicate of this bug. ***