IDM JMX monitoring - Synchronization MBean

Does anyone know how to additionally expose Waveset data using JMX MBeans? In earlier versions of the product (at least 7.0) I thought it provided insight into the synchronization processes currently running within the system, under:
ObjectName=IDM:type=Cluster,service=Synchronization,component=ActiveSync,resType=”<Resource type>”,name=”<resource name>”
However, looking at the documentation for 8.1.1, for example, I only see the following:
From: http://docs.sun.com/app/docs/doc/820-7976/byajd?l=en&a=view
Data Exposed in JMX
So what kind of data does Waveset expose using JMX MBeans? The following table contains a list of MBeans, describes the data they provide, and explains how to use that data.
List of MBeans:
Cluster
Names of the servers in the Waveset cluster, including which servers Waveset considers active.
Provides a quick status of the cluster from the perspective of one Waveset server.
ObjectRepository
Waveset repository configuration data, including database name and version, JDBC driver version, and connection pooling settings
Shows everything you need to know about how Waveset talks to the repository.
Performance
Contains sub-beans for DataExporter, DataQueue, FormConverter, ObjectChangeNotification, Reconcile, Rule, TaskInstanceCache, ViewMaster, and WorkItemCache execution.
Identifies GUI performance problems and provides visibility into how these subsystems perform. You can enable these beans to capture data that can quickly isolate why a particular page loads slowly on a production server.
Scheduler
Internal processing counters for the Scheduler
Provides detailed visibility into what the Scheduler is doing at any given point in time. Making use of this bean requires an in-depth understanding of how the Scheduler works.
Server
Current status of this Waveset server
Shows server status
<resource name>
Operational statistics for each resource and connector used by Waveset.
Shows the count and maximum, minimum, and average time for each resource operation. Gives visibility into the performance of the resource, the Waveset interface, and the Waveset activity on each resource.
Was the ability to monitor ActiveSync taken out sometime between 7.0 and 8.1.1? Is there a way to incorporate this into JMX again? Anything I am missing?
Any additional info would be great.
Thanks again!

How is the WebSphere node connected to the cluster? Is it using TCMP? Extend?
Local, Distributed, Replicated, Near, Overflow, External and Optimistic cache statistics appear in the Coherence JMX server. However, near and local caches created on extend nodes do not appear. Therefore the -Dtangosol.coherence.management.remote=true on an Extend client will not register the near or local caches.
Thanks,
Everett

Similar Messages

About using OSB JMX Monitoring API

hi Experts,
My customer is using OSB11.1.1.7, they are trying to use JMX Monitoring API to get the statistic info, but have the following issues:
1. For the non-soap service, the serviceDomainMbean.getBusinessServiceStatistics method always return error when typeFlag was set with ResourceType.WEBSERVICE_OPERATION.value(), reason is there is no ws operation for this service, customer wants to know how to know if a service has no ws operation ,therefore they can avoid to get ws-operation statistic info for those kind of services.
2. Is there a way to get statistic info for the current aggregation interval? the api seems works with period from last reset.
3. Further more, How to get statistic info for special period, for example, customer want to query statistic info from 05/01 to 05/03, or from 05/03 12:00 to 05/03 13:00
Thanks for the help.
Best regards

Davinder Singh wrote:
Hi ,
I have an application deployed on weblogic server 8.1 . This has some MBeans exposed
for management purposes. This needs to be accessed from another web application
running on another weblogic instance on different machine. For this the managed
application has a Connector server and the management application is trying to
connect it through Connector client.
At the managed application side , i am getting NoSuchMethodError: javax.management.MBeanServer.getClassLoaderRepository()
I am not using weblogic implementation of JMX (MBean Server).
My guess about the error :the weblogic implements JMX version 1.0 and i am using
JMX remoting API (RI from Sun) which requires JMX 1.2
Is there a way i can make weblogic use JMX 1.2 ?I dont think there is a way to do this. But I might be wrong.
>
Thanx,
Davinder

Limiting JMX Monitor Executor Pool size

