[JBoss JIRA] Created: (JGRP-1002) Merge: make the coordinator remain the same if possible after a merge
by Bela Ban (JIRA)
Merge: make the coordinator remain the same if possible after a merge
---------------------------------------------------------------------
Key: JGRP-1002
URL: https://jira.jboss.org/jira/browse/JGRP-1002
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.0
When we have {C, A, B} and split into {C,A} and {B}, then a merge will produce {A,B,C}. Therefore the coord is moved from C to A. For certain apps, e.g. JBoss singletons, this is not good, as we're moving the singleton services from a perfectly healthy node to a different node.
GOAL: come up with a deterministic policy of picking a coord such that we minimize coord switching if the existing coord is still member of the cluster.
This depends on or is related to the flexible coord pick policy JIRA issue
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBAS-7965) jta resource recovery problem
by Nicolae Petridean (JIRA)
jta resource recovery problem
-----------------------------
Key: JBAS-7965
URL: https://jira.jboss.org/jira/browse/JBAS-7965
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager (Arjuna)
Reporter: Nicolae Petridean
Assignee: Jonathan Halliday
Priority: Critical
Hi all,
i noticed that there is some problems with the transaction recovery in JBOSS.
When a number of warnings like this : "WARN oggerI18N om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa Could not find new XAResource to use for recovering non-serializable XAResource" appear , at some time the exceptions mechanism is affected (the exceptions are not thrown anymore). If the application uses timers those are also blocked (the timeouts dont appear anymore), it seems that the transcations that are not finished are blocking the timers. Why aren't those transactions just ended after some specific time ? Or is there another way to deal with the situation ?
Thanks in advance, Nicu
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBAS-6532) TCLFilter doesn't work in jboss 5 with war's in any documented way
by robert lazarski (JIRA)
TCLFilter doesn't work in jboss 5 with war's in any documented way
------------------------------------------------------------------
Key: JBAS-6532
URL: https://jira.jboss.org/jira/browse/JBAS-6532
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.0.0.GA
Environment: jdk 6, linux
Reporter: robert lazarski
Assignee: Scott M Stark
Reading this doc:
http://www.jboss.org/community/docs/DOC-12203
Indicates a *-exp.war syntax is needed for TCLFilter war use, but there are no files of that type on my system running jboss 5. I've tried all the possible combinations I can think of, posted the problem to the forum, and the result is always that the file sizes and contents of the log files generated are exactly the same for the different war's, ie, no separated content. Here's my current config:
<appender name="penguinLog" class="org.apache.log4j.FileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
<param name="Append" value="false"/>
<param name="File" value="${jboss.server.home.dir}/log/penguinLog.log"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/>
</layout>
<filter class="org.jboss.logging.filter.TCLFilter">
<param name="AcceptOnMatch" value="true"/>
<param name="DeployURL" value="penguin"/>
</filter>
</appender>
<appender name="wtfLog" class="org.apache.log4j.FileAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
<param name="Append" value="false"/>
<param name="File" value="${jboss.server.home.dir}/log/wtfLog.log"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/>
</layout>
<filter class="org.jboss.logging.filter.TCLFilter">
<param name="AcceptOnMatch" value="true"/>
<param name="DeployURL" value="wtf-exp.war"/>
</filter>
</appender>
<root>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
<appender-ref ref="penguinLog"/>
<appender-ref ref="wtfLog"/>
</root>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months