|
From: Colin S. <col...@ex...> - 2004-02-10 19:30:28
|
Just did a quick test of dropping in ojdbc14.jar into JBoss, where my=20
app is working ok with the 8i classes12.jar, and JBoss CMP is not happy=20
all of a sudden:
2004-02-10 13:53:28,595 DEBUG=20
[com.opensymphony.workflow.loader.XMLWorkflowFactory] getWorkflow build=20
descriptor=3Dcom.opensymphony.workflow.loader.WorkflowDescriptor@1626c6d
2004-02-10 13:53:28,611 ERROR [org.jboss.ejb.plugins.LogInterceptor]=20
TransactionRolledbackLocalException in method: public abstract=20
java.lang.Long=20
com.opensymphony.workflow.spi.ejb.CurrentStepLocal.getId(), causedBy:
java.lang.ArrayIndexOutOfBoundsException: -90
at oracle.sql.LnxLibThin.lnxnuc(LnxLibThin.java:5744)
at oracle.sql.NUMBER.toInt(NUMBER.java:412)
at=20
oracle.jdbc.dbaccess.DBConversion.NumberBytesToInt(DBConversion.java:2884=
)
at=20
oracle.jdbc.driver.OracleStatement.getIntValue(OracleStatement.java:4489)
at=20
oracle.jdbc.driver.OracleResultSetImpl.getInt(OracleResultSetImpl.java:53=
6)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil$24.readResult(JDBCUtil.java:876)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil$AbstractPrimitiveReader.get(JDBCU=
til.java:803)
at=20
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadArgu=
mentResults(JDBCAbstractCMPFieldBridge.java:424)
at=20
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadInst=
anceResults(JDBCAbstractCMPFieldBridge.java:373)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEnti=
tyCommand.java:188)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEnti=
tyCommand.java:72)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManag=
er.java:612)
at=20
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManag=
er.java:594)
at=20
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceMana=
ger.java:381)
at=20
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEnti=
ty(CachedConnectionInterceptor.java:352)
at=20
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynch=
ronizationInterceptor.java:239)
at=20
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(C=
achedConnectionInterceptor.java:185)
at=20
org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentrance=
Interceptor.java:114)
at=20
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInte=
rceptor.java:163)
at=20
org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.=
java:89)
at=20
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInte=
rceptor.java:54)
at=20
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxIntercep=
tor.java:84)
at=20
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorC=
MT.java:297)
at=20
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:128)
at=20
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java=
:118)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:19=
1)
at=20
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFi=
nderInterceptor.java:122)
at=20
org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:489)
at org.jboss.ejb.Container.invoke(Container.java:700)
at=20
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFa=
ctory.java:375)
at org.jboss.ejb.plugins.local.EntityProxy.invoke(EntityProxy.java:38=
)
at $Proxy126.getId(Unknown Source)
This is OsWorkflow EJB based code. All my Spring/Hibernate code is still=20
happy though.
So who knows who's at fault here? :-) All I know is I'm staying with=20
the 8i classes12 until we either move to Oracle 9i, or have no more=20
JBoss EJB dependencies....
tri...@tr... wrote:
>I did some more digging and I can get JDK 1.3 and a recent classes12.jar=
to work
>with 8i. Have not tried 9i today, but it should work too.
>
>The reason I said it did not work was that I tested the JDK 1.4 and 1.3 =
with
>different versions of WebLogic. I used WebLogic 6.1 for JDK 1.3 and eve=
n when I
>added the most recent oracle driver it blew up on
>"oracle.sql.BLOB.getField(DURATION_SESSION)". I started digging some mo=
re and
>it turns out that the weblogic.jar for 6.1 contains an outdated version =
of the
>oracle.sql.BLOB and oracle.sql.CLOB classes. By putting the latest
>classes12.jar first on the classpath everything works fine.
>
>If I have some time later, I will try 9i as well.
>
>Thomas
>
>
>Quoting Colin Sampaleanu <col...@ex...>:
>
> =20
>
>>I think Thomas is saying that classes12 didn't work with JDK 1.3 with=20
>>8i. It probably works with 9i... Thomas, please correct me if I am wron=
g.
>>
>>
>>j=FCrgen h=F6ller [werk3AT] wrote:
>>
>> =20
>>
>>>Thanks for testing, Thomas. It's a pity that this approach just works =
for
>>> =20
>>>
>>JDK 1.4; however, JDKs are easier to upgrade than databases. I've never=
tried
>>it on JDK 1.3, but I did try classes12 with JDK 1.4, and that did work =
(after
>>I've changed our code to read the Oracle constants via reflection; the
>>constant values differ between classes12 and ojdbc14!). I'm not sure wh=
y JDK
>>1.3 causes a problem here.
>> =20
>>
>>>I'm finally gonna release RC1 tonight, so there's still a couple of ho=
urs to
>>> =20
>>>
>>go if you find any issues :-)
>> =20
>>
>>>Juergen
>>>
>>>
>>>________________________________
>>>
>>>Von: spr...@li... im Auftrag =
von
>>> =20
>>>
>>tri...@tr...
>> =20
>>
>>>Gesendet: Di 10.02.2004 17:40
>>>An: spr...@li...
>>> =20
>>>
>
> =20
>
>>>Betreff: Re: [Springframework-developer] Ready for 1.0 RC1
>>>
>>>
>>>
>>>I tried the imagedb sample application for Oracle. It works using JDK=
1.4
>>> =20
>>>
>>and
>> =20
>>
>>>the odbcj14.jar jdbc driver for an 8i database. It does not work at a=
ll
>>> =20
>>>
>>using
>> =20
>>
>>>JDK 1.3 and classes12.zip/jar. This means that we are limited to JDK=
1.4
>>> =20
>>>
>>for
>> =20
>>
>>>this type functionality with Oracle for now.
>>>
>>>Just to clarify the Oracle drivers - there are no particular 8i or 9i =
jdbc
>>>drivers. They are just labeled based on which database version they a=
re
>>>distributed with. They should be backwards compatible, and if they ar=
e not
>>> =20
>>>
>>it
>> =20
>>
>>>is a bug. (There is even a patch for the driver that came with 8i to =
fix a
>>>problem connecting to a 9i database.) The only driver availale for JD=
K 1.4
>>> =20
>>>
>>is
>> =20
>>
>>>the ojdbc14.jar that comes with 9i. Haven't checked out the 10g drive=
rs
>>> =20
>>>
>>yet.
>> =20
>>
>>>I ran into a small problem with the html generated by the application.=
The
>>>browser did not pick up the end of the <textarea> for the description.=
I
>>> =20
>>>
>>added
>> =20
>>
>>>a separate closing tag and comitted it to cvs.
>>>
>>>Thomas
>>>=20
>>>
|