[Clustering] - Re: IP binding, Multicast, and Mod_jk loadbalancing
by wrexcil
I am also having the same problem. The only difference being I am also changing the port via workers.properties:
#define 1 worker using ajp13 for q01-rpt-report01
worker.list=ajp13_q01-rpt-report01
#set properties for worker ajp13
worker.ajp13_d01-rpt-report01.port=7102
worker.ajp13_d01-rpt-report01.host=10.63.81.165
worker.ajp13_d01-rpt-report01.type=ajp13
worker.ajp13_d01-rpt-report01.local_worker=1
After I start tomcat I can see it listening on 7102 (and not 8009), but it still attempts to connect to 127.0.0.1:8009. No where in my configs is 8009 enabled... but it still tries it! Any ideas?
mod_jk log:
[Tue Sep 01 11:07:59 2009] [11456:42752] [debug] jk_open_socket::jk_connect.c (328): socket TCP_NODELAY set to On
[Tue Sep 01 11:07:59 2009] [11456:42752] [debug] jk_open_socket::jk_connect.c (426): trying to connect socket 15 to 127.0.0.1:8009
[Tue Sep 01 11:07:59 2009] [11456:42752] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252869#4252869
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252869
16 years, 7 months
[JBoss Messaging Users] - JBoss messaging performance.
by damian.sinczak
I have problem with JBoss Messaging performance. I have queue that is persistent and supports transactions. Whole operation looks like this:
1. In servlet I receive e.g. 1,5 GB of data
2. I parse this data (there are numbers there)
3. For every number in data I creating message and sending it on queue (there is some about 1 million of messages)
4. After everything is parsed and all messages are send I commit transaction (and from now messages are committed so they can be consumed by message driven beans)
Problem occurs when I'm putting messages on queue and later during commit (I have to have persistent and transactional messages). Everything is Ok when I put 500 000 and JBoss is not using whole RAM problem occurs when there is more messages and maximum amount of ram is taken. Is there any possibility to configure message producer (or anything else) so he doesn't gather messages in memory but save them in database (postgres 8.1). Of course I need it to be transactional so I can roll back send messages when I want to.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252852#4252852
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252852
16 years, 7 months
[EJB 3.0 Users] - Custom StrictMaxPool settings in ...-aop.xml ignored
by rbattenfeld
Hi
I have to limit the number of MDB running in parallel. Therefore, I created an own aop file called obe-aop.xml:
| <?xml version="1.0" encoding="UTF-8"?>
| <aop xmlns="urn:jboss:aop-beans:1.0">
|
| <domain name="OBE-Singleton-Stateless-Session-Bean" extends="Stateless Bean"
| inheritBindings="true">
| <annotation expr="!class((a)org.jboss.ejb3.annotation.Pool)">
| @org.jboss.ejb3.annotation.Pool (value="StrictMaxPool", maxSize=1, timeout=10000)
| </annotation>
| </domain>
|
| <domain name="OBE-Singleton-Message-Driven-Bean" extends="Message Driven Bean"
| inheritBindings="true">
| <annotation expr="!class((a)org.jboss.ejb3.annotation.Pool)">
| @org.jboss.ejb3.annotation.Pool (value="StrictMaxPool", maxSize=1, timeout=10000)
| </annotation>
|
| </domain>
| </aop>
|
The limitatiob works fine for stateless session beans but not for MDBs. The only way which works is the chenge the settings in the ejb3-interceptors-aop.xml file.
At the moment this is ok but I would prefer to be able to adjust it individually for each MDB.
Thanks a lot for any help
Ralf
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252849#4252849
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252849
16 years, 7 months