See the Strange error by Tomcat thread for more info on this, but your
npe is happening a few lines after the error associated with Tomcat. 
You are getting a npe when the user data is being stored to the database
as the session times out, it is likely to be harmless.  Have you altered
o.a.t.util.map.TurbineMapBuilder?  Other than that I would suggest
adding debugging statements to BasePeer where the npe is happening and
getting info such as is it the db map that is null or the table map and
what table name is being used to look for the map.  Let us know if you
delve deeper.

john mcnally

"Cromer, Deborah" wrote:
> 
> These are my database settings from TR.props. I am not altering the database
> keys or anything. In fact the error seems to be unrelated to any database
> alterations.
> 
> Deborah
> # -------------------------------------------------------------------
> #
> #  D A T A B A S E  S E T T I N G S
> #
> # -------------------------------------------------------------------
> # These are your database settings.  Look in the
> # org.apache.turbine.util.db.pool.* packages for more information.
> # The default driver for Turbine is for MySQL.
> #
> # The parameters to connect to the default database.  You MUST
> # configure these properly.
> # -------------------------------------------------------------------
> 
> database.default.driver=org.gjt.mm.mysql.Driver
> database.default.url=jdbc:mysql://host/appname
> database.default.username=***
> database.default.password=***
> 
> # The number of database connections to cache per ConnectionPool
> # instance (specified per database).
> 
> database.default.maxConnections=3
> 
> # The amount of time (in milliseconds) that database connections will be
> # cached (specified per database).
> #
> # Default: one hour = 60 * 60 * 1000
> 
> database.default.expiryTime=3600000
> 
> # The amount of time (in milliseconds) a connection request will have to
> wait
> # before a time out occurs and an error is thrown.
> #
> # Default: ten seconds = 10 * 1000
> 
> database.connectionWaitTimeout=10000
> 
> # The interval (in milliseconds) between which the PoolBrokerService logs
> # the status of it's ConnectionPools.
> #
> # Default: No logging = 0 = 0 * 1000
> 
> database.logInterval=0
> 
> # These are the supported JDBC drivers and their associated Turbine
> # adaptor.  These properties are used by the DBFactory.  You can add
> # all the drivers you want here.
> 
> database.adaptor=DBMM
> database.adaptor.DBMM=org.gjt.mm.mysql.Driver
> 
> # Determines if the quantity column of the IDBroker's id_table should
> # be increased automatically if requests for ids reaches a high
> # volume.
> 
> database.idbroker.cleverquantity=true
> 
> -----Original Message-----
> From: John McNally [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 11 July 2001 10:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Strange exception?
> 
> Jon Stevens wrote:
>   This points to a line looking up the table map for the TurbineUser.
> Are you doing anything like altering the database key used to define
> connections to the Turbine tables?  Can I see your database entries from
> TR.props (not username/password info)?
> 
> john mcnally
> 
> >
> > on 7/10/01 4:13 PM, "Cromer, Deborah" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > I Can't figure out why this sould be being thrown, can anyone help me?
> > >
> > > Deborah.
> >
> > Someone just posted about this earlier today.
> >
> > Just ignore it for now, it isn't a big deal.
> >
> > What is happening is that when the session is unbound, the TurbineUser
> > object attempts to serialize the perm hashtable to the database and is
> > failing for some reason.
> >
> > -jon
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to