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 104361 - snmp traps not received with profiler on
Summary: snmp traps not received with profiler on
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P4 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-20 16:29 UTC by jarome
Modified: 2011-11-02 20:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jarome 2007-05-20 16:29:09 UTC
I have code that listens to port 160 for snmp traps, so I run NB6 using sudo.
But if I ask the profiler to run my project, I receive no traps.

This worked under Windows using 5.5.
Comment 1 Tomas Hurka 2007-07-12 09:53:19 UTC
I am sorry, but I do not understand your error description. Can you please be more specific? What is 'snmp traps'? In the same context what do you mean by 'I 
receive no traps'? Are you able to create test-case to demonstrate the problem? Thanks.
Comment 2 jarome 2007-07-12 21:53:46 UTC
snmp traps are sent by network devices. I wrote some Java code to capture these traps, process them, 
and send them to a chat room, where they are scraped by another application. My application receives traps
(send by another server on the network) on port 161 or 162 if I do not turn on the profiler. But with the profiler on,
I receive no traps. I have to run NetBeans as root to get it to connect to these ports.

#!/bin/sh
sudo /Applications/"NetBeans 6.0 M9.app"/Contents/MacOS/executable

Alas, its not possible to make a simple test case because it depends on several other applications, and a rempot device
sending me traps.
Comment 3 Tomas Hurka 2007-09-11 13:54:29 UTC
Hmm, I am not sure how to fix it without test case. Can you please attach message.log from NetBeans and also log from profiled application? Maybe this will 
give us some hints about what went wrong. Thanks.
Comment 4 jarome 2007-09-11 14:26:18 UTC
Alas, the source of my traps moved behind a firewall, and I can no longer test my program.

But this does raise some other issues that should be addressed. To receive a trap, the program needs to listen on a
low-numbered port, which means it must be run as root. On Windows, this is not an issue, but on a Mac (or Linux), it
requires running something as root. Running the script in my second message is a bad solution because it changes the
permissions on my NB files so that everything gets screwed up if I run NB as myself on another project. I must reset
ownerships of log files, for example. What is needed is a way to use sudo in NB to just connect to the port, but to have
the rest of the IDE run as myself.
Comment 5 Alexander Kouznetsov 2007-10-23 10:00:01 UTC
Removing INCOMPLETE due to answer from user.
Comment 6 Jiri Sedlacek 2007-10-30 17:18:59 UTC
Restoring INCOMPLETE, cannot go deeper into the problem without at least the logfile. Please attach it here if you will
be able to reproduce the problem in future.

For now lowering priority as this is quite a cornercase not affecting most of profiler users. Please file a RFE if you
have some concrete idea about how NB should support sudo.
Comment 7 Tomas Hurka 2007-11-07 10:37:00 UTC
Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode.
Comment 8 mariadavydova 2008-09-01 15:09:14 UTC
Please provide any comments on this issue.
Comment 9 jarome 2008-09-01 19:00:02 UTC
I no longer get these traps, so I can't give you a log file. But the issue is not trap-related. You need to be able to
run NetBeans as yourself, but with some sudo privileges. If you run it as root, it screws up all your NB permissions.
Comment 10 mariadavydova 2008-09-23 14:32:34 UTC
remove incomplete
Comment 11 Tomas Hurka 2009-04-08 10:11:26 UTC
Target milestone cleanup.
Comment 12 Tomas Hurka 2009-04-08 12:54:18 UTC
Milestone cleanup: future->next