June 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3076) Support declarative configuration of event listeners (process, agenda, working memory)

by Vinod Kiran Paidimarry (JIRA)

Support declarative configuration of event listeners (process, agenda, working memory) --------------------------------------------------------------------------------------- Key: JBRULES-3076 URL: https://issues.jboss.org/browse/JBRULES-3076 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-spring Reporter: Vinod Kiran Paidimarry Assignee: Mark Proctor Support declarative configuration of event listeners (process, agenda, working memory) using Spring XML -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1826) Removing a reference and deleting a message in DB should be wrapped in a single transaction in JDBCPersistenceManager

by Yong Hao Gao (JIRA)

Removing a reference and deleting a message in DB should be wrapped in a single transaction in JDBCPersistenceManager ---------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1826 URL: https://jira.jboss.org/browse/JBMESSAGING-1826 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP11, 1.4.8.GA In JDBCPersistenceManager, when a message is delivered and completed, the message is removed from DB. It includes two deletes in the DB - the reference in JBM_MSG_REF and the message in JBM_MSG. The two deletes are currently done in two separate local transactions as in removeReference() method: ... new RemoveReferenceRunner().executeWithRetry(); deleteMessage(ref.getMessage().getMessageID()); ... If a server crashes between the two operations, it will leave the tables in an inconsistent state, i.e. ref removed but the message still there. This may result in message stuck, as in this case: 1. A server is crashing when a client_ack comes in, the clienk_ack will cause the message to be cleared from the server. If the client_ack processing goes as far as that the removing of reference succeeds but failed to delete the message due to the crashing, the message is left in JBM_MSG table but the corresponding entry in JBM_MSG_REF is gone. 2. Eventually the jms client will get ack failure exception. It then expects the messages to be re-delivered after server start-up. But that will never happen. When the server starts up it loads references in JBM_MSG_REF for delivery, but this message's ref is gone. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
18
0 / 0

[JBoss JIRA] Created: (HIBERNATE-54) problems w/ column names beginning with '_' (underscore) w/ apache derby database

by bugra uytun (JIRA)

problems w/ column names beginning with '_' (underscore) w/ apache derby database --------------------------------------------------------------------------------- Key: HIBERNATE-54 URL: http://jira.jboss.com/jira/browse/HIBERNATE-54 Project: Hibernate Issue Type: Bug Environment: windows xp, java 1.5.0_09, eclispe 3.2.1, hibernate 3.2.1, derby 10.2.2.0, hibernate tools 3.2 beta8 Reporter: bugra uytun Assigned To: Steve Ebersole derby has problems with column names beginning with underscore, see also http://db.apache.org/derby/docs/10.1/ref/crefsqlj1003454.html therefore such column names should be between double quotation marks (notice that double quotation marks also sets the case sensitivity on column names.) but hibernate translates a HQL statement like this "from table1 t where t.id = '1'" to something like: select table1_.id as id4, table1_._colname1 as column27_4_ schema1.table1 table1_ where table1_.id = '1' but because of the columns that are beginning with an underscore the translation should be: select table1_."id" as id4, table1_."_colname1" as column27_4_ schema1."table1" table1_ where table1_."id" = '1' the errors i got are: DEBUG [JDBCExceptionReporter]: could not execute query [<translated sql statement>] ERROR 42X01: Syntax error: Encountered "_" at line 1, column 987. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.compile.ParserImpl.parseStatement(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source) at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Unknown Source) at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:497) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:415) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1538) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2211) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2095) at org.hibernate.loader.Loader.list(Loader.java:2090) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:388) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at <mypackage>.MyHibernate.main(MyHibernate.java:13) WARN main org.hibernate.util.JDBCExceptionReporter - SQL Error: 20000, SQLState: 42X01 ERROR main org.hibernate.util.JDBCExceptionReporter - Syntax error: Encountered "_" at line 1, column 987. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2248) singleton time bean starts with uninitialized EJBs

by Chris Wesdorp (JIRA)

