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 191697 - run command on JME project does not start Java ME Mobility SDK 3.0
Summary: run command on JME project does not start Java ME Mobility SDK 3.0
Status: RESOLVED WONTFIX
Alias: None
Product: javame
Classification: Unclassified
Component: Build System (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-06 19:15 UTC by marcotts
Modified: 2011-11-16 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
complete log from output window (120.63 KB, text/plain)
2010-11-06 19:15 UTC, marcotts 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description marcotts 2010-11-06 19:15:57 UTC 
Created attachment 102833 [details]
complete log from output window

run command on an opened JME project fails with an exception shown in the output window.

Clean and build command on the JME project works correctly. When the IDE tries to launch the Java ME Mobility SDK 3.0, it waits for a few seconds than it fails showing an exception, reported in the attachment.

Steps to reproduce:
1) open a JME project (known to work)
2) "Run" command on the JME project
Comment 1 marcotts 2010-11-06 19:35:07 UTC 
found a fix to the problem:

- I run from a windows cmd prompt the following command: 
"C:\Java\NetBeans Dev 201011060000\mobility\Java_ME_platform_SDK_3.0\bin\emulator" -Xdevice:"ClamshellCldcPhone1" -Xjam
- windows firewall asked authorization for the emulator to listen for incoming connections, I clicked on "allow"
- the Java ME SDK 3.0 emulator started correctly
- I closed the Java ME SDK 3.0 emulator
- I tried again to run a JME Project from the Netbeans IDE; now it works.
Comment 2 Adam Sotona 2011-01-18 14:04:35 UTC 
It seems like firewall issue, probably combined with some other antivfirus/antimalware protection.