August 2008 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: Using Connection Pool in EJB 3.0

by mabimal

Thank you PeterJ I will try to continue with that. Thank you Mabimal View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171658#4171658 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171658

17 years, 8 months

1
0
0 / 0

[EJB 3.0] - Re: deleted entity passed to persist exception ???

by nonreva

With Jboss 4.2.2GA I am experiencing a similar problem. The gist of it is (within a single container managed transaction): 1. I remove an item from this collection... | @OneToMany(mappedBy = "ivrAccount", cascade = CascadeType.ALL) | public Collection<LinkedAccountBean> linkedAccounts = new HashSet<LinkedAccountBean>(); 2. I perform a query on another bean... | try { | System.out.println("************ 1 **************"); | String number = accountReference.getNumber(); | System.out.println("************ 2 ************** " + number); | | Query q= em.createNamedQuery( | BankAccountReference.FIND_BY_ACCOUNT_NUMBER_QUERY) | .setParameter("number", number); | System.out.println("************ 3a **************"); | Object o = q.getSingleResult(); | System.out.println("************ 3b **************"); | linkedAccount.accountReference = (BankAccountReference) o; | System.out.println("************ 3c **************"); | | } catch (NoResultException ex) { | System.out.println("************ 4 **************"); | linkedAccount.accountReference = BankAccountReferenceHelper | .createBankAccountReference(em, accountReference); | } catch (EntityNotFoundException ex) { | System.out.println("************ XXXXX **************"); | throw ex; | } | This results in an EntityNotFoundException... | 14:29:51,593 ERROR [STDERR] Caused by: javax.persistence.EntityNotFoundException: deleted entity passed to persist: [ae. | hilal.j2ee.entity.account.LinkedAccountBean#<null>] | 14:29:51,593 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityM | anagerImpl.java:613) | 14:29:51,593 ERROR [STDERR] at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:99) | 14:29:51,593 ERROR [STDERR] at ae.hilal.j2ee.session.helper.LinkedAccountHelper.update(LinkedAccountHelper.java:40) | 14:29:51,593 ERROR [STDERR] at ae.hilal.j2ee.session.helper.LinkedAccountHelper.createLinkedAccount(LinkedAccountHel | per.java:123) | This can be seenn from the following output: 16:40:02,156 INFO [STDOUT] ************ 1 ************** | 16:40:02,156 INFO [STDOUT] ************ 2 ************** 4444444444 | 16:40:02,156 INFO [STDOUT] ************ 3a ************** | 16:40:02,156 INFO [STDOUT] ************ XXXXX ************** this appears to me to be the cause of a anonymous wrote : 14:29:51,593 ERROR [STDERR] javax.ejb.EJBTransactionRolledbackException: deleted entity passed to persist: [ae.hilal.j2e | e.entity.account.LinkedAccountBean#] | 14:29:51,593 ERROR [STDERR] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) | ... What is ironic about this is that if I do the remove after the query it works... i.e. I collect up the objects that need to be removed and I remove them after I have done additions and updates to the collection. Whilst this workaround appears to solve the problem in this particular instance, there is only an indirect relationship between the object deleted and the query. Furthuermore I am not convinced that if further queries were to follow the delete (untested scenarios) that these might also lead to problemd. The EJB persistence specification (A.4) says that anonymous wrote : Replaced EntityNotFoundException with NoResultException in | entities might be returned, and exception should be recoverable., so I am also wondering why such an exception is still being propagated from a query (if my understanding of the stack trace is correct) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171657#4171657 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171657

17 years, 8 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Managing over 10 nodes in a Load balanced Farm

by kjacobsz

Hi, I was wondering if there was any tools out there that can manage a load-balancing farm of over 10 Jboss instances? I am looking for a tool to provide some or all the following functions 1) install each JBoss instance 2)configure the instances 3)configure the load balancer (Apache mod_proxy) 4)each instance is located on separate systems. Sincerely View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171656#4171656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171656

17 years, 8 months

1
0
0 / 0

[JBoss Messaging] - Re: Is the destination for DLQ mandatory?

by ckaushalya

Thank you for your response Peter! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171655#4171655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171655

17 years, 8 months

1
0
0 / 0

[JBoss jBPM] - Re: workaround for StackOverflow exception

by alex.guizar＠jboss.com

JBSEAM-1575 depends on JBPM-1135 which is already resolved. That said, I have two suggestions. The first is to replace the timer with an asynchronous continuation, unless you need the delay (which I understand you do not). Just set the node's async attribute to true. It does not need to be a separate emtpy state, you can decorate any of your existing nodes with that attribute. The second is to implement a ThreadLocal based solution which prevents recursive calls once the loop node is reached. I came to it for preventing the stack overflow in the BPEL while activity, but it can be implemented for jPDL as well. You can browse the code in the online repository. Look at Loop.execute(). It is much of a hack - you might want to stick to asynchronous continuations unless you need more performance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171652#4171652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171652

17 years, 8 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: AbstractServerLogin module.logout and cached principals

by ragavgomatam

Yes possible this way too. Though it has nothing to do with the LoginModule. You will have to invoke the Jboss JaasSecurityManager with JMX.This way you can bypass HttpSession invalidation to clear the security cache . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171650#4171650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171650

17 years, 8 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: AbstractServerLogin module.logout and cached principals

by maggu

ragavgomatam, if I do programatic flushing via JMX in my custom login module, wouldn't that be equivalent? do you see any dis advantage of doing this? I am looking at these options because I wanted to remove the subject from the cache only based on some condition and not everytime the user closes the browser. let me know your thoughts http://wiki.jboss.org/wiki/CachingLoginCredentials View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171649#4171649 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171649

17 years, 8 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: some questions on authentication

by ragavgomatam

Check out the sticky anonymous wrote : JAAS Howto:README FIRST in this forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171648#4171648 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171648

17 years, 8 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: servlet: how to spawn all processors

by PeterJ

The best way to run on more that 4 CPUs is to run multiple instances of the app server, affinitizing each to its own set of CPUs. See my LinuxWorld presentation at http://www.linuxworld.com/events/2007/slideshows/A2-johnson.pdf. It is somewhat dated, but does cover affinity management. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171645#4171645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171645

17 years, 8 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: servlet: how to spawn all processors

by john_woo＠canada.com

"PeterJ" wrote : Running your web app across 16 CPUs is not a good idea. Due to CPU cache issues, contention among threads, and various other issues it is usually better to run such apps while affinitized to 2, 3 or 4 CPUs (depening on your app). At least that is what we have found in our testing. | | In Linux, you can use the taskset utility to set affinity. I suggest adding this to the script that starts jbossas. Thanks lots for the info, Peter. I did try the affinity setting (to 4 cpus for the app), but only 1-2 cpu busy. I guessed b/c all threads running in the same process from the main servlet. As the app is big one, and it's required to put it in 16-32 cpus machine. I'm still thinking how to make use of 4/8 cpus. -- John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171644#4171644 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171644

17 years, 8 months

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 August 2008