singleton time bean starts with uninitialized EJBs -------------------------------------------------- Key: EJBTHREE-2248 URL: https://issues.jboss.org/browse/EJBTHREE-2248 Project: EJB 3.0 Issue Type: Bug Components: ejb3_1 Environment: jboss 6.0.0 final Reporter: Chris Wesdorp Attachments: jboss-timer-singleton.zip During the deployment of a (large) EAR the following problem occurs. In one of the JARs a singleton EJB is included which has a method annotated with @Schedule. The time out for this schedule is every minute. This singleton has references to other EJBS in the project. But at deployment the singleton is loaded before the referenced EJBs are added registered in JNDI. When the time out of the singleton occurs a NullPointerException is thrown because the container isn't able to inject the other EJBs. {noformat}2011-05-12 13:21:01,201 ERROR [org.jboss.ejb3.timerservice.mk2.task.TimerTask] (pool-99-thread-3) Error during retyring timeout for timer: [id=2d8011ca-66e3-4746-a035-3fa2b5a68263 timedObjectId=jboss.j2ee:ear=ht-ear-1.8.0-SNAPSHOT.ear,jar=ht-system.jar,name=BatchExecutor,service=EJB3 auto-timer?:true persistent?:true timerService=org.jboss.ejb3.timerservice.mk2.TimerServiceImpl@1d261c7e initialExpiration=2011-05-10 00:00:00.0 intervalDuration(in milli sec)=0 nextExpiration=Tue May 10 16:03:00 CEST 2011 timerState=RETRY_TIMEOUT: javax.ejb.EJBException: java.lang.NullPointerException at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java:137) [:1.0.0-alpha-28] at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.get(SingletonEJBInstanceManagerImpl.java:152) [:1.0.0-alpha-28] at org.jboss.ejb3.singleton.impl.container.SingletonContainer.invoke(SingletonContainer.java:201) [:1.0.0-alpha-28] at org.jboss.ejb3.singleton.aop.impl.AOPBasedSingletonContainer.callTimeout(AOPBasedSingletonContainer.java:886) [:1.0.0-alpha-28] at org.jboss.ejb3.timerservice.mk2.task.CalendarTimerTask.callTimeout(CalendarTimerTask.java:80) [:1.0.0-alpha-13] at org.jboss.ejb3.timerservice.mk2.task.TimerTask.run(TimerTask.java:127) [:1.0.0-alpha-13] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_24] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: org.jboss.injection.manager.spi.InjectionException: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: ConfigDAO not bound]] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:87) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionContext.proceed(DefaultInjectionContext.java:58) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:58) [:1.0.0-alpha-6] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:64) [:1.0.0-alpha-6] at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:140) [:1.7.17] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:125) [:1.7.17] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.7.17] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116) [:1.7.17] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116) [:1.7.17] at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1363) [:1.7.17] at org.jboss.ejb3.singleton.aop.impl.AOPBasedSingletonContainer.postConstruct(AOPBasedSingletonContainer.java:759) [:1.0.0-alpha-28] at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java:133) [:1.0.0-alpha-28] ... 13 more{noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1577) Require at least maven 2.0.9

by Carlo de Wolf (JIRA)

Require at least maven 2.0.9 ---------------------------- Key: EJBTHREE-1577 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1577 Project: EJB 3.0 Issue Type: Feature Request Components: build Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.0-Beta7 Because a bug in Maven with the ordering of the class path, you need at least version 2.0.9. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2573) Planner should support phasing several solvers after each other

by Geoffrey De Smet (JIRA)

Planner should support phasing several solvers after each other --------------------------------------------------------------- Key: JBRULES-2573 URL: https://jira.jboss.org/browse/JBRULES-2573 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: FUTURE First start with a 80% of the time simulateted annealing phase and then do 20% of the time tabu search. Notice that initialization is also a phase (a special phase). Needs to get a good name. Alternative naming proposals: * phasing * chaining (not really correct with GoF definition?) * ... (more welcome!) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2427) Extract the commons parts of a deterministic StartingSolutionInitizalizer into a build-in class

by Geoffrey De Smet (JIRA)

Extract the commons parts of a deterministic StartingSolutionInitizalizer into a build-in class ----------------------------------------------------------------------------------------------- Key: JBRULES-2427 URL: https://jira.jboss.org/jira/browse/JBRULES-2427 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet It's always the same thing (see manual) Meanwhile fix the need to provide the internal LocalSearchSolverScope to a method of a public interface which we expect more then 80% of the users to implement: void initializeSolution(LocalSearchSolverScope localSearchSolverScope); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9026) Create JBoss AS Javadoc aggregate project

by David Lloyd (JIRA)

Create JBoss AS Javadoc aggregate project ----------------------------------------- Key: JBAS-9026 URL: https://issues.jboss.org/browse/JBAS-9026 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: John Casey Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

12
84
0 / 0

[JBoss JIRA] Created: (AS7-818) Fix or remove @Ignore in WebAppTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in WebAppTestCase --------------------------------------- Key: AS7-818 URL: https://issues.jboss.org/browse/AS7-818 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Kabir Khan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
10
0 / 0

[JBoss JIRA] Created: (JBAS-9034) Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference

by Scott Marlow (JIRA)

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2011