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?
Andreas

Andreas-
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

Similar Messages

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

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,
Carsten

Carsten-
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 advance

I 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".

OAM Integration with WAS 6.1 -main" java.lang.NoClassDefFoundError

I am running the registryTester after installing connector for WebSphere on WAS 6.1. The registry gets started and after providing the credentials, it gives the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: com.ibm.ws.bootstrap.
RASWsLoggerFactory
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:59)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:120)
at com.ibm.ws.security.core.ContextManagerFactory.<clinit>(ContextManage
rFactory.java:36)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
at com.ibm.websphere.security.WSSecurityException.printStackTrace(WSSecu
rityException.java:154)
at com.oblix.registry.RegistryLogger.logException(RegistryLogger.java:21
3)
at com.oblix.tools.registryTester.main(registryTester.java:104)
I notice that wssec.jar which is in the classpath for registryTester.bat is not present in %WAS_INSTALL_DIR%\lib\wssec.jar location. Is that the problem?
Thanks!

Seems to be a CLASSPATH problem. Try:
java -cp . ExampleProgramIt should help. (Beware there are three arguments, the . is the second.)
Maybe you have a classpath variable set where the path doesn't contain the working directory (the "."). You may then consider adding it to the end.
Hope it helps
Ivan

JMS Connector WebSphere MQ JMS Problems

