Internal DC log

Hi,
I'm facing a minor issue with the log for the internal delivery channel. Here is a snippet from my ip/config/tip.properties file:
oracle.tip.adapter.b2b.appTransportTrace = /tmp/apptransport.log
oracle.tip.adapter.b2b.transportTrace = /tmp/transport.log
Both the above files are created in the tmp directory but the apptransport (internal delivery channels)file remains empty and the other
one (external delivery channel) grows in size as more logs are written in.
Is the appTransportTrace a deprecated feature (after patch 3) or is it still in use ? Also, note that I manually edited the tip.properties file as it did not show these properties in the UI. Do let me know in case someone has used this property successfully.
regards,
Narayanan

Hi Ramesh,
Yes, the empty file is what I observed. Actually what I was trying to find out was if the state of a transaction changes to "Complete" before or after writing to the internal delivery channel.
If the high level steps involved are the following:
1. Inbound File (say 850) picked up from VAN and successfully translated to XML.
2. Ack (997) created and sent out.
3. 850 XML instance written to internal delivery channel.
Then, Is there a message state which provides information if (3) fails ? Or does "Complete" indicate that (3) was successful.
regards,
Narayanan

Similar Messages

Regarding internal daemon log rotation...

I found a problem with internal daemon log rotation in iplanet webserver.it is not happening properly..........how to troble shoot this issue?

Web Server 6.0 is EOSLed. Please move to the newer Web Servers 6.1 or 7.0. Check [http://www.sun.com/download/index.jsp?cat=Web%20%26%20Proxy%20Servers&tab=3&subcat=Web%20Servers|http://www.sun.com/download/index.jsp?cat=Web%20%26%20Proxy%20Servers&tab=3&subcat=Web%20Servers]. If you still have problems in these(6.1 or 7.0) versions of Web Server let us know.

SQ Developer internal SQL Log

Is there a way to watch the internal SQL calls that SQL Developer issues to the DB (for example, the SQL it uses to calculate the dependencies tab in the Materialized View properties window)? I need to do something very similar, and it would be nice if I could use that code as a starting point.
I could swear I had seen and used it a while back, but my age must be showing, because I can't find either it or any reference to it on this forum.
Thanks,
Archer

Setting the Log Level to Finest (though the context menu in the Logging Page ), you should see all the statements issued.
You might have to set this in sqldeveloper\bin\sqldeveloper.conf:
#IncludeConfFile sqldeveloper-nondebug.conf
IncludeConfFile sqldeveloper-debug.confHope that helps,
K.

When is Internal Manager log file updated?

Hi:
I thought SID_date.mgr file (on 12.1.3 and db 11.1.0.7, linux) is created when you start applications. I saw entries today. Would you please tell me when and what this file is updated?
Thanks.

gbite wrote:
Apart from the head of the log saying the ICM is starting etc, I get the following every 2-3 minutes:
Process monitor session ended : 25-APR-2012 17:07:35Process Monitor Started and Ended Every Several Seconds in ICM log file [ID 308809.1]
Many Defunct Processes Created on System [ID 461684.1]
Many Dead Processes Referencing WFMGSMS Concurrent Manager [ID 801362.1]
Concurrent Processing - Concurrent Manager Generic Platform Questions and Answers [ID 105133.1]
Thanks,
Hussein

LV-RT "internal error" logged, connection lost

Please see attached file for full question.
Installed on PXI-8145RT: FlexMotion RT 5.1.0, PabVIEW RT 6.1.0, NI-488.2RT 1.0.0, NI-DAQ RT 6.9.2, NI-Serial RT 2.0.1, NI-VISA 2.6.0.
Attachments:
questions_re_PXI-8145RT,_LabVIEW_RT.doc ‏27 KB
rtlog ‏9 KB

Hi LJ,
You did not mention if you tried putting the "first" controller back in the chasis to try it again.
I have seen similar errors when my memory usage grew beyond what was available. This was a coding error on my part.
Have you tried calling NI and talking to their tech support people? The RT people are pretty sharp and should be able to help you get the module repaired if it is indeed defective.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Javax.transaction.SystemException: Timed out while in 'Logging' state!!!!

Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
     - locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
     at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
     at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
     at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
     at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
     at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
     at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
     at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
     at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
     at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
     at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM

Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
     - locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
     at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
     at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
     at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
     at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
     at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
     at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
     at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
     at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
     at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
     at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM

Java.lang.NullPointerException at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:292)

          Hi,
          intermittently we are seeing this exception in the server log files on weblogic 6.1
          sp2, I was wondering what the cause is:
          java.lang.NullPointerException
               at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:292)
               at weblogic.servlet.internal.HttpServer.log(HttpServer.java:835)
               at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1002)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2209)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


