webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

console is not opening in TN

  • 1.  console is not opening in TN

    Posted Sun January 10, 2010 08:09 AM

    Hi
    please tell me wat is the problem in this ?
    how to over come?
    I configured jdbc pool successfully and i runed scripts successfully.
    im using webmethods6.1.
    if another scripts need pls provide me some .





    Title:
    wm.tn.route:init
    Message:
    Error encountered while reading processing rules from the database. The exception message is : [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    (0) java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    FONT=&quot [/FONT]java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    class:
    com.wm.app.tn.route.RoutingException
    Stack trace:
    java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
    at com.wm.dd.jdbc.base.BaseExceptions.createException(Unknown Source)
    at com.wm.dd.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.wm.dd.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
    at com.wm.dd.jdbc.base.BaseStatement.commonExecute(Unknown Source)
    at com.wm.dd.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
    at com.wm.dd.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
    at com.wm.app.tn.db.RROperations.insertRuleModification(RROperations.java:557)
    at com.wm.app.tn.db.RROperations.getChangeId(RROperations.java:533)
    at com.wm.app.tn.db.RROperations.loadAll(RROperations.java:364)
    at com.wm.app.tn.route.RoutingRuleStore.load(RoutingRuleStore.java:172)
    at wm.tn.route.init(route.java:54)
    at wm.tn.admin.startup(admin.java:732)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)

    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:100)
    at com.wm.app.b2b.server.SessionInvoke.run(Session.java:705)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
    at java.lang.Thread.run(Thread.java:534)

    thanks&regards

    siva


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 2.  RE: console is not opening in TN

    Posted Sun January 10, 2010 11:08 AM

    Hi,

    At what action on TN you are getting this error.
    You have certainly some finite length for storing documentID, conversationID…rtc. if you are tying to store value in these fields larger than the specified lenght… you might get this exception. Recheck the TN attributes which for the bizdoc in question and see if all the values are proper.
    Moreover if i recall properly, there were some fixes as well to handle these errors on TN… check advantage page for the same.

    Hope it helps.

    -nD


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: console is not opening in TN

    Posted Sat January 16, 2010 02:25 PM

    i put fixes and configured successfully and run oracle scripts
    im not getting what is the problem ?
    is scripts problem?


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB