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 85245 - OOM on tutorial security config sysmmetric binding no RM
Summary: OOM on tutorial security config sysmmetric binding no RM
Status: RESOLVED DUPLICATE of bug 75588
Alias: None
Product: webservices
Classification: Unclassified
Component: WSIT (show other bugs)
Version: 5.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-19 15:30 UTC by tamiro
Modified: 2006-09-20 20:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
netbeans message log right after OOM (188.00 KB, application/octet-stream)
2006-09-19 15:31 UTC, tamiro
Details
GF b15 server log from session leading up to OOM (389.43 KB, application/octet-stream)
2006-09-19 15:32 UTC, tamiro
Details
AddWSApp project files (30.77 KB, application/octet-stream)
2006-09-19 15:42 UTC, tamiro
Details
AddWSClient project files (44.43 KB, application/octet-stream)
2006-09-19 15:43 UTC, tamiro
Details
Chapter 7 of wsit tutorial (70.20 KB, application/octet-stream)
2006-09-19 18:31 UTC, tamiro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tamiro 2006-09-19 15:30:24 UTC
I have hit this Out of Memory error twice on Solaris; it didn't happen on Windows.

Configuration:
Solaris 10 on Sparc
Glassfish v2 b15 installed with setup.xml defaults
WSIT M2 b03c (Sept 14)
NetBeans 5.5 Beta 2
wsit nbm 1.31
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

Steps leading to OOM:
1. Started NB and GF
2. Created web service with RM enabled and client servlet according 
   to instructions in Chapter 7 of tutorial (will attach).
   web app worked displaying wsdl in browser and client servlet 
   worked displaying correct number in browser
3. Changed numbers in client AddServlet.java and reran it 
   a few times. It worked but after a 10 minute (or so) wait 
   the GF log showed a flood of heartbeat messages and WebApp 
   class loader errors (see wsit issue 75)
4. Restarted GF to get around wsit issue 75 
   (runaway hearbeat messages from client 
   servlet thread left dangling when client servlet is redeployed). 
   Now able to run client OK but saw a few strange errors in GF server.log
[#|2006-09-18T16:26:37.465-0400|INFO|sun-appserver-pe9.1|org.apache.catalina.loader.WebappClassLoader|_ThreadID=15;_ThreadName=Thread-31;|PWC1635:
Illegal access: this web application instance has been stopped already (the
eventual following stack trace is caused by an error thrown for debugging
purposes as well as to attempt to terminate the thread which caused the illegal
access, and has no functional impact)|#]
5. Edited web service attributes and turned off RM in the service.
6. Ran service and wsdl displayed in browser fine.
7. Did Refresh Client on client servlet, then stopped and started GF
   and ran client, getting good result in browser. 
   Waiting a while to see if server.log showed any spewing of heartbeat msgs, 
   and it didn't. So at this point have a non-security app and client without 
   RM that work.
8. Edited web service attributes on service app to configure Symmetric Binding 
   config according to Chapter 5. Configured keystores from xwss.dev.java.net,
   set token configuration to Symmetric with signature token X509 and so on.
9. Rebuilt, deployed, and ran security-enabled app. Noticed NB was getting slow.
10. Edited web service attributes on client to set keystore config
11. Did Refresh Client
12. Bounced GF.
13. On client servlet tried Clean and Build, but was so slow seemed like 
    nothing was happening. Also clicked Run Project. Waited, waited ... 
    went home and in the morning saw the Out of Memory error
Comment 1 tamiro 2006-09-19 15:31:46 UTC
Created attachment 34161 [details]
netbeans message log right after OOM
Comment 2 tamiro 2006-09-19 15:32:51 UTC
Created attachment 34164 [details]
GF b15 server log from session leading up to OOM
Comment 3 tamiro 2006-09-19 15:42:37 UTC
Created attachment 34165 [details]
AddWSApp project files
Comment 4 tamiro 2006-09-19 15:43:20 UTC
Created attachment 34166 [details]
AddWSClient project files
Comment 5 tamiro 2006-09-19 16:23:18 UTC
After getting the OOM error, I restarted NB to see if I could continue.
Running the client worked. On selecting the AddWSApp project, got FSException error

   Warning cannot get shared access to 
   /var/Sun/netbeans5.5beta2/AddWSApp/web/WEB-INF/sun-jaxws.xml

Didn't know if that was serious, so continued with Security config 2,
Symmetric Binding with RM and secure conversation. After doing 
Clean and Build, Deploy, Run, get a 404 error on 
http://localhost:8080/AddWSApp/AddWS?wsdl
Comment 6 tamiro 2006-09-19 18:31:15 UTC
Created attachment 34174 [details]
Chapter 7 of wsit tutorial
Comment 7 tamiro 2006-09-20 20:05:16 UTC
I tried the daily dev build date 9-16-06 which is supposed to 
fix this problem and was not able to reproduce it.

Also, with 5.5 beta2 and wsit module 1.31, after setting 
-J-Mx512m in netbeans.conf and closing the Navigator window, 
the problem didn't happen. So I'm closing it as a dup of 75588

*** This issue has been marked as a duplicate of 75588 ***