Hi,
Is it possible to restart jboss messaging server using jmx-console ?
Some times (due to some db errors) jboss messaging server doesn't take up JMS
messages from db.
Is there a way to reget messages from database ?
or could we restart jboss messaging service using JMX-console ?
we don't want t
After changing to Messaging 1.4.0.GA there is no problem. After database
reconnection old JMS messages are correctly taken
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093288#4093288
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&
but as on all nodes routerpolicy configured properly (using roundrobin)
then it should not be a problem if all messages are overtaken by first started
node.
Then other nodes will come up JMS messages will be spreaded again correctly to
other nodes. Or I'm not correct ?
View the original post :
Thanks for explanation.
Just some real case for clearance.
Imagine node A is crashed completely (disk failure). It means that I will not
be able to start it.
Do I understand correctly that I have to install jboss messaging server on new
machine and assign the same serverpeer id as it was on nod
Hi,
I'm testing failover situations with JBOSS Messaging server 1.3GA running on
jboss4.2.1GA (got it from branch as it is not yet released, but almost ready
for release) on two node cluster.
I installed clustered jboss messaging server 1.3.0GA using release-admin.xml
build script. And did addi
after putting logging on debug level found the cause of an issue.
Problem is that in tomcat separate thread is running to destroy expired
sessions. But logon credentials are associated with another thread - which is
served a connection from browser.
So ContainerBackgroundProcessor[StandardEngine[
Still have exactly the same issue in jboss4.0.4GA (probably JBOSS4.0.5.GA as
sources of this part are not changed).
We also have thousands of users.
For a moment only possible solution is to extend TimedCachePolicy class and
reiplement run() method. Currently this method only changes current tim
yes,
It happens exactly during web timeout.
Our web session timeout is 30 minutes (defined in web.xml)
and I also set default timeout for stateless beans to 1800 secs (30 minutes)
I also set the defaultCacheTimeout for JAAS (in jboss-service.xml) to more that
30 minutes -7200
View the original p
With seam 1.0 we have an issue dueing destroying of bean.
Stateful bean is defined as
@Stateful
@SerializedConcurrentAccess
@Scope(ScopeType.SESSION)
@Name("studioAuditTracking")
@Interceptors(SeamInterceptor.class)
@SecurityDomain("OurDomain")
public class StudioAuditTrackingBean implements Seria
http://jira.jboss.com/jira/browse/EJBTHREE-768
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982011#3982011
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982011
___
jboss-us
I have similar issue with my MDB. I also got such exception, but strange thing
that on my class I have implements javax.jmx.MessageListener.
After some debugging and looking in source code of EJB3 probably I found the
cause of problem. this exception is thrown from
org.jboss.ejb3.mdb.MDB.java:
did you do all steps ?
did you get latest version from SVN, build it and deployed it to your JBOSS
instance?
Did you add @HandlerChain annotation to your class?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958383#3958383
Reply to the post :
http://www.jbos
I downloaded latest version from SVN and build it.
Based on test case for JSR181EJB I modified my class file.
I added annotation on my EJB bean class:
@HandlerChain(file = "resource://config/ServerHandlers.xml", name =
"SecureHandlerChain")
during packaging of my JAR file I add config/ServerHandl
added JIRA issue: http://jira.jboss.com/jira/browse/JBWS-1071
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957318#3957318
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957318
_
have the same issue :(. And didn't find for a moment any clue how to do it.
Maybe we could open an JIRA issue with simple test case?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957271#3957271
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
15 matches
Mail list logo
