[Messaging, JMS & JBossMQ] - jms client behind fireall cannot detect dropped jboss connec
by yangju
I am using jboss 4.2 and jbossmq. The jms client is behind a firewall (Sonic ESB container). The client listens to the destinations (queue or topic) on jboss server. Everything seems working fine except that when jboss is stopped, the client cannot detect this. When the jboss is restarted, the jms listener cannot pick up message anymore.
On the client, I have a separate thread running all the time to verify the host connection by calling ConnectionFactory factory = (ConnectionFactory) lookup("ConnectionFactory"); The lookup is based on InitialContext which is obtained based on remote jboss server. I expected that if the jboss server is down, factory that is returned should be null, but it is not null. Looks as if the client cache the connection factory? As a result, I cannot detect whether jboss is down or not.
I am forced to periodically closeReceiver and recreatReceiver, which should be unnecessary.
My firewall ports seems opened properly. I am using uil2-service.
I don't have this issue if my client is not behind a firewall (even it is on a different machine from the jboss server). Looks like the fact that the client is behind a firewall causes this problem.
Is there better way to check jboss connection to see if it is alive and if it is different from before?
Please help.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109589#4109589
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109589
18 years, 4 months
[JBoss Seam] - observing database updates
by robshep
I'd like to observe the changes being made to persisted entities.
I'm currently using an EntityHome instance for entity management and have something like this.
| @Override
| public String update()
| {
| MyObj old = (MyObj)this.getEntityManager().find(MyObj.class, this.getInstance().getId());
| MyObj incoming = this.getInstance();
| System.out.println("OLD: " + old.getDescription() + ", NEW: " + incoming.getDescription() );
| return super.update();
| }
|
I've seen however, that even though the entity instance isn't persisted through to the underlying DB yet, the entitymanager is being clever and finding the instance coming in from the JSF components.
To enable me to see the differences between the a) the data actually in the DB and b) the data currently known to the entitymanager.....
I think I need to get hold of a new fresh entitymanager instance, one which doesn't have a cache of anything related.
Please could somebody explain how I may get such an instance. OR, if you have any better places in mind for where I can observe this data flow.
many thanks and kindest regards
Rob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109586#4109586
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109586
18 years, 4 months
[JBoss Seam] - Seam and performance..
by minamti
After reading the paper by Dave Jaffe and Michael Yuan on Seam performance, I was wondering if the authors had more data on number of concurrent users.
For example, if you had 25,000 concurrent users, what would be the performance figures. (I am assuming 25,000 concurrent testing threads would mean about 150,000 -200,000 real users... which would be traffic on a normal consumer site.. Does anybody has concurrent user figures on popular consumer web sites?)
Also the graphs show response times > 1 sec. What is the upper bound of the response times in the graphs. For example, during stress testing 30 percent of the response times are > 1 sec. How much more than 1 sec. are the response times.
Thanks,
M
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109578#4109578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109578
18 years, 4 months