I'm having problems configuring and using Oracle's JMS Connector with IBM WebSphere MQ JMS, as explained in the following Oracle How-to:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-connect-to-mqseries/doc/how-to-connect-to-mqseries.html
by Jeff Steidl
When trying to deploy the application to the oc4j (wich is done as part of the default ant target), I get the following error in the oc4j console:
2006-07-20 12:04:29.859 ERROR J2EE EJB3027 [how-to-connect-to-mqseries] An error
occured deploying EJB module: java.lang.InstantiationException: Resource except
ion(MQJMSRAInstanceName) for MessageDrivenBean DealerEjbName during endpoint act
ivation: failure looking up resource provider factory for XAConnectionFactoryWra
pper [XA Unified]-OracleGJRA.XAConnectionFactoryWrapper.pedroec.-7b007002:10c88d
48c98:-7fff.171 []: javax.resource.spi.ResourceAdapterInternalException: Looking
up java:comp/resource/MQJMSReference/mqxacf: javax.naming.NameNotFoundException
: No resource named 'MQJMSReference/mqxacf'found
I assume the problem is that I don't have an appropriate WebShpere binding for the resource.
Before going through the mentioned How-to, I followed the install instructions in:
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/Install.html
In order to create a queue manager, a queue, a topic and the appropriate bindings.
After following the previous document, I end up with the following bindings (listing obtained using JMSAdmin console):
InitCtx> dis ctx
Contents of InitCtx
.bindings java.io.File
a MQXAQCF com.ibm.mq.jms.MQXAQueueConnectionFactory
a MQTCF com.ibm.mq.jms.MQTopicConnectionFactory
a MQQCF com.ibm.mq.jms.MQQueueConnectionFactory
a MQQ com.ibm.mq.jms.MQQueue
a MQT com.ibm.mq.jms.MQTopic
a MQXATCF com.ibm.mq.jms.MQXATopicConnectionFactory
7 Object(s)
0 Context(s)
7 Binding(s), 6 Administered
And as you can see there is no mqxacf binding.
So the question is, should I define a new binding with that name? If so, what would be the command (def xacf(mqxacf) ?)
As you can see, ther is a MQXAQCF binding so Instead of defining a new mqxacf (which I really don't know how to do...) I thought that maybe I could use this one, being a xa queue connection factory instead of a plain xa connection factory.
This is used by the MDB, so I modified orion-ejb-jar.xml changing:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyXACF"
name = "jms/DealerConnectionFactory"/>
<config-property>
<config-property-name>ConnectionFactoryJndiName
</config-property-name>
<config-property-value>MQJMSRASubcontext/MyXACF
</config-property-value>
</config-property>
for this:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyXAQCF"
name = "jms/DealerConnectionFactory"/>
<config-property>
<config-property-name>ConnectionFactoryJndiName
</config-property-name>
<config-property-value>MQJMSRASubcontext/MyXAQCF
</config-property-value>
</config-property>
I changed MyXACF with MyXAQCF because oc4j-ra.xml defines a jndi location of mqxacf (which is not beign found in the bindings) for MyXACF while it defines a jndi location of MQXAQCF for MyXAQCF, which is defined in the bindings.
With this change, the application deploys ok ... but when I run the client (ant larry) I get the following error (from the client console, not the oc4j console... in the oc4j console, nothing is reported):
run-demo:
[exec] java.lang.NullPointerException
[exec] at oracle.j2ee.ra.jms.generic.RAUtils.lookupUsingResourceProvide
r(RAUtils.java:254)
[exec] at oracle.j2ee.ra.jms.generic.CommonManagedConnectionFactoryImpl
.getFactory(CommonManagedConnectionFactoryImpl.java:605)
[exec] at oracle.j2ee.ra.jms.generic.CommonFactoryWrapper.localCreateCo
nnection(CommonFactoryWrapper.java:121)
[exec] at oracle.j2ee.ra.jms.generic.ConnectionFactoryWrapper.createCon
nection(ConnectionFactoryWrapper.java:62)
[exec] at MyChannel.<init>(MyChannel.java:46)
[exec] at Player.play(Player.java:242)
[exec] at Player.main(Player.java:30)
Since MyCF is bound to the jndi location mqcf (in oc4j-ra.xml) which does not exist in my MQ bindings I decided to modify orion-ejb-jar.xml as I did for the MyXACF of the MDB.
I changed
<resource-ref-mapping
location = "MQJMSRASubcontext/MyCF"
name = "jms/PlayerConnectionFactory"/>
with this:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyQCF"
name = "jms/PlayerConnectionFactory"/>
I changed MyCF to MyQCF, which has a jndi location of MQQCF (specified inside of oc4j-ra.xml) which has a valid MQ binding.
.... but I get the following error:
run-demo:
[exec] Exception in thread "main" java.lang.AbstractMethodError: com.ibm.mq
.jms.MQQueueConnectionFactory.createConnection()Ljavax/jms/Connection;
[exec] at oracle.j2ee.ra.jms.generic.CommonManagedConnectionFactoryImpl
.createManagedConnection(CommonManagedConnectionFactoryImpl.java:261)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.cr
eateManagedConnection(ApplicationConnectionManager.java:1333)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnect
ionFromFactory(ConnectionPoolImpl.java:324)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.access$800(Connectio
nPoolImpl.java:95)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl$NonePoolingScheme.ge
tManagedConnection(ConnectionPoolImpl.java:1209)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection
(ConnectionPoolImpl.java:782)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.ge
tConnectionFromPool(ApplicationConnectionManager.java:1532)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.ac
quireConnectionContext(ApplicationConnectionManager.java:1477)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.al
locateConnection(ApplicationConnectionManager.java:1423)
[exec] at oracle.j2ee.connector.OracleConnectionManager.unprivileged_al
locateConnection(OracleConnectionManager.java:244)
[exec] at oracle.j2ee.connector.OracleConnectionManager.allocateConnect
ion(OracleConnectionManager.java:198)
[exec] at oracle.j2ee.ra.jms.generic.CommonFactoryWrapper.localCreateCo
nnection(CommonFactoryWrapper.java:130)
[exec] at oracle.j2ee.ra.jms.generic.QueueConnectionFactoryWrapper.crea
teConnection(QueueConnectionFactoryWrapper.java:84)
[exec] at MyChannel.<init>(MyChannel.java:46)
[exec] at Player.play(Player.java:242)
[exec] at Player.main(Player.java:30)
[exec] Result: 1
So as you can see I'm stuck.
Maybe it is just a simple matter of defining the appropriate objects and bindigs for mqxacf and mqcf, but I don't know how to do that.
I would appreciate any help.
Message was edited by:
pablokrause

Thanks again for your quick and useful response Jeff.
Regarding the extra administration steps to get topic consumers working in MQ, I had already executed them a few days ago as part of the MQ setup as is described in another JMS resource adapter demo (see references at bottom of this reply) but I thought that doing it once was enough. Well, it seems that you have to execute those commands each time you start MQ!
I executed them (again), as you kindly suggested in your last response and voila, it worked!... well sort of.
After starting the clients, I get the following random error in oc4j:
06/07/21 15:39:18 Got message: PING
06/07/21 15:39:18 randomly testing rollback:
06/07/21 15:39:18 sending a junk message
06/07/21 15:39:18 Sent message: Invalid junk message
06/07/21 15:39:18 marking transaction for rollback
06/07/21 15:39:18 sending a junk message
06/07/21 15:39:18 Sent message: Invalid junk message
2006-07-21 15:39:18.921 WARNING J2EE JTA0107 Error in resource driver during rol
lback: javax.transaction.xa.XAException: XA operation failed, see errorCode
2006-07-21 15:39:18.921 WARNING J2EE JTA0104 Failed to add the resource due to e
rror in the resource : javax.transaction.xa.XAException: Attempt to start transa
ction while transaction Xid( Global Id c0.a7.ff.20.b0.22.00.00.0c.00.00.00.00.00
.00.00.00.00.00.00.00.00.00.00, Format Id 4660, Branch Id 7d.20.c6.d9.00.00.00.0
0.00.00.00.00.00.00.00.00) is active. errorcode : -6 : Enlistment of resource fa
iled. Attempt to start transaction while transaction Xid( Global Id c0.a7.ff.20.
b0.22.00.00.0c.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00, Format Id 4660, Bra
nch Id 7d.20.c6.d9.00.00.00.00.00.00.00.00.00.00.00.00) is active.
followed, after a few seconds, by the following stack trace:
06/07/21 16:13:30 Got message: PING
06/07/21 16:13:30 MQJMS3011: Failed to publish message to MQ queue
06/07/21 16:13:30 javax.jms.JMSException: MQJMS3011: Failed to publish message t
o MQ queue
06/07/21 16:13:30 at com.ibm.mq.jms.services.ConfigEnvironment.newExceptio
n(ConfigEnvironment.java:553)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.publish(MQMessagePro
ducer.java:1855)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProduc
er.java:976)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProduc
er.java:1056)
06/07/21 16:13:30 at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.send
(CommonProducerWrapper.java:121)
06/07/21 16:13:30 at MyChannel.send(MyChannel.java:73)
06/07/21 16:13:30 at Dealer.onMessage(Dealer.java:210)
06/07/21 16:13:30 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native M
ethod)
06/07/21 16:13:30 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMet
hodAccessorImpl.java:39)
06/07/21 16:13:30 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Deleg
atingMethodAccessorImpl.java:25)
06/07/21 16:13:30 at java.lang.reflect.Method.invoke(Method.java:585)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoin
PointImpl.invoke(EJBJoinPointImpl.java:35)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.system.DMSInterce
ptor.invoke(DMSInterceptor.java:52)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.system.SetContext
ActionInterceptor.invoke(SetContextActionInterceptor.java:34)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at oracle.j2ee.connector.messageinflow.MessageEndpointIm
pl.invokeMessageInflowCallbacks(MessageEndpointImpl.java:294)
06/07/21 16:13:30 at MessageListener_MessageEndpoint1.onMessage(MessageLis
tener_MessageEndpoint1.java:39)
06/07/21 16:13:30 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsu
mer.java:237)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(
WorkWrapper.java:242)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWra
pper.java:215)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrappe
r.java:190)
06/07/21 16:13:30 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worke
r.run(PooledExecutor.java:814)
06/07/21 16:13:30 at java.lang.Thread.run(Thread.java:595)
In the Dealer code, I found a piece of code that randomly generating a junk message and marking the transaction for rollback. If I comment out this code, everything works fine.
So, even when I managed to make the demo work, the transactional stuff is not working.
It would be really nice to know what is going on, but I'm tired, its fiday and I'm clueless...
Now, for the "Unable to load message properties file - mqji(xx).properties", it is still showing up, but as you said, MQ seems to work fine.
Thank you very much again Jeff for your invaluable and extremely responsive help.
References:
I can't seem to find an demo that was very useful for me for setting up MQ in the Oracle site, but the direct links seem to still be working:
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/readme.html
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/Install.html
and the sample code and scripts:
http://otn.oracle.com/tech/java/oc4j/1003/how_to/jcajmsmq.zip
Message was edited by:
pablokrause

