1 Reply Latest reply on Oct 11, 2001 2:57 PM by rkilgore

    java.lang.UnsupportedOperationException

    rkilgore

      I get this exception constantly on my log file, and
      sometimes when I try to deploy a new version of my
      jar file, the cpu usage goes up to 100%, these things
      come flying into the log file, and I have to kill
      JBoss forceably.

      Most of what I see on the net indicates this exception
      is related to accessing a database. So I've included
      my db2 config section in jboss.jcml (JBoss 2.2.2 btw)
      along with an example of the stack trace.

      Does anyone know what to do about this?

      java.lang.UnsupportedOperationException
      at org.jboss.proxy.ProxyProxy.getHandle(ProxyProxy.java:104)
      at org.jboss.ejb.plugins.SessionObjectOutputStream.replaceObject(SessionObjectOutputStream.java:
      70)
      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:323)
      at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
      at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
      at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
      at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionF
      ilePersistenceManager.java:278)
      at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.jav
      a:54)
      at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:668)
      at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:199)
      at java.lang.Thread.run(Thread.java:484)

      And here is my data source config:


      org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl
      Db2DB
      jdbc:db2:aasdbdev
      xxxxxxxx
      yyyyyyyy
      60
      AutoCommit=true
      <!-- true
      true
      300000 -->




        • 1. Re: java.lang.UnsupportedOperationException
          rkilgore

          Anyone heard of this?

          Anyone been using jboss a while and never heard of
          this?

          Someone throw me a bone.

          I just figured out that it only happens when I use
          jre 1.2 clients and include the setting

          java.vm.version=1.2

          in my jboss.properties file. I wish I didn't have to
          do so, but most of the developers at my company develop
          in vaj 3.5.3 (_v_ery _a_ggrivating _j_oke :).