July 2009 - jboss-user - Jboss List Archives

[Installation, Configuration & DEPLOYMENT] - Re: Hide the http://localhost:8080 From the world

by PeterJ

To completely remove it, remove the server/xxx/deploy/ROOT.war directory. To secure it, add security settings to the ROOT.ware/WEB-INF/web.xml file. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244393#4244393 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244393

17 years

1
0
0 / 0

[Remoting] - Re: javax.jms.JMSException: Failure on underlying remoting c

by KrisFra

Yes, when exception listener callback occurs, the exception being reported is essentially the subject (title) of this post, that is, javax.jms.JMSException: Failure on underlying remoting connection. So, I concluded that I have a remoting problem ... made sense to me. I do have somewhat of an update. Further investigation into the spurious exceptions related to the underlying remoting connection ultimately led me to the topic Unexplained ConnectionValidator Timeout (see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151168 for details). After reading the description and noting that the topic poster was using Red Hat (RH) JBoss EAP 4.3.0.GA_CP03, I did the obvious â¦ I updated from RH JBoss EAP 4.3.0.GA_CP02 to 4.3.0.GA_CP04 (latest/greatest non-alpha install). Then, I re-ran my test. The test ran overnight with over 150K message transfers to the JMS queue and over 150K from JMS queue without any random exceptions "heard" on the client connections. The spurious exceptions appeared to have completely disappeared! Unfortunately, I ran my test again several days later, executed roughly the same number of message transfers, but observed one failure. So, it appears the problem may still be there, but has been greatly reduced. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244392#4244392 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244392

17 years

1
0
0 / 0

[Clustering/JBoss] - JBoss 4.2.3 Quartz CronTrigger resume on failover

by lensaenz

We have a JBoss 4.2.3 cluster successfully set up and failing over properly, except for one thing: Quartz Cron Triggers don't resume on the node we fail over to. We have to manually resume the Job through through our SLSB to get it going again. We upgraded to Quartz 1.6.5 and Quartz is running as a JBoss service. We have set the RequestsRecovery flag to true on the Quartz Job. In the Quartz database, the QRTZ_PAUSED_TRIGGER_GRPS is empty when we failover which surprised us because resuming the Job manually works. As a possible workaround, is there any way to detect when a failover has happened so that we can programatically resume the Quartz Job? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244391#4244391 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244391

17 years

1
0
0 / 0

[JBoss Messaging] - JMB2 Beta3 and JBAS51 - Using jbm-jms.xml to define queues.

by simon_temple

I tried creating my own jbm-jms.xml file and dropped it in the deploy folder but it doesn't look like it's deployed. i.e. I can't see the queue or topic when looking at the JMX Console (I added the JMX work-around to see org.jboss.messaging) Is the jbm-jms.xml file only processed when in the messaging.sar folder or can I configure where the configuration file(s) live? Can I have multiple configuration files or do I need to maintain one master? When the queues used to be created via MBeans we made our services depend upon the queue MBeans ensuring that queues were created before the services started. How can we ensure this startup dependency with JBM2? TIA My jbm-jms.xml <configuration xmlns="urn:jboss:messaging" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="urn:jboss:messaging /schema/jbm-jms.xsd"> | | <queue name="MyQueue"> | <entry name="/queue/MyQueue"/> | </queue> | | <topic name="MyTopic"> | <entry name="/topic/MyTopic"/> | </topic> | | </configuration> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244390#4244390 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244390

17 years

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Hide the http://localhost:8080 From the world

by miracles

Hey All, I am running a jboss 5 server on unix system. I will like to know how I can stop from shown the jboss main page(Menu): http://llocalhost:8080. Can i make him be accessible only for me (one user) or even from specified IP ? Thank You View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244389#4244389 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244389

17 years

1
0
0 / 0

[Clustering/JBoss] - Re: Deprecated DistributedState in Cluster API for JBossAS 5

by bstansberry＠jboss.com

For info on custom usage of JBoss CacheSee Chapter 11, particularly section 11.2, in the Clustering Guide draft (available in PDF via [/url]https://www.jboss.org/community/wiki/JBossAS5ClusteringGuide). For general JBC usage information, see the JBoss Cache 3 documentation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244388#4244388 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244388

17 years

1
0
0 / 0

[JBoss Messaging] - Re:

by timfox

The resources and tx mgr need to sync too and it doesn't solve that View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244387#4244387 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244387

17 years

1
0
0 / 0

[JBoss Messaging] - Re:

by clebert.suconic＠jboss.com

If we had transactions done per batch, we would solve not only the messaging bottleneck, but also the database bottleneck. say... you could batch commits per 100 records. If 1 record failed you would eventually process the 100 records again what would give you a better throughput on both the database and messaging. You still guarantee transaction on each message. I' m almost sure this is what other companies are doing with SpecJ. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244386#4244386 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244386

17 years

1
0
0 / 0

[JBoss Messaging] - Re:

by timfox

Now not only are you doing that once you're doing that twice, so that will involve 2 JTA transactions. Each JTA transactions will involve a minimum of 3 syncs to the file system, so that's 6 syncs +2 more for the databases = probably around 8 syncs. So yes, it will be slow (and it's not because of JBM) ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244385#4244385 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244385

17 years

1
0
0 / 0

[JBoss Messaging] - Re: JBoss 5.1.0GA with JBM2.0.0. b3

by simon_temple

I performed the workaround for BETA3 and can see the org.jboss.messaging node in the JMX console. Why didn't you use the jboss.messaging name that already exists in JBAS5.1? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244384#4244384 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244384

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2009