Kodo JCA in WebSphere 5.1
Hello!
I am packaging the Kodo 3.2.2 JCA RAR inside my EAR and deploy it to
WebSphere 5.1.0. During the first use of JDO in my application, Kodo
wants to find the application servers Transaction Manager to integrate
with the J2EE transaction. While this obviously works in WebSphere
Application Server 5.0, Kodo fails to "guess" the TransactionManager in
5.1.0. The output I get is:
==========
java.rmi.RemoteException: ; nested exception is:
kodo.util.FatalInternalException: Could not perform automatic
lookup of EJB container's javax.transaction.TransactionManager
implementation. Please ensure that you are running the application from
within an EJB 1.1 compliant EJB container, and then set the
kodo.ManagedRuntime property to the appropriate value to obtain the
TransactionManager.
NestedThrowables:
javax.naming.NameNotFoundException: Context:
bes724/nodes/bes724/servers/server1, name:
javax.transaction.TransactionManager: First component in name
javax.transaction.TransactionManager not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
javax.naming.NameNotFoundException: Name not found in context "java:".
javax.naming.NameNotFoundException: Name not found in context "java:".
javax.naming.NameNotFoundException: Name comp/pm not found in context
"java:".
javax.naming.NameNotFoundException: Name "comp/TransactionManager" not
found in context "java:".
javax.naming.NameNotFoundException: Name pm not found in context "java:".
java.lang.ClassNotFoundException: com.arjuna.jta.JTA_TransactionManager
java.lang.ClassNotFoundException:
com.bluestone.jta.SaTransactionManagerFactory
java.lang.ClassNotFoundException: com.ibm.ejs.jts.jta.JTSXA
java.lang.ClassNotFoundException:
com.ibm.ejs.jts.jta.TransactionManagerFactory
java.lang.ClassNotFoundException: org.openejb.OpenEJB
java.lang.ClassNotFoundException: com.sun.jts.jta.TransactionManagerImpl
java.lang.ClassNotFoundException:
com.inprise.visitransact.jta.TransactionManagerImpl
java.lang.ClassNotFoundException: com.sun.enterprise.Switch
at
com.ibm.ejs.container.RemoteExceptionMappingStrategy.setUncheckedExceptio
n(RemoteExceptionMappingStrategy.java:196)
at com.ibm.ejs.container.EJSDeployedSupport.setUncheckedException
(EJSDeployedSupport.java:296)
==========
My ManagedRuntime property still defaults to "auto".
What is going on here? Has IBM changed the class/package that implements
the TransactionManager?
I have seen that a class com.ibm.ws.Transaction.TransactionManagerFactory
exists. Should I implement kodo.ee.ManagedRuntime as a wrapper of the
com.ibm.ws.Transaction.TransactionManagerFactory and name my
implementation in the ManagedRuntime property?
If anyone has done such a thing before, I'd be happy to have an
example...
Thanks in advance for any help!
Carsten
This is odd as we have tested against 5.1.
Can you try sett the ManagedRuntime property explicitly to:
invocation("TransactionManagerMethod=com.ibm.ws.Transaction.TransactionManagerFactory.getTransactionManager")
Are you running in any non-standard environment (i.e. inside WSAD or
something)?
Carsten Jahn wrote:
Hello!
I am packaging the Kodo 3.2.2 JCA RAR inside my EAR and deploy it to
WebSphere 5.1.0. During the first use of JDO in my application, Kodo
wants to find the application servers Transaction Manager to integrate
with the J2EE transaction. While this obviously works in WebSphere
Application Server 5.0, Kodo fails to "guess" the TransactionManager in
5.1.0. The output I get is:
==========
java.rmi.RemoteException: ; nested exception is:
kodo.util.FatalInternalException: Could not perform automatic
lookup of EJB container's javax.transaction.TransactionManager
implementation. Please ensure that you are running the application from
within an EJB 1.1 compliant EJB container, and then set the
kodo.ManagedRuntime property to the appropriate value to obtain the
TransactionManager.
NestedThrowables:
javax.naming.NameNotFoundException: Context:
bes724/nodes/bes724/servers/server1, name:
javax.transaction.TransactionManager: First component in name
javax.transaction.TransactionManager not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
javax.naming.NameNotFoundException: Name not found in context "java:".
javax.naming.NameNotFoundException: Name not found in context "java:".
javax.naming.NameNotFoundException: Name comp/pm not found in context
"java:".
javax.naming.NameNotFoundException: Name "comp/TransactionManager" not
found in context "java:".
javax.naming.NameNotFoundException: Name pm not found in context "java:".
java.lang.ClassNotFoundException: com.arjuna.jta.JTA_TransactionManager
java.lang.ClassNotFoundException:
com.bluestone.jta.SaTransactionManagerFactory
java.lang.ClassNotFoundException: com.ibm.ejs.jts.jta.JTSXA
java.lang.ClassNotFoundException:
com.ibm.ejs.jts.jta.TransactionManagerFactory
java.lang.ClassNotFoundException: org.openejb.OpenEJB
java.lang.ClassNotFoundException: com.sun.jts.jta.TransactionManagerImpl
java.lang.ClassNotFoundException:
com.inprise.visitransact.jta.TransactionManagerImpl
java.lang.ClassNotFoundException: com.sun.enterprise.Switch
at
com.ibm.ejs.container.RemoteExceptionMappingStrategy.setUncheckedExceptio
n(RemoteExceptionMappingStrategy.java:196)
at com.ibm.ejs.container.EJSDeployedSupport.setUncheckedException
(EJSDeployedSupport.java:296)
==========
My ManagedRuntime property still defaults to "auto".
What is going on here? Has IBM changed the class/package that implements
the TransactionManager?
I have seen that a class com.ibm.ws.Transaction.TransactionManagerFactory
exists. Should I implement kodo.ee.ManagedRuntime as a wrapper of the
com.ibm.ws.Transaction.TransactionManagerFactory and name my
implementation in the ManagedRuntime property?
If anyone has done such a thing before, I'd be happy to have an
example...
Thanks in advance for any help!
Carsten--
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com
Similar Messages
-
Kodo Connector in WebSphere 4.0.2
Hello,
WebSphere 4.0.2 supports JCA.
Could I install the Kodo Connector in WebSphere?
Are there any tests and/or documents?
AndreasAndreas-
The current version of Kodo does not support WebSphere, but we expect
that it will be supported in the final release of 2.3.
It is probably possible to implement the simple ManagedRuntime class
yourself in order to provide this support: please e-mail
[email protected] if you want more details on how to do this.
-Marc
Andreas <[email protected]> wrote:
Hello,
WebSphere 4.0.2 supports JCA.
Could I install the Kodo Connector in WebSphere?
Are there any tests and/or documents?
Andreas
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code -
Tranaction with KODO JCA and DAO
Hi,Abe,
I use KODO JCA with JBoss3.2.1.We encounter some problem with transaction.We use CMT(Container Management Transaction)provider by JBoss EJB container.
the seniario is:
public class SessBeanA iimplements SessionBean{
public void method(){
A a_new A();
a.method1();
B b_new B();
b.method2();
public class A{ _
method1(){
//use KODO jdo insert one record. _
public class B{
method2(){
//use DAO query the record insert.
method() inSessBeanA is configued use CMT and start new tranction when called.
We want to keep a.method1() and b.method2() in same transaction(method1() and method2() use transaction created by method()).but unfortunately,as they use different DB connection instance(one is from KODO JDO JCA,the other is from direct JDBC),they didn't keep in same transaction.so b.method2() can't find the record insert by a.method1() because method1() hasn't commit.
you know,as for complexity,we can't use only KODO for insert/query,we had to use other technology like DAO.Would you pls tell us how to keep KODO JDO call and our DAO call in same transaction?
Regards,
geduoConsider getting a database connection from Kodo using JDBCStoreManager,
i.e.
KodoPersistenceManager.getStoreManager().getConnection() or
KodoPersistenceManager.getConnection() I think.
Then you'll get the same connection Kodo is using and hence the same
transaction associated with it.
Alex.
geduo wrote:
This is a multi-part message in MIME format.
------=_NextPart_000_001D_01C3CF8B.2D85C0D0
Content-Type: text/plain;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Hi,Abe,
I use KODO JCA with JBoss3.2.1.We encounter some problem with =
transaction.We use CMT(Container Management Transaction)provider by =
JBoss EJB container.
the seniario is:
public class SessBeanA iimplements SessionBean{
public void method(){
A a=3Dnew A();
a.method1();
B b=3Dnew B();
b.method2();
public class A{ =20
method1(){
//use KODO jdo insert one record. =20
public class B{
method2(){
//use DAO query the record insert.
method() inSessBeanA is configued use CMT and start new tranction when =
called.
We want to keep a.method1() and b.method2() in same =
transaction(method1() and method2() use transaction created by =
method()).but unfortunately,as they use different DB connection =
instance(one is from KODO JDO JCA,the other is from direct JDBC),they =
didn't keep in same transaction.so b.method2() can't find the record =
insert by a.method1() because method1() hasn't commit.
you know,as for complexity,we can't use only KODO for insert/query,we =
had to use other technology like DAO.Would you pls tell us how to keep =
KODO JDO call and our DAO call in same transaction?
Regards,
geduo
------=_NextPart_000_001D_01C3CF8B.2D85C0D0
Content-Type: text/html;
charset="gb2312"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>
<DIV><FONT face=3DArial size=3D2>Hi,Abe,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I use KODO JCA with JBoss3.2.1.We =
encounter some=20
problem with transaction.We use CMT(Container Management =
Transaction)provider by=20
JBoss EJB container.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the seniario is:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>public class SessBeanA iimplements=20
SessionBean{</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> public void=20
method(){</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> A =
a=3Dnew=20
A();</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
a.method1();</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> B =
b=3Dnew=20
B();</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
b.method2();</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> }</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>}</FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2>public class A{ =
</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2> =
method1(){</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
//use KODO=20
jdo insert one record. </FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2> }</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>public class B{</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
method2(){</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
//use DAO=20
query the record insert.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> }</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>method() inSessBeanA is configued =
use CMT and=20
start new tranction when called.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We want to keep a.method1() and =
b.method2() in same=20
transaction(<STRONG>method1() and method2() use transaction =
created</STRONG>=20
<STRONG>by method()).</STRONG>but unfortunately,as they use different DB =
connection instance(one is from KODO JDO JCA,the other is from direct =
JDBC),they=20
didn't keep in same transaction.so b.method2() can't find the record =
insert by=20
a.method1() because method1() hasn't commit.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>you know,as for complexity,we can't use =
only KODO=20
for insert/query,we had to use other technology like DAO.Would you pls =
tell us=20
how to keep KODO JDO call and our DAO call in same =
transaction?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>geduo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></DIV></BODY></HTML>
------=_NextPart_000_001D_01C3CF8B.2D85C0D0-- -
Class Cast Exception running Kodo JCA in Weblogic 8.1
Hi,
I have a stateless session EJB that accesses Kodo through the JCA adapter.
The database I'm connecting to is mysql.
The problem I'm having is that the persistence manager throws a class cast
exception when trying to commit the transaction. See below for the stack
trace. I suspect it has something to do with the mapping, but the error
doesn't give me enough information to tell.
Any idea where to start looking to solve this problem?
Merrill
<Sep 14, 2004 9:09:40 AM PDT> <Error> <EJB> <BEA-010026> <Exception
occurred during commit of transaction Name=[EJB ossj
inventory.bean.impl.JVTInventorySessionBean.createEntitySpecificationByValue(javax.oss.cbe.EntitySpecificationValue)],X
id=BEA1-0003E542E34E0D33F21F(21266875),Status=Rolled back.
[Reason=kodo.util.FatalException: java.lang.ClassCastExceptio
n
NestedThrowables:
java.lang.ClassCastException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=13,seconds left=30,SCInfo[os
sj+myserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
ossj.inventory.bean.impl.JVTInventorySession
Bean.createEntitySpecificationByValue(javax.oss.cbe.EntitySpecificationValue)]}),OwnerTransactionManager=ServerTM[Server
CoordinatorDescriptor=(CoordinatorURL=myserver+10.4.110.92:7001+ossj+t3+,
XAResources={},NonXAResources={})],Coordinator
URL=myserver+10.4.110.92:7001+ossj+t3+): kodo.util.FatalException:
java.lang.ClassCastException
NestedThrowables:
java.lang.ClassCastException
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:825)
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:1184)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1910)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:244)
at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:299)
at
weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140)
at
ossj.inventory.bean.impl.JVTInventorySession_h5aqa8_EOImpl.createEntitySpecificationByValue(JVTInventorySessi
on_h5aqa8_EOImpl.java:4968)
at
ossj.inventory.bean.impl.JVTInventorySession_h5aqa8_EOImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
at
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassCastException
at kodo.jdbc.sql.AbstractRow.toSQL(AbstractRow.java:657)
at kodo.jdbc.runtime.RowImpl.flush(RowImpl.java:250)
at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:125)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:361)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:168)
at
kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:73)
at
kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:590)
at
kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:152)
at
kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:964)
at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:813)Can you use 3.1.5. Can you also be sure that you don't have multiple
versions of Kodo around, i.e. in the system classpath, JCA kodo.rar
directory, etc?
Merrill Higginson wrote:
Abe White wrote:
What version of Kodo?I'm using Kodo V 3.1.2
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com -
Kodo JCA integration with Oracle AS 10g
Hi guys,
even though I know that Oracle Application Server is not officially
supported by SolarMetric, it is fundamental for us being able to
preferalby integrate Kodo as a JCA connector.
In the last three days I've been working on this issue obtaining some
results, but now I am running out of ideas about how to solve the
problem I am going to describe to you.
So, the first problem was about finding out how to deploy a connector in
the OC4J. Thanks to an how-to I am attaching to this e-mail I've been
able to accomplish this first step. It has been a bit tricky: I've had
to modify all the "config-property" "name" attributes in the ra.xml file
shipped within your kodo.rar appropriately.
Appropriately means that property names like "AggregateListeners" had to
be rewritten as "aggregateListeners", and property names like "MBeans"
had to be left untouched.
Solved this problem I've been able to reboot the AppServ without any
error/warning message, but I am still far away from being able to
retrieve a PersisteceManager from the PersistenceManagerFactory without
exceptions. The complete stack trace follows:
com.evermind.server.rmi.OrionRemoteException: Transaction was rolled back:
Error in transaction: MarshallingXAException : invalid arguments in call
at
Jaas_StatelessSessionBeanWrapper2.protectedMethod(Jaas_StatelessSessionBeanWrapper2.java:143)
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.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
at connection to mercurio.cineca.it/130.186.3.63 as root
at
com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1520)
at
com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1473)
at
com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
at
com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
at
com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:50)
at __Proxy1.protectedMethod(Unknown Source)
at
it.cineca.test.jaastestclient.JaasBeanTestClient.protectedMethod(JaasBeanTestClient.java:236)
at
it.cineca.test.jaastestclient.JaasBeanTestClient.main(JaasBeanTestClient.java:328)
Nested exception is:
MarshallingXAException : invalid arguments in call
at
com.evermind.sql.DriverManagerXAConnection.start(DriverManagerXAConnection.java:114)
at
com.evermind.server.TransactionEnlistment.<init>(TransactionEnlistment.java:45)
at
com.evermind.server.ApplicationServerTransaction.enlistResource(ApplicationServerTransaction.java:249)
at
com.evermind.sql.OrionCMTConnection.tryToDelistEnlist(OrionCMTConnection.java:309)
at
com.evermind.sql.OrionCMTConnection.intercept(OrionCMTConnection.java:126)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:74)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:57)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:624)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:870)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:960)
at
kodo.jdbc.runtime.JDBCStoreManager.setPersistenceManager(JDBCStoreManager.java:68)
at
kodo.runtime.DelegatingStoreManager.setPersistenceManager(DelegatingStoreManager.java:76)
at
kodo.runtime.PersistenceManagerImpl.initialize(PersistenceManagerImpl.java:196)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:139)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:102)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:95)
at
kodo.jdbc.ee.JDBCConnectionFactory.getPersistenceManager(JDBCConnectionFactory.java:163)
at it.cineca.test.jaas.JaasBean.protectedMethod(JaasBean.java:53)
at
Jaas_StatelessSessionBeanWrapper2.protectedMethod(Jaas_StatelessSessionBeanWrapper2.java:98)
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.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:985)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:198)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:377)
at
oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:515)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:345)
at
com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:181)
at
com.evermind.sql.DriverManagerConnectionPoolDataSource.getPooledConnection(DriverManagerConnectionPoolDataSource.java:36)
at
com.evermind.sql.OrionPooledDataSource.getPooledConnection(OrionPooledDataSource.java:561)
at
com.evermind.sql.PooledConnectionUsage.getPooledConnection(PooledConnectionUsage.java:22)
at
com.evermind.sql.OrionPooledDataSource.checkAndGetMinConnections(OrionPooledDataSource.java:431)
at
com.evermind.sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:338)
at
com.evermind.sql.DriverManagerXADataSource.getNonAutoCommitConnection(DriverManagerXADataSource.java:330)
at
com.evermind.sql.DriverManagerXAConnection.start(DriverManagerXAConnection.java:97)
at
com.evermind.server.TransactionEnlistment.<init>(TransactionEnlistment.java:45)
at
com.evermind.server.ApplicationServerTransaction.enlistResource(ApplicationServerTransaction.java:249)
at
com.evermind.sql.OrionCMTConnection.tryToDelistEnlist(OrionCMTConnection.java:309)
at
com.evermind.sql.OrionCMTConnection.intercept(OrionCMTConnection.java:126)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:74)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:57)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:624)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:870)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:960)
at
kodo.jdbc.runtime.JDBCStoreManager.setPersistenceManager(JDBCStoreManager.java:68)
at
kodo.runtime.DelegatingStoreManager.setPersistenceManager(DelegatingStoreManager.java:76)
at
kodo.runtime.PersistenceManagerImpl.initialize(PersistenceManagerImpl.java:196)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:139)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:102)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:95)
at
kodo.jdbc.ee.JDBCConnectionFactory.getPersistenceManager(JDBCConnectionFactory.java:163)
at it.cineca.test.jaas.JaasBean.protectedMethod(JaasBean.java:53)
at
Jaas_StatelessSessionBeanWrapper2.protectedMethod(Jaas_StatelessSessionBeanWrapper2.java:98)
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.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
at connection to mercurio.cineca.it/130.186.3.63
at
com.evermind.server.rmi.OrionRemoteException.receive(OrionRemoteException.java:130)
at
com.evermind.server.rmi.RMIConnection.handleMethodInvocationResponse(RMIConnection.java:1643)
at com.evermind.server.rmi.RMI-- Failed: protectedMethod(protected)
-- Return value from protectedMethod(protected): .
-- Calling unprotectedMethod(unprotected)
Connection.run(RMIConnection.java:407)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:287)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:985)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:198)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:377)
at
oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:515)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:345)
at
com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:181)
at
com.evermind.sql.DriverManagerConnectionPoolDataSource.getPooledConnection(DriverManagerConnectionPoolDataSource.java:36)
at
com.evermind.sql.OrionPooledDataSource.getPooledConnection(OrionPooledDataSource.java:561)
at
com.evermind.sql.PooledConnectionUsage.getPooledConnection(PooledConnectionUsage.java:22)
at
com.evermind.sql.OrionPooledDataSource.checkAndGetMinConnections(OrionPooledDataSource.java:431)
at
com.evermind.sql.OrionPooledDataSource.getConnection(OrionPooledDataSource.java:338)
at
com.evermind.sql.DriverManagerXADataSource.getNonAutoCommitConnection(DriverManagerXADataSource.java:330)
at
com.evermind.sql.DriverManagerXAConnection.start(DriverManagerXAConnection.java:97)
at
com.evermind.server.TransactionEnlistment.<init>(TransactionEnlistment.java:45)
at
com.evermind.server.ApplicationServerTransaction.enlistResource(ApplicationServerTransaction.java:249)
at
com.evermind.sql.OrionCMTConnection.tryToDelistEnlist(OrionCMTConnection.java:309)
at
com.evermind.sql.OrionCMTConnection.intercept(OrionCMTConnection.java:126)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:74)
at com.evermind.sql.FilterConnection.getMetaData(FilterConnection.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:75)
at
kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:57)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:624)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:870)
at
kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:960)
at
kodo.jdbc.runtime.JDBCStoreManager.setPersistenceManager(JDBCStoreManager.java:68)
at
kodo.runtime.DelegatingStoreManager.setPersistenceManager(DelegatingStoreManager.java:76)
at
kodo.runtime.PersistenceManagerImpl.initialize(PersistenceManagerImpl.java:196)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:139)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:102)
at
kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:95)
at
kodo.jdbc.ee.JDBCConnectionFactory.getPersistenceManager(JDBCConnectionFactory.java:163)
at it.cineca.test.jaas.JaasBean.protectedMethod(JaasBean.java:53)
at
Jaas_StatelessSessionBeanWrapper2.protectedMethod(Jaas_StatelessSessionBeanWrapper2.java:98)
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.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)Sorry,
my previous post is taken from an e-mail I sent to the support, so it
talks about some files that should be attached to it. Obviously these
files are not available along with the post, but the content of the
message (and so my problem) is still valid.
Thanks,
Francesco -
Recent Kodo versions and WebSphere 4.0
Hi,
we may have to use WebSphere 4.0 with Kodo until the IT infrastructure
department supports the latest version WebSphere 5.0.
Is anyone still developing with Kodo and WebSphere 4.0? Can I use Kodo
2.5 / 3.0 with the 'old' version of WebSphere?
Thanks a lot!
Yours,
CarstenCarsten-
Our only feedback is that Kodo has not been tested with Websphere
versions before 5.0.
Note that you can always just Kodo directly: the only hiccup might be in
the automatic global transaction synchronization. As long as Websphere
4.0 provides a JTA-compliant TransactionManager, though, you might be
able to solve any problems you see by writing a custom ManagedRuntime
implementation.
I'm sure the rest of the community will be interested in hearing the
results of your tests.
In article <bn38qa$d1i$[email protected]>, Carsten Jahn wrote:
Hi,
we may have to use WebSphere 4.0 with Kodo until the IT infrastructure
department supports the latest version WebSphere 5.0.
Is anyone still developing with Kodo and WebSphere 4.0? Can I use Kodo
2.5 / 3.0 with the 'old' version of WebSphere?
Thanks a lot!
Yours,
Carsten
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Session problem in Websphere 5
I have an J2ee application deployed in weblogic 8. Its working fine. When the same application is deployed in Websphere 5, iam not able to retrieve the http session values when logged in. Do i need to configure any settings in websphere?
Please provide your valuable suggestions.
Thanks in advanceI think you already answered my implicit question. :)
I know Kodo can't control the type of exception being thrown. My concern
is if you know any issue between Kodo JCA and WebSphere transaction
rollback.
Since the cause of the rollback is a sql exception, I can't "see" it being
thrown in another way than by a nested exception in the EJB container
exception. In JBoss the JDO exception is nested. In WebSphere it is not.
Abe White wrote:
As far as I can tell you didn't ask a question. If the question is whether
there's some way for Kodo to control the type of exception the appserverthrows,
or what information that exception contains, then the answer, unfortunately,is
"No". -
Ok
I give up ... how do you set up the Kodo JCA adapter for WebSphere 5.1 for
the enterprise version? I seem to always get an error if I try to access it.
My resource adapter is bound to the name "kodo" and I can see the name in
the JNDI dump :
"(top)/nodes/Eleanor/servers/server1/kodo KodoJDO"
Yet when I try to access the adapter through the CarBean example (JNDI name
"kodo" specified in the properties file) I always get an error:
[02/02/04 15:38:38:494 GMT] 3a66b2c2 ConnectionFac I J2CA0122I: Resource
reference kodo could not be located, so default values of the following are
used: [Resource-ref settings]
res-auth: 1 (APPLICATION)
res-isolation-level: 0 (TRANSACTION_NONE)
res-sharing-scope: false (UNSHAREABLE)
res-resolution-control: 999 (undefined)
[Other attributes]
isCMP1_x: false (not CMP1.x)
isJMS: false (not JMS)
What do i do wrong?
Cheers
Sven ErikStijn-
Are you sure that Kodo is successfully bound into JNDI? If you
configured it using JCA (i.e., by deploying the kodo.rar), did you I
successfully configure the adapter as described in the installation
instructions?
What is the complete exception and stack trace that you receive when you
try to look it up?
In article <[email protected]>, Stijn Van den Enden wrote:
Hi,
sorry for my late reply ...
This is the excerpt of the ejb DD, where the resource ref is defined:
<resource-ref id="ResourceRef_1073662418157">
<description></description>
<res-ref-name>jdo/PersistenceManagerFactory</res-ref-name>
<res-type>javax.resource.cci.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Kind regards,
Stijn
Sven Erik Knop wrote:
Hallo Stijn
Could you give me an example of how to add the resource ref to the
deployment descriptor? I am not familiar with J2EE.
Cheers
Sven Erik
"Stijn Van den Enden" <[email protected]> wrote in message
news:[email protected]...
Hi Sven,
the best way to look up the PersistenceManagerFactory is through the
JNDI ENC, as Global JNDI names are error prone. So in order to get a
handle to the PersistenceManagerFactory use the ENC e.g.
java:comp/env/jdo/PersistenceManagerFactory in your code, add a
ResourceRef for jdo/PersistenceManagerFactory to the DD, and map it in
the DD to kodo (Websphere will do the mapping to the right JNDI context
automatically).
Cheers,
Stijn
Sven Erik Knop wrote:
This is Kodo 3.0.2 by the way
"Sven Erik Knop" <[email protected]> wrote in message
news:[email protected]...
Ok
I give up ... how do you set up the Kodo JCA adapter for WebSphere 5.1
for
the enterprise version? I seem to always get an error if I try to accessit.
My resource adapter is bound to the name "kodo" and I can see the name
in
the JNDI dump :
"(top)/nodes/Eleanor/servers/server1/kodo KodoJDO"
Yet when I try to access the adapter through the CarBean example (JNDIname
"kodo" specified in the properties file) I always get an error:
[02/02/04 15:38:38:494 GMT] 3a66b2c2 ConnectionFac I J2CA0122I: Resource
reference kodo could not be located, so default values of the followingare
used: [Resource-ref settings]
res-auth: 1 (APPLICATION)
res-isolation-level: 0 (TRANSACTION_NONE)
res-sharing-scope: false (UNSHAREABLE)
res-resolution-control: 999 (undefined)
[Other attributes]
isCMP1_x: false (not CMP1.x)
isJMS: false (not JMS)
What do i do wrong?
Cheers
Sven Erik
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Multiple Kodo Datasources in WebLogic 8.1 using JCA - How?
Greetings
I am trying to set up WebLogic (8.1) such that I can deploy a single Kodo
JCA connector but use it to access multiple data sources. Assuming that the
JCA adaptor has been deployed to the Server with a name and jndi key of
"kodo", I believe that the way to do it is to deploy a second copy of the
weblogic-ra.xml and ra.xml files and use an <ra-link-ref> tag to refer to
the primary deployed JCA adaptor. The second ra.xml has different kodo
config-property-values for connection URL, Username/password, etc from the
primary ra.xml.
This seems to work - to a point. Accessing the second "adaptor" ("kodo2")
does work and seems to link to the primary one, but the ra.xml
config-properties which are used appear to be from the primary deployment :(
not the second one as I hoped.
Can anyone point me in the right direction? Below is a copy of the
secondary weblogic-ra.xml file:
<!DOCTYPE weblogic-connection-factory-dd PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 Connector//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic600-ra.dtd'>
<weblogic-connection-factory-dd>
<connection-factory-name>kodo2</connection-factory-name>
<jndi-name>kodo2</jndi-name>
<ra-link-ref>kodo</ra-link-ref>
<pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>8</max-capacity>
<capacity-increment>1</capacity-increment>
<shrinking-enabled>false</shrinking-enabled>
<shrink-period-minutes>200</shrink-period-minutes>
</pool-params>
<security-principal-map>
</security-principal-map>
</weblogic-connection-factory-dd>
Thanks
..droo.Drew-
It should be possible to use two separate Kodo JCA configurations in the
same application server. Could you post your two configurations (without
the license keys, please) so we can take a look of the different places
where you are configuring the sequence table names? I suspect that there
might be a simple misconfiguration or type somewhere.
In article <BD4AB2EE.8DA%[email protected]>, Drew Lethbridge wrote:
I think I have partially figured this out. Actually I shouldn't have ra.xml
in the second JCA adaptor, instead I can specify different config properties
in weblogic-ra.xml such as:
<map-config-property>
<map-config-property-name>Schemas</map-config-property-name>
<map-config-property-value>FRED</map-config-property-value>
</map-config-property>
I am still getting some weird behaviour though. For example, I currently
get an exception when trying to to an update because kodo2 tries to get the
sequence from the wrong schema, i.e.:
com.solarmetric.jdbc.ReportingSQLException: ORA-00942: table or view does
not exist
{prepstmnt 7569347 SELECT SEQUENCEX FROM MARY.JDO_SEQUENCEX WHERE PKX = ?
FOR UPDATE [reused=0]} [code=942, state=42000]
at
kodo.jdbc.schema.DBSequenceFactory.getNext(DBSequenceFactory.java:227)
Etc...
It should be getting the sequence from FRED (kodo2), not MARY (kodo).
Any tips about how to configure multiple kodo JCA properties in Weblogic 8.1
would still be very much appreciated.
Cheers!
.droo.
On 19/8/04 2:39 PM, in article BD4A6C2D.7A0%[email protected], "Drew
Lethbridge" <[email protected]> wrote:
Greetings
I am trying to set up WebLogic (8.1) such that I can deploy a single Kodo
JCA connector but use it to access multiple data sources. Assuming that the
JCA adaptor has been deployed to the Server with a name and jndi key of
"kodo", I believe that the way to do it is to deploy a second copy of the
weblogic-ra.xml and ra.xml files and use an <ra-link-ref> tag to refer to
the primary deployed JCA adaptor. The second ra.xml has different kodo
config-property-values for connection URL, Username/password, etc from the
primary ra.xml.
This seems to work - to a point. Accessing the second "adaptor" ("kodo2")
does work and seems to link to the primary one, but the ra.xml
config-properties which are used appear to be from the primary deployment :(
not the second one as I hoped.
Can anyone point me in the right direction? Below is a copy of the
secondary weblogic-ra.xml file:
<!DOCTYPE weblogic-connection-factory-dd PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 Connector//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic600-ra.dtd'>
<weblogic-connection-factory-dd>
<connection-factory-name>kodo2</connection-factory-name>
<jndi-name>kodo2</jndi-name>
<ra-link-ref>kodo</ra-link-ref>
<pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>8</max-capacity>
<capacity-increment>1</capacity-increment>
<shrinking-enabled>false</shrinking-enabled>
<shrink-period-minutes>200</shrink-period-minutes>
</pool-params>
<security-principal-map>
</security-principal-map>
</weblogic-connection-factory-dd>
Thanks
.droo.
Marc Prud'hommeaux
SolarMetric Inc. -
Configuring kodo-jdo-2.5.3 with weblogic 8.1 using JCA
Hi there.
I am trying to configure kodo-jdo-2.5.3 in WebLogic 8.1 using JCA method.
The issue I got was that I got DB authentication failed. I have tested my
JDBC connect -- working fine, I have turned on JDBC log in WL, it looks
fine.
It looks like that KODO was still trying to create its own JDBC connection
even I have specified
<config-property>
<description>The JNDI name of the connection factory to use for
obtaining connections.</description>
<config-property-name>ConnectionFactoryName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>datasource.oracle9</config-property-value>
</config-property>
"datasource.oracle9" is the JNDI name of my data source.
The error message is the following. I will really appreciate your help.
Melvin
Oct 19, 2003 4:20:53 AM com.solarmetric.kodo.impl.jdbc.RegisterListener
registerClass
SEVERE: com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, f
ailed to be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLExceptions.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassInternal(JDBCPe
rsistenceManagerFactory.java:455)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(JDBCPersistenc
eManagerFactory.java:338)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListener.java:53)
at
javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at samples.j2ee.Car.<clinit>(Car.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at samples.j2ee.ejb.CarBean.class$(CarBean.java:11)
at samples.j2ee.ejb.CarBean.list(CarBean.java:136)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
NestedThrowablesStackTrace:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
weblogic.jdbc.common.internal.RmiDataSource.getSubject(RmiDataSource.java:257)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(DataSourceConnec
tor.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassInternal(JDBCPe
rsistenceManagerFactory.java:455)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(JDBCPersistenc
eManagerFactory.java:338)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListener.java:53)
at
javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at samples.j2ee.Car.<clinit>(Car.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at samples.j2ee.ejb.CarBean.class$(CarBean.java:11)
at samples.j2ee.ejb.CarBean.list(CarBean.java:136)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Oct 19, 2003 4:20:53 AM CDT> <Info> <EJB> <BEA-010051> <EJB Exception
occurred during invocation fr
om home: samples.j2ee.ejb.CarEJB_pgfrtx_HomeImpl@1c059f6 threw exception:
com.solarmetric.kodo.runti
me.FatalDataStoreException: java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0
;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLExceptions.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCStoreManager.ja
va:753)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1023)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1037)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCExtent.getResultList(JDBCExtent.java:71)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCExtent.getIterator(JDBCExtent.java:47)
at
com.solarmetric.kodo.runtime.ExtentImpl$MultipleSubclassIterator.newIterator(ExtentImpl.j
ava:344)
at serp.util.MultiIterator.setIterator(MultiIterator.java:74)
at serp.util.MultiIterator.hasNext(MultiIterator.java:29)
at serp.util.LookaheadIterator.setNext(LookaheadIterator.java:133)
at
serp.util.LookaheadIterator.initialize(LookaheadIterator.java:118)
at serp.util.LookaheadIterator.hasNext(LookaheadIterator.java:48)
at serp.util.MultiIterator.setIterator(MultiIterator.java:73)
at serp.util.MultiIterator.hasNext(MultiIterator.java:29)
at
com.solarmetric.kodo.runtime.ExtentImpl$TransactionAwareIterator.hasNext(ExtentImpl.java:
403)
at samples.j2ee.ejb.CarBean.list(CarBean.java:138)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
NestedThrowablesStackTrace:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
weblogic.jdbc.common.internal.RmiDataSource.getSubject(RmiDataSource.java:257)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(DataSourceConnec
tor.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCStoreManager.ja
va:753)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1023)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1037)Alex Robbins wrote:
Try removing <authentication-mechanism> from the ra.xml file of the Kodo
JCA connector. Then it won't try to authenticate against the WL security
realm. (If you want connector-level authentication as well as DB-conn
authentication i think you'll have to configure WL security. I don't know
how). This worked for me.
Alex.Hi, The following is the ra.xml, please see any problem.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector
1.0//EN' 'http://java.sun.com/dtd/connector_1_0.dtd'>
<connector>
<display-name>KodoJDO</display-name>
<description>Resource Adapter for integration of the Kodo Java Data
Objects (JDO) implementation with J2EE 1.3 compliant managed
environments</description>
<icon>
<small-icon>kodo16.gif</small-icon>
<large-icon>kodo32.gif</large-icon>
</icon>
<vendor-name>Solarmetric, Inc.</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>jdo</eis-type>
<version>1.0</version>
<license>
<description>See http://www.solarmetric.com for terms and license
conditions.</description>
<license-required>true</license-required>
</license>
<resourceadapter>
<managedconnectionfactory-class>com.solarmetric.kodo.impl.jdbc.ee.ManagedConnectionFactoryImpl</managedconnectionfactory-class>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.solarmetric.kodo.ee.EEPersistenceManager</connection-impl-class>
<transaction-support>XATransaction</transaction-support>
<config-property>
<description>The number of hard references to cached objects that the
PersistenceManager's cache will retain (in addition to the soft reference
cache that it maintains). Setting this to a higher value will result in
more objects being retained in the cache, at the cost of utilizing more
memory resources. Setting it to -1 will cause the PersistenceManager to
maintain hard references only. This will result in better performance, but
can have adverse effects on memory usage.</description>
<config-property-name>CacheReferenceSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>1000</config-property-value>
</config-property>
<config-property>
<description>The class name of ether the JDBC java.sql.Driver, or an
instance of a javax.sql.DataSource to use to connect to the data
source.</description>
<config-property-name>ConnectionDriverName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
finding non-transactional connections. If specified, this is the
connection that will be used for access for obtaining sequence
numbers.</description>
<config-property-name>ConnectionFactory2Name</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>jdbc/petshop</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to be passed to
the JDBC Driver when obtaining a Connection for the ConnectionFactory2
(which will be used to obtain sequence numbers). Properties are of the
form "key=value". If a javax.sql.DataSource class is defined in the
javax.jdo.option.ConnectionDriverName property, then this property will be
used to set bean-like properties in the DataSource instance upon creation.
These properties vary depending on the DataSource in use: see the
documentation for your DataSource for details on the properties to
use.</description>
<config-property-name>ConnectionFactory2Properties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
obtaining connections.</description>
<config-property-name>ConnectionFactoryName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>PetShopXADataSource</config-property-value>
</config-property>
<config-property>
<description>The password for the user specified in
ConnectionUserName</description>
<config-property-name>ConnectionPassword</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to be passed to
the JDBC Driver when obtaining a Connection. Properties are of the form
"key=value". If a javax.sql.DataSource class is defined in the
javax.jdo.option.ConnectionDriverName property, then this property will be
used to set bean-like properties in the DataSource instance upon creation.
These properties vary depending on the DataSource in use: see the
documentation for your DataSource for details on the properties to
use.</description>
<config-property-name>ConnectionProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The connection retain mode. Possible options are
"persistence-manager", "transaction", and "on-demand". Default value is
"on-demand".</description>
<config-property-name>ConnectionRetainMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>on-demand</config-property-value>
</config-property>
<config-property>
<description>The number of seconds to wait between testing
connections retrieved from the connection pool. Only valid when using the
built-in Kodo connection pooling.</description>
<config-property-name>ConnectionTestTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>10</config-property-value>
</config-property>
<config-property>
<description>The URL for the data source.</description>
<config-property-name>ConnectionURL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The username for the connection listed in
ConnectionURL.</description>
<config-property-name>ConnectionUserName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for caching of data loaded
from the data store. Must implement
com.solarmetric.kodo.runtime.datacache.DataCache.</description>
<config-property-name>DataCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.DataCacheClass upon
initialization.</description>
<config-property-name>DataCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the default class to use for mapping
persistent classes to the database. Must extend
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.</description>
<config-property-name>DefaultClassMappingClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping</config-property-value>
</config-property>
<config-property>
<description>The number of seconds that data in the data cache is
valid for. A value of 0 or less means that by default, cached data does
not time out.</description>
<config-property-name>DefaultDataCacheTimeout</config-property-name>
<config-property-type>java.lang.Double</config-property-type>
<config-property-value>0.0</config-property-value>
</config-property>
<config-property>
<description>The number of rows that will be pre-fetched when an
element in a Query result is accessed.</description>
<config-property-name>DefaultFetchBatchSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>10</config-property-value>
</config-property>
<config-property>
<description>The threshold below which result lists will be
completely instantiated upon their creation. A value of -1 will always
force all results to be completely instantiated, thus disabling lazy
result loading.</description>
<config-property-name>DefaultFetchThreshold</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>30</config-property-value>
</config-property>
<config-property>
<description>The name of the default class to use for managing
subclass indicator columns. Must implement the
com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProvider interface. See
custom class indicator documentation for more information about subclass
providers.</description>
<config-property-name>DefaultSubclassProviderClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in
com.solarmetric.kodo.impl.jdbc.DefaultSubclassProviderClass upon
initialization.</description>
<config-property-name>DefaultSubclassProviderProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The DBDictionary to use for this configuration. This is
auto-detected based on the setting of javax.jdo.option.ConnectionURL, so
you need only set this to override the default with your own custom
DBDictionary or if you are using an unrecognized driver.</description>
<config-property-name>DictionaryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of name-value properties
settings to pass to the dictionary defined by
com.solarmetric.kodo.impl.jdbc.DictionaryClass. Many of the DBDictionary
options are automatically configured by concrete subclasses of
GenericDictionary. The defaults can, however, be overridden by using this
property.</description>
<config-property-name>DictionaryProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then Kodo JDO will allow the use of query
filter extensions. See the query extensions documentation for more
information.</description>
<config-property-name>EnableQueryExtensions</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of fetch group names that
PersistenceManagers will load by default when loading data from the
database.</description>
<config-property-name>FetchGroups</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then all fields of all classes in a given
inheritance hierarchy will by default map into the least-derived type's
default primary table. If false then a new default primary table will be
created for each class in the inheritance hierarchy, and each type's
declared fields will map to that table by default.</description>
<config-property-name>FlatInheritanceMapping</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>A String value indicating whether or not Kodo should
automatically flush modifications to the data store before executing
queries.</description>
<config-property-name>FlushBeforeQueries</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>with-connection</config-property-value>
</config-property>
<config-property>
<description>If false, then the JDO implementation must consider
modifications, deletions, and additions in the PersistenceManager
transaction cache when executing a query inside a transaction. Else, the
implementation is free to ignore the cache and execute the query directly
against the data store.</description>
<config-property-name>IgnoreCache</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The license key provided to you by SolarMetric. Keys
are available at www.solarmetric.com</description>
<config-property-name>LicenseKey</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>xxxx</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for obtaining a reference
to the transaction manager in an enterprise environment. Must implement
the com.solarmetric.kodo.ee.ManagedRuntime interface.</description>
<config-property-name>ManagedRuntimeClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.ee.AutomaticManagedRuntime</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.ManagedRuntimeClass upon
initialization.</description>
<config-property-name>ManagedRuntimeProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The maximum number of connections to pool. If all of
these are in use, then PersistenceManager instances must wait for a
connection to become available. This option has been removed from the
specification, but we still use the javax.jdo.option for backwards
compatibility.</description>
<config-property-name>MaxPool</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>200</config-property-value>
</config-property>
<config-property>
<description>The minimum number of connections to keep in the pool.
This option has been removed from the specification, but we still use the
javax.jdo.option for backwards compatibility.</description>
<config-property-name>MinPool</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>2</config-property-value>
</config-property>
<config-property>
<description>The number of milliseconds to wait for a pooled
connection before throwing an exception if the pool is empty. This option
has been removed from the specification, but we still use the
javax.jdo.option for backwards compatibility.</description>
<config-property-name>MsWait</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>30000</config-property-value>
</config-property>
<config-property>
<description>If true, then the application plans to have multiple
threads simultaneously accessing a single PersistenceManager, so measures
must be taken to ensure that the implementation is thread-safe. Otherwise,
the implementation need not address thread safety.</description>
<config-property-name>Multithreaded</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to read persistent data
outside the context of a transaction. Otherwise, a transaction must be in
progress in order read data.</description>
<config-property-name>NontransactionalRead</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to write to fields of a
persistent-nontransactional object when a transaction is not in progress.
If false, such a write will result in a JDOUserException.</description>
<config-property-name>NontransactionalWrite</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>Selects between optimistic and pessimistic (data store)
transactional modes.</description>
<config-property-name>Optimistic</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class that the
PersistenceManagerFactory should create when creating a new
PersistenceManagerImpl. Must extend
com.solarmetric.kodo.runtime.PersistenceManagerImpl.</description>
<config-property-name>PersistenceManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the concrete implementation of
javax.jdo.PersistenceManagerFactory that
javax.jdo.JDOHelper.getPersistenceManagerFactory () should create. For
Kodo JDO, this should be
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory or
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory, or a custom
extension of one of these types.</description>
<config-property-name>PersistenceManagerFactoryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.PersistenceManagerClass upon
initialization.</description>
<config-property-name>PersistenceManagerProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of classes that will be
initialized whenever a new PersistenceManager is instantiated. This can be
used to get around issues with application identity classes not being
associated with their respective persistent classes.</description>
<config-property-name>PersistentTypes</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use to proxy second class
objects in managed instances. Must implement
com.solarmetric.kodo.util.ProxyManager.</description>
<config-property-name>ProxyManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.util.SimpleProxyManager</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.ProxyManagerClass upon
initialization.</description>
<config-property-name>ProxyManagerProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for caching of queries
loaded from the data store. Must implement
com.solarmetric.kodo.runtime.datacache.QueryCache.</description>
<config-property-name>QueryCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.runtime.datacache.query.QueryCacheImpl</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.QueryCacheClass upon
initialization.</description>
<config-property-name>QueryCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A list of query filter listeners to add to the default
list of extensions. Ignored if com.solarmetric.kodo.EnableQueryExtensions
is false.</description>
<config-property-name>QueryFilterListeners</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for communicating commit
information among JVMs. Must implement
com.solarmetric.kodo.runtime.event.RemoteCommitProvider.</description>
<config-property-name>RemoteCommitProviderClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.RemoteCommitProviderClass upon
initialization.</description>
<config-property-name>RemoteCommitProviderProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then fields in a persistence-capable object
that have been changed during a transaction will be rolled back to their
original values upon a rollback. Otherwise, the values will not be changed
upon rollback.</description>
<config-property-name>RestoreValues</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>The name of the class that will be used as the
Collection implementation for returning ResultList instances. It must be
an instance of
com.solarmetric.kodo.runtime.objectprovider.ResultList.</description>
<config-property-name>ResultListClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The property string used to configure the instance of
the ResultListClass.</description>
<config-property-name>ResultListProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then fields in a persistence-capable object
that have been read during a transaction must be preserved in memory after
the transaction commits. Otherwise, persistence-capable objects must
transition to the hollow state upon commit, meaning that subsequent reads
will result in a database round-trip.</description>
<config-property-name>RetainValues</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for generating sequence
numbers when using data store identity. Must implement the
com.solarmetric.kodo.impl.jdbc.SequenceFactory interface.</description>
<config-property-name>SequenceFactoryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.impl.jdbc.SequenceFactoryClass upon
initialization.</description>
<config-property-name>SequenceFactoryProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The class names of a SQLExecutionListener
implementation to install on the SQLExecutionManager.</description>
<config-property-name>SQLExecutionListenerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of a custom SQLExecutionManager to be used for
all issuance of SQL to the data store. Must implement
com.solarmetric.kodo.impl.jdbc.SQLExecutionManager.</description>
<config-property-name>SQLExecutionManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl</config-property-value>
</config-property>
<config-property>
<description>The size of the PreparedStatement cache that is
maintained in the DataSource implementation.</description>
<config-property-name>StatementCacheMaxSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>70</config-property-value>
</config-property>
<config-property>
<description>The time, in seconds, after which a JDBC query will be
aborted if it has not yet returned any values. This value is simply passed
to the JDBC driver's Statement.setTimeout method; Kodo does not perform
any addition timeout actions. Note that many JDBC drivers either ignore
this request, or improperly handle it, which may result in application
deadlocks.</description>
<config-property-name>StatementExecutionTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>-1</config-property-value>
</config-property>
<config-property>
<description>If true, the Kodo runtime will automatically attempt to
refresh the database schema when persistent classes are referenced,
allowing the developer to bypass the schematool step. This property is
only intended to be used for development. As automatic schema migration
can result in data loss, this feature should never be enabled on a
production system. Furthermore, this feature has serious adverse affects
on Kodo's runtime performace. Ensure that it is disabled before doing any
performance analysis.</description>
<config-property-name>SynchronizeSchema</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use to store
persistence-capable objects involved in a PM's transaction cache. Must
implement com.solarmetric.kodo.runtime.StateManagerSet.</description>
<config-property-name>TransactionCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.runtime.FifoStateManagerSet</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.TransactionCacheClass upon
initialization.</description>
<config-property-name>TransactionCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property -
We want to use the kodo JCA resource adapter. I have now been through
installing it on jboss 4 and websphere 6, trying to make it work. I have
run into the following:
1. Kodo.rar need the jdo-1.0.2.jar available. This is so on both jboss and
websphere. According to manual it should only be installed on jboss and
not on websphere 5. I believe this would be the same on websphere 5, since
it all fails due to not being able to find the classes in the
jdo-1.0.2.jar file.
a. I fixed this on websphere 6 by uploading the jar to the server and
adding it to the class path for the resource adapter. I guess this is the
only way to do this? If so, I guess it should be part of the manual.
b. Why is the jdo-1.0.2.jar file not included in the kodo.rar file?
2. Is supplying default properties possible? For now, I have simply
documented the properties that need to be setup for the application to
work, but these are pretty important ones like:
DBDictionary: oracle (StoreCharsAsNumbers=false)
SequenceFactory: native
Expecting the deployer to put in these makes no sense (as opposed to the
connection factory name and other properties) and I can foresee problems
with these being set wrongly when systems are installed. Is there a way to
give these default values? The only way that I can think of myself is by
repacking the kodo.rar archive. Is that legal according to license
conditions?
Thanks for any input you may have to this,
Kind regards,
Henning Andersen, Stibo Catalog.Henning Andersen wrote:
We want to use the kodo JCA resource adapter. I have now been through
installing it on jboss 4 and websphere 6, trying to make it work. I have
run into the following:
1. Kodo.rar need the jdo-1.0.2.jar available. This is so on both jboss and
websphere. According to manual it should only be installed on jboss and
not on websphere 5. I believe this would be the same on websphere 5, since
it all fails due to not being able to find the classes in the
jdo-1.0.2.jar file.
a. I fixed this on websphere 6 by uploading the jar to the server and
adding it to the class path for the resource adapter. I guess this is the
only way to do this? If so, I guess it should be part of the manual.That's an oversight in the manual. I apologize for the trouble.
b. Why is the jdo-1.0.2.jar file not included in the kodo.rar file?Those classes need to be seen by classes that are usually not loaded by
the same classloader, and so putting it in the system CLASSPATH is the
easiest way of satisfying that requirement.
2. Is supplying default properties possible? For now, I have simply
documented the properties that need to be setup for the application to
work, but these are pretty important ones like:
DBDictionary: oracle (StoreCharsAsNumbers=false)
SequenceFactory: native
Expecting the deployer to put in these makes no sense (as opposed to the
connection factory name and other properties) and I can foresee problems
with these being set wrongly when systems are installed. Is there a way to
give these default values? The only way that I can think of myself is by
repacking the kodo.rar archive. Is that legal according to license
conditions?Repacking the kodo.rar archive is the way to go, and is perfectly legal
according to our license.
Thanks for any input you may have to this,
Kind regards,
Henning Andersen, Stibo Catalog. -
Kodo 4.1.2 in Weblogic 10 Problem
I was told by BEA that Kodo/openJPA is included in Weblogic 10. However, now I have Weblogic 10 but I could not located much Kodo classes from Weblogic libraries. I searched all the JARs under BEA_HOME\wlserver_10.0\server\lib.
I also tried to migrate Kodo/JPA application from Weblogic 9.2 to Weblogic 10. My application depends on Kodo JCA deployment in managed environment. The application and Kodo JCA deployed fine into Weblogic 10. But when I test any application, the test failed when I tried to create EntityMaanger from EntityManagerFactory:
Caused by: <4|false|0.9.7> org.apache.openjpa.persistence.ArgumentException: config-error
at weblogic.kodo.event.ClusterRemoteCommitProvider.endConfiguration(ClusterRemoteCommitProvider.java:112)
at org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurations.java:447)
at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiate(RemoteCommitProviderValue.java:122)
at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiateProvider(RemoteCommitProviderValue.java:103)
at org.apache.openjpa.conf.RemoteCommitProviderValue.instantiateProvider(RemoteCommitProviderValue.java:95)
at org.apache.openjpa.conf.OpenJPAConfigurationImpl.newRemoteCommitProviderInstance(OpenJPAConfigurationImpl.java:708)
at org.apache.openjpa.event.RemoteCommitEventManager.(RemoteCommitEventManager.java:56)
at org.apache.openjpa.conf.OpenJPAConfigurationImpl.getRemoteCommitEventManager(OpenJPAConfigurationImpl.java:720)
at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:177)
at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:139)
at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:187)
at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:140)
at kodo.persistence.jdbc.JPAConnectionFactory.createEntityManager(JPAConnectionFactory.java:144)
at kodo.persistence.jdbc.JPAConnectionFactory.createEntityManager(JPAConnectionFactory.java:23)
at com.psi.vida.ejb.JPASessionBean.list(JPASessionBean.java:165)
at com.psi.vida.ejb.JPASessionEJB_lvtqkz_EOImpl.list(JPASessionEJB_lvtqkz_EOImpl.java:134)
at com.psi.vida.ejb.JPASessionEJB_lvtqkz_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
... 17 more
Caused by: java.lang.Exception: <0|true|0.9.7> org.apache.openjpa.persistence.PersistenceException: no-trasport
at org.apache.openjpa.util.Exceptions.replaceNestedThrowables(Exceptions.java:230)
at org.apache.openjpa.persistence.ArgumentException.writeObject(ArgumentException.java:104)
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:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:890)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1333)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
at weblogic.rmi.extensions.server.CBVOutputStream.writeObject(CBVOutputStream.java:84)
at weblogic.rmi.internal.ServerRequest.unmarshalThrowable(ServerRequest.java:349)
at weblogic.rmi.internal.ServerRequest.getThrowable(ServerRequest.java:62)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:203)
... 17 moreI was told by BEA that Kodo/openJPA is included in
Weblogic 10. However, now I have Weblogic 10 but I
could not located much Kodo classes from Weblogic
libraries. I searched all the JARs under
BEA_HOME\wlserver_10.0\server\lib. They're in the (new) modules directory. weblogic.jar refers to stuff in the modules directory via its manifest classpath.
I also tried to migrate Kodo/JPA application from
Weblogic 9.2 to Weblogic 10. My application depends
on Kodo JCA deployment in managed environment. The
application and Kodo JCA deployed fine into Weblogic
10. But when I test any application, the test failed
when I tried to create EntityMaanger from
EntityManagerFactory:Interesting. I do not know what the status of Kodo JCA testing is in WebLogic 10, but it sounds like something is a bit wonky.
Basically, in a WLS environment, the default remote commit provider is automatically set to the new weblogic.kodo.event.ClusterRemoteCommitProvider, which uses the WLS clustering protocol to communicate cache notifications. The error that you're seeing indicates that cluster services are not available in the execution context. You can probably get around this by explicitly setting the 'kodo.RemoteCommitProvider' option to 'sjvm' (if you're not running in a cluster), or to whatever you had it set to in the past. (I'm guessing that it was unset in the past, as otherwise, the configuration should be picking up that instead of the new default.)
However, personally, I much prefer the new persistence.xml configuration file format, compared to JCA configuration. (You can trivially use the persistence.xml format with Kodo JDO, even though it's a JPA-specified feature.) You might want to look into moving away from JCA and to the persistence.xml style instead.
If you do this, you'll end up putting a META-INF/persistence.xml file in your EAR (and possibly a META-INF/persistence-configuration.xml file, if you want to use the strongly-typed Kodo XML configuration format), and replacing your JNDI lookups with java:comp/env/persistence/<persistence-unit-name>. (I think that's the right location. I might be mistaken, though.)
Also, I can't guarantee that WebLogic 10 really handles JCA configuration all that well; some bits of that exception make it look like maybe some resources are not available in the classloader, which is surprising. So, it's possible that there is some sort of more fundamental JCA problem here (and not just a problem with the new remote commit provider).
-Patrick -
Hello all,
I have a problem with jboss 3.2 & Kodo JCA. I can't deploy this product .
exist any example the configuration file ?
Carlos.-Carlos-
Check out:
http://solarmetric.com/Support/Newsgroups/news/article.php?id_article=%3Cpan.2003.05.06.17.40.54.720806%40solarmetric.com%3E&grp_id=1
If this isn't working for you, can you post any error messages you are
seeing?
In article <b9gddk$oe9$[email protected]>, Carlos Miranda wrote:
>
Hello all,
I have a problem with jboss 3.2 & Kodo JCA. I can't deploy this product .
exist any example the configuration file ?
Carlos.---
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Install RAR in WAS 5 throws Exception
I try to install Kodo JCA to a Websphere v5.0 Test Environment in WSAD 5.1.0
via the Administartive console.
Kodo is 3.0.1 Enterprise evaluation
Console output below
Any help appreciated
/jan
*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with process name
localhost\localhost\server1 and process id 1816
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT enabled:
jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\Program Files\IBM\WebSphere Studio\Application
Developer\v5.1\runtimes\base_v5
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R
com.ibm.websphere.management.exception.ConfigServiceException
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:272)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:208)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:78)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:104
9)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:314
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAc
cessor.java:137)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(R
ootObjectDelegator.java:238)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(C
onfigObjectDelegator.java:139)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemp
late(ConfigServiceImpl.java:680)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(Confi
gServiceImpl.java:712)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResou
rceAdapter(InstallRARTask.java:109)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CR
esourceAdapterDetailAction.java:293)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1791)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServle
tInstance.java:110)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecy
cleServlet.java:174)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServ
let.java:313)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecyc
leServlet.java:116)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java
:283)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidSer
vletReferenceState.java:42)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletIns
tanceReference.java:40)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:948)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques
tDispatcher.java:530)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest
Dispatcher.java:176)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker
..java:201)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(C
achedInvocation.java:71)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq
uestProcessor.java:182)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene
r.java:334)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav
a:56)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R ---- Begin backtrace for
nested exception
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R
java.lang.NullPointerException
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:239)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:208)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:78)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:104
9)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:314
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAc
cessor.java:137)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(R
ootObjectDelegator.java:238)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(C
onfigObjectDelegator.java:139)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemp
late(ConfigServiceImpl.java:680)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(Confi
gServiceImpl.java:712)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResou
rceAdapter(InstallRARTask.java:109)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CR
esourceAdapterDetailAction.java:293)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1791)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServle
tInstance.java:110)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecy
cleServlet.java:174)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServ
let.java:313)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecyc
leServlet.java:116)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java
:283)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidSer
vletReferenceState.java:42)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletIns
tanceReference.java:40)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:948)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques
tDispatcher.java:530)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest
Dispatcher.java:176)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker
..java:201)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(C
achedInvocation.java:71)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq
uestProcessor.java:182)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene
r.java:334)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav
a:56)
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)The DB2 Fixpak did the trick, it only took about 400 MBytes of downloading,
unzipping and installing :-)
I'm now on "Database version is SQL08014 JDBC Driver version is 1.5.54" for
DB2.
/jan
"Jan Vasternas" <[email protected]> wrote in message
news:[email protected]...
Thanks for your help.
I applied the workaround and the installation worked fine.
I also ran a small sample application. I have tested it in
an unmanaged environment and also in
a JBoss 2.3.2 managed environment using the kodo rar and a JBossdatasource.
Both these test were succcessful using DB2 ( Database version is SQL08010,
DataSource JDBC Driver version is 1.0.581 ).
But running the same application in websphere using a websphere datasource
( based on com.ibm.db2.jcc.DB2ConnectionPoolDataSource) threw theexception:
com.solarmetric.jdbc.ReportingSQLException: getMaxFieldSize is notsupported
in JCC 1.0 {SELECT DISTINCT JDOCLASS FROM JAN.ANIMALJDO} [code=-99999,
state=null]
com.ibm.db2.jcc.b.SQLException: getMaxFieldSize is not supported in JCC1.0
>
I found someone else that had got the same error
http://www.dbforums.com/t927844.html
The suggestion is to install DB2 FIXPACK 3. I'll see if I can get that.
/jan
"Marc Prud'hommeaux" <[email protected]> wrote in message
news:[email protected]...
Jan-
It appears to be a bug in Websphere 5.1.0. It appears to be fixed in
5.1.1.
If you cannot upgrade, can you try the workaround described at:
http://www-106.ibm.com/developerworks/forums/dw_expandTree.jsp?thread=22186&forum=275&cat=9&message=99904#99904
>>
and let us know if it works?
In article <[email protected]>, Jan Vasternas wrote:
I try to install Kodo JCA to a Websphere v5.0 Test Environment in WSAD
5.1.0
via the Administartive console.
Kodo is 3.0.1 Enterprise evaluation
Console output below
Any help appreciated
/jan
*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with processname
localhost\localhost\server1 and process id 1816
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JITenabled:
jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\Program Files\IBM\WebSphere Studio\Application
Developer\v5.1\runtimes\base_v5
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R
com.ibm.websphere.management.exception.ConfigServiceException
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:272)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:208)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:78)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:104
9)
[12/29/03 17:52:24:890 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:314
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAc
cessor.java:137)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(R
ootObjectDelegator.java:238)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(C
onfigObjectDelegator.java:139)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemp
late(ConfigServiceImpl.java:680)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(Confi
gServiceImpl.java:712)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResou
rceAdapter(InstallRARTask.java:109)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CR
esourceAdapterDetailAction.java:293)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1791)
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
>>>
[12/29/03 17:52:24:900 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServle
tInstance.java:110)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecy
cleServlet.java:174)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServ
let.java:313)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecyc
leServlet.java:116)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java
:283)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidSer
vletReferenceState.java:42)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletIns
tanceReference.java:40)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:948)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques
tDispatcher.java:530)
[12/29/03 17:52:24:910 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest
Dispatcher.java:176)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker
.java:201)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(C
achedInvocation.java:71)
[12/29/03 17:52:24:920 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq
uestProcessor.java:182)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene
r.java:334)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav
a:56)
[12/29/03 17:52:25:030 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
>>>
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R ---- Begin backtracefor
nested exception
[12/29/03 17:52:25:040 CET] 2fbb5bfb SystemErr R
java.lang.NullPointerException
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:239)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHel
per.java:208)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:78)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:104
9)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:314
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAc
cessor.java:137)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(R
ootObjectDelegator.java:238)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(C
onfigObjectDelegator.java:139)
[12/29/03 17:52:25:050 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemp
late(ConfigServiceImpl.java:680)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(Confi
gServiceImpl.java:712)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResou
rceAdapter(InstallRARTask.java:109)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CR
esourceAdapterDetailAction.java:293)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1791)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
>>>
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[12/29/03 17:52:25:060 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServle
tInstance.java:110)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecy
cleServlet.java:174)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServ
let.java:313)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecyc
leServlet.java:116)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java
:283)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidSer
vletReferenceState.java:42)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletIns
tanceReference.java:40)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:948)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppReques
tDispatcher.java:530)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequest
Dispatcher.java:176)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[12/29/03 17:52:25:071 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker
.java:201)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(C
achedInvocation.java:71)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletReq
uestProcessor.java:182)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListene
r.java:334)
[12/29/03 17:52:25:081 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.jav
a:56)
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
>>>
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
[12/29/03 17:52:25:091 CET] 2fbb5bfb SystemErr R at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Here's my code
Person demographics = new Person(firstName,lastName);
Consumer consumer = new Consumer(demographics);
pm.makePersistent(consumer);
When I get the object id from the person object I get a null!!!!!! What am
I missing? I need to have an object id in the dependent object as soon as I
call makePersistent!!
This call returns null
JDOHelper.getObjectId(demographics);
I am using KODO 3.3.1 and the JCA for Websphere. But the behavior happens
with or without the app server.
public class Consumer{
private Person demographics;
Consumer(Person demographics){
setDemographics(demographics);
public class Person{
private String firstName;
private String lastName;
Person(String firstName, String lastName){
// Sets the attributes etc...
etc...
EduardoIt is safe for you to call preFlush ().
There isn't a setting that changes the behavior of makePersistent () to
cascade immediately, but you could extend PersistenceManager yourself to
extend makePersistent () so that it called preFlush () upon every
invocation.
-brian
Is there a configuration that allows Kodo to persist by reachability
without having to call the preFlush() method? Is it safe to call
preFlush() inside the application server?
Eduardo
"Abe White" <[email protected]> wrote in message
news:dbgosc$ft8$[email protected]..
Kodo doesn't assign oids to objects unless that object is the direct
target of makePersistent or until you've flushed. Although you can force
Kodo to run persistence-by-reachability and other pre-flush activities
with:
((KodoPersistenceManager) pm).preFlush ();
Maybe you are looking for
-
Laserjet m1217 will not print through easyprint on windows 2008 server 64Bit
We have a client that has the LaserJet M1217 that is connecting to our Window 2008 Server SP2 64Bit via Remote Desktop. Easyprint recognizes the printer, but will not even print a test page. We get a FAIL message. We either need to know how to pri
-
I erased my iPhone and when I sign in online I can see my old content like the notes and contacts but when I try to restore them from the iCloud, it does not show any back up. What do you think is the problem?
-
3850's using WLC 2504 as a guest anchor
Hi, Does anyone know if it's possible to use a WLC2504 as a guest anchor when we have deployed 3850's for regular corporate WLAN? The corporate stuff is all up and running OK using 3850's but i've now to come to look at the guest provisioning and i'd
-
Aperture/Dreamweaver compatibility
sorry if this question has previously been asked but i am new to using aperture. i am creating a web gallery style website for a school major works assignment and was wonder if i could create a web gallery in aperture and then export it and open in D
-
Several plugins disappear from Firefox [SOLVED]
Hello, Firefox suddenly began to complain about not having appropriate plugins, which have worked flawlessly long ago. The functionality was lost during a session, I just refreshed a site containing streaming video which was played well before refres