Did your C:\Lighthammer\Security\userdata\IlluminatorUsers.xml or other files in this directory get corrupted somehow?
If you've rebooted the box or bounced the ServletExec-xMII service, do you see anything in the SYSTEM level messages that are forced during the initialization sequence in either the Lighthammer General log or the LHSecurity General log that would give any indications to the problem?
Regards,
Jeremy

Trouble with FCP7, .mts, and Log and Transfer

I'm trying to upload footage from a Canon Vixia S200, and Log and Transfer won't work. For reference, the footage is stored on the SD cards in the camera rather than internal memory. When I tried Log and Transfer for an older Vixia that used internal memory, Log and Transfer worked. Is there some way around this?

FCP 7 doesn't work with 1080p60. That format came out after it's last update. You need to use ClipWrap2 to convert the footage to ProRes 422...or use another editing app that will work with this footage.

Should I use the built in log rolling function on iWS 6 or roll my own using a cron job using stop and start scripts in the web server instance root?

Hi,
You can use either OS cron job based log rotation
OR
Internal daemon log rotation.
It is recommeded to use OS cron job log rotation.
OS=Operating System
Regards,
Dakshin.
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers/support.

Where is my concurrent log file

Hi:
Would you tell how to find the concurrent request log and internal manager log? We have 12.1.3 on linux. I have tried $APPLCSF, $INST_TOP but didn't work.
Thank you.

Would you tell how to find the concurrent request log and internal manager log? We have 12.1.3 on linux. I have tried $APPLCSF, $INST_TOP but didn't work. Concurrent Requests/Manager log files can be found under $APPLCSF/$APPLLOG directory. Concurrent requests output files can be found under $APPLCSF/$APPLOUT directory. Please login as applmgr user and source the application env file before changing to those directories.
You can also view the same from the application:
System Administrator > Concurrent > Manager > Administer > Query the CM > Processes > Internal Manager Log
System Administrator > Requests > View > Query the Concurrent Request > View Log
You can find more details in "Oracle E-Business Suite System Administrator's Guide Documentation Set" -- http://docs.oracle.com/cd/B53825_08/current/html/docset.html
Thanks,
Hussein

Change opmn log level

how to change opmn log level in OAS 10.1.3.3. I want to set it to debug level.
Thanks
AB

Thanks, I looked at the following section but still not sure what exactly to change in opmn.xml
2.2 There used to be a level attribute in the <log-file> tag that I don’t find anymore. How do I define log levels?
In 10.1.3.1.0, logging is configured by component codes rather than level codes. The logging messages contain the literal value based on logging levels rather than an integer value; for example: none, fatal, error, warn, notify, debug1, debug2, debug3, and debug4.
All OPMN log messages of non-debug type (none, fatal, error, warn and notify) for the ONS and PM components go in opmn.log file. If debugging is enabled, then all OPMN debug log messages (of type debug1, debug2, debug3 and debug4) are written into opmn.dbg file.
You can configure the following component codes for logged events for both log and debug:
• internal: a log for the common internal information for OPMN
• ons: a log for the ONS component information for OPMN
• pm: a log for the PM component information for OPMN
Both the ons and pm components consist of subcomponents that can also be configured. Refer to the Oracle Process Manager and Notification Server Administrator’s Guide 10g Release 3 (10.1.3.1.0) for the list of ons and pm subcomponents.
I looked at http://download-west.oracle.com/docs/cd/B25221_04/core.1013/b15976/common.htm#g1044967
and there is a section
<debug>
Required: false
Default: see attributes
Parents: <opmn>
Attributes: path, comp, rotation-size, rotation-hour
Can you tell me an example how i can set it?

Flash Builder crash with error log

