February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2251) Fix JBoss Cache / AS integration issues

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2251?page=all ] Dimitris Andreadis updated JBAS-2251: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Unresolved issues to CR1. > Fix JBoss Cache / AS integration issues > --------------------------------------- > > Key: JBAS-2251 > URL: http://jira.jboss.com/jira/browse/JBAS-2251 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > > The JBossCache standalone build includes: > jboss-aop.jar (ok - should be standalone project) > jboss-common.jar (ok - should be standalone project(s)) > jboss-j2ee.jar (TransactionManager interfaces) > jboss-jmx.jar (only for JBossNotificationBroadcasterSupport leaking from jboss-system.jar?) > jboss-minimal.jar (for MarshalledValue, etc.) > jboss-system.jar (for ServiceMBeanSupport) > We are heading for a fall on this (not to mention the other thirdparty jars that could get out-of-sync) > Some of this will probably have to wait until we have the proper federated build. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2149) ByValueContainerInvoker

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2149?page=all ] Dimitris Andreadis updated JBAS-2149: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Unresolved issues to CR1. > ByValueContainerInvoker > ----------------------- > > Key: JBAS-2149 > URL: http://jira.jboss.com/jira/browse/JBAS-2149 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Fix For: JBossAS-5.0.0.CR1 > > > Remove the use of ByValueInvokerInterceptor from the testsuite. > This was deprecated in JBoss4 and removed in JBoss5, it should be using the MarshalledInvokerInterceptor. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-647) Potentially Meaningless InterruptedIOException Can Be Logged Repeatedly

by Jimmy Wilson (JIRA)

Potentially Meaningless InterruptedIOException Can Be Logged Repeatedly ----------------------------------------------------------------------- Key: JGRP-647 URL: http://jira.jboss.com/jira/browse/JGRP-647 Project: JGroups Issue Type: Bug Affects Versions: 2.6, 2.5.1, 2.5, 2.4.1 SP4, 2.4.1 SP3 Reporter: Jimmy Wilson Assigned To: Bela Ban Priority: Minor Fix For: 2.4.2, 2.7 TP.down doesn't catch/handle the InterruptedIOException that can be thrown from the underlying send call when interrupted: try { if(use_outgoing_packet_handler) outgoing_queue.put(msg); else send(msg, dest, multicast); } catch(QueueClosedException closed_ex) { } catch(InterruptedException interruptedEx) { } catch(Throwable e) { if(log.isErrorEnabled()) { String dst=msg.getDest() == null? "null" : msg.getDest().toString(); log.error("failed sending message to " + dst + " (" + msg.getLength() + " bytes)", e.getCause()); } } This can lead to it being logged repeatedly at the ERROR level: 2007-11-14 10:02:30,040 ERROR -> (PingSender) [UDP] failed sending message to null (0 bytes) java.io.InterruptedIOException: operation interrupted at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:612) at org.jgroups.protocols.UDP._send(UDP.java:316) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:286) at org.jgroups.protocols.TP.doSend(TP.java:937) at org.jgroups.protocols.TP.send(TP.java:926) at org.jgroups.protocols.TP.down(TP.java:712) at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499) at org.jgroups.stack.Protocol.passDown(Protocol.java:533) at org.jgroups.protocols.PING.sendMcastDiscoveryRequest(PING.java:214) at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:208) at org.jgroups.protocols.PingSender.run(PingSender.java:59) at java.lang.Thread.run(Thread.java:595) 2.5/2.6 don't handle the InterruptedIOException either, but since this was reported with EAP 4.2 (JGroups 2.4.1.SP3), I 'd like to see it in 2.4.2 if possible. That way, it can make it into a 4.2/4.3 EAP CP. -- 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

18 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAOP-524) Annotation processing is slow

by Kabir Khan (JIRA)

Annotation processing is slow ----------------------------- Key: JBAOP-524 URL: http://jira.jboss.com/jira/browse/JBAOP-524 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR7 -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1287) CacheLoader load operations nnot deserialize types not visible to cache

by Brian Stansberry (JIRA)

CacheLoader load operations nnot deserialize types not visible to cache ----------------------------------------------------------------------- Key: JBCACHE-1287 URL: http://jira.jboss.com/jira/browse/JBCACHE-1287 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.1.0.CR3 Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Cache loaders no longer are able to deserialize types not visible to the cache's classloader during load operations. New test org.jboss.test.marshall.CacheLoaderMarshallingTest shows the issue. When trying to deserialize, the cache loaders are calling into the marshalling code. The marshalling code *always* sets the TCCL to the cache's class loader. So, if a caller app properly sets its TCCL to one that can load the app's custom types, tje marshalling code will undo this. If region-based marshalling is enabled, the correct classloader still isn't assigned, because the serialized data does not include the FQN information needed to find the correct region. So again the cache's class loader is used. This is all a side effect of using the replication marshalling code for cache loader ops, which are somewhat different use cases. When deserializing a replication message, the JGroups thread is unlikely to have a TCCL that has visibility to the needed types. Cache loader load operations usually have the correct TCCL in place. -- 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

