March 2007 - jboss-user - Jboss List Archives

[Installation, Configuration & Deployment] - Chnaging JBoss JDBC connection pool size

by inderjeet

Hi all I have setup a JDBC connection pool in JBoss using oracle-ds.xml. I have a requirement in my web application to change the size of the pool using my web application itself. Can I do it? Does Jboss provide some API to do it in runtime? Earlier we had our own connection pool where we had this flexibility. but now we have switched to JBoss connection pool. One more I have that similar to my above mentioned problem, can we supply the database schema password also in runtime to the JBoss connection pool? Please let me the solution if we can do it or not? Thanks in Advance Inder Jeet Singh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026091#4026091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026091

19 years, 1 month

1
0
0 / 0

[EJB 3.0] - EAR file module SubDeployment ordering

by pakemann

Is it possible to configure 4.0.5 to deploy modules in an ear file in the order they are listed in application.xml? I have some code I need to execute at the end of the deployment of an EAR file and this seems like the best way to do it. I found discussions in the developer forum on the topic of respecting application.xml ordering, but I am not clear if the matter was resolvced, and if so, how to go about actually doing it. If anyone could help with an explanation of how exactly to do this, (or alternate suggestions on how to approach the problem) I would greatly appreciate it. For reference here are: The discussion thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78376&start=10&p... The feature tracker entry: [urlhttp://jira.jboss.com/jira/browse/JBAS-2904[/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026088#4026088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026088

19 years, 1 month

1
0
0 / 0

[JBoss/Spring Integration] - What version of Spring that JBoss supports?

by hondawei

I can't find infromation about what version of Spring that JBoss 4.0.4 and JBoss 4.0.5 support. Should I upload Spring library when I use JBoss or JBoss had built-in Spring library? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026083#4026083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026083

19 years, 1 month

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - What version of Hibernate that JBOSS supports?

by hondawei

I know JBoss built-in support Hibernate 3.2.1GA in 4.0.5. I want to know what version of Hibernate that JBoss 4.0.4 and 4.2.0 CR1 support.Should I upload Hibernate library when I use JBoss 4.0.4 or 4.2.0 CR1? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026082#4026082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026082

19 years, 1 month

1
0
0 / 0

[JBoss Seam] - Re: Rollback exceptions without ending the conversation

by enazareno

Hi, Thanks for pointing that out. Here is my sample code | @In | EntityManager em; | | @In | UserList userList; | | boolean isnew; | | @Out | User user; | | @Begin( id="#{user.id}" ) | public void edit() { | user = em.merge(userList.getSelectedUser()); | isnew = false; | } | | @End | public void save() { | if(isnew) | em.persist( user ); | else | em.merge( user ); | userList.refresh(); //can also use event for this | isnew = false; | } | The conversation actually ends when I press save. However it is my understanding that you cant put a try catch inside the save because the entity manager is flushed only when it ends so at this point there is no error yet? Is this correct? Let's say I'll just accept that limitation and I want to create another conversation instead. I've already specified the conversation id, can't I just use that as a reference to my new conversation that I will create? Or is there no chance to get back to that conversation? I agree with you, this seems like a complex solution and I'd prefer number one too. It just kinda reminds me of the old days developing Clipper applications where you manage this kind of validation yourself. With client-server development, you are encouraged to let the database handle this. Now its back. Life's a cycle isnt it? so retro :) Regards, Elmo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026081#4026081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026081

19 years, 1 month

1
0
0 / 0

[Security & JAAS/JBoss] - Re: exception when run jboss-4.0.4 with the jboss federation

by charles751

Thank you for your recommend. I have found few little problems through my test using your framework demo: 1.In the package of jboss-identity-management.jar,there is missing a resource bundle for me. For some Chinese user,they need a users_zh_CN.properties.Perhaps this is not a problem. After all,there is so many different locale of the world. 2.In the package of jboss-sso.sar,there is missing log4j.jar and log4j-core.jar.Certainly,users can add these jar into the package.Another suggestion:I think that the jars about log of your project is a little older. good luck! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026080#4026080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026080

19 years, 1 month

1
0
0 / 0

[JBoss Seam] - Re: Seam & clustering

by gavin.king＠jboss.com

anonymous wrote : The use of CONVERSATION-scoped or SESSION-scoped Entity Bean Seam components is not considered truly cluster-safe. | | If you need to be cluster safe, hold the reference to the entity bean inside a stateful session bean (in any version of Seam) or inside a JavaBean Seam component that implements Mutable (in Seam 1.1). This is no longer true in recent versions of Seam. Its safe, but perhaps not efficient. Read the docs, not olde forum posts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026079#4026079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026079

19 years, 1 month

1
0
0 / 0

[JBoss Seam] - Re: more than one Seam Phase Listeners?

by detiber

It appears that your error is slightly different than the one I was encountering. I would only get the multiple SeamPhaseListener exception when trying to do an asynchronous call, there was no message on deployment. Are you sure that you are not including files multiple times in your deployment? But if that is not the problem, then I would double check that your included libraries are not including a Phase Listener that is causing problems with the SeamPhaseListener. Hope this helps, Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026078#4026078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026078

19 years, 1 month

1
0
0 / 0

[JBoss Seam] - Re: Seam & clustering

by holtak

Hello Gavin, anonymous wrote : | The use of CONVERSATION-scoped or SESSION-scoped Entity Bean Seam components is not considered truly cluster-safe. | | If you need to be cluster safe, hold the reference to the entity bean inside a stateful session bean (in any version of Seam) or inside a JavaBean Seam component that implements Mutable (in Seam 1.1). | This means, that if I have an Entity Bean "Item" and use it as #{item.price} in JSF, I shoud create an SFSB "ItemClusteraware" with getters for Item item = new Item() or em.find(..) from DB (create/edit-feature), remove @Name from Item and use it like this #{itemClusteraware.item.price} in my JSF? Is that right? I tried to clusterify my application: - put "distributable" into web.xml - anotate Session Beans with @Clustered - I didn`t do do Entity - SFSB stuff mentioned before, because that would mean lot of refactoring. Currently I have only one PC with Jboss with the cluster profile, so I deployed there. The app deployed well and I saw some INFO about TreeCache taking care of SFSB replication. The app works well too, but just for some period of time. After this period, jboss console output gets polluted with this exception once per second to infinity ProjectActionImpl is declard like this | @Stateful | @Clustered | @Name("projectAction") | @CacheConfig(idleTimeoutSeconds=SCRatingDefaults.SFSBTimeout) | public class ProjectActionImpl implements ProjectAction, Serializable { | | 03:42:07,162 INFO [TxInterceptor] There was a problem handling this request | java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: org.proaut.scrating.ejb3.session.ProjectActionImpl | at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.prePassivate(LifecycleInterceptorHandler.java:169) | at org.jboss.ejb3.stateful.StatefulContainer.invokePrePassivate(StatefulContainer.java:382) | at org.jboss.ejb3.stateful.StatefulBeanContext.prePassivate(StatefulBeanContext.java:178) | at org.jboss.ejb3.cache.tree.StatefulTreeCache$ClusteredStatefulCacheListener.nodePassivate(StatefulTreeCache.java:288) | at org.jboss.cache.TreeCache.notifyNodePassivate(TreeCache.java:5739) | at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:62) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345) | at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:179) | at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5520) | at org.jboss.cache.TreeCache.evict(TreeCache.java:3716) | at org.jboss.cache.eviction.BaseEvictionPolicy.evict(BaseEvictionPolicy.java:34) | at org.jboss.cache.eviction.BaseEvictionAlgorithm.evictCacheNode(BaseEvictionAlgorithm.java:210) | at org.jboss.cache.eviction.BaseEvictionAlgorithm.emptyRecycleQueue(BaseEvictionAlgorithm.java:461) | at org.jboss.cache.eviction.BaseEvictionAlgorithm.process(BaseEvictionAlgorithm.java:97) | at org.jboss.cache.eviction.EvictionTimerTask.run(EvictionTimerTask.java:80) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | Caused by: java.lang.RuntimeException: java.io.IOException: org.proaut.scrating.ejb3.session.ProjectActionImpl | at org.jboss.ejb3.stateful.StatefulBeanContext.extractBeanAndInterceptors(StatefulBeanContext.java:367) | at org.jboss.ejb3.stateful.StatefulBeanContext.getInterceptorInstances(StatefulBeanContext.java:333) | at org.jboss.ejb3.interceptor.LifecycleInvocationContextImpl.getLifecycleInvocationContext(LifecycleInvocationContextImpl.java:65) | at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.prePassivate(LifecycleInterceptorHandler.java:160) | ... 19 more | Caused by: java.io.IOException: org.proaut.scrating.ejb3.session.ProjectActionImpl | at org.jboss.serial.classmetamodel.ClassMetamodelFactory.getClassMetaData(ClassMetamodelFactory.java:332) | at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:72) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643) | at org.jboss.serial.persister.ArrayPersister.readObjectArray(ArrayPersister.java:196) | at org.jboss.serial.persister.ArrayPersister.readData(ArrayPersister.java:172) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643) | at org.jboss.serial.io.JBossObjectInputStream.readObjectOverride(JBossObjectInputStream.java:163) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:342) | at org.jboss.serial.io.MarshalledObject.get(MarshalledObject.java:68) | at org.jboss.ejb3.stateful.StatefulBeanContext.extractBeanAndInterceptors(StatefulBeanContext.java:342) | at org.jboss.ejb3.stateful.StatefulBeanContext.getInterceptorInstances(StatefulBeanContext.java:333) | at org.jboss.ejb3.interceptor.LifecycleInvocationContextImpl.getLifecycleInvocationContext(LifecycleInvocationContextImpl.java:65) | at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.prePassivate(LifecycleInterceptorHandler.java:160) | at org.jboss.ejb3.stateful.StatefulContainer.invokePrePassivate(StatefulContainer.java:382) | at org.jboss.ejb3.stateful.StatefulBeanContext.prePassivate(StatefulBeanContext.java:178) | at org.jboss.ejb3.cache.tree.StatefulTreeCache$ClusteredStatefulCacheListener.nodePassivate(StatefulTreeCache.java:288) | at org.jboss.cache.TreeCache.notifyNodePassivate(TreeCache.java:5739) | at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:62) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345) | at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:179) | Caused by: java.lang.ClassNotFoundException: org.proaut.scrating.ejb3.session.ProjectActionImpl | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at org.jboss.serial.classmetamodel.ClassMetamodelFactory.resolveClassByName(ClassMetamodelFactory.java:269) | at org.jboss.serial.classmetamodel.ClassMetamodelFactory.getClassMetaData(ClassMetamodelFactory.java:289) | at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:72) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643) | at org.jboss.serial.persister.ArrayPersister.readObjectArray(ArrayPersister.java:196) | at org.jboss.serial.persister.ArrayPersister.readData(ArrayPersister.java:172) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643) | at org.jboss.serial.io.JBossObjectInputStream.readObjectOverride(JBossObjectInputStream.java:163) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:342) | at org.jboss.serial.io.MarshalledObject.get(MarshalledObject.java:68) | at org.jboss.ejb3.stateful.StatefulBeanContext.extractBeanAndInterceptors(StatefulBeanContext.java:342) | at org.jboss.ejb3.stateful.StatefulBeanContext.getInterceptorInstances(StatefulBeanContext.java:333) | at org.jboss.ejb3.interceptor.LifecycleInvocationContextImpl.getLifecycleInvocationContext(LifecycleInvocationContextImpl.java:65) | at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.prePassivate(LifecycleInterceptorHandler.java:160) | at org.jboss.ejb3.stateful.StatefulContainer.invokePrePassivate(StatefulContainer.java:382) | at org.jboss.ejb3.stateful.StatefulBeanContext.prePassivate(StatefulBeanContext.java:178) | at org.jboss.ejb3.cache.tree.StatefulTreeCache$ClusteredStatefulCacheListener.nodePassivate(StatefulTreeCache.java:288) | at org.jboss.cache.TreeCache.notifyNodePassivate(TreeCache.java:5739) | at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:62) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345) | at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) | at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:179) | at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5520) | at org.jboss.cache.TreeCache.evict(TreeCache.java:3716) | the timeout of the SFSB is public static final int SFSBTimeout=((600*60)+60); what exactly is going on? it looks like an EJB3 thing but I didn`t find nothing comparable in the EJB3 forum... thank you, Juraj Holtak View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026077#4026077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026077

19 years, 1 month

1
0
0 / 0

[JBoss Seam] - Re: Remoting problem in mozilla

by enazareno

Hi Shane, OK, I've been able to find the culprit. Actually my remote bean did work successfully. The problem was if the button was located inside a form like this: | <form> | <button onclick="javascript:sayHello()">Say Hello</button> | </form> | This will not work in Mozilla. In IE, it works OK. Now in most cases, my button will reside in a form. At least the remoting worked. FYI Regards, Elmo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026076#4026076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026076

19 years, 1 month

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 March 2007