3 Replies Latest reply on Feb 17, 2005 11:57 AM by ajordens

    "The backend currently does not support this feature." when

    ajordens

      I've just done a first pass at migrating an existing application from 3.2.7 to 4.0.1.

      Has anyone ran in to the "The backend currently does not support this feature." when running 4.0.1 against PostgreSQL 7.4.X.

      I haven't made any changes to the jar file beyond re-compiling, is there some place someone can point me. I'll continue to search through the forums, a google search didn't reveal much other than a bug report with the same problem.

      Exception trace has been included below, any questions? Thanks in advance.

      16:37:15,794 INFO [STDOUT] javax.ejb.FinderException: Find failed: org.postgresql.util.PSQLException: The backend currently does not support this feature.
      16:37:15,795 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:223)
      16:37:15,795 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128)
      16:37:15,795 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:47)
      16:37:15,795 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:589)
      16:37:15,811 INFO [STDOUT] at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:300)
      16:37:15,811 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:298)
      16:37:15,811 INFO [STDOUT] at org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1086)
      16:37:15,811 INFO [STDOUT] at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:663)
      16:37:15,811 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      16:37:15,811 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      16:37:15,811 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      16:37:15,811 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324)
      16:37:15,812 INFO [STDOUT] at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
      16:37:15,812 INFO [STDOUT] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113)
      16:37:15,812 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
      16:37:15,840 INFO [STDOUT] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:192)
      16:37:15,840 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:212)
      16:37:15,840 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
      16:37:15,840 INFO [STDOUT] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:117)
      16:37:15,840 INFO [STDOUT] at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61)
      16:37:15,840 INFO [STDOUT] at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28)
      16:37:15,841 INFO [STDOUT] at org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41)
      16:37:15,841 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109)
      16:37:15,841 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:313)
      16:37:15,841 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:126)
      16:37:15,869 INFO [STDOUT] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:101)
      16:37:15,869 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121)
      16:37:15,869 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
      16:37:15,870 INFO [STDOUT] at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:508)
      16:37:15,870 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java:891)
      16:37:15,870 INFO [STDOUT] at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:342)
      16:37:15,870 INFO [STDOUT] at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:118)
      16:37:15,870 INFO [STDOUT] at $Proxy217.findByUsername(Unknown Source)
      


        • 1. Re:
          willy.ong

          I encountered the same problem, submitted it as a bug

          http://jira.jboss.com/jira/browse/JBAS-1383?page=all

          • 2. Re:
            ajordens

            Where you able to get around it?

            Everytime I deploy I seem to get the same error. I'm going to try it against oracle tommorow and see if I get the same error.

            • 3. Re:
              ajordens

              My fix for this, which appears to work for the few tests I've run.

              is to upgrade to the 8.0 jdbc driver.

              and

              append ?protocolVersion=2 to the jdbc url in your datasource configuration.


              You may not have to do the latter but it threw some exceptions for me b/c the db column was boolean and the application was treating it as a character. I'll worry about that later, for now it appears to be working.