[jboss-user] [EJB/JBoss] - Re: EJB Passivation Time
Alright I figured out what is going on. Need to use the ejb3-aop-interceptors.xml file to configure ejb3 beans. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4126406#4126406 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4126406 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Beginners Corner] - Re: JBoss runs without standardjboss.xml
Alright I figured out what is going on. Need to use the ejb3-aop-interceptors.xml file to configure ejb3 beans. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4126407#4126407 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4126407 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - EJB Passivation Time
Hi, I've deployed an EJB (in a .ear file using EJB3 annotations) to my JBoss server, and for some reason, they always take 10 minutes of inactivity to passivate (and then I let the server run for another 12 hours and the bean was still not removed from the container completely). I'm running the default configuration and I've modified the JBoss standardjboss.xml file (in server\default\conf) that relates to the container configuration to look as follows: container-configuration | container-nameStandard Stateful SessionBean/container-name | call-loggingfalse/call-logging | invoker-proxy-binding-namestateful-unified-invoker/invoker-proxy-binding-name | container-interceptors | interceptororg.jboss.ejb.plugins.ProxyFactoryFinderInterceptor/interceptor | interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor | !-- CMT -- | interceptor transaction=Containerorg.jboss.ejb.plugins.TxInterceptorCMT/interceptor | interceptor transaction=Containerorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor | interceptor transaction=Containerorg.jboss.ejb.plugins.StatefulSessionInstanceInterceptor/interceptor | !-- BMT -- | interceptor transaction=Beanorg.jboss.ejb.plugins.StatefulSessionInstanceInterceptor/interceptor | interceptor transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor | interceptor transaction=Beanorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor | interceptororg.jboss.resource.connectionmanager.CachedConnectionInterceptor/interceptor | interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor | /container-interceptors | instance-cacheorg.jboss.ejb.plugins.StatefulSessionInstanceCache/instance-cache | persistence-managerorg.jboss.ejb.plugins.StatefulSessionFilePersistenceManager/persistence-manager | container-cache-conf | cache-policyorg.jboss.ejb.plugins.LRUStatefulContextCachePolicy/cache-policy | cache-policy-conf | min-capacity50/min-capacity | max-capacity100/max-capacity | remover-period30/remover-period | max-bean-life30/max-bean-life | overager-period30/overager-period | max-bean-age30/max-bean-age | resizer-period5/resizer-period | max-cache-miss-period5/max-cache-miss-period | min-cache-miss-period1/min-cache-miss-period | cache-load-factor0.75/cache-load-factor | /cache-policy-conf | /container-cache-conf | container-pool-conf | MaximumSize100/MaximumSize | /container-pool-conf | /container-configuration I would think the beans should now passivate within 30 seconds of inactivity. Can anyone explain why passivation still takes 10 minutes or why the beans are never removed from the container? Thanks. Also, I am using the default jboss configuration and just starting it with bin/run.bat script. Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4125859#4125859 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125859 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Beginners Corner] - JBoss runs without standardjboss.xml
Hi, I'm trying to learn more about what jboss configuration files do what, and everything I've read said that standardjboss.xml file controls a lot about the cache configurations. However I didn't think my jboss was actually reading it and to test that I removed it from the server/default/conf, and sure enough jboss ran just fine. Is this normal, or do I need to do something specific to get it to use that file? Thanks, Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4125988#4125988 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125988 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration DEPLOYMENT] - Passivation time configuration
Hi, I've deployed an EJB (in a .ear file using EJB3 annotations) to my JBoss server, and for some reason, they always take 10 minutes of inactivity to passivate (and then seem to be hours until they are removed from the container entirely). I'm running the default configuration and I've modified the JBoss standardjboss.xml file (in server\default\conf) that relates to the container configuration to look as follows: container-configuration | container-nameStandard Stateful SessionBean/container-name | call-loggingfalse/call-logging | invoker-proxy-binding-namestateful-unified-invoker/invoker-proxy-binding-name | container-interceptors | interceptororg.jboss.ejb.plugins.ProxyFactoryFinderInterceptor/interceptor | interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor | !-- CMT -- | interceptor transaction=Containerorg.jboss.ejb.plugins.TxInterceptorCMT/interceptor | interceptor transaction=Containerorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor | interceptor transaction=Containerorg.jboss.ejb.plugins.StatefulSessionInstanceInterceptor/interceptor | !-- BMT -- | interceptor transaction=Beanorg.jboss.ejb.plugins.StatefulSessionInstanceInterceptor/interceptor | interceptor transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor | interceptor transaction=Beanorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor | interceptororg.jboss.resource.connectionmanager.CachedConnectionInterceptor/interceptor | interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor | /container-interceptors | instance-cacheorg.jboss.ejb.plugins.StatefulSessionInstanceCache/instance-cache | persistence-managerorg.jboss.ejb.plugins.StatefulSessionFilePersistenceManager/persistence-manager | container-cache-conf | cache-policyorg.jboss.ejb.plugins.LRUStatefulContextCachePolicy/cache-policy | cache-policy-conf | min-capacity50/min-capacity | max-capacity100/max-capacity | remover-period30/remover-period | max-bean-life30/max-bean-life | overager-period30/overager-period | max-bean-age30/max-bean-age | resizer-period5/resizer-period | max-cache-miss-period5/max-cache-miss-period | min-cache-miss-period1/min-cache-miss-period | cache-load-factor0.75/cache-load-factor | /cache-policy-conf | /container-cache-conf | container-pool-conf | MaximumSize100/MaximumSize | /container-pool-conf | /container-configuration | I would think the beans should now passivate within 30 seconds of inactivity (or in my case, after the application shuts down -- I wrote a small test app that just looks up the bean then ends so the bean becomes inactive). Can anyone explain why passivation still takes 10 minutes? Thanks. Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4125800#4125800 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125800 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - EJB Passivation Error
Hi - I've been having an issue where I receive errors about EJB passivation - cannot find class org/apache/Logging/VariableContext and similar errors like that. Basically, the errors all seem to relate to serializing/passivating log4j and the jaxen library. I can post a full stack trace if you think it would be helpful, but I think this should be enough information. The strange problem is that I don't use log4j, so I'm not sure why I would be getting these errors. I've seen other people post questions similar to this, but so far there has been no luck in answering them. Does anyone have a solution to how to fix this problem or at least some insight to help me figure out what is causing this? Thank you - Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3981581#3981581 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3981581 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Registering Listeners
Hi -
I'm trying to register a listener with an EJB bean and I'm not really sure how
to do it. Before I switched to EJB, I used to be able to do as follows:
myBean.registerListener(myListener);
And myListener would have methods such as:
myActionPerformed() {}
which would be invoked when myBean performs a specific event. However, now that
I've switched to EJB3 (away from JINI), I cannot seem to do that since the bean
cannot resolve the type of the listener - does this make sense?
I've been reading about using the CallbackListener annotation, but I can't seem
to translate it correctly.
If anyone has any advice on this topic, could you please help?
Thanks,
Jeff
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3976977#3976977
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3976977
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Messages to a Single Client
I'm trying to figure out a way to have a stateful session bean send an asycnhronous message back to the client that is currently using it. More specifically, the different private methods in the beans should send a message back to the client informing it of its progress. I've looked into JMS but that looks like it more-so broadcasts a message or sends a response to an arbitrary client. Is there a good way to do this with EJB/JBoss? Thanks, Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977065#3977065 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977065 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration Deployment] - Re: Deploying a JAR with props file in it
Peter, Thanks, your advice has been helpful. I have one other question that maybe you may be able to help with if you don't mind...I have a label that is a status listener - it gets registered with some process running on the server side and is notified whenever that process' status changes. The problem is when I try to register this client-side component with the server, I get errors about ClassNotFoundException (RMI classloader disabled). I guess it has something to do with the server not being able to resolve that class type - but I wouldn't think the server should need to know specifics about the client. Is there a way around this - I don't really want to include the client component in the server war file. That doesn't make much sense logically. Thanks, Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3976033#3976033 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3976033 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration Deployment] - Deploying a JAR with props file in it
Hi everyone, I have a bunch of EJB stateful and stateless beans I would like to deploy on a JBoss server. These beans have methods in them that read from a props file (using the getResource method to find the props file). To avoid hard-coding the path of this props file, I want to include it in my JAR file that gets deployed. However, when I do that, JBoss throws exceptions during deployment that say things like: could not initialize deployment error parsing meta data jar When I take the props file out of the jar and hard code the path (which I obviously don't want to do), the error is gone and all runs smoothly. Does anyone know why this might be happening and how to fix this? Thanks! Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3975773#3975773 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3975773 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration Deployment] - Re: Deploying a JAR with props file in it
Hi Peter, Thanks for the response. I just found out (actually a few minutes ago) that my network connection was weak and sometimes dropping. When it dropped in the middle of deploying my beans, that's when the problem happened. Now, my connection is stable again and all seems to be fine. Thanks. Jeff View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3975851#3975851 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3975851 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
