November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBPM-611) replace scheduler and timer service implementations with quartz

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-611?page=all ] Tom Baeyens closed JBPM-611. ---------------------------- Resolution: Rejected i evaluated and didn't opt for quartz. integrating it into jBPM was too hard. mainly the db connection management would be really hacky to get quartz to use the same jdbc connection as jBPM. That is what we needed to run fine in a standard environment. also the extra indirection layer between quartz and jBPM would have added extra unnecessary complexity. i did get inspired by reading their code and i have developed a unified job scheduler that is used for both asynchronous messaging and timers in jbpm. there's also a completely new locking mechanism. > replace scheduler and timer service implementations with quartz > --------------------------------------------------------------- > > Key: JBPM-611 > URL: http://jira.jboss.com/jira/browse/JBPM-611 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-452) Refactor SchedulerThread.executeTimers() to execute Timers in seperate Transactions

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-452?page=all ] Tom Baeyens closed JBPM-452. ---------------------------- Fix Version/s: jBPM 3.2 alpha 2 Resolution: Done the new job executor impl indeed executes every job in a separate transaction. > Refactor SchedulerThread.executeTimers() to execute Timers in seperate Transactions > ----------------------------------------------------------------------------------- > > Key: JBPM-452 > URL: http://jira.jboss.com/jira/browse/JBPM-452 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4 > Reporter: Rainer Alfoeldi > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 alpha 2 > > > SchedulerThread.executeTimers() executes in a single transaction. > All Timers execute() methods are called in this transaction and the changes to the Timers themselves are persisted in this transaction. > The failure of any one of the transacted resources in any one of the Timers would roll back all changes (workflow state as well as application resources) made during this call and we would effectively be where we started (probably running into the same failure the next time executeTimers() is called.) > The use of a single transaction seems to be intentional (http://jira.jboss.com/jira/browse/JBPM-46 where Tom states that "we only use one transactional resource (jdbc connection) so ..." > As we are talking about potentially thousands of Timers executing in a single transaction this doesn't seem to be viable. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-141) Paging is not efficient

by Ryszard Kozmik (JIRA)

Paging is not efficient ----------------------- Key: JBFORUMS-141 URL: http://jira.jboss.com/jira/browse/JBFORUMS-141 Project: JBoss Forums Issue Type: Bug Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta Paging is not efficient because when it is initialized it gets all objects for paging. It is serious problem when number of topics/posts is very big because it causes loading a lot of objects into memory and a large performance hit. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Reopened: (JBAS-2780) NullPointerException at DeploymentSorter with IBM's JDK

by Heiko W. Rupp (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2780?page=all ] Heiko W. Rupp reopened JBAS-2780: --------------------------------- > NullPointerException at DeploymentSorter with IBM's JDK > ------------------------------------------------------- > > Key: JBAS-2780 > URL: http://jira.jboss.com/jira/browse/JBAS-2780 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1 > Environment: The IBM JDK I've used is: > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20051104) > IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20051103 (JIT enabled) > J9VM - 20051027_03723_lHdSMR > JIT - 20051027_1437_r8 > GC - 20051020_AA) > JCL - 20051102 > OS: Debian GNU/Linux unstable > Eclipse 3.1.1 + JBoss IDE 1.5 > JBOSS: jboss-4.0.3SP1 > Reporter: Horacio de Oro > Priority: Minor > > I've a project working well with JBoss 4.0.3SP1 + Sun JDK 1.5.0_06. I start JBoss in debug mode and if I make a change to the class the "hot-code-replace" works well. But with IBM's JDK I get the following exception after making any change to a class: > 02:04:10,212 ERROR [AbstractDeploymentScanner$ScannerThread] Scanning failed; continuing > java.lang.NullPointerException > at java.lang.String.endsWith(String.java :494) > at org.jboss.deployment.DeploymentSorter.getExtensionIndex (DeploymentSorter.java:84) > at org.jboss.deployment.DeploymentSorter.compare(DeploymentSorter.java:72) > at java.util.Arrays.mergeSort(Arrays.java:1299) > at java.util.Arrays.mergeSort (Arrays.java:1310) > at java.util.Arrays.mergeSort(Arrays.java:1310) > at java.util.Arrays.mergeSort(Arrays.java:1310) > at java.util.Arrays.sort(Arrays.java:1238) > at java.util.Collections.sort (Collections.java:174) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:496) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan (AbstractDeploymentScanner.java:192) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop (AbstractDeploymentScanner.java:203) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run (AbstractDeploymentScanner.java:182) > That stack trace start appearing in logs after making a change to a class, and continue appearing again and again and again. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2780) NullPointerException at DeploymentSorter with IBM's JDK

