Hi Heiko,
 
Is this a bug with Oracle or with JBoss ? Does Oracle Client 9.2.0.4 work well with other App. Servers without making changes in the Data type mapping ?
 
regards,
Shubhu

"Rupp, Heiko" <[EMAIL PROTECTED]> wrote:
Hi,
 
there is a bug report open on this (#729719)

https://sourceforge.net/tracker/?func=detail&atid=376687&aid=729719&group_id=22866

Can you confirm/verify the solution from there?

  Heiko

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] im Auftrag von shubhu mutta
Gesendet: Mo 05.01.2004 09:35
An: [EMAIL PROTECTED]
Cc:
Betreff: [JBoss-user] JBoss 3.2.4 and Oracle9i: SQLException: Invalid conversion requested

Hi,

I updated my Oracle Client from 9.2.0.1 to 9.2.0.4. Jboss is 3.2.0.

After that I tried to execute my application and got this in

server.log:

javax.ejb.EJBException: Internal error setting parameters for field status; CausedByException is:

Invalid conversion requested

java.sql.SQLException: Invalid conversion requested

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)

at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java)

at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java)

at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:607)

at org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.setParameter(JDBCUtil.java:280)

at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.setArgumentParameters(JDBCAbstractCMPFieldBridge.java:301)

at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.setInstanceParameters(JDBCAbstractCMPFieldBridge.java:280)

at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand.insertEntity(JDBCCreateEntityCommand.java:285)

at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand.execute(JDBCCreateEntityCommand.java:182)

at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.createEntity(JDBCStoreManager.java:569)

at org.jboss.ejb.plugins.CMPPersistenceManager.createEntity(CMPPersistenceManager.java:225)

at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.createEntity(CachedConnectionInterceptor.java:270)

at org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:725)

at java.lang.reflect.Method.invoke(Native Method)

at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:998)

at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88)

at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:188)

at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:215)

at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88)

at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:91)

at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61)

at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28)

at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:88)

at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:243)

at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:74)

at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:92)

at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120)

at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)

at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:477)

at org.jboss.ejb.Container.invoke(Container.java:694)

at java.lang.reflect.Method.invoke(Native Method)

at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)

at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)

at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:88)

at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77)

at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)

at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:175)

at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:82)

at $Proxy194.create(Unknown Source)

at home.create(uow);

All worked fine before the Oracle update.

The exception is thrown when setting the value for a

EJB-Field of type Short.

The default typemapping for Oracle9i is choosen

(NUMERIC/NUMBER(5) ( specified in standarjaws.xml,standardjbosscmp-jdbc.xml).

Has anybody encountered this problem ?

Is it a bug with Oracle Client 9.2.0.4 ?

My datasource definition is like this

<datasources >

<local-tx-datasource>

<jndi-name>OracleDS</jndi-name>

<!--<connection-url>jdbc:oracle:thin:@(protected):1521:TEMP</connection-url>-->

<connection-url>jdbc:oracle:oci8:@bplin32</connection-url>

<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>

<user-name>xxx</user-name>

<password>xxx</password>

<min-pool-size>1</min-pool-size>

<max-pool-size>5</max-pool-size>

<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>

</local-tx-datasource>

</datasources>

 

Regards,

Shubhu


Do you Yahoo!?
Free Pop-Up Blocker - Get it now


Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes

Reply via email to