"No suitable driver" error using Kodo 3.1.0, MySQL Connector/J & eclipse 3.0M8

Hi,
I'm getting the following error when trying to use the mapping tool from
within eclipse 3.0M8:
<error>-An error occurred running MappingTool
kodo.util.FatalDataStoreException: No suitable driver
NestedThrowables:
java.sql.SQLException: No suitable driver
<info>-Done.
I followed the instructions on using the eclipse plugin, including copying
all jars from kodo's lib folder to the plugin folder, copying the MySQL
Connector/J jar to the kodo plugin folder, adding all of those jars to the
project classpath, and even added an entry to the plugin.xml file to
include the MySQL Connector/J jar. If I remove the project reference to
the MySQL Connector/J jar, the error changes to:
<error>-An error occurred running MappingTool
kodo.util.FatalDataStoreException: com.mysql.jdbc.Driver
NestedThrowables:
java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
<info>-Done.
This would imply that adding a <library> entry for the MySQL Connector/J
jar in my plugin.xml does not have any effect; if I remove it, I see the
same error as above. If I add the MySQL jar back to the project
classpath, the error changes back to 'No suitable driver' as above.
The behavior is the same whether I use the Kodo preferences
(Window\Preferences\Kodo Preferences) individually without a
kodo.properties file, or when I clear all individual properties and
indicate a kodo.properties file.
Help?
Thanks,
Matthew
Here's my kodo.properties file:
# Kodo JDO Properties configuration
kodo.LicenseKey: xxx
javax.jdo.PersistenceManagerFactoryClass:
kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName: com.mysql.jdbc.Driver
javax.jdo.option.ConnectionUserName: root
javax.jdo.option.ConnectionPassword:
javax.jdo.option.ConnectionURL: jdbc:mysql://localhost/kodo
javax.jdo.option.Optimistic: true
javax.jdo.option.RetainValues: true
javax.jdo.option.NontransactionalRead: true
kodo.Log: DefaultLevel=WARN, Runtime=INFO, Tool=INFO
Here's my eclipse-3.0M8/plugins/kodo.eclipse_2.1.0/plugin.xml:
<?xml version="1.0" encoding="UTF-8"?>
<plugin id="kodo"
name="%name"
version="1.0.1"
provider-name="%provider-name"
class="kodo.jdbc.integration.eclipse.KodoPlugin">
<runtime>


<library name="mysql-connector-java-3.0.11-stable-bin.jar"/>





<library name="kodo-jdo.jar"/>
<library name="jakarta-commons-collections-2.1.jar"/>
<library name="jakarta-commons-lang-1.0.1.jar"/>
<library name="jakarta-commons-pool-1.0.1.jar"/>
<library name="jakarta-regexp-1.1.jar"/>
<library name="jca1.0.jar"/>
<library name="jdbc2_0-stdext.jar"/>
<library name="jdo-1.0.1.jar"/>
<library name="jta-spec1_0_1.jar"/>
<library name="xalan.jar"/>
<library name="xercesImpl.jar"/>
<library name="xml-apis.jar"/>
<library name="jfreechart-0.9.16.jar"/>
<library name="jcommon-0.9.1.jar"/>
<library name="mx4j-admb.jar"/>
<library name="mx4j-jmx.jar"/>
<library name="mx4j-tools.jar"/>
<library name="jline.jar"/>
<library name="sqlline.jar"/>
</runtime>
<requires>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.jdt.core"/>
<import plugin="org.eclipse.jdt.launching"/>
</requires>
<extension point="org.eclipse.ui.actionSets">
<actionSet id="kodo.jdbc.integration.eclipse.actionSet"
label="%action-set-name"
visible="true">
<menu id="kodo.menu"
label="%group-label">
<separator name="baseGroup"/>
</menu>
<action id="kodo.removeBuilder"
label="%remove-builder-label"
class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
tooltip="%remove-builder-tooltip"
menubarPath="kodo.menu/baseGroup"
enablesFor="1">
</action>
<action id="kodo.addbuilder"
label="%add-builder-label"
class="kodo.jdbc.integration.eclipse.AddBuilderAction"
tooltip="%add-builder-tooltip"
menubarPath="kodo.menu/baseGroup"
enablesFor="1">
</action>
<action id="kodo.mapping.build"
label="%mapping-build-label"
tooltip="%mapping-build-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
icon="icons/BuildSchemaMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.mapping.drop"
label="%mapping-drop-label"
tooltip="%mapping-drop-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
icon="icons/DropMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.mapping.refresh"
label="%mapping-refresh-label"
tooltip="%mapping-refresh-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
icon="icons/RefreshMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.enhance"
label="%enhance-label"
icon="icons/EnhancerAction.gif"
class="kodo.jdbc.integration.eclipse.EnhancerAction"
tooltip="%enhance-tooltip"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
</actionSet>
</extension>

