Logging in monitoring

Can anyone help, Is there anyway I could check the last 5 times the database was shutdown and startup internally apart from checking alert log file.

You must rely on external sources of information in order to know that. alert log is the perfect file to get this info.
you can also use $ORACLE_HOME/rdbms/audit/*.aud to get this info. It's a bit more complicated, but doable.
Yoann.

Similar Messages

Error handling, logging and monitoring business process

I would like to know more about error handling, logging and monitoring in business process? Can someone give more information on this one?

Chandran
Please refer to following tutorials to understand each of these topics in detail:
Validations:
http://www.orafmwschool.com/validations/
Exception Handling:
http://www.orafmwschool.com/exception-handling/
Fault Management Tutorial:
http://www.orafmwschool.com/fault-management-tutorial/
Business Activity Monitoring Tutorial:
http://www.orafmwschool.com/bam-tutorial/
You'll have to refer to Oracle documentation to understand more finer details.
-Amjad.

Text log file Monitor

Hi Team,
i have a task to create a log file example SCOM.log, the log has all text entries and the pattern is like below
"[0014 20140724 094527069 SCOM E] ProcessDeposits(), DMGATEWAY internal error in plugin: An exception occurred while processing terminal transaction with HostTransactionID: '4143', tracking fact Id: '3' in the Deposit Gateway Processor task 7. The transaction
will be NOT be re-queued. // "
we need to monitor anything which has "DMGATEWAY internal error in plugin:" string.
sometimes we have greater then 10 entries with in few seconds.
once the log file reaches 10MB all the entries are moved to an archive log file that means the present SCOM.log file is empty and start from line one again.
any suggestions \ solution will be a great help and also let me know if you need any further information
-Vrkumar01
RajKumar

Hi Raj,
Have a read through this post it highlights issues with log monitoring: http://social.technet.microsoft.com/Forums/systemcenter/en-US/827464fd-ff06-495d-8ac6-4a6e337314d3/bug-in-scom-log-file-monitor?forum=operationsmanagergeneral
Have a look at creating a script monitor to monitor the log file:
http://www.opsmanager.se/2012/11/06/text-log-monitoring-part-1/
http://www.opsmanager.se/2012/12/17/text-log-monitoring-in-operations-manager-part-2/
The issue you are experiencing is a limitation of scom which is documented here:
http://support.microsoft.com/kb/2691973/en-us
Snippet from KB:
Additional Information
When monitoring a log file, Operations Manager remembers the last line read within the file (a 'high water mark'). It will not re-read data before
this point unless the file is deleted and recreated, or renamed and recreated, which will reset the high water mark.
If a logfile is deleted and recreated with the same name within the same minute, the high water mark will not be reset, and log entries will
be ignored until the high water mark is exceeded.
An implication of this is that log files that are cleared periodically without being renamed and recreated, or deleted and recreated, will not have entries in them processed until the high water mark from before the log is cleared is exceeded.
Operations Manager cannot monitor 'circular log files' (i.e. log files that get to a certain size or line count, then start writing the newest entries at the beginning of the log) for the same reason. The log file must be deleted or renamed and then recreated,
or the application configured to write to a new log once the current log is filled.
Cheers,
Martin
Blog:
http://sustaslog.wordpress.com
LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SUPER user logging and Monitoring

Since SAP does not recommend using GRC Access Control to log actions performed using SUPER users such as SAP, DDIC, or other powerful id's, what tools are available? When SAP, DDIC, or other powerful super users are used in your SAP environment. Are these activities being logged? Is anyone monitoring these activities? Do you even use SUPER id's in your environment or assign access directly to your BASIS team? Have you used GRC SPM or Virsa Firefighter to manage these users? Are you using monitoring tools such as Cyber-Ark to log and monitor your BASIS team? How do you ensure your management or audit team that all activities perfomed by SAP*, DDIC or other powerful SUPER users is logged and available for review?

> Since SAP does not recommend using GRC Access Control to log actions performed using SUPER users such as SAP*, DDIC, or other powerful id's, what tools are available?
Can you reference the source where SAP says that standard super users should not be logged?
SAP also says that standard users such as DDIC and SAP* are known targets of attack vectors(DoS attacks, password brute forcing, DB vulnerabilities...) so once having locked them down (see the other responses) it would make sense to monitor them for any events.
Cheers,
Julius

Setting up a Log File monitor to inactivity for a set amount of time

I have set up a number of log file monitors to alert when certain conditions apply, such as the word "ERROR" or "exception". Now I have a request to set up an alert if the log file has not changed for 20 minutes. I have been
searching and have not found any information on how or if this can be done. Anyone???
I am running Operations Manager 2012 SP1
The log files are simple text files.

Hi!
You could create a timer reset monitor that reads the log file every 19 minutes for a wildcard pattern (everything matches) and configure the successful search to healthy. Further, you've to configure the timer reset to 20 minutes and configure the
timer reset state to unhealthy (warning/critical).
Keep in mind that SCOM reads from the last line from the previous run every time. If your file rotates (based on a schedule or size) SCOM will not read the lines until the latest line is reached. For more information refer to
http://www.systemcenterrocks.com/2011/06/log-file-monitoring.html
HTH, Patrick
Please 'Propose/Mark as answer' if this post solved your problem. <br/> <br/> http://www.syliance.com | http://www.systemcenterrocks.com

Alert Log File Monitoring of 8i and 9i Databases with EM Grid Control 10g

Is it possible to monitor alert log errors in Oracle 8i/9i Databases with EM Grid Control 10g and EM 10g agents? If yes, is it possible to get some kind of notification?
I know that in 10g Database, it is possible to use server generated alerts, but what about 8i/9i?
Regards,
Martin

Hello
i am interested in a very special feature: is it possible to get notified if alerts occur in alert logs in an 8i/9i database when using Grid control and the 10g agent on the 8i/9i systems?
Moreover, the 10g agent should be able to get Performance Data using the v$ views or direct sga access without using statspack, right?
Do you know where I can find documentation about the supported features when using Grid Control with 8i/9i databases?

R12 12.0.4, System Administration, Debug, trace, log enabled monitoring

Hi guys,
I posted the same question with oracle.ittoolbox few days back and yet to get an answer. During the initial stages of implementation, I remember the consultants using a particular jsp/html page under System Administrator responsibility to view the status of diag, trace, log enabled status of the system, akka, if a profile option is enabled to debug, trace, or log was listed...
Now, I want to access the same page (I have system administrator resp). The SQL query provided by metalink is too complex to understand
Please help

Hello again Hussein and others
Our issue was NOT just with FND% profiles, rather with the consultants turning on diag and debug against their respective modules and later forgetting to turn them off. Take our case, we had SLA Debug enabled from last 2010 Feb until two days back, which has created 21 million rows of data with XLA diag table :)
Once after turning the SLA debug and truncating the table (following Oracle guidelines) we have a database which is 1/3 of the size until recent times. Oracle has provided us an SQL query which produces the present status of all profiles with latest values (enabled or disabled). We were able to see a number of profiles with debug enabled and successfully disabled them.
I represent the internal IT team and always have the acceptance for human errors like the SLA debug event. Oracle "apologized" for not having a screen or html form for monitoring such resource hungry activities. The output from the SQL script they provided is too complex for a person who doesn't have core techno functional knowledge about the system.
Anyway, finally feeling a bit better...
Thanks guys

LockManager log or monitor?

Hi,
I've been playing around with the txn attribute of our outermost facade SSB in our architecture.
Its one and only method used to be 'NotSupported' due to many reasons, including the 'diamond
problem' fixed in as well as pessimistic/deadlock issues. WL 5.1 has subsequently came out a sp
fix for the diamond, and I've re-architected many things to avoid concurrent entity bean access.
This week I switched this SSB from 'NotSupported' to 'Required'; unfortunately we witnessed many
deadlock/timeout issues. Ultimately I debugged this by running a load generator that executed 10
identical tasks simultaneously and did a 'kill -3'; the stacktraces below clearly shows 9 out of 10
threads are all locking on the same entity bean: RoleBean.
I was wondering if there is a LockManager log or an ability to monitor LockManager in cases like
these? It would be REALLY nice for WL to notice us when locking occurs either frequently or for a
prolonged time (say, over 10 seconds)... this way we can diagnose the problems easily without
having to do server 'kill -3's.
Anyone know of such a debug flag or log? If such does not exist, is this not a reasonable
enhancement to ask for? ;-)
Gene
"ExecuteThread-10" daemon prio=5 tid=0x2b4760 nid=0x17 waiting on monitor [0xec580000..0xec581a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-9" daemon prio=5 tid=0x2b2218 nid=0x16 waiting on monitor [0xec680000..0xec681a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-8" daemon prio=5 tid=0x2b2078 nid=0x15 runnable [0xec77f000..0xec781a30]
at oracle.jdbc.oci8.OCIDBAccess.do_execute(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java:1107)
at oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1232)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1313)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1353)
at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1807)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:332)
at weblogic.jdbcbase.jts.Statement.executeUpdate(Statement.java:317)
at
weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:54)
at
weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatement.java:55)
at com.kiko.bean.access.AccessQuery.executeAccessProcedure(AccessQuery.java:548)
at com.kiko.bean.access.AccessQuery.executeAccessInstanceProcedure(AccessQuery.java:520)
at com.kiko.bean.access.AccessQuery.getAccessInstances(AccessQuery.java:336)
at com.kiko.bean.access.AccessQuery.getInstances(AccessQuery.java:226)
at com.kiko.bean.access.InstanceManager.getInstances(InstanceManager.java:241)
at
com.kiko.ejb.service.permission.PermissionManagerBean.getAccessPermissions(PermissionManagerBean.jav
a:303)
at
com.kiko.ejb.service.permission.PermissionManagerBean.getPermissions(PermissionManagerBean.java:119)
at
com.kiko.ejb.service.permission.PermissionManagerBeanEOImpl.getPermissions(PermissionManagerBeanEOIm
pl.java:362)
at
com.kiko.ejb.service.permission.PermissionManagerBeanEOImpl_ServiceStub.getPermissions(PermissionMan
agerBeanEOImpl_ServiceStub.java:447)
at com.kiko.ejb.service.graph.GraphManagerBean.getPermissions(GraphManagerBean.java:1294)
at
com.kiko.ejb.service.graph.GraphManagerBeanEOImpl.getPermissions(GraphManagerBeanEOImpl.java:262)
at
com.kiko.ejb.service.graph.GraphManagerBeanEOImpl_ServiceStub.getPermissions(GraphManagerBeanEOImpl_
ServiceStub.java:2067)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBean.getAllPermissions(XMLStoreManagerBean.java:2524)
at com.kiko.ejb.service.xmlstore.XMLStoreManagerBean.setXML(XMLStoreManagerBean.java:195)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBeanEOImpl.setXML(XMLStoreManagerBeanEOImpl.java:1061)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBeanEOImpl_ServiceStub.setXML(XMLStoreManagerBeanEOImpl
_ServiceStub.java:1763)
at
com.kiko.bean.AbstractPersistentBeanManager.setXML(AbstractPersistentBeanManager.java:460)
at com.kiko.bean.AbstractPersistentBeanManager.save(AbstractPersistentBeanManager.java:1130)
at com.kiko.bean.AbstractPersistentBeanManager.save(AbstractPersistentBeanManager.java:1079)
at com.kiko.bean.AbstractPersistentBean.save(AbstractPersistentBean.java:313)
at com.kiko.state.member.CreateLearningCenter.execute(CreateLearningCenter.java:95)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-7" daemon prio=5 tid=0x2b1598 nid=0x14 waiting on monitor [0xec880000..0xec881a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-6" daemon prio=5 tid=0x2b0ab8 nid=0x13 waiting on monitor [0xec980000..0xec981a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-5" daemon prio=5 tid=0x2affd8 nid=0x12 waiting on monitor [0xeca80000..0xeca81a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-4" daemon prio=5 tid=0x2af4f8 nid=0x11 waiting on monitor [0xecb80000..0xecb81a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-3" daemon prio=5 tid=0x2adf00 nid=0x10 waiting on monitor [0xecc80000..0xecc81a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
at com.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-2" daemon prio=5 tid=0x2adc98 nid=0xf waiting on monitor [0xecd80000..0xecd81a30]
at java.lang.Object.wait(Native Method)
at weblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.Loc

Well, I KNOW RoleBean is now the deadlocker by doing 'kill -3' and found a way in my codes to
circumvent it.
What I want, though, is for LockManager to warn me of potential deadlocking beans. For example, if
it witnesses beans that are consistently being locked, or locked for an unreasonably long time
(threshhold can be set, say, 1 second), for LockManager to LOG the suspected bean so I can inspect
the log and say "a ha, there's the culprit!". This bean can be RoleBean, GroupBean, or any bean I
have in my application.
I was wondering if this feature is already availabe in LockManager, or if not, would it be
reasonable to add it?
Gene
"Dimitri Rakitine" <[email protected]> wrote in message news:[email protected]...
If you suspect a deadlock I guess you can instrument the RoleBean, for example:
class LockDebugger {
static Hashtable waiters = new Hashtable();
static Hashtable owners = new Hashtable();
public static tryLock(pk) {
waiters.put(Thread.currentThread(), new Exception()); // or stacktrace and pk
public static locked(pk) {
owners.put(Thread.currentThread(), new Exception()); // or stacktrace and pk
and make each method in RoleBean to call LockDebugger.locked() and MemberBean to
call LockDebugger.tryLock() before it uses RoleBean. Then you can make LockDebugger
to spawn an extra thread which listens on some port and dumps lock states - when the
deadlock happens you telnet to this port and look at the lockStates. In case of a deadlock
this should be enough to track it's origin.
In weblogic.developer.interest.ejb Gene Chuang <[email protected]> wrote:
Hi,
I've been playing around with the txn attribute of our outermost facade SSB in our architecture.
Its one and only method used to be 'NotSupported' due to many reasons, including the 'diamond
problem' fixed in as well as pessimistic/deadlock issues. WL 5.1 has subsequently came out a
sp
fix for the diamond, and I've re-architected many things to avoid concurrent entity bean access.
This week I switched this SSB from 'NotSupported' to 'Required'; unfortunately we witnessed
many
deadlock/timeout issues. Ultimately I debugged this by running a load generator that executed10
identical tasks simultaneously and did a 'kill -3'; the stacktraces below clearly shows 9 outof 10
threads are all locking on the same entity bean: RoleBean.
I was wondering if there is a LockManager log or an ability to monitor LockManager in cases like
these? It would be REALLY nice for WL to notice us when locking occurs either frequently or for
a
prolonged time (say, over 10 seconds)... this way we can diagnose the problems easily without
having to do server 'kill -3's.
Anyone know of such a debug flag or log? If such does not exist, is this not a reasonable
enhancement to ask for? ;-)
Gene
"ExecuteThread-10" daemon prio=5 tid=0x2b4760 nid=0x17 waiting on monitor
[0xec580000..0xec581a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-9" daemon prio=5 tid=0x2b2218 nid=0x16 waiting on monitor
[0xec680000..0xec681a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-8" daemon prio=5 tid=0x2b2078 nid=0x15 runnable [0xec77f000..0xec781a30]
at oracle.jdbc.oci8.OCIDBAccess.do_execute(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java:1107)
at oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1232)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1313)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1353)
at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1807)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:332)
at weblogic.jdbcbase.jts.Statement.executeUpdate(Statement.java:317)
at
weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:54)
at
weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatement.java:55)
at com.kiko.bean.access.AccessQuery.executeAccessProcedure(AccessQuery.java:548)
at com.kiko.bean.access.AccessQuery.executeAccessInstanceProcedure(AccessQuery.java:520)
at com.kiko.bean.access.AccessQuery.getAccessInstances(AccessQuery.java:336)
at com.kiko.bean.access.AccessQuery.getInstances(AccessQuery.java:226)
at com.kiko.bean.access.InstanceManager.getInstances(InstanceManager.java:241)
at
com.kiko.ejb.service.permission.PermissionManagerBean.getAccessPermissions(PermissionManagerBean.jav
a:303)
at
com.kiko.ejb.service.permission.PermissionManagerBean.getPermissions(PermissionManagerBean.java:119)
at
com.kiko.ejb.service.permission.PermissionManagerBeanEOImpl.getPermissions(PermissionManagerBeanEOIm
pl.java:362)
at
com.kiko.ejb.service.permission.PermissionManagerBeanEOImpl_ServiceStub.getPermissions(PermissionMan
agerBeanEOImpl_ServiceStub.java:447)
atcom.kiko.ejb.service.graph.GraphManagerBean.getPermissions(GraphManagerBean.java:1294)
at
com.kiko.ejb.service.graph.GraphManagerBeanEOImpl.getPermissions(GraphManagerBeanEOImpl.java:262)
at
com.kiko.ejb.service.graph.GraphManagerBeanEOImpl_ServiceStub.getPermissions(GraphManagerBeanEOImpl_
ServiceStub.java:2067)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBean.getAllPermissions(XMLStoreManagerBean.java:2524)
atcom.kiko.ejb.service.xmlstore.XMLStoreManagerBean.setXML(XMLStoreManagerBean.java:195)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBeanEOImpl.setXML(XMLStoreManagerBeanEOImpl.java:1061)
at
com.kiko.ejb.service.xmlstore.XMLStoreManagerBeanEOImpl_ServiceStub.setXML(XMLStoreManagerBeanEOImpl
_ServiceStub.java:1763)
at
com.kiko.bean.AbstractPersistentBeanManager.setXML(AbstractPersistentBeanManager.java:460)
atcom.kiko.bean.AbstractPersistentBeanManager.save(AbstractPersistentBeanManager.java:1130)
atcom.kiko.bean.AbstractPersistentBeanManager.save(AbstractPersistentBeanManager.java:1079)
at com.kiko.bean.AbstractPersistentBean.save(AbstractPersistentBean.java:313)
at com.kiko.state.member.CreateLearningCenter.execute(CreateLearningCenter.java:95)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-7" daemon prio=5 tid=0x2b1598 nid=0x14 waiting on monitor
[0xec880000..0xec881a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-6" daemon prio=5 tid=0x2b0ab8 nid=0x13 waiting on monitor
[0xec980000..0xec981a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-5" daemon prio=5 tid=0x2affd8 nid=0x12 waiting on monitor
[0xeca80000..0xeca81a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-4" daemon prio=5 tid=0x2af4f8 nid=0x11 waiting on monitor
[0xecb80000..0xecb81a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:445)
at com.kiko.ejb.entity.access.RoleBeanEOImpl.getKey(RoleBeanEOImpl.java:297)
at com.kiko.ejb.entity.member.MemberBean.ejbCreate(MemberBean.java:158)
at com.kiko.ejb.entity.member.MemberBeanEOImpl.create(MemberBeanEOImpl.java:54)
at com.kiko.ejb.entity.member.MemberBeanHomeImpl.create(MemberBeanHomeImpl.java:32)
at
com.kiko.ejb.entity.member.MemberBeanHomeImpl_ServiceStub.create(MemberBeanHomeImpl_ServiceStub.java
:113)
at com.kiko.ejb.service.member.MemberManagerBean.createMember(MemberManagerBean.java:82)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl.createMember(MemberManagerBeanEOImpl.java:107)
at
com.kiko.ejb.service.member.MemberManagerBeanEOImpl_ServiceStub.createMember(MemberManagerBeanEOImpl
_ServiceStub.java:367)
at com.kiko.state.member.SaveMember.execute(SaveMember.java:414)
at com.kiko.state.AbstractProcessState.executeProcess(AbstractProcessState.java:96)
at com.kiko.state.StateMachineEngine.executeState(StateMachineEngine.java:369)
at com.kiko.state.StateMachineEngine.execute(StateMachineEngine.java:175)
at com.kiko.ejb.service.state.StateMachineBean.execute(StateMachineBean.java:51)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl.execute(StateMachineBeanEOImpl.java:107)
at
com.kiko.ejb.service.state.StateMachineBeanEOImpl_ServiceStub.execute(StateMachineBeanEOImpl_Service
Stub.java:161)
at com.kiko.state.StateMachine.execute(StateMachine.java:148)
atcom.kiko.servlet.StateMachineServlet.processRequestInternal(StateMachineServlet.java:145)
at com.kiko.servlet.StateMachineServlet.processRequest(StateMachineServlet.java:82)
at com.kiko.servlet.AbstractServlet.doGet(AbstractServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-3" daemon prio=5 tid=0x2adf00 nid=0x10 waiting on monitor
[0xecc80000..0xecc81a30]
at java.lang.Object.wait(Native Method)
atweblogic.ejb.internal.LockManagerImpl$LockEntry.waitWithtimeout(LockManagerImpl.java:263)
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:44)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:138)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:448)
at

Automatic log files monitoring

Hi all!
is there any tool available which is capable of checking or monitoring my log files, maybe against some (pre)defined rules, and alerts me if some error/failure occurs?
Best regards!

Splunk is nice, but it is non-free. It looks like fluentd (AUR) can do the same stuff, though. I haven't tried fluentd personally, but it looks pretty cool.

I am using fieldpoint and labview to log and monitor the temperatures of my system. but i am not using Labview 6i with DSC, how can i do it??

i am using fieldpoint 2.0 and labview 6i to monitor my system, but i think i don't have labview DSC.

I have written a relatively large Fieldpoint application "just" using LV5.1 FDS, so it can be done.
Fieldpoint can be seen as an external instrument, so you need to use the driver/vi's that comes with FP.
I believe using DSC would only make the job easier for you.

IPS log and monitoring

Hi, All
Few Queries on Cisco IPS.!!!!
1. Which are best tool for fetching cisco IPS logs??
2. Where or Which directory Cisco Logs/Events are saved?
3. I am only able to see today log but not able to view past any logs? what are possible cause?
4. Any free-ware tool that fetch logs and events from cisco IPS?
5. Cisco IPS express manager is free-ware or we need only cisco customer account?
For any type of help.. Thanks
Jignesh

1. You can use IME (IPS Manager Express) to view all your IPS events.
Here is the IME page for your reference:
http://www.cisco.com/en/US/products/ps9610/index.html
2. The logs on the IPS device itself has very small storage space and it wraps once the log is full, therefore if you have a lot of events triggered, you are only able to see the latest events.
3. As per my above description.
4. Cisco IME - it's free (no extra license is required to use IME).
5. As long as you have CCO account, you should be able to download the IME software.
Hope this helps.

Admin logs to monitor all the changes done in ESA

We have a situation wherein we want to see who accessed the Ironport ESA appliance and did a configuration change. Would we be able to do it? or Can Cisco Support can find it out from backend?

Grep your system_logs files for the word "commit". That will list the date/time and person who committed a change, along with their description of the change if they provided one. Of course, their description is only as accurate as they wanted it to be.
Wed May 7 12:42:34 2014 Info: PID 1633: User jsmith commit changes: Added SMTP route for new email domain new.mycompany.com.

Unix Log Monitoring regular expression not picking up alerts

Hi,
We are moving our unix monitoring to SCOM 2012 SP1 rollup 4.
What I have got working is indvidual alert logging of Unix Log alerts by exporting the MP and changing the <IndividualAlerts> value to true and removing the suppression xml section then reimporting the MP.
What I am trying to do is use the regular expression to peform the suppression of specific event (such as event codes).
The expression is:
((?i:warning)(?!(.*1222)|(.*1001)))
ie Search the log for "warning" (not case sensitive) then check if events 1222 or 1001 exist if so return no match, if they dont exist then return true.
I use the built in test function in SCOM when creating the rule and the tests come back as expected but when I inject test lines into the unix log, no alerts get generted.
I suspect it could be the syntax not being accepted on the system (its running RedHat 6 )
I have tested this with regex tools and works.
When I try and test it on the server i get:
[root@bld02 ~]# grep ((?i:Warning)(?!(.*1222)|(.*1001))) /var/log/messages
-bash: !: event not found
[root@bld02 ~]# tail /var/log/messages
Nov 13 15:07:26 bld02 root: SCOM Test Warning Event ID 1001 Round 18
Nov 13 15:07:29 bld02 root: SCOM Test Warning Event ID 1000 Round 18
Nov 13 15:07:35 bld02 root: SCOM Test Warning Event ID 1002 Round 18
So I am expecting 2 alerts to be generated.
SCOM tests to show expression working:
Test 1 Matching
Test 2 to exclude
Need some help with this, Thankyou in advance :)

Hello,
Here's an example of modifying the MP to exclude particular events. Firstly, I created a log file rule using the MP template that is fairly inclusive - matching the string Warning (with either a lower or upper case W).
I then exported the MP, and modified the rule. I set the IndividualAlerts = true and removed the AlertSuppression element, so that every matched line will fire a unique alert. You don't have to remove the AlertSuppression, but you should use
Individual alerts so that the exclusion logic doesn't exclude concurrent events that you actually want to match.
Implementing the exclusion logic involves the addition of a System.ExpressionFilter definition in the rule. This will use a conditional evaluation of the //row element of the data item. Here's an example of a dataitem matching an individual row:
<DataItem type="System.Event.Data"time="2013-11-15T10:33:14.8839662-08:00"sourceHealthServiceId="667FF365-70DD-6607-5B66-F9F95253B29F">
<EventOriginId>{86AB962D-2F44-29FD-A909-B99FF6FEB2C5}</EventOriginId>
<PublisherId>{EC7EA4B1-0EA5-7E8E-701F-82FEF3367BC4}</PublisherId>
<PublisherName>WSManEventProvider</PublisherName>
<EventSourceName>WSManEventProvider</EventSourceName>
<Channel>WSManEventProvider</Channel>
<LoggingComputer/>
<EventNumber>0</EventNumber>
<EventCategory>3</EventCategory>
<EventLevel>0</EventLevel>
<UserName/>
<RawDescription>Detected Entry: warning 1002</RawDescription>
<CollectDescription Type="Boolean">true</CollectDescription>
<EventData>
<DataItem type="SCXLogProviderDataSourceData"time="2013-11-15T10:33:14.8839662-08:00"sourceHealthServiceId="667FF365-70DD-6607-5B66-F9F95253B29F">
<SCXLogProviderDataSourceData>
<row>warning 1002</row>
</SCXLogProviderDataSourceData>
</DataItem>
</EventData>
<EventDisplayNumber>0</EventDisplayNumber>
<EventDescription>Detected Entry: warning 1002</EventDescription>
</DataItem>
Here is the rule in the MP XML. The <ConditionDetection>...</ConditionDetection> content was what I added to do the exclusion filtering:
<Rule ID="LogFileTemplate_66b86eaded094c309ffd2631b8367a32.Alert" Enabled="false" Target="Unix!Microsoft.Unix.Computer" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Unix!Microsoft.Unix.SCXLog.VarPriv.DataSource">
<Host>$Target/Property[Type="Unix!Microsoft.Unix.Computer"]/PrincipalName$</Host>
<LogFile>/tmp/test</LogFile>
<UserName>$RunAs[Name="Unix!Microsoft.Unix.ActionAccount"]/UserName$</UserName>
<Password>$RunAs[Name="Unix!Microsoft.Unix.ActionAccount"]/Password$</Password>
<RegExpFilter>warning</RegExpFilter>
<IndividualAlerts>true</IndividualAlerts>
</DataSource>
</DataSources>
<ConditionDetection TypeID="System!System.ExpressionFilter" ID="Filter">
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">//row</XPathQuery>
</ValueExpression>
<Operator>DoesNotContainSubstring</Operator>
<Pattern>1001</Pattern>
</RegExExpression>
</Expression>
</ConditionDetection>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertName>Log File Alert: ExclusionExample</AlertName>
<AlertDescription>$Data/EventDescription$</AlertDescription>
</WriteAction>
</WriteActions>
</Rule>
I traced this with the Workflow Analyzer as I tested, which shows the logic being applied. Here is the exclusion happening:
Here's more info on the definition of an ExpressionFilter:
http://msdn.microsoft.com/en-us/library/ee692979.aspx
And more information on Regular Expressions in MPs:
http://support.microsoft.com/kb/2702651/en-us
You can also have multiple Expressions in the ExpressionFilter joined by OR or AND operators.
Also, if you are comfortable with the MP authoring, you can just skip the step of creating the rules in the MP template and just author your own MP with the VSAE tool:
http://social.technet.microsoft.com/wiki/contents/articles/18085.scom-2012-authoring-unixlinux-log-file-monitoring-rules.aspx
www.operatingquadrant.com

Deleting a request in ODS that has no request number and monitor log

Hai All,
I have a request that failed. It oesn't even have a request id and is not getting deleted. Even if I delete it, the trash can symbol appears onits side and then disappears but the request still satys. I changed the status to red and deleted. Still its not getting deleted. There is no log in monitor also. I have a lot of data in the ODS and cannot afford to delete all data and load. Is there any table in SAP where I cn go in and delete it or is there any other way around?

Hello BI,
Please check the job logs in SM37 and see what job log says for deleting ODS request at the end though the job finished successfully. See if the job is still running in SM51 at the backend on server. If so please stop that job. I doubt that the request is still running either in R3 or BW in the backend. That could be one reason why it sometimes doesnt allow the request to be deleted.
Hope this helps,
Bye,
Naga.
Message was edited by: Naga Timmaraju

Recommendations for log monitoring software

Hi there
I'm looking for recommendations of log file monitoring software, preferably with a GUI rather than purely CLI based.
I need to collate and monitor log files from OSX servers, OSX clients, antivirus software, network switches and firewalls.
Any ideas?

Hi and thanks for the advice. I've been looking at Splunk, but it seems a little complicated to set up. Guess I'll keep plugging away at it....

Logging in monitoring

Similar Messages

Maybe you are looking for