by Heiko W. Rupp (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2780?page=comments#action_12347057 ] Heiko W. Rupp commented on JBAS-2780: ------------------------------------- I see the same stack trace appearing after the server is running for some time This is on 13:17:36,794 INFO [ServerInfo] Java version: 1.5.0_06,Apple Computer, Inc. 13:17:36,796 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_06-64,"Apple Computer, Inc." 13:17:36,797 INFO [ServerInfo] OS-System: Mac OS X 10.4.8,ppc 13:17:36,798 DEBUG [ServerInfo] Full System Properties Dump 13:17:36,798 DEBUG [ServerInfo] java.vendor: Apple Computer, Inc. 13:17:36,798 DEBUG [ServerInfo] sun.management.compiler: HotSpot Client Compiler 13:17:36,799 DEBUG [ServerInfo] os.name: Mac OS X 13:17:36,799 DEBUG [ServerInfo] sun.boot.class.path: /jboss/lib/endorsed/resolver.jar:/jboss/lib/endorsed/serializer.jar:/jboss/lib/endorsed/xalan.jar:/jboss/lib/endorsed/xercesImpl.jar:/jboss/lib/endorsed/xml-apis.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/sunrsasign.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar 13:17:36,799 DEBUG [ServerInfo] java.vm.specification.vendor: Sun Microsystems Inc. 13:17:36,799 DEBUG [ServerInfo] java.runtime.version: 1.5.0_06-112 What can I do to help debugging this? > NullPointerException at DeploymentSorter with IBM's JDK > ------------------------------------------------------- > > Key: JBAS-2780 > URL: http://jira.jboss.com/jira/browse/JBAS-2780 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1 > Environment: The IBM JDK I've used is: > java -version > java version "1.5.0" > Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20051104) > IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20051103 (JIT enabled) > J9VM - 20051027_03723_lHdSMR > JIT - 20051027_1437_r8 > GC - 20051020_AA) > JCL - 20051102 > OS: Debian GNU/Linux unstable > Eclipse 3.1.1 + JBoss IDE 1.5 > JBOSS: jboss-4.0.3SP1 > Reporter: Horacio de Oro > Priority: Minor > > I've a project working well with JBoss 4.0.3SP1 + Sun JDK 1.5.0_06. I start JBoss in debug mode and if I make a change to the class the "hot-code-replace" works well. But with IBM's JDK I get the following exception after making any change to a class: > 02:04:10,212 ERROR [AbstractDeploymentScanner$ScannerThread] Scanning failed; continuing > java.lang.NullPointerException > at java.lang.String.endsWith(String.java :494) > at org.jboss.deployment.DeploymentSorter.getExtensionIndex (DeploymentSorter.java:84) > at org.jboss.deployment.DeploymentSorter.compare(DeploymentSorter.java:72) > at java.util.Arrays.mergeSort(Arrays.java:1299) > at java.util.Arrays.mergeSort (Arrays.java:1310) > at java.util.Arrays.mergeSort(Arrays.java:1310) > at java.util.Arrays.mergeSort(Arrays.java:1310) > at java.util.Arrays.sort(Arrays.java:1238) > at java.util.Collections.sort (Collections.java:174) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:496) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan (AbstractDeploymentScanner.java:192) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop (AbstractDeploymentScanner.java:203) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run (AbstractDeploymentScanner.java:182) > That stack trace start appearing in logs after making a change to a class, and continue appearing again and again and again. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-631) Update the build script to produce an unscoped SAR

by Ovidiu Feodorov (JIRA)

Update the build script to produce an unscoped SAR -------------------------------------------------- Key: JBMESSAGING-631 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-631 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta1 Needed by Scott for integration -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-527) Websphere MQ cannot be integrated with EJB3 (deployment fails)

