jboss-dev-forums

[Jboss-dev-forums] [Design of the JBoss EJB Container] - Re: Connection Timeout into Pooled Invokers

[<cle...@jb...>]

oops... sorry... 

My text get inside the code... my bad:


This is happening just when all the load is being initialized. So it's kind of everybody starting at
 the same time.

So, I need to understand if a high initial load would cause this (as I only have one AcceptThread), 
or if a delay in the application (like query delays) would be causing this.


Any help is appreciated.


thanks,


Clebert Suconic	

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<ad...@jb...>]

Moved to the benchmarking forum, although this is not really a development issue.

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<ad...@jb...>]

anonymous wrote : 
  | java.net.SocketTimeoutException: Read timed out
  |         at java.net.SocketInputStream.socketRead0(Native Method)
  |         at java.net.SocketInputStream.read(SocketInputStream.java:129)
  |         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
  |         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
  |         at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
  |         at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2490)
  |         at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2500)
  |         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
  |         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
  |         at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:
  | 

Means the client was waiting for a response from the server, but got bored
waiting and closed the connection.

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<ad...@jb...>]

The default is 60 seconds and can be changed with

  | <attribute name="SocketTimeout">60000</attribute>
  | 

60 seconds looks like a stupid timeout when the default transaction timeout is 300 seconds (or five minutes).

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<ad...@jb...>]

Also, if you are using 4.0.x
make sure you enable interrupt threads on the transaction manager
to stop threads blocking inside crappy DBs that don't detect deadlocks or other
resource problems.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss4FAQ


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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<cle...@jb...>]

Thanks...

I wasn't sure if the accept thread would take any collateral affects when everybody is starting new threads. I know I could have profiled it myself but I needed a quick answer for now. Thanks for the help.

And just one thing about the timeout... I was using 4 minutes at my configuration. I've copied the wrong version. And I will increase it to 5 minutes.


Thanks a lot,

Clebert

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<cle...@jb...>]

Thanks for appointing me the threading blocking.

I was having other non related problems that can be related to this.

Thank you so much,


Clebert

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<cle...@jb...>]

Talking about transactions and Pooled invokers,

I'm also setting the ClientUserTransaction to use pooled invokers.

I have tested and I didn't find any problems until now. I'm just wondering if someone sees any issue on this option.

Here is the changed configuration:

  |    <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
  |       name="jboss:service=ClientUserTransaction"
  |       xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">
  |       <depends>
  |          <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
  |             name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">
  |             <attribute name="InvokerName">jboss:service=invoker,type=pooled</attribute> <!-- here -->
  |             <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
  |             <attribute name="JndiName">UserTransactionSessionFactory</attribute>
  |             <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute>
  |             <attribute name="ClientInterceptors">
  |                <interceptors>
  |                   <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
  |                   <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                </interceptors>
  |             </attribute>
  |             <depends>jboss:service=invoker,type=pooled</depends> <!-- here -->
  |          </mbean>
  |       </depends>
  |       <depends optional-attribute-name="TxProxyName">
  |          <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
  |             name="jboss:service=proxyFactory,target=ClientUserTransaction">
  |             <attribute name="InvokerName">jboss:service=invoker,type=pooled</attribute> <!-- here -->
  |             <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
  |             <attribute name="JndiName"></attribute>
  |             <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute>
  |             <attribute name="ClientInterceptors">
  |                <interceptors>
  |                   <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
  |                   <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  |                </interceptors>
  |             </attribute>
  |             <depends>jboss:service=invoker,type=pooled</depends> <!-- here -->
  |          </mbean>
  |       </depends>
  | 
  |    </mbean>
  | 



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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<ad...@jb...>]

Why would it cause any issue?

Pooled = TCP/IP
JRMP = RMI

The invoker is just mechanism to transport the begin()/commit() 
event to the server.

Now if you needed a feature that required a full RMI implementation (like remote classloading) then it would be an issue.

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

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

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: Connection Timeout into Pooled Invokers

[<cle...@jb...>]

I just wanted to make sure I'm taking the right decision and anyone (you :-) ) would see an issue on this options. (issue regarding performance for example)


Thanks again


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

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