Hi Rick,
Have you tried this one, it alone should do the job.
PersistenceBrokerFactoryFactory.instance().shutdown();
-- Ilkka
Rick Roman wrote:
Update: From other threads, I have tried using a contextDestroy listener
to run:
PersistenceBroker broker =
PersistenceBrokerFactory.defaultPersi
Update: From other threads, I have tried using a contextDestroy listener
to run:
PersistenceBroker broker =
PersistenceBrokerFactory.defaultPersistenceBroker();
broker.clearCache();
broker.close();
PersistenceBrokerFactory.releaseAllInstances();
ConnectionFactoryFactory.getInstance().c
Here it is Jakob,
DEBUG - OJB: TableAlias(): using hints ? false,null,,swav,123,2005-12-09
14:42:51.649
DEBUG - OJB: SQL:SELECT
A0.MODIFY_DTIME,A0.PARAMETER_NAME,A0.SYSTEM_ID,A0.DATA_TAG,A0.MODIFY_USE
R,A0.CREATE_DTIME,A0.CREATE_USER,A0.PARAMETER_VALUE,A0.DESCRIPTION,A0.SY
STEM_PARAMETER_ID,A0.MOD
hi eric,
i do not have an oracle installation here so i can only guess.
but afaik ojb only sets the escapeProcessing. btw could you please post
the oracle sql exception ?
jakob
Ferrer, Eric schrieb:
Hi Jakob,
OJB is the persistence layer used throughout the project. I can create
a test co
Hi Jakob,
OJB is the persistence layer used throughout the project. I can create
a test connecting to Oracle directly and see what happens. I am
currently creating a SQL Server instance and seeing if I get similar
results from OJB.
Could it be the OraclePlatform implementation in OJB that is doi
hi eric,
the error is caused by stmt.setEscapeProcessing(true) in
the paltform:
public void afterStatementCreate(Statement stmt) throws PlatformException
{
try
{
stmt.setEscapeProcessing(true);
}
catch (SQLException e)
{
throw n
I am using OBJ to access PostgreSQL via a JNDI datasource. My problem is
that every time I reload my application context, I get a big jump in
Tomcat Perm Gen memory. After a several reloads, tomcat eventually
crashes with an out of memory error. I believe this has to do with my
OBJ configuratio