Hi all,
does anybody know how to limit (or in general, set) the size of the Scheduler/Executor Pool in JMX for Monitors?
By default it seems that 10 threads are created, named [JMX Monitor Executor Pool [Thread-n]]. They get created when I create the first Monitoring MBean, in my case this was a simple GaugeMonitor.
I don't have a problem with the 10 threads, but its just that our app already has enough threads as it is, plus the granularity period we will use is fairly big (minutes) and we only have a few Monitor beans, so we won't have high load on them.
Any help appreciated.
Cheers, Mark

Mark,
You can set the system property jmx.x.monitor.maximum.pool.size to control this, either on the command line with e.g. -Djmx.x.monitor.maximum.pool.size=3 or by calling System.setProperty("jmx.x.monitor.maximum.pool.size", "3"). The value of this property is consulted the first time the class javax.management.monitor.Monitor is loaded (typically when you create your first monitor), and not thereafter, so you must be sure to set it beforehand.
This property is non-standard and will not necessarily work with other implementations of the JMX API, but it does work with the implementation that is in the JDK platform, starting with JDK 6. (Before JDK 6, every monitor had its own thread, so if you are seeing a limit of 10 threads then you are using JDK 6.)
From my reading of the code, it does look as if more threads will be created than strictly necessary. For example, if you only have one monitor then you don't need more than one thread, but if the monitor's granularity period is less than 60 seconds you will end up with 60/period threads, up to the maximum (default 10). For example 4 threads if the period is 15 seconds. I think we should probably fix that. (The core pool size should probably be 1 rather than the same as the max pool size.)
Regards,
�amonn McManus -- JMX Spec Lead -- [http://weblogs.java.net/blog/emcmanus]

Near Cache JMX Monitoring

Hi,
Can the JMX monitoring capabilities of Coherence be used to monitor the hit-rate of a near cache, i.e. by adding the JMX command line options to the extend client - to determine how effective it is?
Thanks

Hi dxfelcey,
You can get to the NearCache statistics by querying CacheMBean(s) with key attribute "tier=front". For example, the following query will return you a set of ObjectNames for all MBeans representing NearCache called "test" instances across the cluster:
MBeanServer mbs=MBeanHelper.findMBeanServer();
Set setNames = mbs.queryNames(new ObjectName("type=Cache,name=test,tier=front,*"), null);For more information please see the Registry Javadoc here:
http://download.oracle.com/otn_hosted_doc/coherence/330/com/tangosol/net/management/Registry.html
and the Coherence Wiki page here:
http://wiki.tangosol.com/display/COH33UG/Managing+Coherence+using+JMX
Regards,
Gene

Service Bus JMX monitoring

How can i use JMX monitroing feature?
Server started with:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
I trying to check can i use ServiceDomainMBean:
java -jar c:\pdprogram\java_lib\cmdline.jar - 192.168.154.142:7092 | grep -i "ServiceDomainMbean"
But result is null.
Am i right understand documentation (http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/app_jmx_monitoring.htm) that some MBean's thread (com.bea.wli) must be open for access for working with JMX monitoring?

What is in c:\pdprogram\java_lib\cmdline.jar ? And what exactly are you trying to achieve?

JMX monitoring front Coherence cache running on IBM WebSphere

I have a question regarding JMX monitoring a Coherence front cache running in a IBM WebSphere v6.1 JVM (1.5).
My setup is that I have three Coherence nodes (back cache) each running 10 JVMs each. Via JMX all these 30 JVMs are setup to be monitored from one of the 30 JVMs which is configured to be the JmxServer for the other 29 instances. The other 29 JVMs set -Dtangosol.coherence.management.remote=true at startup to indicate that their MBean tree will be managed centrally. This works fine but when I try to extend this to also be able to manage the front cache (running on WebSphere on a separate node in the tier above) by adding the same flag (-Dtangosol.coherence.management.remote=true) it does not appear in the MBean tree as the other 30 Coherence cache (Sun) JVMs do.
Are there other things I have to consider to get this working? There are no firewalls in between the nodes so that is not the problem. How much of IBM WebSpheres (non-standard) JMX-functionality is required to get this to work?
/Jonas

How is the WebSphere node connected to the cluster? Is it using TCMP? Extend?
Local, Distributed, Replicated, Near, Overflow, External and Optimistic cache statistics appear in the Coherence JMX server. However, near and local caches created on extend nodes do not appear. Therefore the -Dtangosol.coherence.management.remote=true on an Extend client will not register the near or local caches.
Thanks,
Everett

Writing a jmx monitor for a message driven bean

I've been reading about using jmx to monitor some jms resources I have deployed to my
WL server. This monitor would monitor "some" MBean to watch for some Stuck Threads which
cause a disconnect to the jms queue to which I listen.
The problem is I'm not sure which, I'm not exactly sure which MBean I need to monitor. My
JMS Listener is an MDB which listens to a queue on a remote weblogic server. What happens is
something on the remote end causes a connection reset. About 10 mins later, I get a stack trace
dump and after that happens I'm no longer able to pull messages off my jms queue. I see logged
events where it says I'm successfully reconnected to my queue, but no amount of wishing will
let the MDB pull a message off the queue.
When the monitor detects a Stuck Thread, I'd like to force an application restart/redeployment, whichever
will accomplish a reconnection to the queue to which I'm listening. The other day, I went in through
the console, did a Lock/Edit and simply updated the already deployed application. Monitoring the log
file, I saw the mdb successfully reastablish connection to my remote end.
However, with 600+ MBeans, I'm kinda stuck on where I should start! Since I see the
stack trace in the AdminServer.log file, I'm thinking I should monitor some LoggingMBean.
But, it is JMS related, so there exists some confusion on my part.
If anyone with JMX experience could point me in the right direction, I'd appreciate
it. I'm just learning jmx, so pls be patient.
Thanks,
John

You have a couple of options here. You could monitor the WorkManagerRuntimeMBean's StuckThreadCount using a JMX Counter monitor, and trigger the action when that goes above 0.
You could also use WLDF to configure a Log watch to look for the Stuck thread log message, or use a Collected Metrics watch on the WM attribute, and assign it a JMX Notification. You could then write a JMX Notification listener to capture this event and perform the necessary corrective actions.

The JMX Monitoring APIs for OSB

hi
I know Using the JMX Monitoring APIs can monitor Oracle Service Bus at run time to know how many messages in a particular service have processed successfully and how many have failed. but those are Statistical Information . i want to monitor the details when a particular service is invoked,such as the caller's IP address, the call is successful or not, the error message and error code.
帖子经 David编辑过

There are no public API that are present except for monitoring and Deployment.
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/app_apis.htm#CHDHAJGD
The runtime information for OSB artifacts and their instances are not exposed though API.This use-case can be accomplished by using reporting action. http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/reporting_console.htm#CACJFDGF
Getting IP address of cleints invoking proxy on OSB is little tricky, but some transports do support. eg HTTP. Can you describe in brief actual business case so that we can come-up with some solution. Is this monitoring, part of Business logic or Administrator requirement (Technical) etc.
Thanks
Manoj

Siebel JMX monitoring using JRuby

Hi,
I am trying to use JRuby to monitor the performance of a Siebel adapter using JRuby. Whist I am able to read the mbean data from the server I am unable to successfully submit the command "reset = conn.invoke(name, 'Reset', '', '' )" The error message I receive is
D:\Scripts\JRuby\jmx.rb:17: for method RemoteMBeanServerConnection.invoke expected [class javax.management.ObjectName, class java.lang.String, class [Ljava.lang.Object;, class [Ljava.lang.String;]; got: [javax.management.ObjectName,java.lang.String,java.lang.String,java.lang.String]; error: argument type mismatch (TypeError)
     from C:/Program Files/jruby-1.4.0/lib/ruby/site_ruby/shared/builtin/java/java.util.rb:21:in `call'
     from C:/Program Files/jruby-1.4.0/lib/ruby/site_ruby/shared/builtin/java/java.util.rb:21:in `each'
     from D:\Scripts\JRuby\jmx.rb:15
The complete code is listed below.
#!/usr/bin/env jruby
include Java
include_class 'javax.management.ObjectName'
include_class 'javax.management.remote.JMXConnectorFactory'
include_class 'javax.management.remote.JMXServiceURL'
jmxurl = 'service:jmx:rmi:///jndi/rmi://localhost.au:8687/jmxrmi'
username, password = 'admin', 'sun12345'
svcurl = JMXServiceURL.new(jmxurl)
cred = java.lang.String[2].new
cred[0], cred[1] = username, password
env = {'jmx.remote.credentials' => cred}
conn = JMXConnectorFactory.connect(svcurl, env).getMBeanServerConnection
names = conn.query_names(ObjectName.new( 'IDM:serverName=localhost,resourceAdapterType=CCB Siebel CRM Position,resourceAdapterName=CCB Siebel CRM Position'), nil)
names.each do |name|
    puts "OperationCount: #{conn.get_attribute(name, 'Account_Get_OperationCount')} " + "OperationMaxTime: #{conn.get_attribute(name, 'Account_Get_OperationMaxTime')}"
    reset = conn.invoke(name, 'Reset', '', '' )
end

Hi,
Does anyone have any clues.
Thanks

Polling JMX monitor

I'm looking for a tool that can pull data from an RMI JMX connection and use it for generating alerts and storing historical JMX attributes. I've seen many solutions that want to "push" the data via a Java agent to their monitoring servers but I haven't seen many that try to pull data.
Any ideas of some good products out there?

Hi,
The short answer is yes to all your questions.
The longer answer is that you should be careful when using custom types
in your MBeans, because 1) you will need to make them serializable, and
take care of compatibility issues when they evolve, and 2) you will need to
make the jar that contain them available on the manager side.
To overcome this, JMX defines the notion of Open MBeans and OpenTypes, that
is, generic data-types (CompositeData and TabularData) that can be used to
model custom types.
In JDK 6, we're also introducing the notion of MXBean (see the excellent article
on http://java.sun.com/developer/technicalArticles/J2SE/mxbeans/ ).
MXBeans are just like MBeans, except that the MBeanServer will automatically
transform your custom types into OpenTypes (not all custom types can be
automatically converted - but a great many of them).
In JDK 6 build 98 you will find a new advanced JMX example that demonstrate
configuration MXBeans using XML serializable beans as MBean attributes.
Concerning Notifications, the same concerns applies. We usually recommend
not to create any custom subclass of notification, but use one of the standard
base classes instead. A JMX notification has a user data field in which you
could embed an instance of a generic Open Type (CompositeData/TabularData)
if needed.
The new advanced JMX example also show how you can 'reuse' the base
notification classes.
See:
http://blogs.sun.com/jmxetc/entry/looking_for_jmx_overview_examples
for JMX tutorial, examples, etc...
and
http://blogs.sun.com/jmxetc/entry/an_advanced_jmx_example_for
for instruction on the new JDK 6 JMX example.
I hope this will get you started on JMX!
-- daniel
JMX, SNMP, Java, etc
http://blogs.sun.com/jmxetc

Does jconsole support monitoring of MBeans registered to New MBean Server?

I see that jconsole is displaying the MBeans registered to Platform MBean Server (obtained through java.lang.ManagementFactory.getPlatformMBeanServer()) but not the MBeans that are registered to a newly created MBean Server (created using javax.management.MBeanServerFactory.createMBeanServer()).
Is there a way through which I can view the MBeans registered to newly created MBean Server in the jconsole?

Thank you for the information emcmanus.
So what I understand is that the jconsole if opened in a normal way (i.e. Local), it loads MBeans by looking up the Platform MBean Server.
All the MBeans belonging to other MBean Servers or custom created MBean Servers can be managed & monitored if jconsole is loaded using Advanced option (i.e. providing JMX URL) and with the help of remote connectors.
When I open Platform MBean Server, I dont see MBeans of other MBean Server and vice versa. (I think they are mutually exclusive).
Please correct me if what I have mentioned above is incorrect.
One confusing thing is that I see "JVImplementation" MBean is available when I open jconsole with either of the two option mentioned above.
Is there any specific reason for that?
Is that MBean part of Platform MBean Server or some other MBean Server?

JMX 1.0 client to JMX 1.2 mbean possilbe?

Hi!
I'm using Weblogic 8.1 which supports JMX 1.0 spec.
I would like to query mbeans in a Weblogic 10.0 server that support JMX 1.2.
Is that possible? and how is it done?
Regards,
Jesper Vrelits

Hi!
I'm using Weblogic 8.1 which supports JMX 1.0 spec.
I would like to query mbeans in a Weblogic 10.0 server that support JMX 1.2.
Is that possible? and how is it done?
Regards,
Jesper Vrelits

Please help! Fitness Monitor synchronization probl...

Dear All,
I just bought a Nokia Fitness Monitor(LS-2). I tried to synchronize with my 5140i mobilephone, but it didn’t work.
So I browsed the internet to find the reason. I found that in the earlier 5140 phones included Fitness Coach application contains separate menu for Fitness Monitor under the sychronization. See the link:
http://www.nokia.com/EUROPE_NOKIA_CO...ish/index.html
My mobile contains a Fitness Coach II. application(version: 0.7), and this one have only the possibility to communicate through infrared with other equippments.
Is there any solution to be able to synchronize my 5140i mobile with the Fitness MonitorMaybe with installing an earlier Fitness Coach application? Is it possible? Is it aviable somewhere?)
Thank You in advance!

