July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5728) Upgrade jboss remoting to v2.2.2.SP8 (from v2.2.2.SP5)

by Ron Sigal (JIRA)

Upgrade jboss remoting to v2.2.2.SP8 (from v2.2.2.SP5) ------------------------------------------------------ Key: JBAS-5728 URL: http://jira.jboss.com/jira/browse/JBAS-5728 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal EAP 4.2/4.3 are currently shipping with Remoting 2.2.2.SP7 and testing with 2.2.2.SP8 for the next CP releases. We could just update to 2.2.2.SP7, but I think JBREM-949 in 2.2.2.SP8 is important to JBossMessaging. Many of the other bug reports arose in support cases: JBREM-962, JBREM-965, JBREM-981 Reported by Galder: JBREM-954, JBREM-960 Reported by Ovidiu: JBREM-972, JBREM-973 ======================================================================================================== Release Notes - JBoss Remoting - Version 2.2.2.SP8 - Text format Bug * [JBREM-949] - CLONE [JBREM-947] - ConnectionValidator hangs when server dies * [JBREM-954] - InterruptedException should not be rethrown as CannotConnectionException * [JBREM-960] - Remoting configured with Servlet invoker can return misleading Exceptions when Servlet path is incorrect * [JBREM-962] - Remote classloading does not work with Isolated EARs * [JBREM-965] - Fix PortUtil.getRandomStartingPort() * [JBREM-981] - CLONE [JBREM-980] - ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator * [JBREM-1003] - Verify IPv6 addresses are handled correctly, part 2 Feature Request * [JBREM-972] - CLONE [JBREM-971] - Enhance client-side connection error handling so certain (potentially revealing) socket-related exceptins are not discarded * [JBREM-973] - CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted Release * [JBREM-948] - Release 2.2.2.SP8 Task * [JBREM-950] - Assure version compatibility with earlier versions of Remoting * [JBREM-995] - Apply unit test timing fixes * [JBREM-1001] - Update Remoting Guide * [JBREM-1002] - Allow ServerThread to keep running after SocketTImeoutException, part 2 * [JBREM-1004] - Run manual servlet unit tests -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1357) Root nodes of marshalled regions won't be loaded correclty from cache loaders

by Galder Zamarreno (JIRA)

Root nodes of marshalled regions won't be loaded correclty from cache loaders ----------------------------------------------------------------------------- Key: JBCACHE-1357 URL: http://jira.jboss.com/jira/browse/JBCACHE-1357 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP9 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Yesterday while looking at a support case, I discovered an awkward behavior when it came to root region based marshalling nodes and cache loaders. Let's say you have a cache configured with a cache loader and have a region marshaled called starting at /me. I have created an MBean so that I can register/unregister classloader and activate/deactivate the region upon deployment/undeployment of the classes I wanna put under /me. Now, let's say that I put a k,v in /me which will get stored in the cache loader. If I know touch the deployment archive to force a redeployment and check the contents of the cache, they're empty. If I try to get the k I put under /me, it'll return nothing. Why? Simple: The cache instance is configured to preload from root (/) but when the region is activated, /me node is created. When the preloading phase comes, a check is made to see whether the node needs to be loaded: private boolean mustLoad(DataNode n, Object key) { if (log.isTraceEnabled()) { log.trace("mustLoad called with key=" + key + " and datanode=" + n); } return n == null || (n.containsKey(TreeCache.UNINITIALIZED) && (key == null || !n.containsKey(key))); } The problem is that nothing will be preloaded for at least the /me node, because the node is not null, and it's not TreeCache.UNINITIALIZED. Any child nodes under the region node do not have issues like this. This is likely a bug: maybe when the region is activated, the node should probably be created as TreeCache.UNINITIALIZED? I think this would work). It's true that you could say that putting data at the root node of the region is not a good idea regardless, but I think deep down this is a bug. p.s. This is at least present in 1.4.x, need to check trunk. Manik: I agree this is a bug. Could you raise a JIRA for this? Also agree with your solution, that when a region is activated and if a node needs to be created, it should be uninitialized. If you create a unit test, could you add it to trunk as well? -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-57) Change annotated class lookup in AnnotationEnvironment

by Ales Justin (JIRA)

Change annotated class lookup in AnnotationEnvironment ------------------------------------------------------ Key: JBDEPLOY-57 URL: http://jira.jboss.com/jira/browse/JBDEPLOY-57 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.0.Beta18 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBDEPLOY-2.0.0.CR1 In order to make things fully lazy - http://jira.jboss.com/jira/browse/JBAS-5558 current classIsAnnotated method on AnnotationEnvironment is not suited for this. Changing it to look like other methods, lazy via Element interface. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-45) complete JBoss50Creator

by Alexey Loubyansky (JIRA)

