April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-25) Saving processdefinition should add problem markers and entries in problem view if any problems occur

by Koen Aers (JIRA)

Saving processdefinition should add problem markers and entries in problem view if any problems occur ----------------------------------------------------------------------------------------------------- Key: GPD-25 URL: http://jira.jboss.com/jira/browse/GPD-25 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-827) Define a management interface for JBoss Remoting

by David Lloyd (JIRA)

Define a management interface for JBoss Remoting ------------------------------------------------ Key: JBREM-827 URL: http://jira.jboss.com/jira/browse/JBREM-827 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 -- 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, 3 months

2
20
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-130) Array part of the Javassist reflection implementation is broken

by Adrian Brock (JIRA)

Array part of the Javassist reflection implementation is broken --------------------------------------------------------------- Key: JBMICROCONT-130 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-130 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Javassist is returning wrong values for interfaces of arrays and modifiers of array classes. These errors have been suppressed in org.jboss.test.classinfo.test.JavassistArrayUnitTestCase by subclassling the tests to do nothing: protected void assertInterfaces(Class<?> clazz, ClassInfo classInfo) throws Throwable { // TODO this is broken for javassist } protected void assertModifiers(Class<?> clazz, ClassInfo classInfo) throws Throwable { // TODO this is broken for javassist } This needs fixing in javassist -- 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, 4 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-4963) invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA

by Galder Zamarreno (JIRA)

invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA ----------------------------------------------------------------------------------------------------------------- Key: JBAS-4963 URL: http://jira.jboss.com/jira/browse/JBAS-4963 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta3 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Exception handling is different between JRMPInvokerProxyHA and UnifiedInvokerHAProxy when it comes to, at least, calls to invocationHasReachedAServer(): 1.- JRMPInvokerProxyHA Exception handling that does not lead to invocationHasReachedAServer() being called: * java.net.ConnectException * java.net.UnknownHostException * java.rmi.ConnectException * java.rmi.ConnectIOException * java.rmi.NoSuchObjectException * java.rmi.UnknownHostException * GenericClusteringException.NO Exception handling that leads to invocationHasReachedAServer() being called: * GenericClusteringException.YES * java.rmi.ServerException * java.lang.Exception 2.- UnifiedInvokerHAProxy Exception handling that does not lead to invocationHasReachedAServer() being called: * org.jboss.remoting.CannotConnectException * GenericClusteringException.NO * java.rmi.RemoteException * java.lang.Throwable Exception handling that leads to invocationHasReachedAServer() being called: * GenericClusteringException.YES This JIRA tracks discussions to clarify the correctness of UnifiedInvokerHAProxy and any potential coding required. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5245) JBossMQ services: table creation fails with Sybase Adaptive Server Anywhere (ASA)

by Luc Texier (JIRA)

JBossMQ services: table creation fails with Sybase Adaptive Server Anywhere (ASA) --------------------------------------------------------------------------------- Key: JBAS-5245 URL: http://jira.jboss.com/jira/browse/JBAS-5245 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.2.GA Reporter: Luc Texier Assigned To: Adrian Brock the database is Sybase Adaptive Server Anywhere (ASA). The JDBC driver jConnect for JDBC 3.0 v6.0x 2008-02-14 18:25:01,640 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE TABLE dbo.JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER NULL, TXOP CHAR(1) NOT NULL, MESSAGEBLOB IMAGE NOT NULL, PRIMARY KEY (MESSAGEID, DESTINATION) ) LOCK DATAROWS com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -131: Syntax error near 'LOCK' on line 1 at com.sybase.jdbc3.tds.Tds.a(Unknown Source) at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.updateLoop(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source) at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeUpdate(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251) at org.jboss.mq.pm.jdbc2.PersistenceManager.createSchema(PersistenceManager.java:280) at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1796) Note that those issues do NOT occur when these services are connected to Adaptive Server Enterprise (ASE) Note2: internal reference Issue #162081 -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3753) HAParititonImpl implements org.jgroups.ChannelListener

by Brian Stansberry (JIRA)

HAParititonImpl implements org.jgroups.ChannelListener ------------------------------------------------------ Key: JBAS-3753 URL: http://jira.jboss.com/jira/browse/JBAS-3753 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 Currently if a JChannel is shunned and disconnects, higher level services are unaware of this and can't take any remedial action. We need to do something like implement ChannelListener so an HAPartition is aware when the events on the underlying channel occur. Then devise a scheme to propagate some of the events to user code. Preferably this will follow as much as possible the existing notification scheme; i.e. pass a new view to HAMembershipListener impls that doesn't include the current node. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-5044) Rework the JavaEE deployers to fix problems in the current implementation

by Adrian Brock (JIRA)

Rework the JavaEE deployers to fix problems in the current implementation ------------------------------------------------------------------------- Key: JBAS-5044 URL: http://jira.jboss.com/jira/browse/JBAS-5044 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-5.0.0.CR1 See the forum thread and subtasks for specific issues. -- 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, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-5046) Move code from JBossEjbParsingDeployer out of createMetaData into relevant deployers

by Adrian Brock (JIRA)

Move code from JBossEjbParsingDeployer out of createMetaData into relevant deployers ------------------------------------------------------------------------------------ Key: JBAS-5046 URL: http://jira.jboss.com/jira/browse/JBAS-5046 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2, EJB3 Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1 The processing that is now in JBossEjbParsingDeployer.createMetaData() should be moved into more relevant deployers. -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBCL-10) Document new classloader syntax

by Scott M Stark (JIRA)

Document new classloader syntax ------------------------------- Key: JBCL-10 URL: http://jira.jboss.com/jira/browse/JBCL-10 Project: JBoss ClassLoader Issue Type: Feature Request Components: Docs Affects Versions: JBossCL.2.0.0.Beta11 Reporter: Scott M Stark Fix For: JBossCL.2.0.0.CR1 We need to document the new class loader and add examples to the mc user guide. Some of the design threads related to this include: DeploymentClassLoader as a bean http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131362 ClassLoader for a subdeployment http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130518 ClassLoadingMetaData ease-of-use (this is the best discussion of the new class loader simplifed usage) http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130122 New ClassLoadING projects in MC trunk http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130223 New ClassLoader initial checkin (design discussion) http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107465 -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-139) Create a general purpose group RPC API

by Brian Stansberry (JIRA)

Create a general purpose group RPC API -------------------------------------- Key: JBCLUSTER-139 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-139 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Abstraction on top of JGroups RpcDispatcher. Start with HAPartition as a base, but minus DRM and DS. Consider what Messaging has done as well as JBCACHE-311. Consider separating the group membership API from the RPC API. RPC API would probably be a subinterface of the group membership one, as group RPC implies being aware of who the group is. This is lower priority, as, except for AS, its an internal implementation detail that can be changed. But, AS exposes HAPartition as an API for end-user code. -- 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, 4 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008