Hi community,

as you can see in my first post there are very much byte and char arrays. 
I went into the detail and determined that most of the objects were instantiated in 
JSSE classes. 
Indeed we use encrypted communication between our web start swing clients and our 
jboss server:

using ssl:

  | <invoker-proxy-bindings>
  |                 <!-- Aufruf der Stateless SessionBeans per SSL -->
  |                 <invoker-proxy-binding>
  |                         <name>stateless-rmi-invoker</name>
  |                         
<invoker-mbean>jboss:service=invoker,type=jrmp,socketType=SSL</invoker-mbean>
  |                         
<proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
  |                         <proxy-factory-config>
  |                                 <client-interceptors>
  |                                         <home>
  |                                                 
<interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                                         </home>
  |                                         <bean>
  |                                                 
<interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                                         </bean>
  |                                 </client-interceptors>
  |                         </proxy-factory-config>
  |                 </invoker-proxy-binding>
  |                 <!-- Aufruf der Stateful SessionBeans per SSL -->
  |                 <invoker-proxy-binding>
  |                         <name>stateful-rmi-invoker</name>
  |                         
<invoker-mbean>jboss:service=invoker,type=jrmp,socketType=SSL</invoker-mbean>
  |                         
<proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
  |                         <proxy-factory-config>
  |                                 <client-interceptors>
  |                                         <home>
  |                                                 
<interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                                         </home>
  |                                         <bean>
  |                                                 
<interceptor>org.jboss.proxy.ejb.StatefulSessionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
  |                                                 
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                                         </bean>
  |                                 </client-interceptors>
  |                         </proxy-factory-config>
  |                 </invoker-proxy-binding>
  |         </invoker-proxy-bindings>
  | 

Allocation points of objects that weren't garbage collected (app was stress tested 
about 1/2 hour):

  | (number of allocations) (allocation place)
  | 5367 No trace available   null   
  | 2340 SunJSSE_au.<init>(byte[])      
  | 1404 SunJSSE_at.<init>(SunJSSE_ar)      
  | 1018 Unsafe.defineClass(String, byte[], int, int, ClassLoader, ProtectionDomain)   
Unsafe.java   
  |  936 Object.clone()   Object.java   
  |  539 JDBCEntityBridge$EntityState.<init>(JDBCEntityBridge)   
JDBCEntityBridge.java: 1104   
  |  468 SunJSSE_ax.b(byte[])      
  |  270 ClassLoader.defineClass0(String, byte[], int, int, ProtectionDomain)   
ClassLoader.java   
  |  238 SocketOutputStream.<init>(PlainSocketImpl)   SocketOutputStream.java: 31   
  |  235 AppInputStream.<init>(SSLSocketImpl)      
  |  235 InputRecord.<init>()      
  |  235 AppOutputStream.<init>(SSLSocketImpl)      
  |  235 ByteArrayOutputStream.<init>(int)   ByteArrayOutputStream.java: 59   
  |  234 MD5.init()   MD5.java: 206   
  |  234 MD5.init()   MD5.java: 207   
  |   28 SunJSSE_a2.<init>(SecureRandom)      
  | ...
  | 

After deactivating the encryption the big memory leak seems to be away: the jboss runs 
and runs and runs.

Does anyone know if this is a JSSE leak in the classes of sun? Or is it a jboss leak?

We cannot run our application without encryption so the problem isn't really solved 
yet.



View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833820#3833820

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833820


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to