complete JBoss50Creator ----------------------- Key: JBMETA-45 URL: http://jira.jboss.com/jira/browse/JBMETA-45 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: 1.0.0.CR1 Following JBMETA-20, JBoss50Creator was introduced which is supposed to parse EJB3 spec and JBoss-specific annotations and produce a merged metadata view in the form of JBoss50MetaData. -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMETA-20) Include JBoss extensions to EJB3

by Kabir Khan (JIRA)

Include JBoss extensions to EJB3 -------------------------------- Key: JBMETA-20 URL: http://jira.jboss.com/jira/browse/JBMETA-20 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Alexey Loubyansky Fix For: 1.0.0.Beta8 @Service and @Consumer are not picked up. I added testEJBExtensions to AnnotationEjb3UnitTestCase. The corresponding assertMyServiceBean() and assertMyService() methods will need tweaking to check for the real metadata. -- 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, 10 months

5
9
0 / 0

[JBoss JIRA] Updated: (JBAS-2750) Create integration tests using JBossCache and JBoss TM

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2750?page=all ] Brian Stansberry updated JBAS-2750: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-5.0.0.CR2) This should really be done in the JBC testsuite. > Create integration tests using JBossCache and JBoss TM > ------------------------------------------------------ > > Key: JBAS-2750 > URL: http://jira.jboss.com/jira/browse/JBAS-2750 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Backlog > > > Need to add integration tests that confirm that JBossCache works properly with JBoss TM as its transaction manager. The standalone cache unit tests use DummyTransactionManager, as use of JBoss TM requires the app server. Beginning with 4.0.4, the AS web-tier state replication tests also no longer use JBoss TM. > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76306 for an example of the kind of thing such tests should find. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1799) Create additional integration tests for JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1799?page=all ] Brian Stansberry updated JBAS-1799: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-5.0.0.CR2) Moving to backlog. The existent AS testsuite thoroughly exercises the API. Further improvement should be done in the JBC itself by ensuring there are tests that exercise the AS call patterns using the AS configs. > Create additional integration tests for JBossCache > -------------------------------------------------- > > Key: JBAS-1799 > URL: http://jira.jboss.com/jira/browse/JBAS-1799 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Backlog > > Original Estimate: 1 week > Remaining Estimate: 1 week > > When JBossCache module is supplied through the thirdparty jar, we will need additioanl integration testing under current AS to make sure the API is compliant. > Pieces that I can think of are: > 1. Core system classes > 2. JBossAop. This one can be more volatile. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1647) Incorrect reporting by verifier of unmatchable pattern with connective OR

by Michael Neale (JIRA)

Incorrect reporting by verifier of unmatchable pattern with connective OR ------------------------------------------------------------------------- Key: JBRULES-1647 URL: http://jira.jboss.com/jira/browse/JBRULES-1647 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Verifier Affects Versions: 5.0.0-M1 Reporter: Michael Neale Assigned To: Toni Rikkola Fix For: 5.0.0-M1 rule "Gold Discount High Priority" dialect "mvel" when customer : Customer( status > "30" && < "50" ) order : OrderHeader( customer == customer , orderPriority == "3" || == "4" ) then order.setOrderDiscount( 6.0 ); end Generates this error: Restriction LiteralRestriction from rule [Gold Discount High Priority] value '== 4' and LiteralRestriction from rule [Gold Discount High Priority] value '== 3'are in conflict. Because of this, pattern that contains them can never be satisfied. when a connective (like || ==) is used, this should not be treated as a conjunction of extra literal restrictions. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1341) Analytics fails on Inner Class Enums

by Steve Shabino (JIRA)

Analytics fails on Inner Class Enums ------------------------------------ Key: JBRULES-1341 URL: http://jira.jboss.com/jira/browse/JBRULES-1341 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0 Reporter: Steve Shabino Drools Analytics fails when flattening a condition with an inner-class enum like this: vs : WorkerStatus(type != WorkerStatus.Type.ON_JOB) NPE in PackageDescrFlattener when executing method: private void flatten(QualifiedIdentifierRestrictionDescr descr, AnalyticsComponent parent, int orderNumber) on line: restriction.setVariableId(variable.getId()); Running in the debugger proves that variable == null. One can reproduce this error by running analytics on the "dispatch" example in contrib/benchmarks -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-264) Remove the old schema binding initializer from the kernel project

by Adrian Brock (JIRA)

Remove the old schema binding initializer from the kernel project ----------------------------------------------------------------- Key: JBMICROCONT-264 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-264 Project: JBoss MicroContainer Issue Type: Sub-task Components: Deployment Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC.2.0.0.CR1 This can't be removed until aop-mc-int no longer depends upon it. Once that has been updated to jaxb, the initializer can be moved to the spring-int project, -- 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, 10 months

2
4
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 July 2008