<extension point="org.eclipse.ui.perspectiveExtensions">
<perspectiveExtension
targetID="org.eclipse.ui.resourcePerspective">
<actionSet
id="kodo.jdbc.integration.eclipse.actionSet">
</actionSet>
</perspectiveExtension>
</extension>

<extension point="org.eclipse.ui.preferencePages">
<page name="%preference-name"
class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
</page>
</extension>

<extension point="org.eclipse.ui.editors">
<editor name="%mappingeditor-name" extensions="mapping"
icon="icons/mapping.gif"
contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
</editor>
<editor name="%editor-name" extensions="jdo,schema"
icon="icons/metadata.gif"
contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
</editor>
</extension>

<extension point="org.eclipse.ui.views">
<view id="kodo.jdbc.integration.eclipse.KodoView"
name="%view-name"
category="org.eclipse.jdt.ui.java"
icon="icons/kodosmall.gif"
class="kodo.jdbc.integration.eclipse.KodoView">
</view>
</extension>

<extension point="org.eclipse.core.resources.builders"
id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
name="%builder-name">
<builder>
<run
class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
</run>
</builder>
</extension>

<extension point="org.eclipse.ui.perspectiveExtensions">
<perspectiveExtension
targetID="org.eclipse.debug.ui.DebugPerspective">
<view id="kodo.jdbc.integration.eclipse.KodoView"
relative="org.eclipse.debug.ui.ExpressionView"
relationship="stack"/>
<viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
</perspectiveExtension>
</extension>
</plugin>

I am not using Eclipse but am also experiencing problems similar to those
described below. The fact is I cannot validate a configuration file which
specifies either a traditional MySQL driver or a MySQL DataSoure.
I am using what I believe to be the official stable version of MySQL
Connector/J which is 3.0.11 and has been for several months. Are you
saying that 3.0.11 (or even 3.0.8) is not supported?
3.0.12 was recently released as the latest stable version so 3.0.11 should
at least be supported by now.
-Neil
Stephen Kim wrote:
The milestones are not fully supported versions as they are of beta
quality. I would suggest using a proper release instead.
Wolfgang Kundrus wrote:
Hi,
I have excactly the same behaviour here with Eclipse 3.0M8 and MySQL. It
is the same with 3.0.8. and 3.0.11. What is the solution ?
Best regards
Wolfgang Kundrus
Marc Prud'hommeaux wrote:
Matthew-
Everything looks correct to me. If you try an older version of the MySQL
driver (such as 3.0.8, which is what we test with), do you see anything
different?
If you try to run a stand-alone Kodo program using the MySQL driver, do
you see the same exception? If so, can you post the complete stack
trace?
In article <[email protected]>, Matthew T. Adams wrote:
Hi,
I'm getting the following error when trying to use the mapping tool from
within eclipse 3.0M8:
<error>-An error occurred running MappingTool
kodo.util.FatalDataStoreException: No suitable driver
NestedThrowables:
java.sql.SQLException: No suitable driver
<info>-Done.
I followed the instructions on using the eclipse plugin, including copying
all jars from kodo's lib folder to the plugin folder, copying the MySQL
Connector/J jar to the kodo plugin folder, adding all of those jars to the
project classpath, and even added an entry to the plugin.xml file to
include the MySQL Connector/J jar. If I remove the project reference to
the MySQL Connector/J jar, the error changes to:
<error>-An error occurred running MappingTool
kodo.util.FatalDataStoreException: com.mysql.jdbc.Driver
NestedThrowables:
java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
<info>-Done.
This would imply that adding a <library> entry for the MySQL Connector/J
jar in my plugin.xml does not have any effect; if I remove it, I see the
same error as above. If I add the MySQL jar back to the project
classpath, the error changes back to 'No suitable driver' as above.
The behavior is the same whether I use the Kodo preferences
(WindowPreferencesKodo Preferences) individually without a
kodo.properties file, or when I clear all individual properties and
indicate a kodo.properties file.
Help?
Thanks,
Matthew
Here's my kodo.properties file:
# Kodo JDO Properties configuration
kodo.LicenseKey: xxx
javax.jdo.PersistenceManagerFactoryClass:
kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName: com.mysql.jdbc.Driver
javax.jdo.option.ConnectionUserName: root
javax.jdo.option.ConnectionPassword:
javax.jdo.option.ConnectionURL: jdbc:mysql://localhost/kodo
javax.jdo.option.Optimistic: true
javax.jdo.option.RetainValues: true
javax.jdo.option.NontransactionalRead: true
kodo.Log: DefaultLevel=WARN, Runtime=INFO, Tool=INFO
Here's my eclipse-3.0M8/plugins/kodo.eclipse_2.1.0/plugin.xml:
<?xml version="1.0" encoding="UTF-8"?>
<plugin id="kodo"
name="%name"
version="1.0.1"
provider-name="%provider-name"
class="kodo.jdbc.integration.eclipse.KodoPlugin">
<runtime>


