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.

Bug 79969 - SIOOBEx in log after opening project
Summary: SIOOBEx in log after opening project
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ pcw
URL: http://qa.netbeans.org/modules/j2ee/p...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-11 12:14 UTC by Lukas Jungmann
Modified: 2006-08-09 19:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide log (88.59 KB, text/plain)
2006-07-11 12:14 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2006-07-11 12:14:06 UTC
[200607110200]

- start IDE w/ new user dir, don't register server
- unzip fotoarchive project and open it in the IDE (w/ all both subprojects)

=> some info exceptions are logged, see attachement
Comment 1 Lukas Jungmann 2006-07-11 12:14:50 UTC
Created attachment 31725 [details]
ide log
Comment 2 _ pcw 2006-07-22 22:36:45 UTC
Can you attach the project that cause this?  I tried to reproduce it, but I
don't get any exceptions, just invalid server markings on all the projects.

The exceptions are begin logged because an unexpected state was encountered, but
I can't tell whose fault this is unless I can reproduce the scenario.
Comment 3 Lukas Jungmann 2006-07-23 00:11:34 UTC
Did you try the fotoarchive project (link is in URL field)?

Maybe I've missed one more required step: in all Missing ... dialogs press
"Close". Exceptions are logged right after that...
Comment 4 _ pcw 2006-08-04 02:24:45 UTC
Are these old projects?  The exception begin logged is because the server
instance does not include the server install folder.  This is because in
private.properties for the WAR project, 

j2ee.server.instance=deployer:Sun:AppServer::localhost:4848

rather than the new form, which is something like 

j2ee.server.instance=[/tools/glassfish_ur1_b03]deployer:Sun:AppServer::localhost:4848

I changed the exception into a pair of warning messages put in into the log file:

"Unable to determine installation location from target server instance ''{0}''.
 Check value of j2ee.server.instance in private.properties."  ({0} is the server
instance string)

followed by 

"Cannot identify version of target application server.  Defaulting to ''{0}''
for descriptor files."  ({0} is the display name of SJSAS [version #] -- 9.0 for
this case.
Comment 5 Lukas Jungmann 2006-08-09 14:26:28 UTC
Yes, these projects were created in NB 5.0. I was working on their upgrade to
5.5 when I found this.

Warning messages are always better than exceptions, thanks.
Comment 6 Lukas Jungmann 2006-08-09 19:13:55 UTC
If you want to see just the second message then create some project from
Samples/BP Solutions, eg. fileupload. First message will not be printed in this
case.

I've also checked content of
/j2ee/external/blueprints-solutions-catalog.zip#fileupload.zip#nbproject
directory and there's no private subdirectory.