[jboss-user] [JBoss Messaging] - restart of jboss messaging server from JMX console
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 to restart jboss server on production because some web applications must run. we need to restart only jboss messaging which is deployed on the same jboss instance. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4121270#4121270 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121270 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM doesn't recover after database restart
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=bbop=viewtopicp=4093288#4093288 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093288 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: strange failover behaviour in clustered config
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 : http://www.jboss.com/index.html?module=bbop=viewtopicp=4063455#4063455 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063455 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - strange failover behaviour in clustered config
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 additionally following changes on both nodes: 1. replaced hsqldb-persistence-service.xml by clustered-oracle-persistence-service.xml 2. added clustered queue in destination-service.xml: mbean code=org.jboss.jms.server.destination.QueueService name=jboss.messaging.destination:service=Queue,name=mytestqueue xmbean-dd=xmdesc/Queue-xmbean.xml depends optional-attribute-name=ServerPeerjboss.messaging:service=ServerPeer jboss.messaging:service=PostOffice true 3. changed messagepullpolicy and clusterrouterfactory: org.jboss.messaging.core.plugin.postoffice.cluster.DefaultMessagePullPolicy org.jboss.messaging.core.plugin.postoffice.cluster.RoundRobinRouterFactory 4. added attributes for ConnectiontFactory and XAConnectionFactory in connection-factories-service.xml true true In messaging-service.xml in one node put server peer id to 1 and on another node to 2. I started both nodes. Pushed about 1000 JMS messages to the queue. Deployed MDB which is listening on this queue and doing some staff with JMS messages. So far so good. Messages good spreaded across nodes. After some time I killed one node (will name it from now as node A). I saw that messages are now was correctly overtaken by remaining node (node B). And now I killed node B too. SO no nodes are running. Then I started node A and it was no messages arriving to my MDB. I checked database and saw that messages were still there in JBM_MSG table. Then I started node B and messages started to arrive to both node A and node B again. How to avoid situation that existing messages are not delivered to the MDB ? Is it by design ? or bug ? Thanks in advance, Ramil View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4063013#4063013 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063013 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: strange failover behaviour in clustered config
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 node A to be able process remaining message? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4063029#4063029 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4063029 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: exception during destroy of stateful bean then @Security
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[jboss.web]]: is expiring session and calling seamListener.sessionDestroyed(). which is trying to destroy bean which is protected by @SecurityDomain annotation. SecurityInterceptor tries to find principal - doesn't find it and do login() with null credentials (because this thread doesn't have associated credentials). And exception occurs. See debug logging below: 2007-01-26 11:23:43,493 639138 DEBUG [org.apache.catalina.session.ManagerBase] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Start expire sessions StandardManager at 1169807023493 sessioncount 1 2007-01-26 11:23:43,494 639139 DEBUG [org.jboss.seam.contexts.Lifecycle] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) End of session, destroying contexts 2007-01-26 11:23:43,494 639139 DEBUG [org.jboss.seam.contexts.Lifecycle] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) destroying conversation contexts: [] 2007-01-26 11:23:43,494 639139 DEBUG [org.jboss.seam.contexts.Lifecycle] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) destroying session context 2007-01-26 11:23:43,494 639139 DEBUG [org.jboss.seam.core.Events] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Processing event:org.jboss.seam.preDestroyContext.SESSION 2007-01-26 11:23:43,494 639139 DEBUG [org.jboss.seam.contexts.Contexts] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) destroying: locale 2007-01-26 11:23:43,500 639145 DEBUG [org.jboss.seam.contexts.Contexts] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) destroying: studioErrorTracking 2007-01-26 11:23:43,500 639145 DEBUG [org.jboss.seam.core.Events] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Processing event:org.jboss.seam.preDestroy.studioErrorTracking 2007-01-26 11:23:43,500 639145 DEBUG [org.jboss.seam.core.Events] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.outermostExceptionInterceptor 2007-01-26 11:23:43,500 639145 DEBUG [org.jboss.seam.core.Events] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.outermostExceptionInterceptor 2007-01-26 11:23:43,514 639159 WARN [be.certipost.am.utils.loginmodule.AMBasedLoginModule] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Password was null and has been set to empty String!!! 2007-01-26 11:23:43,542 639187 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) loadClass(org.apache.log4j.Level, false) 2007-01-26 11:23:43,542 639187 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Searching local repositories 2007-01-26 11:23:43,542 639187 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) findClass(org.apache.log4j.Level) 2007-01-26 11:23:43,543 639188 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Delegating to parent classloader at end: [EMAIL PROTECTED] 2007-01-26 11:23:43,543 639188 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Loading class from parent 2007-01-26 11:23:43,548 639193 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) loadClass(org.apache.log4j.Logger, false) 2007-01-26 11:23:43,548 639193 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Searching local repositories 2007-01-26 11:23:43,548 639193 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) findClass(org.apache.log4j.Logger) 2007-01-26 11:23:43,548 639193 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Delegating to parent classloader at end: [EMAIL PROTECTED] 2007-01-26 11:23:43,548 639193 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) Loading class from parent 2007-01-26 11:23:43,553 639198 DEBUG [org.apache.catalina.loader.WebappClassLoader] (node1) (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) loadClass(org.apache.log4j.Category, false) 2007-01-26 11:23:43,554 639199 DEBUG
[jboss-user] [Security JAAS/JBoss] - Re: TimedCachedPolicy never removes entries from cache
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 time.
But expired objects can be removed at this time.
public void run() {
super.run();
synchronized (entryMap) {
Iterator iter = entryMap.entrySet().iterator();
List removeentries = new ArrayList();
while (iter.hasNext()) {
Map.Entry entry = (Map.Entry) iter.next();
TimedEntry value = (TimedEntry)
entry.getValue();
if (value.isCurrent(now) == false) {
if(log.isDebugEnabled()){
log.debug(destroying
object:+value);
}
value.destroy();
removeentries.add(entry.getKey());
}
}
for (Object object : removeentries) {
if(log.isDebugEnabled()){
log.debug(removing object from
Map:+object);
}
entryMap.remove(object);
}
}
}
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001715#4001715
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001715
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: exception during destroy of stateful bean then @Security
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 post : http://www.jboss.com/index.html?module=bbop=viewtopicp=325#325 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=325 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - exception during destroy of stateful bean then @SecurityDoma
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 Serializable, StudioAuditTracking It works perfect, but during destroy there is an error. And log files full of such errors. I tried to set idleTimeoutSeconds to the same value like in web session timeout following WIKI, but still the same issue. It seems that security principal is not propagated during destroy. 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) javax.ejb.EJBAccessException: Authentication failure 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.handleGeneralSecurityException(Ejb3AuthenticationInterceptor.java:68) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:71) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:188) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at $Proxy290.stop(Unknown Source) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at java.lang.reflect.Method.invoke(Method.java:585) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.util.Reflections.invoke(Reflections.java:13) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:32) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.contexts.Contexts.callDestroyMethod(Contexts.java:211) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:189) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.contexts.Lifecycle.endSession(Lifecycle.java:195) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.jboss.seam.servlet.SeamListener.sessionDestroyed(SeamListener.java:45) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:687) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:579) 2007-01-03 15:00:31,790 ERROR [STDERR] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]:) at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:678)
[jboss-user] [EJB 3.0] - Re: 4.0.5.GA EJB3.0RC9 Message Bean Issue
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: ArrayList list = ProxyFactoryHelper.getBusinessInterfaces(clazz); if (list.size() 1 || list.size() == 0) throw new RuntimeException(unable to determine messagingType interface for MDB); messagingType = list.get(0); As you see it gets all implemented interfaces of your class (and don't get interfaces of parent class probably) and if it is empty (as in your case) or if it is more than one interface on class (as in my case, because I have another interface on my class) exception is thrown. I will create issue in jira. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3982004#3982004 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3982004 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: 4.0.5.GA EJB3.0RC9 Message Bean Issue
http://jira.jboss.com/jira/browse/EJBTHREE-768 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3982011#3982011 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3982011 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: JBossWS 1.0.1GA JSR181 and WS-Security
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=bbop=viewtopicp=3958383#3958383 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3958383 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: JBossWS 1.0.1GA JSR181 and WS-Security
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/ServerHandlers.xml file: | ?xml version=1.0 encoding=UTF-8? | | handler-config |handler-chain | handler-chain-nameSecureHandlerChain/handler-chain-name | handler | handler-nameWSSecurityHandlerInbound/handler-name | handler-classorg.jboss.ws.wsse.WSSecurityHandlerInbound/handler-class | /handler |/handler-chain | /handler-config And now if I try to access it from webservices client without wsse:security I get : This service requires wsse:Security, which is missing. So it is fixed ! Thanks. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3958012#3958012 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3958012 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: JBossWS 1.0.1GA JSR181 and WS-Security
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=bbop=viewtopicp=3957271#3957271 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3957271 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
