January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (HIBERNATE-52) HibernateMBean.SecondLevelCacheEnabled attribute ignored

by Steve Ebersole (JIRA)

HibernateMBean.SecondLevelCacheEnabled attribute ignored -------------------------------------------------------- Key: HIBERNATE-52 URL: http://jira.jboss.com/jira/browse/HIBERNATE-52 Project: Hibernate Issue Type: Bug Reporter: Steve Ebersole Assigned To: Steve Ebersole Thats because transferSettings() ignores it when transferring the properties to the Configuration. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-5016) Update docs for beta3

by Scott M Stark (JIRA)

Update docs for beta3 --------------------- Key: JBAS-5016 URL: http://jira.jboss.com/jira/browse/JBAS-5016 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Scott M Stark Assigned To: Norman Richards Priority: Blocker Fix For: JBossAS-5.0.0.Beta3 We need to update wiki/project pages for changes in beta3. -- 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
7
0 / 0

[JBoss JIRA] Created: (JBAS-5179) Expose statistic type ManagedProperty for DataSources

by Scott M Stark (JIRA)

Expose statistic type ManagedProperty for DataSources ----------------------------------------------------- Key: JBAS-5179 URL: http://jira.jboss.com/jira/browse/JBAS-5179 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service, Management services Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta4 To really complete the DataSource management view prototype we need to expose some statistic type of properties. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAS-5111) Upgrade jboss aop to 2.0.0.CRx (from 2.0.0.CR1)

by Dimitris Andreadis (JIRA)

Upgrade jboss aop to 2.0.0.CRx (from 2.0.0.CR1) ----------------------------------------------- Key: JBAS-5111 URL: http://jira.jboss.com/jira/browse/JBAS-5111 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Dimitris Andreadis Assigned To: Kabir Khan Priority: Critical Fix For: JBossAS-5.0.0.Beta4 Basically we need by Jan/18th (or earlier) a new release of jboss APO that resolves the performance problem of JBAOP-497. -- 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
14
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: (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: (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

[JBoss JIRA] Created: (JGRP-663) Multiplexer: OOB message are currently ignored

by Bela Ban (JIRA)

Multiplexer: OOB message are currently ignored ---------------------------------------------- Key: JGRP-663 URL: http://jira.jboss.com/jira/browse/JGRP-663 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Investigate whether to have OOB message bypass the multiplexer's thread pool -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-5194) DataSource connection properties should use a CompositeMetaType/CompositeValue

by Scott M Stark (JIRA)

DataSource connection properties should use a CompositeMetaType/CompositeValue ------------------------------------------------------------------------------ Key: JBAS-5194 URL: http://jira.jboss.com/jira/browse/JBAS-5194 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Scott M Stark Fix For: JBossAS-5.0.0.Beta4 The current CollectionMetaType of GenericValues is wrong for the connection properties. -- 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

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 2008