[JBoss-user] [Beginners Corner] - Re: Parallell requests fails with message
No, I'm using different stubs. But I shouldn't need to synchronize anything, right? /Patrik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3899315#3899315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3899315 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBossCache] - JBoss 4.0.3 message: No transaction manager lookup class has
I just upgraded from RC2 to 4.0.3 and got the following message when the server starts up: WARN [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used Is this serious? It sounds like it is! /Patrik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3899311#3899311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3899311 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Beginners Corner] - Re: Parallell requests fails with message
I might add that I am using JBoss 4.0.2 RC2 and EJB3 RC2. /Patrik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3899211#3899211 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3899211 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Beginners Corner] - Parallell requests fails with message
I have an application that calls a stateless session bean than in turn calls other stateless session beans, which operates on entity beans. This works fine when one thread calls the first session bean a number of times in serial, but it fails when I do the call with several threads in parallell. What do I have to think about in this scenario? Is it a transaction configuration maybe? Or is it something with the use of the EntityManager? The exception I get is the following: | java.lang.RuntimeException: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=putte/632, BranchQual=, localId=632] status=STATUS_NO_TRANSACTION; - nested throwable: (org.hibernate.cache.CacheException: org.jboss.cache.lock.UpgradeException: acquireWriteLock(): lock upgrade failed for /com/portwise/genua/user/User/com.portwise.genua.user.User#pabry1 (caller=:547); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock)) | at org.jboss.aspects.tx.TxPolicy.handleEndTransactionException(TxPolicy.java:185) | at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:167) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:74) | at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:181) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:32) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:88) | at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:239) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:107) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:69) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:566) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:436) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:239) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:291) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:168) | Caused by: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=putte/632, BranchQual=, localId=632] status=STATUS_NO_TRANSACTION; - nested throwable: (org.hibernate.cache.CacheException: org.jboss.cache.lock.UpgradeException: acquireWriteLock(): lock upgrade failed for /com/portwise/genua/user/User/com.portwise.genua.user.User#pabry1 (caller=:547); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock)) | at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:354) | at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:162) | ... 19 more | Caused by: org.hibernate.cache.CacheException: org.jboss.cache.lock.UpgradeException: acquireWriteLock(): lock upgrade failed for /com/portwise/genua/user/User/com.portwise.genua.user.User#pabry1 (caller=:547); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock) | at org.hibernate.cache.TreeCache.update(TreeCache.java:66) | at org.hibernate.cache.TransactionalCache.update(TransactionalCache.java:71) | at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:143) | at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243) | at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:227) | at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141) | at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) | at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) | at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:877) | at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:185) | at org.jboss.ejb3.entity.ManagedEntityManagerFacto
[JBoss-user] [Installation, Configuration & Deployment] - Can I use log4j 1.3 in JBoss 4.0.3?
Can I somehow replace the log4j with the latest alpha (log4j 1.3 alpha 6)? I tried to just replace the log4j jar with the new one, but I got the following error: 09:31:20,671 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml | 09:31:20,734 WARN [ServiceController] Problem creating service jboss.system:type=Log4jService,service=Logging | java.lang.IncompatibleClassChangeError | at org.apache.log4j.joran.spi.JoranDocument.resolveEntity(JoranDocument.java:125) | at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) | at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) | at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at javax.xml.parsers.SAXParser.parse(Unknown Source) | at javax.xml.parsers.SAXParser.parse(Unknown Source) | at org.apache.log4j.joran.JoranConfigurator$1.parse(JoranConfigurator.java:87) | at org.apache.log4j.joran.JoranConfigurator.doConfigure(JoranConfigurator.java:153) | at org.apache.log4j.joran.JoranConfigurator.doConfigure(JoranConfigurator.java:90) | at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:61) | at org.jboss.logging.Log4jService$URLWatchTimerTask.reconfigure(Log4jService.java:624) | at org.jboss.logging.Log4jService$URLWatchTimerTask.run(Log4jService.java:563) | at org.jboss.logging.Log4jService.setup(Log4jService.java:450) | at org.jboss.logging.Log4jService.createService(Log4jService.java:466) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:233) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:215) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:950) | at $Proxy0.create(Unknown Source) | at org.jboss.system.ServiceController.create(ServiceController.java:342) | at org.jboss.system.ServiceController.create(ServiceController.java:281) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) | at $Proxy4.create(Unknown Source) | at org.jboss.deployment.SARDeployer.create(SARDeployer.java:229) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:919) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:773) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:721) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[JBoss-user] [Beginners Corner] - Re: SocketTimeoutException with TopicConnectionFactory and Q
The same issue is discussed at JBoss.com -> JBoss User -> EJB 3.0 -> Error when starting jboss-4.0.3RC2 (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890832#3890832) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890989#3890989 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890989 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Can I call a session bean from an entity bean?
I want to call methods in a stateless session bean from an entity bean, but it doesn't work. Doesn't the EJB3 spec allow this? I use JBoss AS 4.0.3RC1. Thanks, Patrik View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885103#3885103 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885103 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: Why doesn't @PersistenceContext work for me?
Please forget my previous post! I am supposed to use @EJB instead!!! Sorry about that. /Patrik View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885098#3885098 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885098 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Why doesn't @PersistenceContext work for me?
I use JBoss AS 4.0.3RC1 and I have two session beans with the following classes:
@Local public interface MyManager
@Stateless public class MyManagerBean implements MyManager
@Remote public interface Tester
@Stateless public class TesterBean implements Tester
The first session bean just have one business method that returns a string.
The second session bean also have one business method that calls the method on
the first bean.
My question is: In the Tester bean, why doesn't
@PersistenceContext private static MyManager myManager;
work for me? I get the following exception:
Exception in thread "main" java.lang.RuntimeException: Failed in setting
EntityManager on setter field: private static mytest.bean.MyManager
mytest.bean.TesterBean.myManager
However, the following construct works:
private static MyManager myManager;
| static
| {
| try
| {
| InitialContext ctx = new InitialContext();
| myManager = (MyManager) ctx.lookup(MyManager.class.getName());
| }
| catch (NamingException e)
| {
| e.printStackTrace();
| }
| }
Anybody knows?
/Patrik
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885085#3885085
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885085
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