by Elias Ross (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-527?page=comments#action_12347052 ] Elias Ross commented on EJBTHREE-527: ------------------------------------- I'm guessing something is wrong with your configured connection factory, as the JBossMQ connection factory is accessing the Websphere MQ queue. Likely configuration error. The Wiki examples are also pretty much out of date; the rar adapter and JCA 1.5 are the preferred ways to access foreign queues. > Websphere MQ cannot be integrated with EJB3 (deployment fails) > -------------------------------------------------------------- > > Key: EJBTHREE-527 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-527 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Environment: Windows XP, JBoss 4.0.4 CR2 with EJB3 RC6 > Reporter: Michael Grübsch > > When trying to integrate Websphere MQ with an EJB 3 application the following exception occurs while deploying the application: > 12:28:10,906 WARN [ServiceController] Problem starting service jboss.j2ee:jar=wsmqmdb.jar,name=MDB,service=EJB3 > java.lang.ClassCastException: com.ibm.mq.jms.MQQueue > at org.jboss.mq.SpyConnectionConsumer.<init>(SpyConnectionConsumer.java:107) > at org.jboss.mq.SpyConnection.createConnectionConsumer(SpyConnection.java:209) > at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:530) > at org.jboss.ejb3.mdb.MDB.innerCreate(MDB.java:454) > at org.jboss.ejb3.mdb.MDB.innerStart(MDB.java:267) > at org.jboss.ejb3.mdb.MDB.start(MDB.java:256) > 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.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:99) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > .... > To reproduce the bug do the following: > 1. set up environment JBoss 4.0.4 CR2 with EJB3 RC6 > 2. Download wsmqdemo.zip from the integration tutorial http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... (http://wiki.jboss.org/wiki/attach?page=UsingWebSphereMQSeriesWithJBossASP...) > 3. Configure it for using Websphere for inbound and outbound (see http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA...) > 4. put a valid file "persistence.xml" into the META-INF directory of the application or tag some class using a @Stateful annotation (indicating that EJB3 is to be used(?)) > 5. deploy the application -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-555) Old versions of jdt.core might be used in classpath instead of new required ones

by Kris Verlaenen (JIRA)

Old versions of jdt.core might be used in classpath instead of new required ones -------------------------------------------------------------------------------- Key: JBRULES-555 URL: http://jira.jboss.com/jira/browse/JBRULES-555 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Priority: Minor When the plugins dir contains old versions of a jdt.core jar, in combination with a 3.2 version (which is required), the Drools classpath might include the old version of the jdt.core jar. When searching for the jdt.core jar, we should keep searching if the jar found is not of version 3.2+. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-842) Optimistic Locking improvements - validation on read-only transactions

by Manik Surtani (JIRA)

Optimistic Locking improvements - validation on read-only transactions ---------------------------------------------------------------------- Key: JBCACHE-842 URL: http://jira.jboss.com/jira/browse/JBCACHE-842 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA Don't bother validating workspace nodes at commit time if none of the nodes have been modified in the tx. Throws unnecessary exceptions. E.g.: Transaction A reads object 1 Transaction B modifies object 1 Transaction B commits Transaction A commits Will throw an exception, which is probably not desired. -- 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

19 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3695) Integrate JBC 2.0.0 DR1 into HEAD

by Brian Stansberry (JIRA)

Integrate JBC 2.0.0 DR1 into HEAD --------------------------------- Key: JBAS-3695 URL: http://jira.jboss.com/jira/browse/JBAS-3695 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta The JBC team has cut a "JBossCache_2_0_DR1" release, which is really a pre-alpha snapshot for internal use. Need to integrate this into HEAD so we can see the issues it raises. -- 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

19 years, 8 months

1
1
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 November 2006