I started a trial FB 4.6 a couple of weeks ago. Yesterday FB started crashing arbitrarily while simply using the editor. Error log entries (from workspace/.metadata/.log) like the snippet below immediately precede the crash. FB is open from anywhere between 10 seconds to 20 minutes before crashing.
Crashing: the whole Flash Builder UI locks up and needs to be force-quit.
Problems seemed to start after I did these new things; installed Android USB driver for my device, debugged on the device, and also tried the Profile feature. Doing those things seemed to work fine, and I otherwise don't know what they'd have to do with the message(s like the one) below. At crash time, the file noted is not there, instead there is single file:
"...\.metadata\.plugins\com.adobe.flexbuilder.codemodel\SwcCache\swcPaths.cache".
However as I browse the .plugins folder looking for files related to this problem, I've seen folders/files suddenly appear and disappear, not related to any build process.
I've tried rebooting. I'm going to try changing workspaces. Here's a log snip:
... !ENTRY com.adobe.flexbuilder.project 4 43 2012-01-26 11:32:18.858 !MESSAGE Cannot load nonexistent library swf C:\stuffo7\FlexMoreWorkspace\.metadata\.plugins\com.adobe.flexbuilder.codemodel\SwcCache\ mobile.swc-293353047\library.swf for swc C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\frameworks\themes\Mobile\mobile.swc !STACK 0 java.lang.Exception at com.adobe.flexbuilder.project.internal.FlexProjectCore.createErrorStatus(FlexProjectCore. java:1019) at com.adobe.flexbuilder.project.internal.FlexProjectCore.log(FlexProjectCore.java:867) at com.adobe.flexbuilder.util.logging.GlobalLogImpl.log(GlobalLogImpl.java:56) at com.adobe.flexbuilder.util.logging.GlobalLog.log(GlobalLog.java:41) at com.adobe.flexide.designitems.loaders.LibrarySWCLoader.loadNextSWF(LibrarySWCLoader.java: 111) at com.adobe.flexide.designitems.loaders.LibrarySWCLoader.access$5(LibrarySWCLoader.java:96) at com.adobe.flexide.designitems.loaders.LibrarySWCLoader$SwcLoaderCallbacks.SWFLoaded(Libra rySWCLoader.java:218) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.adobe.flexide.playerview.DesignCall.invoke(DesignCall.java:96) at com.adobe.flexide.playerview.PlayerListenerHost.notifyDesignCall(PlayerListenerHost.java: 173) at com.adobe.flexide.playerview.PlayerListenerHost.callFunction(PlayerListenerHost.java:47) at com.adobe.flexide.embeddedplayer.PlayerNativeCallbacks.CallJavaFunction(PlayerNativeCallb acks.java:48) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2530) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Message was edited by: tedalde2 (fix broken formatting)
Message was edited by: tedalde2 (define crashing)

Apparently related to switching workspaces... the error log identifies a path to an old workspace I changed out of weeks ago. I created a new workspace and moved the project (just the source, etc, not the settings) into it. been running fine for a while now... though funny how this problem didn't show up until yesterday.

Is it possible to rotate log of iplanet server once a month ?

Instead of changing log file each day or each week, I would like to know if is possible to rotate log of iplanet server once a month.

Yes, you may use the internal daemon log rotation (available in iPlanet Web Server 4.x and 6).
Using this new feature introduced in iWS 4, you may set up the rotation start time and the interval for the next rotation to happen (in minutes).
For every hour the interval is 60, every day 1440.
To config internal daemon to perform log rotation every 30 days the interval would be 43200 minutes.

Kodo logging issue on IBM WAS 5.0

Hi All,
Thank you for reading this. I could use a good advice here, I have been
banging my head against wall for a while ...
We have a J2EE application that uses Kodo 2.4.2 with IBM WAS 5.0. Due to
'class not found' problems (related to registering the PMfactory with
JNDI, I reckon), I was forced to use a Websphere extension classloader to
load Kodo. (deploy Kodo libraries to c:\program
files\websphere\AddServer\lib\ext )
That is good and well, however now I want to configure logging (Log4J) for
Kodo. To do that, I have tried (feels like I have tried it all ;-)) to put
the log4j.properties to:
c:\program files\websphere\AddServer\properties\log4j.properties
c:\program files\websphere\AddServer\lib\ext\log4j.jar!log4j.properties
c:\program files\websphere\AddServer\lib\ext\log4j.properties
inside of the Kodo.jar (desperate people do desperate things ;-))
log4j.properties is also referenced as a part of shared library
Just for completness, log4j.properties also exists in Java utility jar
file that is part of EAR file (although that probably would not help the
Websphere extension classloader-loaded classes)
I have also tried to define the log4j.configuration in my startServer.bat:
SET LOG4J=-Dlog4j.configuration=file:/c:/log4j.properties
echo LOG4J set %LOG4J%
"%JAVA_HOME%\bin\java" %LOG4J% %WAS_TRACE%
To initialize Log4J differently. Yes, you guessed right, that damn thing
still does not work. What am I missing???
What exactly is happening when Kodo/Log4j configures the logging?
It may sound like just a nuisance, but it is actually quite important,
because we are just inch from production and need to get rid of heaps of
debuging messages (including the annoying SQL Server induced close cursor
exceptions). It just would not shut up!!! ;-))))
Any idea how to silence the bloody thing beside turning off the power? ;-)
Thank you,
Petr