Check with Oracle. We had issues applying BP04. The BP02 patch might not have been tested by Oracle for windows properly.
Also, If you are invoking patch_weblogic.bat then check if patch_oim_wls.profile reflects your environment settings.

Servlet Session Monitoring via MBeans turns up no MBeans

Hi,
I discovered more about why I'm not seeing any Servlet Session Runtime
MBeans when I enable session monitoring. It looks like each time my
managed server creates a new session, two errors get written to my
WebLogic log:
"####<Sep 22, 2002 6:46:43 PM EDT> <Warning> <Dispatcher>
<chile.iso-ne.com> <adminserver> <ExecuteThread: '7' for queue:
'__weblogic_admin_rmi_queue'> <> <> <000000> <RuntimeException thrown
by rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid:
'7074298665992588400S:10.145.220.82:[7001,7001,7002,7002,7001,7002,-1]:smsdomain:adminserver',
oid: '267', implementation:
'weblogic.management.internal.AdminMBeanHomeImpl@3c7b65''>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1637)
and
"####<Sep 22, 2002 6:46:43 PM EDT> <Error> <HTTP Session>
<chile.iso-ne.com> <webuiserver> <ExecuteThread: '0' for queue:
'default'> <> <> <100032> <Error creating servlet session runtime>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy7.getMBeanServer(Unknown Source)
at weblogic.management.internal.MBeanHomeImpl.isAdminHome(MBeanHomeImpl.java:93)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:118)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:590)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:568)
at weblogic.servlet.internal.session.SessionData$1.run(SessionData.java:185)
at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
at weblogic.servlet.internal.session.SessionData.getRuntimeMBean(SessionData.java:179)
at weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:166)
Looks like the managed server is making a request of the admin server
and propagating the "guest" principal instead of "system".
These principal propagation errors from managed-to-admin seem to
happen all over the place with different MBeans, and get patched one
place at a time in various BEA service packs. For instance, there's
another issue with accessing the XML Entity Cache from a managed
server, and I'm sure I've read about others. Isn't there a way to
make sure these errors no longer occur with any MBean requests from
the managed server?
Jim