<library name="mysql-connector-java-3.0.11-stable-bin.jar"/>





<library name="kodo-jdo.jar"/>
<library name="jakarta-commons-collections-2.1.jar"/>
<library name="jakarta-commons-lang-1.0.1.jar"/>
<library name="jakarta-commons-pool-1.0.1.jar"/>
<library name="jakarta-regexp-1.1.jar"/>
<library name="jca1.0.jar"/>
<library name="jdbc2_0-stdext.jar"/>
<library name="jdo-1.0.1.jar"/>
<library name="jta-spec1_0_1.jar"/>
<library name="xalan.jar"/>
<library name="xercesImpl.jar"/>
<library name="xml-apis.jar"/>
<library name="jfreechart-0.9.16.jar"/>
<library name="jcommon-0.9.1.jar"/>
<library name="mx4j-admb.jar"/>
<library name="mx4j-jmx.jar"/>
<library name="mx4j-tools.jar"/>
<library name="jline.jar"/>
<library name="sqlline.jar"/>
</runtime>
<requires>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.core.resources"/>
<import plugin="org.eclipse.jdt.core"/>
<import plugin="org.eclipse.jdt.launching"/>
</requires>
<extension point="org.eclipse.ui.actionSets">
<actionSet id="kodo.jdbc.integration.eclipse.actionSet"
label="%action-set-name"
visible="true">
<menu id="kodo.menu"
label="%group-label">
<separator name="baseGroup"/>
</menu>
<action id="kodo.removeBuilder"
label="%remove-builder-label"
class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
tooltip="%remove-builder-tooltip"
menubarPath="kodo.menu/baseGroup"
enablesFor="1">
</action>
<action id="kodo.addbuilder"
label="%add-builder-label"
class="kodo.jdbc.integration.eclipse.AddBuilderAction"
tooltip="%add-builder-tooltip"
menubarPath="kodo.menu/baseGroup"
enablesFor="1">
</action>
<action id="kodo.mapping.build"
label="%mapping-build-label"
tooltip="%mapping-build-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
icon="icons/BuildSchemaMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.mapping.drop"
label="%mapping-drop-label"
tooltip="%mapping-drop-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
icon="icons/DropMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.mapping.refresh"
label="%mapping-refresh-label"
tooltip="%mapping-refresh-tooltip"
class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
icon="icons/RefreshMappingTool.gif"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
<action id="kodo.enhance"
label="%enhance-label"
icon="icons/EnhancerAction.gif"
class="kodo.jdbc.integration.eclipse.EnhancerAction"
tooltip="%enhance-tooltip"
menubarPath="kodo.menu/baseGroup"
toolbarPath="Normal/Kodo"
enablesFor="+">
<selection class="org.eclipse.core.resources.IFile"
name="*.jdo">
</selection>
</action>
</actionSet>
</extension>

<extension point="org.eclipse.ui.perspectiveExtensions">
<perspectiveExtension
targetID="org.eclipse.ui.resourcePerspective">
<actionSet
id="kodo.jdbc.integration.eclipse.actionSet">
</actionSet>
</perspectiveExtension>
</extension>

<extension point="org.eclipse.ui.preferencePages">
<page name="%preference-name"
class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
</page>
</extension>

<extension point="org.eclipse.ui.editors">
<editor name="%mappingeditor-name" extensions="mapping"
icon="icons/mapping.gif"
contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
>>
class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
</editor>
<editor name="%editor-name" extensions="jdo,schema"
icon="icons/metadata.gif"
contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
>>
class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
</editor>
</extension>

<extension point="org.eclipse.ui.views">
<view id="kodo.jdbc.integration.eclipse.KodoView"
name="%view-name"
category="org.eclipse.jdt.ui.java"
icon="icons/kodosmall.gif"
class="kodo.jdbc.integration.eclipse.KodoView">
</view>
</extension>

<extension point="org.eclipse.core.resources.builders"
id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
name="%builder-name">
<builder>
<run
class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
</run>
</builder>
</extension>

<extension point="org.eclipse.ui.perspectiveExtensions">
<perspectiveExtension
targetID="org.eclipse.debug.ui.DebugPerspective">
<view id="kodo.jdbc.integration.eclipse.KodoView"
relative="org.eclipse.debug.ui.ExpressionView"
relationship="stack"/>
<viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
</perspectiveExtension>
</extension>
</plugin>
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Connectors For IBM Websphere

Hi all,
Please guide me on how to access through the WAS, the applications deployed on a WebSphere Application Server, without manually porting the EAR files and stuff.
I believe there might be some connectors.
Your help will be appreciated.
Thanx in advance.
Regards,
Sandip

You will need to check out service.sap.com/connectors or maybe it's connector without s.
You're looking for the JCo connector.