Petr-
The easiest thing to do would be to put some code in your application
that will give information on the definitive location of the
log4j.properties file. E.g.:
System.out.println (getClass().getClassLoader().getResource("/log4j.properties"));
Other than that, note that there are a variety of System properties you
can use to override the logging system that will be use. The Kodo 2.5
documentation covers this a bit better than the 2.4 docs:
http://www.solarmetric.com/Software/Documentation/2.5.0b1/docs/manual.html#ref_guide_logging
Finally, note that some application servers use log4j internally for
logging, and configure it differently (e.g., JBoss uses a log4j.xml
file, rather than a log4j.properties file). You might want to check the
documentation of your appserver to determine if there is an alternate
mechanism for configuring log4j.
Let us know if you still need help with this.
In article <[email protected]>, Petr Bulanek wrote:
Hi All,
Thank you for reading this. I could use a good advice here, I have been
banging my head against wall for a while ...
We have a J2EE application that uses Kodo 2.4.2 with IBM WAS 5.0. Due to
'class not found' problems (related to registering the PMfactory with
JNDI, I reckon), I was forced to use a Websphere extension classloader to
load Kodo. (deploy Kodo libraries to c:\program
files\websphere\AddServer\lib\ext )
That is good and well, however now I want to configure logging (Log4J) for
Kodo. To do that, I have tried (feels like I have tried it all ;-)) to put
the log4j.properties to:
c:\program files\websphere\AddServer\properties\log4j.properties
c:\program files\websphere\AddServer\lib\ext\log4j.jar!log4j.properties
c:\program files\websphere\AddServer\lib\ext\log4j.properties
inside of the Kodo.jar (desperate people do desperate things ;-))
log4j.properties is also referenced as a part of shared library
Just for completness, log4j.properties also exists in Java utility jar
file that is part of EAR file (although that probably would not help the
Websphere extension classloader-loaded classes)
I have also tried to define the log4j.configuration in my startServer.bat:
SET LOG4J=-Dlog4j.configuration=file:/c:/log4j.properties
echo LOG4J set %LOG4J%
"%JAVA_HOME%\bin\java" %LOG4J% %WAS_TRACE%
To initialize Log4J differently. Yes, you guessed right, that damn thing
still does not work. What am I missing???
What exactly is happening when Kodo/Log4j configures the logging?
It may sound like just a nuisance, but it is actually quite important,
because we are just inch from production and need to get rid of heaps of
debuging messages (including the annoying SQL Server induced close cursor
exceptions). It just would not shut up!!! ;-))))
Any idea how to silence the bloody thing beside turning off the power? ;-)
Thank you,
Petr
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Internal monitor ,debug service and Workflow Document Web Services Service

hi,
I have my production oracle apps:R12 12.0.6 ,RHEL 4
showing following error in oracle forms:
internal monitor showing actual 0 and target 1,debug service actual 0 and target 1 and Workflow Document Web Services Service actual 0 and target 1.
Please reply urgently

Hi,
It means, those managers are down.
1. Did you try to restart "Workflow Document Web Services Service" by clicking restart button from Administor Screen ?
2. Were they up and running ? if yes, was there any recent change ?
3. Please check internal manager log and look for any error
4. Use the below Navigation to get more details
From OAM > workflow > Service components > click Web Services OUT Agent > View Log
Thanks
Edited by: user763619 on Jan 16, 2011 9:53 PM

Internal DC log

Similar Messages

Maybe you are looking for