Add
acl.access.weblogic.admin.mbean.MBeanHome=guest
in the filerealm.properties file.
Jim Doyle wrote:
Hi,
I discovered more about why I'm not seeing any Servlet Session Runtime
MBeans when I enable session monitoring. It looks like each time my
managed server creates a new session, two errors get written to my
WebLogic log:
"####<Sep 22, 2002 6:46:43 PM EDT> <Warning> <Dispatcher>
<chile.iso-ne.com> <adminserver> <ExecuteThread: '7' for queue:
'__weblogic_admin_rmi_queue'> <> <> <000000> <RuntimeException thrown
by rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid:
'7074298665992588400S:10.145.220.82:[7001,7001,7002,7002,7001,7002,-1]:smsdomain:adminserver',
oid: '267', implementation:
'weblogic.management.internal.AdminMBeanHomeImpl@3c7b65''>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1637)
and
"####<Sep 22, 2002 6:46:43 PM EDT> <Error> <HTTP Session>
<chile.iso-ne.com> <webuiserver> <ExecuteThread: '0' for queue:
'default'> <> <> <100032> <Error creating servlet session runtime>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy7.getMBeanServer(Unknown Source)
at weblogic.management.internal.MBeanHomeImpl.isAdminHome(MBeanHomeImpl.java:93)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:118)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:590)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:568)
at weblogic.servlet.internal.session.SessionData$1.run(SessionData.java:185)
at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
at weblogic.servlet.internal.session.SessionData.getRuntimeMBean(SessionData.java:179)
at weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:166)
Looks like the managed server is making a request of the admin server
and propagating the "guest" principal instead of "system".
These principal propagation errors from managed-to-admin seem to
happen all over the place with different MBeans, and get patched one
place at a time in various BEA service packs. For instance, there's
another issue with accessing the XML Entity Cache from a managed
server, and I'm sure I've read about others. Isn't there a way to
make sure these errors no longer occur with any MBean requests from
the managed server?
Jim--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