Install RAR problem in websphere

I am trying to install the RAR from 3.0 RC1 into Websphere 5.0 (inside
Websphere application developer studio) and I keep getting this error when
I click ok on the New Resource Adaptor page. Any ideas?
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R
com.ibm.websphere.management.exception.ConfigServiceException
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:242)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:178)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:71)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:994)
[10/14/03 10:50:18:214 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:294)
[10/14/03 10:50:18:214 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAccessor.java:120)
[10/14/03 10:50:18:224 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(RootObjectDelegator.java:234)
[10/14/03 10:50:18:224 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(ConfigObjectDelegator.java:134)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemplate(ConfigServiceImpl.java:672)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(ConfigServiceImpl.java:704)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResourceAdapter(InstallRARTask.java:109)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CResourceAdapterDetailAction.java:293)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[10/14/03 10:50:18:265 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[10/14/03 10:50:18:265 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R ---- Begin backtrace
for nested exception
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R
java.lang.NullPointerException
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:209)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:178)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:71)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:994)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:294)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAccessor.java:120)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(RootObjectDelegator.java:234)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(ConfigObjectDelegator.java:134)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemplate(ConfigServiceImpl.java:672)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(ConfigServiceImpl.java:704)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResourceAdapter(InstallRARTask.java:109)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CResourceAdapterDetailAction.java:293)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)

It looks like it does work on standalone. And for WASD I imported the RAR
into a connector project and that seemed to do the trick too. I guess with
WASD you can't do much with the admin. thanks.
Stephen Kim wrote:
I don't see any Kodo involved... where are you in the setup process and
on what configuration page?
Does it happen standalone?
Elan wrote:
I am trying to install the RAR from 3.0 RC1 into Websphere 5.0 (inside
Websphere application developer studio) and I keep getting this error when
I click ok on the New Resource Adaptor page. Any ideas?
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R
com.ibm.websphere.management.exception.ConfigServiceException
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:242)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:178)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:71)
[10/14/03 10:50:18:204 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:994)
[10/14/03 10:50:18:214 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:294)
[10/14/03 10:50:18:214 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAccessor.java:120)
[10/14/03 10:50:18:224 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(RootObjectDelegator.java:234)
[10/14/03 10:50:18:224 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(ConfigObjectDelegator.java:134)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemplate(ConfigServiceImpl.java:672)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(ConfigServiceImpl.java:704)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResourceAdapter(InstallRARTask.java:109)
[10/14/03 10:50:18:234 PDT] 510f4349 SystemErr R      at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CResourceAdapterDetailAction.java:293)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[10/14/03 10:50:18:245 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
[10/14/03 10:50:18:255 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[10/14/03 10:50:18:265 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[10/14/03 10:50:18:265 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[10/14/03 10:50:18:305 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
[10/14/03 10:50:18:315 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R ---- Begin backtrace
for nested exception
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R
java.lang.NullPointerException
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:209)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.WorkspaceHelper.getTemplate(WorkspaceHelper.java:178)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.newRefObject(MOFUtil.java:71)
[10/14/03 10:50:18:325 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:994)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:294)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAccessor.java:120)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(RootObjectDelegator.java:234)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(ConfigObjectDelegator.java:134)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemplate(ConfigServiceImpl.java:672)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(ConfigServiceImpl.java:704)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.websphere.management.configservice.tasks.InstallRARTask.installResourceAdapter(InstallRARTask.java:109)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.console.resources.j2c.J2CResourceAdapterDetailAction.perform(J2CResourceAdapterDetailAction.java:293)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[10/14/03 10:50:18:335 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
[10/14/03 10:50:18:345 PDT] 510f4349 SystemErr R      at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Error while configuring kodo to lookup a datasource

We had a working application using EEPersistenceManagerFactory
I changed the kodo.properties to lookup a non XA JDBC datasource.
After that the application is working fine (it creates
,updates,deletes,finds record in the DB)
but SystemOut.log has the following error for every operation
We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
How can we avoid getting this error ?.
We tried to find any property on the Websphere datasource which can be
altered to avoid this error but no luck.
Thanks
Paresh
[10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
destroy failed while trying to execute method destroy on ManagedConnection
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
<null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
exception was received by the Data Store Adapter. See original exception
message: Cannot call 'cleanup' on a ManagedConnection while it is still in
a transaction..
     at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
     at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
     at
com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
     at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
     at
com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
     at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
     at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
     at
com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
     at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
Compiled Code))
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
Code))
     at
com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
Code))
     at
com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
     at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
     at com.paresh.core.vo.Release.writeObject(Release.java)
     at java.lang.reflect.Method.invoke(Native Method)
     at
com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
     at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
     at
com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
     at
com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
     at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
     at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
     at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
     at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
     at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
     at
com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
     at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
     at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
     at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
     at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
     at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
     at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
kodo.properties
com.solarmetric.kodo.LicenseKey=
#com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
#com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
#javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
#com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
# Changing these to a non-zero value will dramatically increase
# performance, but will cause in-memory databases such as Hypersonic
# SQL to never exit when your main() method exits, as the pooled
# connections in the in-memory database will cause a daemon thread to
# remain running.
javax.jdo.option.MinPool=5
javax.jdo.option.MaxPool=10

