> the beans are persisting their state in an MS Access database using the
> sun.jdbc.odbc.JdbcOdbcDriver bridge.

Here's your problem. Do Not Ever use MS Access and/or the JDBC bridge with
transactional software such as EJB. Won't work. Sorry, nothing we can do
anything about.

/Rickard

> Now when I set the transaction property of the beans to REQUIRED
everything
> works fine,
> however when I set it to SUPPORTS it works well on every 2 of 3 client app
> executions. On every third execution I get the follwing dump on the client
> side:
>
> 5: no visa information there4
> 6: no visa information there5
> 7: no visa information there6
> 8: no visa information there7
>
> S:\jboss\jBoss20\proj\visa>runclient
> The obj ref is: AEJBHome
> Got a reference! Preparing to narrow...
> The obj ref is: BEJBHome
> Got a reference! Preparing to narrow...
> Caught an exception.
> javax.ejb.CreateException: Create failed(could not call
> ejbCreate):java.lang.ref
> lect.InvocationTargetException
>         at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknow
> n Source)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
>         at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>         at
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.invokeHom
> e(Unknown Source)
>         at
> org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invoke(HomeProxy.java
> :221)
>         at $Proxy1.create(Unknown Source)
>         at MyClient.main(VisaClient.java:30)
>
> on the server side the trace is:
>
> [Default] Tx is null
> [Default] invokeHome
> [MoreInfEJB] TX_SUPPORTS for create
> [MoreInfEJB] in ejbCreate
> [Default] javax.ejb.CreateException: Create failed(could not call
> ejbCreate):jav
> a.lang.reflect.InvocationTargetException
>         at
> org.jboss.ejb.plugins.BMPPersistenceManager.createEntity(BMPPersisten
> ceManager.java:113)
>         at
> org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:432)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at
> org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityC
> ontainer.java:590)
>         at
> org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(Ent
> itySynchronizationInterceptor.java:162)
>         at
> org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInst
> anceInterceptor.java:79)
>         at
> org.jboss.ejb.plugins.TxInterceptor.invokeNext(TxInterceptor.java:130
> )
>         at
> org.jboss.ejb.plugins.TxInterceptor.runWithTransactions(TxInterceptor
> .java:271)
>         at
> org.jboss.ejb.plugins.TxInterceptor.invokeHome(TxInterceptor.java:83)
>
>         at
> org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityIntercep
> tor.java:122)
>         at
> org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:1
> 03)
>         at
> org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:310)
>         at
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRM
> PContainerInvoker.java:194)
>         at
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRM
> PContainerInvoker.java:148)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
>         at sun.rmi.transport.Transport$1.run(Unknown Source)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Unknown Source)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
Source)
>         at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
> Sour
> ce)
>         at java.lang.Thread.run(Unknown Source)
>
> Please let me know what are the recommended transaction settings for the
> container managed transactions (except REQUIRED which seems to be working
> without any problem but is slow)
> when I want to avoid the transaction overhead.
>
> One more question - is there a way to set the verbosity level of the
server?
>
> Regards,
> Kamen.
> ----- Original Message -----
> From: "Aaron Mulder" <[EMAIL PROTECTED]>
> To: "jBoss" <[EMAIL PROTECTED]>
> Sent: Monday, September 25, 2000 5:26 PM
> Subject: Re: [jBoss-User] EJB-ref problem
>
>
> > No, as you saw, it causes protocol errors in some of the
> > underlying libraries.  We would like to work around this, but there is
not
> > a short-term solution.
> >
> > Aaron
> >
> > On Mon, 25 Sep 2000, Kamen wrote:
> > > Hi Aaron,
> > > is there a setting somewhere in the configuration files that I could
> modify
> > > so that I could keep jboss installed in the 'Program Files' folder.
> > > Regards,
> > > Kamen
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
>



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to