November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1345) Subflow can specify whether this process should wait for its completion

by Kris Verlaenen (JIRA)

Subflow can specify whether this process should wait for its completion ----------------------------------------------------------------------- Key: JBRULES-1345 URL: http://jira.jboss.com/jira/browse/JBRULES-1345 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Kris Verlaenen Assigned To: Kris Verlaenen -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4643) Fix org.jboss.test.xml.DDValidatorUnitTestCase (5 failures)

by Dimitris Andreadis (JIRA)

Fix org.jboss.test.xml.DDValidatorUnitTestCase (5 failures) ----------------------------------------------------------- Key: JBAS-4643 URL: http://jira.jboss.com/jira/browse/JBAS-4643 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta3 testEjbJar Failure 5 from 165 are invalid expected:<0> but was:<5> junit.framework.AssertionFailedError: 5 from 165 are invalid expected:<0> but was:<5> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testEjbJar(DDValidatorUnitTestCase.java:76) 9.162 testJBossXml Failure 3 from 143 are invalid expected:<0> but was:<3> junit.framework.AssertionFailedError: 3 from 143 are invalid expected:<0> but was:<3> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossXml(DDValidatorUnitTestCase.java:81) 2.797 testJBossCmpJdbc Success 0.994 testWebXml Success 1.930 testJBossWeb Failure 4 from 39 are invalid expected:<0> but was:<4> junit.framework.AssertionFailedError: 4 from 39 are invalid expected:<0> but was:<4> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossWeb(DDValidatorUnitTestCase.java:96) 0.455 testApplicationXml Failure 8 from 50 are invalid expected:<0> but was:<8> junit.framework.AssertionFailedError: 8 from 50 are invalid expected:<0> but was:<8> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testApplicationXml(DDValidatorUnitTestCase.java:101) 0.635 testJBossApp Failure 2 from 37 are invalid expected:<0> but was:<2> junit.framework.AssertionFailedError: 2 from 37 are invalid expected:<0> but was:<2> at org.jboss.test.xml.DDValidatorUnitTestCase.validate(DDValidatorUnitTestCase.java:115) at org.jboss.test.xml.DDValidatorUnitTestCase.testJBossApp(DDValidatorUnitTestCase.java:106) 0.825 -- 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

17 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1152) Investigate whether we should include state column in tx index

by Tim Fox (JIRA)

Investigate whether we should include state column in tx index -------------------------------------------------------------- Key: JBMESSAGING-1152 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1152 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: Stable branch This may lessen the likelihood of deadlocks especially on sql server. Same issue may apply on other DBs too... need to investigate and change default DB config as appropriate -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-305) annotations not found for non-generic implementations of generic interface methods

by Havoc Pennington (JIRA)

annotations not found for non-generic implementations of generic interface methods ---------------------------------------------------------------------------------- Key: JBAOP-305 URL: http://jira.jboss.com/jira/browse/JBAOP-305 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Havoc Pennington I'm not sure if this is an AOP problem or a how-jboss-is-using-AOP-on-EJB3-session-beans problem, but I'll file it here to start. The original issue is TransactionAttribute(NEVER) being ignored on certain session bean methods, the test case / details on that are in this list post: http://groups.google.com/group/mugshot/browse_thread/thread/bc43e0dd34c8c... I made an AOP test case that either shows an AOP problem or shows a way jboss could easily misuse AOP. In the AOP test case, If there is an interface Foo<T> with method frobate(T t), then you look that up in AOP as resolveAnnotation("frobate", new Class[] { Object.class }) But if you implement that interface ("class FooImpl implements Foo<Double>") then you have to look that up in AOP as resolveAnnotation("frobate", new Class[] { Double.class }) - looking it up with the erasure (Object.class arg) will not work, it returns null for the annotation. So if someone were iterating over methods in the interface, looking each one up on the implementing class, they would not get the annotation for any generic methods in the interface implemented in the class. The case that's going wrong in EJB3 is a little bit more complicated, so maybe there is some attempt at handling this that isn't catching all the cases. It looks like further investigation requires messing with jboss TxInterceptor etc. itself, which is a little bit more than I think I can bite off, but hopefully this info is a helpful start. Thanks -- 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

17 years, 1 month

4
13
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1353) Captcha support

by Julien Viet (JIRA)

Captcha support --------------- Key: JBPORTAL-1353 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1353 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.8 Final -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1808) Enhance the usability for "Window name" under Content definition uder layout config

by Wesley Hales (JIRA)

Enhance the usability for "Window name" under Content definition uder layout config ----------------------------------------------------------------------------------- Key: JBPORTAL-1808 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1808 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales Fix For: 2.6.4 Final Possibly supply a better default id for the portlet if name is not entered.... or just enhance usability -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4937) EJB3 testsuite doesn't complete due to server start/stop issues

by Dimitris Andreadis (JIRA)