We do have a makeTransientAll() before the object returns from Session
Bean.
We also tried the JCA path
After installing the JCA RAR and doing a lookup for
PersistenceManagetFactory the same code is not throwing any exception.
The exception is thrown only if datasource is used.
Thanks
Paresh
Marc Prud'hommeaux wrote:
Paresh-
It looks like you are returning a collection of instances from an EJB,
which will cause them to be serialized. The serialization is happening
outside the context of a transaction, and Kodo needs to obtain a
connection. Websphere seems to not like that.
You have a few options:
1. Call makeTransientAll() on all the instances before you return them
from your bean methods
2. Manually instantiate all the fields yourself before sending them
back. You could use a bogus ObjectOutputStream to do this.
3. In 3.0, you can use the new detach() API to detach the instances
before sending them back to the client.
In article <[email protected]>, Paresh wrote:
We had a working application using EEPersistenceManagerFactory
I changed the kodo.properties to lookup a non XA JDBC datasource.
After that the application is working fine (it creates
,updates,deletes,finds record in the DB)
but SystemOut.log has the following error for every operation
We are using Kodo 2.5.0, Websphere 5.0 and Oracle 8
How can we avoid getting this error ?.
We tried to find any property on the Websphere datasource which can be
altered to avoid this error but no luck.
Thanks
Paresh
[10/7/03 15:30:45:467 IST] 3d8b2d1a MCWrapper E J2CA0081E: Method
destroy failed while trying to execute method destroy on ManagedConnection
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@437f6d23 from resource
<null>. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An
exception was received by the Data Store Adapter. See original exception
message: Cannot call 'cleanup' on a ManagedConnection while it is still in
a transaction..
     at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:222)
     at
com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:172)
     at
com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:182)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:1826)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:1389)
     at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1032)
     at
com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:259)
     at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:777)
     at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1304)
     at
com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:195)
     at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java:843)
     at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:569)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java:132)
     at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:814)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java(Inlined
Compiled Code))
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java(Compiled
Code))
     at
com.solarmetric.kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java(Compiled
Code))
     at
com.solarmetric.kodo.runtime.StateManagerImpl.preSerialize(StateManagerImpl.java:784)
     at com.paresh.core.vo.Release.jdoPreSerialize(Release.java)
     at com.paresh.core.vo.Release.writeObject(Release.java)
     at java.lang.reflect.Method.invoke(Native Method)
     at
com.ibm.rmi.io.IIOPOutputStream.invokeObjectWriter(IIOPOutputStream.java:703)
     at com.ibm.rmi.io.IIOPOutputStream.outputObject(IIOPOutputStream.java:671)
     at
com.ibm.rmi.io.IIOPOutputStream.simpleWriteObject(IIOPOutputStream.java:146)
     at
com.ibm.rmi.io.ValueHandlerImpl.writeValueInternal(ValueHandlerImpl.java:217)
     at com.ibm.rmi.io.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:144)
     at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1590)
     at com.ibm.rmi.iiop.CDROutputStream.write_value(CDROutputStream.java:1107)
     at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie.findCorrectionAction(_EJSRemoteStatelessValidation_da16513c_Tie.java:309)
     at
com.paresh.core.interfaces._EJSRemoteStatelessValidation_da16513c_Tie._invoke(_EJSRemoteStatelessValidation_da16513c_Tie.java:104)
     at
com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:582)
     at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:437)
     at com.ibm.rmi.iiop.ORB.process(ORB.java:320)
     at com.ibm.CORBA.iiop.ORB.process(ORB.java:1544)
     at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2063)
     at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
     at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
kodo.properties
com.solarmetric.kodo.LicenseKey=
#com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=java:/TransactionManager
>>
>
com.solarmetric.kodo.ee.ManagedRuntimeProperties=TransactionManagerName=TransactionFactory
>>
>
TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager
>>
>>
>
#com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.InvocationManagedRuntime
>>
>
com.solarmetric.kodo.ee.ManagedRuntimeClass=com.solarmetric.kodo.ee.AutomaticManagedRuntime
>>
>>
>
#javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
>>
>
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory
>>
javax.jdo.option.ConnectionFactoryName=ds/kodo/DataSource1
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
#com.solarmetric.kodo.DataCacheClass=com.solarmetric.kodo.runtime.datacache.plugins.CacheImpl
>>
>>
# Changing these to a non-zero value will dramatically increase
# performance, but will cause in-memory databases such as Hypersonic
# SQL to never exit when your main() method exits, as the pooled
# connections in the in-memory database will cause a daemon thread to
# remain running.
javax.jdo.option.MinPool=5
javax.jdo.option.MaxPool=10
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

ReportClientDocument throws - Unexpected database connector error