18 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1451) LHS expression comparing a Boolean to a String does not fail but always returns true

by Len Carlsen (JIRA)

LHS expression comparing a Boolean to a String does not fail but always returns true ------------------------------------------------------------------------------------ Key: JBRULES-1451 URL: http://jira.jboss.com/jira/browse/JBRULES-1451 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.4, 4.0.3 Environment: Eclipse IDE Version: 3.3.0 Build id: M20070921-1145 Windows XP Professional SP2 Reporter: Len Carlsen LHS expression comparing a Boolean to a String does not fail but always returns true. Example: -------------------------------------------------------------------------------------------------------------------------- Modified the Drools HelloWorldExample and changed the status from an int to a boolean. import org.drools.examples.HelloWorldExample.Message; rule "Hello World" when m : Message( status == "hello", message : message ) then System.out.println( message ); end public static class Message { public static final boolean HELLO = false; public static final boolean GOODBYE = true; private String message; private Boolean status; public Message() {} public String getMessage() { return this.message; } public void setMessage(final String message) { this.message = message; } public boolean getStatus() { return this.status; } public void setStatus(final boolean status) { this.status = status; } } final Message message = new Message(); message.setMessage( "Hello World" ); message.setStatus( Message.HELLO ); final StatefulSession session = ruleBase.newStatefulSession(); session.insert( message ); session.fireAllRules(); -- 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

18 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-679) Member propagates non-existing coordinator

by Peter Fuchs (JIRA)

Member propagates non-existing coordinator ------------------------------------------ Key: JGRP-679 URL: http://jira.jboss.com/jira/browse/JGRP-679 Project: JGroups Issue Type: Bug Affects Versions: 2.2.8 Environment: Oracle Application Server Cluster running application using JGroups Reporter: Peter Fuchs Assigned To: Bela Ban Priority: Critical Our application is running on a clustered application server environment (Oracle AS 10gR2) with 9 application instances in total. We are using JGroups for keeping the object caches of all application instances in sync. >From time to time we encounter the problem that our application cannot be started and seems to "hang". After setting the JGroups logger to DEBUG we could see that it was JGroups that was trying to connect to a coordinator that did not exist anymore. After some investigation we found out that there was one running instance propagating a coordinator that did not exist any longer. The only solution in that case was to restart the instance that was propagating the wrong coordinator address. As the version we currently use (2.2.8) is quite old I checked Jira for fixes regarding this issue but could not really identify this specific behaviour (maybe due to my poor knowledge about the internals of JGroups). We are planning to use JGroups V2.4.1(SP4) in our future software releases (as we are bound to JDK 1.4.2) but would like to know if this issue has been fixed in that version. Please find attached an example log file excerpt. -- 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

18 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4605) JSP compiler won't compile JDK 1.5 source

by Stan Silvert (JIRA)

JSP compiler won't compile JDK 1.5 source ----------------------------------------- Key: JBAS-4605 URL: http://jira.jboss.com/jira/browse/JBAS-4605 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Stan Silvert Assigned To: Stan Silvert >From the comments in conf/web.xml, it looks like the JSP servlet should detect the JVM version and then set compilerTargetVM and compilerSourceVM automatically. This is not working as a JSP with JDK 1.5 source will not compile. -- 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

18 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1231) Messaging does not have a clustered-[mysql/oracle/postgres] configuration

by Tom Cunningham (JIRA)

Messaging does not have a clustered-[mysql/oracle/postgres] configuration ------------------------------------------------------------------------- Key: JBMESSAGING-1231 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1231 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.1.beta1 Reporter: Tom Cunningham Assigned To: Tim Fox The messaging docs say to go into docs/examples/jms/ and grab the clustered-[mysql/oracle/postgres] configuration for your database, but the only configuration available in that directory is clustered-hsqldb. The messaging docs also say that in clustering, hsqldb is the one configuration you don't want to use - so it would be good to offer officially blessed files for those databases. -- 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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-651) JChannel: set auto_reconnect and auto_getstate to true by default

by Bela Ban (JIRA)

JChannel: set auto_reconnect and auto_getstate to true by default ----------------------------------------------------------------- Key: JGRP-651 URL: http://jira.jboss.com/jira/browse/JGRP-651 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Trivial Fix For: 2.4.2, 2.5.2, 2.6.2, 2.7 -- 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

18 years, 5 months

1
2
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 February 2008