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 207767 - java.util.NoSuchElementException at java.util.ArrayList$Itr.next
Summary: java.util.NoSuchElementException at java.util.ArrayList$Itr.next
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 11:49 UTC by majiknet
Modified: 2012-04-05 14:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 170002


Attachments
stacktrace (506 bytes, text/plain)
2012-01-26 11:49 UTC, majiknet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description majiknet 2012-01-26 11:49:15 UTC
Build: NetBeans IDE 7.1 (Build 201112071828)
VM: Java HotSpot(TM) Client VM, 22.0-b10, Java(TM) SE Runtime Environment, 1.7.0_02-b13
OS: Windows 7

User Comments:
GUEST: debugging on a tomcat server

GUEST: changing from glassfish v3 to apache tomcat server in project properties.

GUEST: starting apache tomcat to run my web application

GUEST: Starting tomcat server to run a web application.

GUEST: deploying my web application to a tomcat server




Stacktrace: 
java.util.NoSuchElementException
   at java.util.ArrayList$Itr.next(ArrayList.java:794)
   at org.netbeans.modules.tomcat5.ide.StartTomcat.getJavaHome(StartTomcat.java:780)
   at org.netbeans.modules.tomcat5.ide.StartTomcat.access$900(StartTomcat.java:95)
   at org.netbeans.modules.tomcat5.ide.StartTomcat$StartRunnable.run(StartTomcat.java:529)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1411)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1991)
Comment 1 majiknet 2012-01-26 11:49:17 UTC
Created attachment 115268 [details]
stacktrace
Comment 2 Petr Hejl 2012-03-29 15:43:35 UTC
Reporters, might this be a bug triggered by wrong configuration? Is the Java platform configured for Tomcat valid (in the configured directory, etc.)?
Comment 3 Petr Hejl 2012-04-05 14:38:26 UTC
Blind fix would be risky. We really need some details. Reporters can you comment?