Hi,
We are getting a weird exception in Websphere 6.1 server when we try to open a crystal report using ReportClientDocument object. It is throwing an unexpected database connector error when we try to change the datasource of the report. It would be great if some one can help us with the solution.
Code:
ReportClientDocument reportClientDocument = new ReportClientDocument();
reportClientDocument.open(REPORT_NAME, 0);
Tables tables = reportClientDocument.getDatabaseController().getDatabase().getTables();
ITable table = tables.getTable(0);
reportClientDocument.getDatabaseController().setDataSource(resultSet0, tableName0 , tableName0+"_ResultSet");
P.S: The same code works fine in Tomcat 6.0 server.
Exception:
[1/11/11 17:34:10:141 GMT+05:30] 00000037 SystemOut     O Connection logon successfully
[1/11/11 17:34:10:145 GMT+05:30] 00000037 SystemOut     O Rowset restart: moveToStart true
[1/11/11 17:34:10:145 GMT+05:30] 00000037 SystemOut     O Rowset execute
[1/11/11 17:34:10:168 GMT+05:30] 00000037 SystemOut     O detected an exception: Unexpected database connector error
     at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2409)
     at com.crystaldecisions.reports.datafoundation.DataFoundation.a(SourceFile:1234)
     at com.crystaldecisions.reports.dataengine.dfadapter.DFAdapter.a(SourceFile:344)
     at com.crystaldecisions.reports.dataengine.dfadapter.CheckDatabaseHelper.a(SourceFile:66)
     at com.crystaldecisions.reports.dataengine.datafoundation.CheckDatabaseCommand.new(SourceFile:100)
     at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
     at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
     at com.crystaldecisions.reports.dataengine.VerifyDatabaseCommand.new(SourceFile:76)
     at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
     at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
     at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
     at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.a(SourceFile:373)
     at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.if(SourceFile:352)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1291)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)
     at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)
     at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)
     at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
     at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
     at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
     at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
     at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
     at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.if(SourceFile:605)
     at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.a(SourceFile:1688)
     at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.new(SourceFile:2650)
     at com.crystaldecisions.sdk.occa.report.application.b9.onDataSourceChanged(SourceFile:301)
     at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:962)
     at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:2834)
     at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setDataSource(SourceFile:2557)
     at com.crystaldecisions.reports.sdk.DatabaseController.setDataSource(SourceFile:87)

It appears that you are trying to pass a resultset to the report, only things i can think of is, either the jar file needed for that type of connection is missing, or maybe the app servers are using different versions of java which causes it to act differently.

Compare creation of Datasources and JMS Queues : SAP vs (Weblogic/Websphere

I am used to creating JDBC Datasources and JMS Queues on Weblogic/Websphere thru their Admin applications.
Can someone compare/contrast that process to that on SAP's netweaver ( either using NWA or Visual Administrator).
Thanks

Hi Parag,
For the process of creating JDBC datasources and JMS resources @ SAP NetWeaver you can refer to the documents here on SDN and help.sap.com, and compare that process for yourself, thus not being influenced by others' biased or unbiased opinions.
For NetWeaver 04 and 04s these would be:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm">JDBC Connector Service</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/cf4e71c46cdb4da31153be96c5389f/frameset.htm">JMS Connector Service</a>
For the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/javaee5">Java EE 5 Edition</a>:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7bb9751d-0e01-0010-febd-c3adce2c408c">Working with Database Tables, DataSources and JMS Resources</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/806e75a0-0e01-0010-2587-fc518de8ac1a">Administration Guide</a> -> section "Application Resources Management" (pages 89-104)
Hope that helps!
Your feedback/findings are very welcome!
-Vladimir

Steps listen to an Oracle AQ queue in IBM Websphere Application Server 7.0

I need to listen to an Oracle AQ queue in a Java EE application that runs under Websphere app server @7.0.
I'd really like to use a MDB to access the Messages in AQ
I can't really find any documentation on this, and I can't find a resource adapter that lets me do this using JCA.
Can anyone tell me what's required to get this to work?
I was able to find the
product\11.2.0\oc4j\j2ee\home\connectors\ojms.rar
but how to configure the same inside WAS

Hi ,
I have attempted to deploy an ADF 11g JSF application into WAS 7 and I am finding that an NPE is being thrown when the Trinidad (1.2.9) ResourceServlet is trying to load various artefacts on a page request.
[28/05/09 12:46:34:568 EST] 00000019 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet resources in application ic-web. Exception created : java.lang.NullPointerException
     at com.ibm.ws.webcontainer.srt.SRTServletResponse.setContentType(SRTServletResponse.java:1191)
     at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:140)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet._setHeaders(ResourceServlet.java:445)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet.doGet(ResourceServlet.java:207)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:726)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.myfaces.trinidad.webapp.ResourceServlet.service(ResourceServlet.java:162)
Does anyone have any thoughts about what might be causing this?
This application deploys fine into WLS 10g.
Thanks and regards,
Andrew
Edited by: user11207057 on 27-May-2009 21:12

Getting error while configuring WebSphere application server in JDeveloper

Hi all,
I have installed Oracle Jdeveloper 11g(11.1.1.5.1) and WebSphere application server 7
I am trying to create New Application server as "WebSphere" and entered following information.
Host Name : wkstn90
SOAP Connector port: 8880
Server Name: server1
Target Node: wkstn90Node01
TargetCell: wkstn90Node01Cell
wsadmin script file location: C:\Program Files\IBM\WebSphere\AppServer\bin\wsadmin.bat
So once click on test connection it will comes up with following error,
Testing WsAdmin ... failed.
Could not connect to SOAP port 8880 using script C:\Program Files\IBM\WebSphere\AppServer\bin\wsadmin.bat.
Testing DeploymentConfig ... failed.
Cell wkstn90Node01Cell was not found on the WebSphere server.
Please help me how to resolve this issue. Any extra configuration am i need to carry out in WebSphere server.
Please let me know. Waiting for positive response.
By,
sk

Hi,
Use the Deployment Manager Soap port not the Application Server port
Maddy

Problem with Send using JMS Adapter with Websphere MQ

Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith Dharmasiri

Checked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work?

Kodo Connector in WebSphere 4.0.2

Similar Messages

Maybe you are looking for