Jdbc log file

Hi all,
Do you know how it is possible to reduce the degree of what is logged in
jdbc.log.
Thanks

Hi Jen!
This is bug in 8.1ga and sp1 and it is fixed ib 81sp2.
When you specify jdbc log name with ".log" suffix, jdbc logging doesn't
rotate as expected. So, the prior log file would be overwrited by new jdbc
log when you restart WLS.
Workaround
Remove ".log" from the file name. It would be added by WLS automatically.
Thanks,
Mitesh
Jen wrote:
Hi,
whenever I restart the wls8.1, the jdbc logs are rewritten. I could not find my
previous log to debug anymore, how can i config to make write to a new file like
wls log. Thanks

Similar Messages

  • How to keep the old jdbc log file

    Hi,
    whenever I restart the wls8.1, the jdbc logs are rewritten. I could not find my
    previous log to debug anymore, how can i config to make write to a new file like
    wls log. Thanks

    Hi Jen!
    This is bug in 8.1ga and sp1 and it is fixed ib 81sp2.
    When you specify jdbc log name with ".log" suffix, jdbc logging doesn't
    rotate as expected. So, the prior log file would be overwrited by new jdbc
    log when you restart WLS.
    Workaround
    Remove ".log" from the file name. It would be added by WLS automatically.
    Thanks,
    Mitesh
    Jen wrote:
    Hi,
    whenever I restart the wls8.1, the jdbc logs are rewritten. I could not find my
    previous log to debug anymore, how can i config to make write to a new file like
    wls log. Thanks

  • SQL queries in JDBC log?

    Hi all.
    I am using CMP entity beans on Weblogic 7.0 and would like to see the SQL queries
    which the EJB container is executing. I would think that I should be able to see
    these in the JDBC log file, but all I see there is DB connection logging.
    I've seen discussion in docs and various newsgroups that implies that these queries
    should be logged in the JDBC log. Do I have to change some parameter in order
    to see the SQL queries in the log file?
    Thanks.
    AL

    I'm using Sybase 12.5 with JConnect 4.5. Since I posted my question, I've found
    a suggestion to define weblogic.ejb20.cmp.rdbms.codegen.verbose=true on the java
    command line when I'm booting WLS. I can now see queries (as well as a bunch of
    other stuff) in the stdout of the weblogic server. But I would still like to have
    the queries logged. Of course, I could redirect stdout, etc. But I thought there
    should be another way, esp considering that the is a JDBC log file. Any suggestions
    would be appreciated.
    AL
    Joe Weinstein <[email protected]> wrote:
    >
    >
    AL wrote:
    Hi all.
    I am using CMP entity beans on Weblogic 7.0 and would like to see theSQL queries
    which the EJB container is executing. I would think that I should beable to see
    these in the JDBC log file, but all I see there is DB connection logging.
    I've seen discussion in docs and various newsgroups that implies thatthese queries
    should be logged in the JDBC log. Do I have to change some parameterin order
    to see the SQL queries in the log file?For 7.0 we do not intercept, copy or log application SQL. Typically jdbc
    logging
    is left to the particular JDBC driver being used. Some drivers can be
    very informative
    or even over chatty, while others will log very little. What DBMS and
    driver are you
    using?
    Joe
    Thanks.
    AL

  • JDBC logging disabled with Oracle thin driver

    Hi,
    I am trying to turn on JDBC logging through the weblogic console application (WL
    6.1 with CMP). In the jdbc log file I do not see the SQL statments.
    It looks like logging is somehow disabled (check one of the logs statements below)
    by some means. Any ideas, I am making use of oracle thin driver.
    Thanks
    Mohit
    Following log messages are generated!!!!!!
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
    trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DRVR OPER Disabled logging
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
    registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing

    Mohit,
    Remove oracle/jdbc/driver/OracleLog from classes12.zip, and it should
    work (it needs to pick up only this class from weblogic.jar).
    Paul
    Hi,
    I am trying to turn on JDBC logging through the weblogic console application (WL
    6.1 with CMP). In the jdbc log file I do not see the SQL statments.
    It looks like logging is somehow disabled (check one of the logs statements below)
    by some means. Any ideas, I am making use of oracle thin driver.
    Thanks
    Mohit
    Following log messages are generated!!!!!!
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
    trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
    DRVR OPER Disabled logging
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
    registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 Statement.setEscapeProcessing
    DRVR DBG1 doDefaultTypes
    DRVR DBG1 doDefinesFromTypes
    DRVR DBG1 ResultSet.getMetaData
    DRVR DBG1 Statement.setEscapeProcessing

  • Informix JDBC logging fails at WLS startup

    Hi,
    I am trying to find out how to see how many db queries I'm doing
    for a CMP finder. I am using the Informix driver I downloaded
    from BEA. When I start up WebLogic, I get the following in the
    jdbc.log file:
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver:
    driver className=weblogic.jdbc.informix4.Driver,weblogic.jdbc.informix4.Driver@20e990]
    SQLException: SQLState() vendor code(-255)
    weblogic.jdbcbase.informix4.InformixException: Informix error: -255 minor code=[0]
    [ at processUpdate <Error> ] See Informix error codes for explanation
    The Informix error manual says -255 means this was not in a
    transaction. It seems to imply that WLS, in trying to start
    logging, was ending a transaction.
    The rest of the stacktrace shows:
    at weblogic.jdbcbase.informix4.Statement.processError Statement.java:1579)
         at weblogic.jdbcbase.informix4.Statement.processUpdate(Statement.java:1344)
         at weblogic.jdbcbase.informix4.Statement.getMoreResults(Statement.java:1100)
         at weblogic.jdbcbase.informix4.Statement.execute(Statement.java:243)
         at weblogic.jdbcbase.informix4.Connection.findDBType(Connection.java:173)
         at weblogic.jdbc.informix4.Driver.newConnection(Driver.java:45)
         at weblogic.jdbcbase.informix4.BaseDriver.connect(BaseDriver.java:96)
         at

    Hi,
    I am trying to find out how to see how many db queries I'm doing
    for a CMP finder. I am using the Informix driver I downloaded
    from BEA. When I start up WebLogic, I get the following in the
    jdbc.log file:
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver:
    driver className=weblogic.jdbc.informix4.Driver,weblogic.jdbc.informix4.Driver@20e990]
    SQLException: SQLState() vendor code(-255)
    weblogic.jdbcbase.informix4.InformixException: Informix error: -255 minor code=[0]
    [ at processUpdate <Error> ] See Informix error codes for explanation
    The Informix error manual says -255 means this was not in a
    transaction. It seems to imply that WLS, in trying to start
    logging, was ending a transaction.
    The rest of the stacktrace shows:
    at weblogic.jdbcbase.informix4.Statement.processError Statement.java:1579)
         at weblogic.jdbcbase.informix4.Statement.processUpdate(Statement.java:1344)
         at weblogic.jdbcbase.informix4.Statement.getMoreResults(Statement.java:1100)
         at weblogic.jdbcbase.informix4.Statement.execute(Statement.java:243)
         at weblogic.jdbcbase.informix4.Connection.findDBType(Connection.java:173)
         at weblogic.jdbc.informix4.Driver.newConnection(Driver.java:45)
         at weblogic.jdbcbase.informix4.BaseDriver.connect(BaseDriver.java:96)
         at

  • Informix JDBC logging fails at WLS startup - repost, 1st one incomplete

    Hi,
    I am trying to find out how to see how many db queries I'm doing
    for a CMP finder. I am using the Informix driver I downloaded
    from BEA. When I start up WebLogic, I get the following in the
    jdbc.log file:
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver:
    driver className=weblogic.jdbc.informix4.Driver,weblogic.jdbc.informix4.Driver@20e990]
    SQLException: SQLState() vendor code(-255)
    weblogic.jdbcbase.informix4.InformixException: Informix error: -255 minor code=[0]
    [ at processUpdate <Error> ] See Informix error codes for explanation
    The Informix error manual says -255 means this was not in a
    transaction. It seems to imply that WLS, in trying to start
    logging, was ending a transaction.
    The rest of the stacktrace shows:
    at weblogic.jdbcbase.informix4.Statement.processError Statement.java:1579)
         at weblogic.jdbcbase.informix4.Statement.processUpdate(Statement.java:1344)
         at weblogic.jdbcbase.informix4.Statement.getMoreResults(Statement.java:1100)
         at weblogic.jdbcbase.informix4.Statement.execute(Statement.java:243)
         at weblogic.jdbcbase.informix4.Connection.findDBType(Connection.java:173)
         at weblogic.jdbc.informix4.Driver.newConnection(Driver.java:45)
         at weblogic.jdbcbase.informix4.BaseDriver.connect(BaseDriver.java:96)
         at
    and the rest of the trace shows it trying to make a connection.
    I don't know why this is happening. Any help would be greatly
    appreciated.
    TIA,
    Matt

    matt wrote:
    >
    Joe,
    Thanks for the info. I downloaded the Informix driver, installed
    it, and configured WebLogic to use it, and it worked fine.
    Informix has its own way of turning debug on, but once I read
    their driver doc, it was fairly easy.cool. glad to help.
    Matt
    Joseph Weinstein <[email protected]> wrote:
    Hi Matt. The stacktrace shows that the problem is coming during
    the driver's attempt to make a new connection. I don't know why
    this is happening, but my standing advice for Informix connectivity
    is for you to download and use Informix's own free type-4 driver.
    It's better, faster and better supported than ours.
    Joe
    matt wrote:
    Hi,
    I am trying to find out how to see how many db queries I'm doing
    for a CMP finder. I am using the Informix driver I downloaded
    from BEA. When I start up WebLogic, I get the following in the
    jdbc.log file:
    DriverManager.initialize: jdbc.drivers = null
    JDBC DriverManager initialized
    registerDriver:
    driver className=weblogic.jdbc.informix4.Driver,weblogic.jdbc.informix4.Driver@20e990]
    SQLException: SQLState() vendor code(-255)
    weblogic.jdbcbase.informix4.InformixException: Informix error: -255minor code=[0]
    [ at processUpdate <Error> ] See Informix error codes for explanation
    The Informix error manual says -255 means this was not in a
    transaction. It seems to imply that WLS, in trying to start
    logging, was ending a transaction.
    The rest of the stacktrace shows:
    at weblogic.jdbcbase.informix4.Statement.processError Statement.java:1579)
    at weblogic.jdbcbase.informix4.Statement.processUpdate(Statement.java:1344)
    at weblogic.jdbcbase.informix4.Statement.getMoreResults(Statement.java:1100)
    at weblogic.jdbcbase.informix4.Statement.execute(Statement.java:243)
    at weblogic.jdbcbase.informix4.Connection.findDBType(Connection.java:173)
    at weblogic.jdbc.informix4.Driver.newConnection(Driver.java:45)
    at weblogic.jdbcbase.informix4.BaseDriver.connect(BaseDriver.java:96)
    at
    and the rest of the trace shows it trying to make a connection.
    I don't know why this is happening. Any help would be greatly
    appreciated.
    TIA,
    Matt

  • JDBC Log Rotation Info.

    We have WebLogic 6.1 Sp1. In the release notes it says that the JDBC log in Sp1 has rotation capability. But it does not say how to enable rotation. Does anyone know?
    Thanks.

    You can specify rotation jdbc log files based on date at server start up.
    Here is an excerpt from the developer's notes regarding this enhancement in 6.1sp1, which I have not tried:
    You can now rotate your jdbc log. We only allow you to do this based on
    date. You can specify how often we should rotate the log file and when we
    should begin that rotation. For example rotate every 6 hours and start the
    first rotation at 4pm today. If rotation is enabled we will automatically
    append a date/time stamp to the end of the log file, you can control the
    format of this timestamp with the property weblogic.jdbc.logFileNameFormat.
    Added properties:
    weblogic.jdbc.rotateLog
    Whether or not to rotate jdbc log file. This is false by default.
    weblogic.jdbc.logRotationPeriodMins
    Defines the period in minutes when the jdbc log will be rotated. 24 hours is
    1440 minutes. One week is 10080 minutes
    weblogic.jdbc.logRotationBeginTime
    Defines the date when the first rotation of jdbc log will begin. The format
    follows java.text.SimpleDateFormat, MM-dd-yyyy-k:mm:ss see the javadocs for
    more details. For example: 11-24-2000-12:30:00 Note: If not set next rotation
    is the next weblogic.jdbc.logRotationPeriodMins. If the date has already
    past, then the DAY_OF_WEEK, HOUR_OF_DAY, MINUTE and SECOND are used with the
    current date to recalculate
    weblogic.jdbc.logFileNameFormat
    Defines the format of the date string that is appended to the jdbc log when
    rotation is turned on. The format follows java.text.SimpleDateFormat, and defaults to:dd_MMM_yyyy__HH_mm_ss see the javadocs for more details.
    Bill Kemp
    BEA Systems
    ravi wrote:
    We have WebLogic 6.1 Sp1. In the release notes it says that the JDBC log in Sp1 has rotation capability. But it does not say how to enable rotation. Does anyone know?
    Thanks.

  • How do I get JDBC Logging with IBM Informix drivers?

    I am trying to get JDBC logging working with IBM Informix drivers.
    I am using the _g jar files; I have specified TRACE, TRACEFILE,
    PROTOCOLTRACE, and PROTOCOLTRACEFILE as properties;
    I have enabled JDBC logging and specified a JDBC log file in the
    WLS console. Regardless of all these machinations, no logging is
    produced.
    What else need I do? Thanks for any advice!
    : jay

    So... a couple weeks later and I've managed to find
    out a bit more. My simple program works and produces
    output, so the debug drivers are doing their thing.
    So, in my simple program, I was using the standard
    informix driver. But, with WebLogic, my connection
    pool is using the XA datasource which is configured
    slightly differently than the driver; in particular,
    the URL is left blank as described in
    http://e-docs.bea.com/wls/docs70/jdbc/thirdparty.html.
    I've actually created another connection pool which
    uses the standard driver, and I do get loggging when
    I use that pool, so the problem seems to be with the
    XA Datasource.
    I'm trying to revise my test program to use the
    datasource, and we'll go from there. Any thoughts
    you have would be appreciated, of course.
    : jay
    Joe Weinstein wrote:
    >
    >
    Jay Schmidgall wrote:
    "Joe Weinstein" <[email protected]> wrote in message
    news:[email protected]..
    Jay Schmidgall wrote:
    I am using the _g jar files; I have specified TRACE, TRACEFILE,
    PROTOCOLTRACE, and PROTOCOLTRACEFILE as properties;Odd. Would you please show me a small java program that
    sets the properties for the connection so you get your
    logging output, and then I'll know what I need for weblogic to do it:I am setting the properties in the weblogic console via the properties
    field
    on the general configuration tab for the connection pool. That's where I
    set all the other properties, so that's where I thought I should set
    these.
    I've tried it with those properties set individually and as part of
    the URL
    property.Oh, yes that's where you should be doing it, but a standalone program
    will prove exactly what properties are needed by the driver per se.
    Ie: the first step is to prove the jdbc driver alone does what we
    want, and then we can know how to get weblogic to get the driver to do
    the same for it.
    Joe
    I'll try to cruft up a small program that does this manually, though.
    : jay

  • JDBC driver log file generation on v8i

    I want to know if there is a means to generate the log files for JDBC driver transactions similar to sqlnet.log file which gets created when the OCI connection is used between the client and server.
    Where should this be done - on the client/server side? Is there a means to enable it without touching any of native Java code by enabling it through Server/Client side setting?
    thanks

    You should ask your question in the JDBC forum found at:
    http://forums.oracle.com/forums/forum.jsp?forum=99

  • SQLException Error in Log file

    Does anyone know of the following error, and how to fix this? I keep getting it in my engine log file like every 30 mn.
    Thank you,
    -Lilach
    --------------------------------------------- Error -----------------------------------------------------------------
    Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
    Caused by: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
    Caused by: [BEA][SQLServer JDBC Driver][SQLServer]The statement has been terminated.
    fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
         at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
         at fuego.directory.provider.jdbc.mssqlserver.MSSQLServerPersistenceManager.mapSQLException(MSSQLServerPersistenceManager.java:116)
         at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:221)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:180)
         at fuego.directory.hybrid.jdbc.DelegatorFuegoParticipantAccessor.updateOrPersistHumanParticipant(DelegatorFuegoParticipantAccessor.java:224)
         at fuego.directory.hybrid.HybridParticipantAccessor.updateHumanParticipant(HybridParticipantAccessor.java:377)
         at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy6.updateHumanParticipant(Unknown Source)
         at fuego.directory.hybrid.HybridParticipantAccessor.fetchHumanParticipant(HybridParticipantAccessor.java:189)
         at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy6.fetchHumanParticipant(Unknown Source)
         at fuego.directory.provider.notifiers.DirObjectType$3.fetchDirObjectFor(DirObjectType.java:74)
         at fuego.directory.provider.notifiers.DirectoryObjectProxy.getObject(DirectoryObjectProxy.java:160)
         at fuego.directory.provider.notifiers.DirectoryObjectProxy.createAddEvent(DirectoryObjectProxy.java:91)
         at fuego.directory.provider.notifiers.BasePollingEventGenerator.buildEvents(BasePollingEventGenerator.java:148)
         at fuego.directory.hybrid.ldap.LDAPPollingEventGenerator.buildEvents(LDAPPollingEventGenerator.java:109)
         at fuego.directory.provider.notifiers.BasePollingEventGenerator.generateEvents(BasePollingEventGenerator.java:51)
         at fuego.directory.hybrid.HybridMultipleEventGenerator.generateEvents(HybridMultipleEventGenerator.java:43)
         at fuego.directory.provider.notifiers.DirectoryNotifier.notifyChanges(DirectoryNotifier.java:403)
         at fuego.server.service.DirectoryListener.updateEngineFromDirectoryImpl(DirectoryListener.java:328)
         at fuego.server.service.DirectoryListener$DirectoryPollingItem.execute(DirectoryListener.java:381)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.fengine.service.FEngineExecution.executeImmediate(FEngineExecution.java:65)
         at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
         at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
         at fuego.server.execution.PollingDirectory.execute(PollingDirectory.java:46)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
         at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
         at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
         at fuego.server.execution.ToDoItem.run(ToDoItem.java:536)
         at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:775)
         at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
         at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
         at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
         at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
    Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
         at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
         at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
         at albpm.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
         at albpm.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
         at albpm.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
         at albpm.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
         at albpm.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
         at albpm.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)
         at albpm.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
         at albpm.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)
         at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at albpm.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
         at albpm.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
         at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createParticipantInfo(JDBCParticipantsAccessor.java:1280)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipantInternal(JDBCParticipantsAccessor.java:1195)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:217)
         ... 49 more

    Hi All ,
    I having this error . Are there any fixes for this bug ?
    my configuration file is like the following ;
    +<?xml version="1.0" encodxxx="UTF-8"?>+
    +<?fuego version="6.1 ALPHA" application="albpmenterprise"?>+
    +<!-- This file contains the propper attribute mappxxx for the FDI Generic Ldap Provider usxxx Oracle Internet Directory.+
    +     * Preference for group object+
    +          <preference id="assignedParticipants.containsId" value="true"/>+
    +          This preference is useful to speed up the provider and it can only be used if the assignedParticipant value is the dn of the user and the dn contains the participant id+
    +          <preference id="assignedParticipants.containsId" value="true"/>+
    +          This preference is useful to speed up the provider and it can only be used if the assignedGroup value is the dn of the group and the dn contains the group id+
    +          <preference id="modifyTimeStamp.suffix" value="Z"/>+
    +          This preference is useful when the suffix mofidyTimeStamp format of your ldap is not .OZ.+
    -->
    +<config>+
    +     <object id="person">+
    +          <object-filter>+
    +               <![CDATA[+
    +                    (objectclass=person)+
    +               ]]>+
    +          </object-filter>+
    +          <relative-dn>ou=xxxBANK,cn=Users</relative-dn>+
    +          <attribute id="id" value="uid"/>+
    +          <attribute id="lastName" value="sn"/>+
    +          <attribute id="firstName" value="givenname"/>+
    +          <attribute id="displayName" value="displayname"/>+
    +          <attribute id="mail" value="mail"/>+
    +          <attribute id="telephoneNumber" value="telephonenumber"/>+
    +          <attribute id="employeeId" value="employeeNumber"/>+
    +          <attribute id="thumbnailPhoto" value="thumbnailPhoto"/>+
    +          <attribute id="manager" value="manager"/>+
    +          <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
    +     </object>+
    +     <object id="group">+
    +          <object-filter>+
    +               <![CDATA[+
    +                    (objectclass=xxxGroupObject)+
    +               ]]>+
    +          </object-filter>+
    +          <relative-dn>+
    +               <!-- the relative dn for group --></relative-dn>+
    +          <attribute id="id" value="cn"/>+
    +          <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
    +          <attribute id="displayName" value="cn"/>+
    +          <attribute id="name" value="cn"/>+
    +          <attribute id="description" value="description"/>+
    +          <attribute id="assignedParticipants" value="uniquemember"/>+
    +          <attribute id="assignedGroups" value="uniquemember"/>+
    +          <attribute id="ou" value="distxxxuishedName"/>+
    +     </object>+
    +     <object id="ou">+
    +          <object-filter>+
    +               <![CDATA[+
    +                    (objectclass=xxxOUObject)+
    +               ]]>+
    +          </object-filter>+
    +          <relative-dn>+
    +               <!-- the relative dn for ous -->+
    +          </relative-dn>+
    +          <attribute id="name" value="ou"/>+
    +          <attribute id="description" value="description"/>+
    +     </object>+
    +</config>+

  • Dates appear different in log file vs. debug page for Deferred Task

    I added a deferred task and in the log file, the date appeared correctly as
    Mon Dec 15 16:34:11 PST 2008
    But when I viewed the user in the debug page, the date appeared as
    <Date>2008-12-16T00:34:11.430Z</Date>
    I called an external java class that return a Date object
    <Action id='0' application='com.waveset.session.WorkflowServices'>
    <Argument name='op' value='addDeferredTask'/>
    <Argument name='date'>
    <invoke name='addWeekDays' class='MyDateUtil'/>
    </Argument>
    </Action>
    Do you have any ideas?

    IDM commonly stores dates in a Java or JDBC date format (which is what your debug date is) but often formats the date differently for log files and for web pages. It's annoying if you're trying to line two different outputs up.

  • Can I modify WLI system Bean's transaction attribute --turn on archiver resulting endless exception in log file

    hi,erveryone,
    one difficult question need help.
    Environment: WLS8.1sp2 + WLI8.1sp2 + ORACLE9i + solaris9
    when I started archiver manually,just for a while, wli system generated about 40,000 JMS messages in
    wli.internal.worklist.timer.queue,and consume the great mass of system resource of Database server,I had to stop these
    archive processes immediately to keep other applicaitons which using the same database running normal. I did so by
    following steps:
    (1) in WLI console, delete wli.internal.worklist.timer.queue;
    (2) in WLI console, reconstruct wli.internal.worklist.timer.queue;
    (3) restart wli server.
    after server was restarted, wli server output endless and repeatly exception to log file ,the typical exception was:
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '54' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B26B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    java.sql.SQLException: Transaction rolled back: Unknown reason.
    java.sql.SQLException: Transaction rolled back: Unknown reason
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1299)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1055)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<May 8, 2005 3:08:26 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '96' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-54B96B551CC1A8856F80> <BEA-010049> <EJB Exception in method: remove:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found..
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_loadGroup0(ListenerBean_1nsp14__WebLogic_CMP_R
    DBMS.java:1165)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:596)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.__WL_setTaskBean_listeners(ListenerBean_1nsp14__Web
    Logic_CMP_RDBMS.java:584)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14__WebLogic_CMP_RDBMS.ejbRemove(ListenerBean_1nsp14__WebLogic_CMP_RDBMS.j
    ava:2423)
         at weblogic.ejb20.manager.DBManager.remove(DBManager.java:1318)
         at weblogic.ejb20.internal.EntityEJBLocalHome.remove(EntityEJBLocalHome.java:214)
         at
    com.bea.wli.worklist.beans.entity.ListenerBean_1nsp14_LocalHomeImpl.remove(ListenerBean_1nsp14_LocalHomeImpl.java:131)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean.removeTaskListeners(RemoteWorklistManagerBean.java:3001)
         at
    com.bea.wli.worklist.beans.session.RemoteWorklistManagerBean_us8t1c_EOImpl.removeTaskListeners(RemoteWorklistManagerBean_us8t
    1c_EOImpl.java:698)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.processListenerToRemove(WorklistTimerMDB.java:102)
         at com.bea.wli.worklist.timer.WorklistTimerMDB.onMessage(WorklistTimerMDB.java:61)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    The wli server generated log file very quickly ,:it can output 1M bytes log file per second,all logged information
    is similar to the <BEA-010049> excetpion metioned above. BEA support engineer suggested me to totally stop the
    archive ,I did so,but the server was still ouput the log file like crazy as before and the normal log information are
    completely override by <BEA-010049> excetpion.
    I checked the EntityEJBs in WLI console :Mywlidomain> Applications> WLI System EJBs> WLI Worklist Persistence$)A#,and
    found that in statistics table :
    ListenerBean : Pool miss ratio = 99.67%, transaction rollback ration = 99.90%,Destory Bean Ratio = 99.48%(see
    attachment)
    WorklistTimerMDB: transaction rollback ratio = 99.97%
    It seems ListenerBean worked incorrectly.I searched in support.bea.com and found one example which also about server
    output endless log file,the author solved this problem by changing Bean's transaction-attribute from 'Required'
    to 'RequiresNew' thought he didn't know why it works. I try this method by changing ListenerBean's
    transaction-attribute from 'Required' to 'RequiresNew'.
    $weblogic_home/integration/lib/wli-ejbs.ear/ejb-jar-generic.xml:
    <ejb-name>CommentBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>ListenerBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute> -----------the default value is Required,I modified it to
    RequiresNew.
    </container-transaction>
    <container-transaction>
    really it works, the log file output resume normal. But there are still some problems:
    (1) this exception is still exist:
    javax.ejb.NoSuchEntityException: [EJB:010140]Bean with primary key: '153.22.52.28-17343c7.10243c3c6ec.a51' not found.
    (2) is this method safe ?(Does "Modify ListenBean's transaction-attribute" impat other parts of wli system?)
    (3) after changed the transaction attribute, if turn on archive again, the server output endless exception:
    ####<Jun 1, 2005 5:14:58 PM CST> <Info> <EJB> <app01> <jcwliserver> <ExecuteThread: '63' for queue:
    'weblogic.kernel.Default'> <<anonymous>> <BEA1-2F43890B86B0A8856F80> <BEA-010036> <Exception from ejbStore:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'weblogic.jdbc.jta.DataSource': XAER_RMERR : A resource manager error has occured in the transaction
    branch
    oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1160)
         at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
         at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:617)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1075)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1007)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:218)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1287)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1292)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1250)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:385)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:343)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.__WL_store(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:363
    6)
         at
    com.bea.wli.worklist.beans.entity.TaskBean_9fxazu__WebLogic_CMP_RDBMS.ejbStore(TaskBean_9fxazu__WebLogic_CMP_RDBMS.java:3548)
         at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:927)
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:745)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1142)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1868)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:250)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    How can I solve these problem ? any suggestion is warm welcome.
    Thanks in advance.
    Great Lou

    Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
    Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
    Using Setup Assistant
    Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
    If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

  • Character Garbled in the log file

    HP-UX ia64
    Netweaver 7.0
    CPS M28.17-35130
    DB2 database
    HP-UX locale: en_US.utf8
    DB2 database encoding: utf8
    1: I have Chinese characters directly in the Redwoodscript(Job Definition), which would be printed into jcsErr/jcsOut.
       then in the log file, the Chinese characters are garbled.
    2: there is a job parameter as input string, and it will be printed into jcsErr/jscOut in the RedwoodScript.
       when submitting the job definition, set the parameter with some Chinese Characters,
       then in the log file, the Chinese characters are shown properly.
    I get down the java file in the /usr/sap/CPT/J00/j2ee/cluster/server0/java/compile0, and open it by Eclipse(utf-8),
    and see that the Chinese Characters in the java source file are shown properly.
    this is tested in our Product env.
    Once in our dev/test env, all is ok.
    and now I don't know what the difference causes issue 1.
    I have no idear how to trace this problem.
    hope you can shed some light to me.

    System_info output like below:
    System branch:M28.17
    System Id: SAP:CPT_00
    Build Id: M28.17-35130
    Server Root Directory  : null
    Job File Directory     : /usr/sap/CPT/J00/j2ee/cluster/server0/scheduler
    Java Work Directory    : /usr/sap/CPT/J00/j2ee/cluster/server0/java
    System Log Directory   : /usr/sap/CPT/J00/j2ee/cluster/server0/log
    Database type: (Open SQL) DatabaseType:DB2_ULW
    Database Driver Version: IBM DB2 JDBC Universal Driver Architecture 3.52.95
    Database Name: DB2/HPUX-IA64 (SQL09052)
    Database Connection URL: jdbc:db2://cpstprd:5912/CPT
    SAP_J2EE_Engine_Version=7.11.3301.221185.20081011173236
    SKIP_CLASS_WRAPPERS=false
    file.encoding=utf8
    file.encoding.pkg=sun.io
    file.separator=/
    http.nonProxyHosts=10.|127.|192.168.*
    j2ee.dbhost=cpstprd
    j2ee.engine.apps.folder=file:/usr/sap/CPT/J00/j2ee/cluster/apps/
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.headless=true
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.version=49.0
    java.endorsed.dirs=/usr/sap/CPT/J00/exe/sapjvm_5/jre/lib/endorsed
    java.ext.dirs=/usr/sap/CPT/J00/exe/sapjvm_5/jre/lib/ext
    java.home=/usr/sap/CPT/J00/exe/sapjvm_5/jre
    java.io.tmpdir=./temp
    java.protocol.handler.pkgs=iaik.protocol
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=5.1.024
    java.security.auth.login.config=./temp/security/fallback.config
    java.security.egd=file:/dev/urandom
    java.security.policy=./../bin/kernel/java.policy
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.5
    java.vendor=SAP AG
    java.vendor.url=http://www.sap.com/
    java.vendor.url.bug=http://service.sap.com/support
    java.version=1.5.0_14
    java.vm.info=Sep  2 2008 10:46:19 - 51_REL - optU - hpux ia64 - bas2:106386 (mixed mode)
    java.vm.name=SAP Java 64-Bit Server VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=SAP AG
    java.vm.version=5.1.024
    javax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    javax.security.jacc.policy.provider=com.sap.engine.system.SystemPolicy
    jco.jarm=1
    jmx.invoke.getters=true
    jstartup.debuggable=yes
    jstartup.mode=JSTART
    jstartup.ownHardwareId=S2011879030
    jstartup.ownProcessId=6447
    jstartup.whoami=server
    line.separator=

  • JDBC logging mechanism in oracle 8i

    I want to know if there is a means to generate the log files for JDBC driver transactions similar to sqlnet.log file which gets created when the OCI connection is used between the client and server.
    Where should this be done - on the client/server side? Is there a means to enable it without touching any of native Java code by enabling it through Server/Client side setting?
    thanks

    Does your APP's/HTTP Server supports loading the http log files in to the Oracle Database. If it supports then you can upload this data into Oracle Database and then run analysis on that.
    Other wise you can use sql*loader to load this http log file into the Oracle Database.
    null

  • ODL log file registration in 10.1.0.2 with B2B installed

    Hi,
    we enabled ODL to default log file for our application by adding this handler
    <!-- In live deployment useParentHandlers='false' to disable console logging -->     
    <logger name='com.gem.ws.proxy' level='INFO' useParentHandlers='true'>
    <handler name='oc4j-handler'/>
    </logger>
    to j2ee-logging.xml for our OC4J instamce.
    It seems that default ODL log file in j2ee/home/log/home_default_island_1/oc4j is not registred by OAS log viewer.
    I tried to experiment with editing files in diagnostics/config/registration and I succeeded only with adding :
    <log path='j2ee/home/log/home_default_island_1/oc4j' componentId='OC4J'>
         <logreader type='ODL'/>
         <logviewer ComponentName='home' ComponentType="OC4J"
              LogType='OC4J_APPLICATION'/>
    </log>
    to INTEGB2B.xml
    However this is not clear solution and ODL log file is registred under incorect attributes. I need to edit the OC4J_logs.xml and register my ODL file here, but I was unable to get it work after many experiments.
    Could anybody post valid XML to register default ODL file in logviewer of OAS 10.1.2???

    user469244,
    I assume you are referring to Oracle's JDBC driver. I am unfamiliar with the "oracle.jar" file. I use the "ojdbc14.jar" file and it does contain the "oracle.jdbc.driver.DatabaseError" class. What is this "oracle.jar" file you mention?
    Perhaps you could post the entire error message (and stack trace) you are getting, as well as the section of your code that is causing the error?
    Good Luck,
    Avi.

Maybe you are looking for