IDM alert monitoring

Hi,
Monitoring the IDM alerts show that one of the internal clients attacking outside IP addresses. Couls someone shed light on the above dynamics.
Thanks.
Said
evIdsAlert: eventId=1216735955474843112 vendor=Cisco severity=informational
originator:
hostId: ips
appName: sensorApp
appInstanceId: 406
time: Jul 29, 2008 12:50:48 UTC offset=0 timeZone=UTC
signature: description=TCP SYN Host Sweep id=3030 version=S2
subsigId: 0
marsCategory: Probe/SpecificPorts
interfaceGroup: vs0
vlan: 0
participants:
attacker:
addr: 192.168.1.207 locality=OUT
port: 4580
target:
addr: 66.150.11.50 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 68.180.219.138 locality=OUT
os: idSource=learned type=bsd relevance=relevant
target:
addr: 74.201.95.4 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 72.247.169.161 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 207.230.151.254 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 216.252.124.207 locality=OUT
os: idSource=learned type=bsd relevance=relevant
target:
addr: 67.228.69.100 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 208.43.2.146 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 66.196.126.101 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 69.22.167.239 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 216.73.87.152 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 12.130.60.4 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 66.94.234.72 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 216.145.50.247 locality=OUT
os: idSource=unknown type=unknown relevance=relevant
target:
addr: 216.252.125.76 locality=OUT
os: idSource=learned type=bsd relevance=relevant
target:
addr: 209.131.37.77 locality=OUT
os: idSource=learned type=bsd relevance=relevant
alertDetails: InterfaceAttributes: context="Unknown" physical="Unknown" backplane="GigabitEthernet0/1" ;
riskRatingValue: 31 targetValueRating=medium attackRelevanceRating=relevant
threatRatingValue: 31
interface: GigabitEthernet0/1 context=Unknown physical=Unknown backplane=GigabitEthernet0/1
protocol: tcp

Hi,
I had the exact same issue going on at my location, and there were two causes.
One was that we had a bluecoat proxy, which uses multiple ports to refresh its website cache, and for new requests.
The other cause was a machine that was infested with spyware.
If it is a users machine, I would suggest downloading the Sysinternals Suite from Microsoft, and doing a PSLOGGEDON \\ to see who is using that machine.
Jason

IDM JMX monitoring - Synchronization MBean

Similar Messages

Maybe you are looking for