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.
can't start up the WTK emulator inside netbeans/mobility pack. (J2SDK = 1.5.0_06) (Windows 2K, SP 4) I've got WTK 2.3beta standalone, and it will execute projects compiled with NB. However, if it's started from inside NB (or even the WTK 2.2 default as supplied) I get "Warning: Failed to initialize WMA message routing support" and the emulator window closes instantly. Sorry, but I don't know if this is netBeans or mobilityPack problem.
I wasn't very clear: the WTK window opens and shows the virtual "phone" graphic, but doesn't get as far as showing the midlet menu.
Do you use any firewall?
no personal firewall, only a site firewall.
I have the similar problem. Whatever midlet I try to start from Netbeans 5.0 w/ Mobility Pack 5.0, it starts well *only* the very first time. After a second start I can see the (bundled) WTK emulator started, but the midlet menu doesn't appear anymore. Also, the overall system network performace drops significantly, and only a system restart solves the problem. I have firewall, but I also tried without network connection and without firewall activated - the behaviour is the same. Thanks.
I made further investigations; it seems the problem is related to ZoneAlarm - even if it is shut down, *but* still installed, the problem is present. After totally uninstalling it, everything works fine!
I had similar problem with ZoneAllarm some time ago but I didn't investigate it - I don't have it more. But another similarity was in problems with Symantec Firewall. Last weeks I found that Symantec sometimes keeps the file handles opened and it seems the locks are even exclusive. First I solved it using Sysinternals - Process Explorer by finding and closing the file handles but then I lost my patience and I completely uninstalled Symantec. BTW: It did not touch the emulator execution only, it affected also various Windows application installations/uninstallations. Some of my application behaved strangely during execution, some reported strange exceptions, or they forgot the settings, etc...
moving to mobility component
Most likely related to the configuration of local environment - firewalls. Can't be fixed in mobility
setting up the target milestone.
close old issues