January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3582) Get the ejb3-4.0 testsuite passing

by Dimitris Andreadis (JIRA)

Get the ejb3-4.0 testsuite passing ---------------------------------- Key: JBAS-3582 URL: http://jira.jboss.com/jira/browse/JBAS-3582 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Bill Burke Fix For: JBossAS-4.0.5.CR1 There are currenlty 28 failures -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-3901) Get the 4.2-compatibility tests passing

by Dimitris Andreadis (JIRA)

Get the 4.2-compatibility tests passing --------------------------------------- Key: JBAS-3901 URL: http://jira.jboss.com/jira/browse/JBAS-3901 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3855) JBosses org.jboss.invocation.InvocationStatistics are not serializable and therfore cant be queried by twiddle.sh

by Ramon Grunder (JIRA)

JBosses org.jboss.invocation.InvocationStatistics are not serializable and therfore cant be queried by twiddle.sh ----------------------------------------------------------------------------------------------------------------- Key: JBAS-3855 URL: http://jira.jboss.com/jira/browse/JBAS-3855 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Ramon Grunder Assigned To: Scott M Stark here is a sample call including the stack trace which describes the error: $ twiddle.sh -s jnp://localhost:1099 get jboss.j2ee:service=EJB,jndiName=ejb/Dummy InvokeStats 13:51:56,120 ERROR [Twiddle] Exec failed java.io.NotSerializableException: org.jboss.invocation.InvocationStatistics at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) ... -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3800) EJBQLToSQL92Compiler should use only searchable columns with DISTINCT

by Alexey Loubyansky (JIRA)

EJBQLToSQL92Compiler should use only searchable columns with DISTINCT --------------------------------------------------------------------- Key: JBAS-3800 URL: http://jira.jboss.com/jira/browse/JBAS-3800 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Currently it selects all columns which causes errors since, e.g. BLOBs are not comparable or searchable and, hence, can't be used with distinct. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-937) Benchmark VersionAwareMarshaller

by Galder Zamarreno (JIRA)

Benchmark VersionAwareMarshaller -------------------------------- Key: JBCACHE-937 URL: http://jira.jboss.com/jira/browse/JBCACHE-937 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Galder Zamarreno Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 Benchmark VersionAwareMarshaller to make it more performant. There's already a unit test to use it as base: VersionAwareMarshallerPerfTest. It should probably make comparison failures based on results from different marshalling methods, i.e, if difference bigger than x, fail. Also add marshalling different types of objects. Potential performance improvements: - Using similar techniques as used in ExposedByteArrayOutputStream (JGroups) for VAM? Needs profiling to determine effect. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3975) support value classes in EJBQLToSQL92Compiler

by Alexey Loubyansky (JIRA)

support value classes in EJBQLToSQL92Compiler --------------------------------------------- Key: JBAS-3975 URL: http://jira.jboss.com/jira/browse/JBAS-3975 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2 The EJBQLToSQL92Compiler doesn't value classes in paths and as parameters. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3993) Test suite should use client libraries for tests' classpaths

by Ryan Campbell (JIRA)

Test suite should use client libraries for tests' classpaths ------------------------------------------------------------ Key: JBAS-3993 URL: http://jira.jboss.com/jira/browse/JBAS-3993 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Ryan Campbell Assigned To: Pavel Tsekov Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 Modify the tests.classpath in the testsuite/build.xml to use only (as far as possible) those jars under build/output/jboss-xxx/client/*.jar. -- 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, 3 months

4
26
0 / 0

[JBoss JIRA] Created: (JBAS-3932) Security Deployer to manage the JACC metadata

by Anil Saldhana (JIRA)

Security Deployer to manage the JACC metadata --------------------------------------------- Key: JBAS-3932 URL: http://jira.jboss.com/jira/browse/JBAS-3932 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta2 Basically there is a need to maintain PolicyConfiguration objects for individual JEE components in a deployment and then link them via graph. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3792) Better error reporting when messages "mysteriously" vanish

by Adrian Brock (JIRA)

Better error reporting when messages "mysteriously" vanish ---------------------------------------------------------- Key: JBAS-3792 URL: http://jira.jboss.com/jira/browse/JBAS-3792 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Fix For: JBossAS-4.0.6.GA It is commonly the case that people try to run two instances of JBossMQ against the same database tables. This can lead to errors like the ones in the parent task or a similar message in the delete when doing acknowledgements. These error messages need improving and also give a hint to the possible reasons, e.g. 1) competing JBossMQs trying to share the same database 2) trying to use a replicating database that does not support synchronous replication (i..e there is a delay in a row getting written to one database before it appears in the other database) The parent issue's error message belongs in org.jboss.mq.pm.jdbc2.PersistenceManager public SpyMessage loadFromStorage(MessageReference messageRef) throws JMSException { ... rs = stmt.executeQuery(); if (rs.next()) return extractMessage(rs); + else throw new JMSException("Unable to load message " + messageRef + " from storage, are you trying to share database tables between JBossMQ instances? Are you using a replicating database that does not support synchronous replication?"); - return null; -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.

by Phillip Thurmond (JIRA)

EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster. ---------------------------------------------------------------------------------------------------------- Key: JBCLUSTER-155 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: Q4Y6 Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5 Reporter: Phillip Thurmond Assigned To: Brian Stansberry Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ . I create two identical server configurations for the ejb3demo application from the all config. I enable query caching in persistence.xml. To reproduce: 1. start up first instance, place order. 2. start up second instance, watch for cluster notification and join. Place order on second and first instances. 3. bring down first instance, watch for cluster removal messages on second host. Place order and receive an EJBTransactionRolledBackException in the browser. No stack traces or error messages are logged on the console. -- 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, 3 months

4
6
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 January 2007