June 2009 - jboss-user - Jboss List Archives

by kukeltje

By using the api? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239002#4239002 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239002

16 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: What's the stable version of Jbpm

by kukeltje

3.2.6SP1 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239000#4239000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239000

16 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Re: Notifications when the state of a user task is changed

by kukeltje

by using the task-assign event? Look at how events/actions work in jBPM http://docs.jboss.com/jbpm/v3.2/userguide/html/processmodelling.html#actions View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238999#4238999 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238999

16 years, 10 months

1
0
0 / 0

[JBossMQ] - JmsXA not installing esception listener on QueueConnection

by stone_42

Hello, I have the following problem: In a cluster of two nodes (both jboss 4.0.3 sp1), I use MDBs and SLSBs sending messages to the MDBs. For this, the SLSBs use the following code to access a queue connection: | InitialContext initialContext = new InitialContext(); | QueueConnectionFactory qcf = (QueueConnectionFactory) initialContext.lookup("java:/JmsXA"); | QueueConnection qc = qcf.createQueueConnection(); | After some time running the cluster, I can see the following error in the log once a minute: anonymous wrote : | 2009-06-17 19:43:28,455 WARN (Connection Monitor Thread) [org.jboss.mq.Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect | org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) | Now, this is my problem: As I'm in an EJB container, I am not allowed to call setExceptionListener(), and this should be handled by the container as described in http://www.jboss.org/community/wiki/IGetIOExceptionPingTimeoutHowDoIFixIt. Can anyone please tell me waht I'm doing wrong? Regards, Martin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238992#4238992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238992

16 years, 10 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Dirty read even though configured as REPEATABLE_READ or

by mircea.markus

This is a duplicate of http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157341. It was answered on the other thread. Please only post once, as this would make the topic easier to follow. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238988#4238988 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238988

16 years, 10 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: JBosscache dirty read even though isolation is REPEATABL

by mircea.markus

On the other post I saw you're using DummyTransactionManagerLookup. You're running in the application server so use GenericTransactionManagerLookup. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238985#4238985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238985

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: How to ignore persistence unit loading

by kariem

Thank you for taking the time to look at this. "jaikiran" wrote : Where in the WAR file is this jar containing persistence.xml located? As far as i know, the WEB-INF/lib folder of an WAR is not scanned for deployments. So that should have skipped the persistence unit from deploying. But i will have to look at this once more to see if that's not how its expected to behave. The JAR containing the persistence unit is located in WEB-INF/lib/xxx.jar. According to the EJB 3 persistence spec (JPA 1.0) section 6.2, the following location may contain the root of a persistence unit (root means the jar file or directory whose META-INF directory contains the persistence.xml): anonymous wrote : | | * an EJB-JAR file | | * the WEB-INF/classes directory of a WAR file | | * a jar file in the WEB-INF/lib directory of a WAR file | | * a jar file in the root of the EAR | | * a jar file in the EAR library directory | | * an application client jar file | | That means that the persistence unit should be scanned with this type of packaging (item 3 in the list above). Is there a way in JBoss (or generally in JEE) to prevent this scanning? Thank you, Kariem View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238984#4238984 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238984

16 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

by timfox

You could add a feature request JIRA if you like, if you want JBM 1.x to also support sub contexts on the name too. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238979#4238979 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238979

16 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

by timfox

In JBM 1.x, if you want to do this kind of thing you need to use JNDIName as Howard mentioned at the beginning of this thread. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238977#4238977 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238977

16 years, 10 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: JBosscache dirty read even though isolation is REPEATABL

by mircea.markus

Are you running both EJB's in the same JVM? That would explain it, as TX rollback won't affect the changes you've done to TestEntity, only the operations you've done on cache. That is the changes TestEntity.update does on the object won't be affected by the TransactionManager.rollback call. Following will be affected though: cache.put(fqn, "key", "1"); | tm.begin(); | cache.put(fqn, "key", "2"); | tm.rollback(); | assert cache.get(fqn, "key").equals("1") : "this is true, won't fail!!!"; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238976#4238976 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238976

16 years, 10 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 June 2009