EJB3 testsuite doesn't complete due to server start/stop issues --------------------------------------------------------------- Key: JBAS-4937 URL: http://jira.jboss.com/jira/browse/JBAS-4937 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Test Suite Reporter: Dimitris Andreadis Assigned To: Carlo de Wolf Priority: Critical Fix For: JBossAS-5.0.0.Beta3 We see server start-up/stop issues that doen't let the ejb3 testsuite complete: http://dev45.qa.atl.jboss.com:8585/hudson/view/EJB3/job/ejb3-head-testsui... test-with-jvmargs: [delete] Deleting: /qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/ejb3/output/log/test.log [server:stop] Shutting down server: all [server:stop] Shutting down server: /qa/tools/opt/jdk1.5.0_12/bin/java -cp /qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/build/output/jboss-5.0.0.Beta3/bin/shutdown.jar:/qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/build/output/jboss-5.0.0.Beta3/client/jbossall-client.jar:/qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/build/output/jboss-5.0.0.Beta3/client/jboss-common.jar org.jboss.Shutdown --server jnp://localhost:1099 --shutdown [server:stop] shutdownTimeout will be=45 [server:stop] Failed to shutdown server "all" before timeout. Destroying the process. Overriding previous definition of reference to jboss.test.classpath init: entity-tests: BUILD FAILED /qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/ejb3/build-test.xml:4322: The following error occurred while executing this line: /qa/services/hudson/hudson_workspace/workspace/ejb3-head-testsuite/trunk/ejb3/build-test.xml:4696: Error starting server "all": Found a process already listening on:http://localhost:8080 or jnp://localhost:1099 Also: http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/140/console ssl-advanced-test: [echo] creating ejb3-ssl-advanced config [copy] Copying 378 files to http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/build/ou... [copy] Copied 101 empty directories to 1 empty directory under http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/build/ou... [echo] Overwriting config descriptors [copy] Copying 2 files to http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/build/ou... [echo] Will start the jboss instance 127.0.0.1 with ejb3-ssl-advanced, dist=http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/build/output/jboss-5.0.0.Beta3 [echo] Waiting for 127.0.0.1 to start (max wait 120 seconds)... BUILD FAILED http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/ejb3/bui... :4324: The following error occurred while executing this line: http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/ejb3/bui... :4896: The following error occurred while executing this line: http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_TRUNK/ws/trunk/ejb3/bui... :92: Timeout waiting for nodes to start -- 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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4975) Usage of read-ahead on-find with entity beans containing binary attributes (mapped to BLOB, VARBINAR, ...) breaks eager loading.

by Rothe Marco (JIRA)

Usage of read-ahead on-find with entity beans containing binary attributes (mapped to BLOB, VARBINAR, ...) breaks eager loading. -------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4975 URL: http://jira.jboss.com/jira/browse/JBAS-4975 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.2.2.GA Reporter: Rothe Marco Assigned To: Alexey Loubyansky I' ve found out that using the read ahead strategy "on-find" on an EJB2 entity bean which contains at least one binary persistent attribute (e.g public abstract byte[] getBinaryImage();) can break the eager loading of attributes causing "strange" exceptions. It is related to the fix of issue http://jira.jboss.org/jira/browse/JBAS-3800. This fix brought in the following code to the JDBCEJBQLQuery.java // exclude non-searchable columns if distinct is used if(compiler.isSelectDistinct()) { boolean[] mask = getEagerLoadMask(); JDBCFieldBridge[] tableFields = selectEntity.getTableFields(); for(int i = 0; i < tableFields.length; ++i) { if(mask[i] && !tableFields[i].getJDBCType().isSearchable()) { mask[i] = false; } Manipulation of mask[i] has the side effect to be visible on ALL finders defined for entity because the mask array is hold by JDBCEntityBridge and shared through all JDBCAbstractQueryCommand instances referencing to this JDBCEntityBridge as selectEntity. Executing an non distinct query on the bean can cause calls with wrong parameters to the method loadArgumentResults in JDBCAbstractQueryCommand.EagerCollectionFactory at line 756 and the following. JDBCFieldBridge[] tableFields = selectEntity.getTableFields(); for(int i = 0; i < eagerLoadMask.length; i++) { if(eagerLoadMask[i]) { JDBCFieldBridge field = tableFields[i]; ref[0] = null; // read the value and store it in the readahead cache index = field.loadArgumentResults(rs, index, ref); if(addPk) { selectReadAheadCache.addPreloadData(curPk, field, ref[0]); } } } Depending on the order of declaring the ejb-find methods for the entity the sql-string of an JDBCAbstractQueryCommand instance maybe compiled before the mask array is changed (by compiling an dictinct-query). In such cases the jdbc-resultset contains the binary column but the if-statement if(eagerLoadMask[i]) skip to load it into the JDBCFieldBridge object. An increment on the index variable (which point to the position to process next from the resultset) is skipped too. Processing the following result set columns cause errors because now JDBC-type at position index does not match the JDBCFieldBridge at tableFields[i]. -- 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

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-188) Incomplete Deployment calculation should be done upfront

by Adrian Brock (JIRA)

Incomplete Deployment calculation should be done upfront -------------------------------------------------------- Key: JBMICROCONT-188 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-188 Project: JBoss MicroContainer Issue Type: Task Reporter: Adrian Brock Fix For: JBossMC-2.0.0.GA Some of the calculation of the IncompleteDeploymentException is done in the exception class itself when it should be done in the Incomplete processing upfront. -- 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

17 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-183) ManifestDeployer has a TODO relating to VFS snapshot update

by Adrian Brock (JIRA)

ManifestDeployer has a TODO relating to VFS snapshot update ----------------------------------------------------------- Key: JBMICROCONT-183 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-183 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC_2_0_0_CR1 Ales, you added this comment @Override protected T parse(VFSDeploymentUnit unit, VirtualFile file, T root) throws Exception { // todo - update once we have new vfs snapshot InputStream is = SecurityActions.openStream(file); Manifest manifest; try { manifest = new Manifest(is); } finally { try { is.close(); } catch (Exception ignored) { } } return createMetaData(manifest); } -- 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

17 years, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007