November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3126) Add tests for org.jboss.varia.scheduler facility

by Elias Ross (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3126?page=comments#action_12346247 ] Elias Ross commented on JBAS-3126: ---------------------------------- There is a org.jboss.test.util.test.SchedulerUnitTestCase which does deploy a org.jboss.varia.scheduler.Scheduler , but there doesn't seem to be any verification that the timer actually is working. Since I'm working on consolidating and testing some other timer thread stuff (javax.management.Timer) in JBAS-2719, I'll take this issue on. > Add tests for org.jboss.varia.scheduler facility > ------------------------------------------------ > > Key: JBAS-3126 > URL: http://jira.jboss.com/jira/browse/JBAS-3126 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Elias Ross > Fix For: JBossAS-4.2.0.CR1 > > > We have zero tests for the scheduler stuff, so add this task as a reminder. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2719) JBoss server threads should have useful names

by Elias Ross (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2719?page=all ] Elias Ross reassigned JBAS-2719: -------------------------------- Assignee: Elias Ross > JBoss server threads should have useful names > --------------------------------------------- > > Key: JBAS-2719 > URL: http://jira.jboss.com/jira/browse/JBAS-2719 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.3 Final > Reporter: Elias Ross > Assigned To: Elias Ross > Attachments: timer-use.txt > > > Most threads do have assigned names. > However, here is a list of thread dumps where they don't appear: > "Thread-3" daemon prio=1 tid=0x9e658538 nid=0x7f9b waiting on condition [9de16000..9de16878] > at java.lang.Thread.sleep(Native Method) > at org.jboss.console.plugins.AOPLister$1.run(AOPLister.java:869) > at java.lang.Thread.run(Thread.java:534) > "Thread-10" daemon prio=1 tid=0x080ce940 nid=0x7f9b in Object.wait() [9c45a000..9c45a878] > at java.lang.Object.wait(Native Method) > - waiting on <0xa5fd77d0> (a org.jboss.mx.util.RunnableScheduler) > at org.jboss.mx.util.RunnableScheduler.waitOutstanding(RunnableScheduler.java:202) > - locked <0xa5fd77d0> (a org.jboss.mx.util.RunnableScheduler) > at org.jboss.mx.util.RunnableScheduler.run(RunnableScheduler.java:96) > at java.lang.Thread.run(Thread.java:534) > There are also a few created java.util.Timer threads, with no name, but these may belong to my own application. I'm attaching a "grep" for this class for reference. > It's useful to be able to know which system component a JBoss thread originates from. This would be a separate documentation step. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3126) Add tests for org.jboss.varia.scheduler facility

by Elias Ross (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3126?page=all ] Elias Ross reassigned JBAS-3126: -------------------------------- Assignee: Elias Ross > Add tests for org.jboss.varia.scheduler facility > ------------------------------------------------ > > Key: JBAS-3126 > URL: http://jira.jboss.com/jira/browse/JBAS-3126 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Elias Ross > Fix For: JBossAS-4.2.0.CR1 > > > We have zero tests for the scheduler stuff, so add this task as a reminder. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-115) XTS trailmap talks about webMethods only deployment

by Mark Little (JIRA)

XTS trailmap talks about webMethods only deployment --------------------------------------------------- Key: JBTM-115 URL: http://jira.jboss.com/jira/browse/JBTM-115 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, WS-T Implementation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 -- 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

19 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3636) Port HASingletonElectionPolicy to Branch_4_0

by Brian Stansberry (JIRA)

Port HASingletonElectionPolicy to Branch_4_0 -------------------------------------------- Key: JBAS-3636 URL: http://jira.jboss.com/jira/browse/JBAS-3636 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Alex Fu Fix For: JBossAS-4.0.6.CR1 -- 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

19 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-166) The modified jar files for 4.0.3SP1 and 4.0.4GA should be added into the source repository

by Kevin Conner (JIRA)

The modified jar files for 4.0.3SP1 and 4.0.4GA should be added into the source repository ------------------------------------------------------------------------------------------ Key: JBTM-166 URL: http://jira.jboss.com/jira/browse/JBTM-166 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 There are a number of jars which are required for correct operation in JBoss 4.0.3SP1 and 4.0.4GA. Currently these are not under source control. -- 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

19 years, 6 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBAS-3183) Integration with WebSphere MQ 5.x

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12346238 ] Weston Price commented on JBAS-3183: ------------------------------------ I believe we should put this only on 4.2. It's fairly significant change that really doesn't warrant being fixed in a SP release. > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Critical > Fix For: JBossAS-4.2.0.CR1 > > Attachments: mq-trace.jar, mq-xa.zip > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-165) webservice.xml for the XTS demo application should have QNames for the wsdl-port elements

by Kevin Conner (JIRA)

webservice.xml for the XTS demo application should have QNames for the wsdl-port elements ----------------------------------------------------------------------------------------- Key: JBTM-165 URL: http://jira.jboss.com/jira/browse/JBTM-165 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 The values in the wsdl-port elements are unqualified, they should be qualified. -- 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

19 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3805) Validation problem with jboss-web_4_0.dtd's replication-field-batch-mode element

by Alex Fu (JIRA)

Validation problem with jboss-web_4_0.dtd's replication-field-batch-mode element -------------------------------------------------------------------------------- Key: JBAS-3805 URL: http://jira.jboss.com/jira/browse/JBAS-3805 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.GA Reporter: Alex Fu Assigned To: Alex Fu Priority: Minor Fix For: JBossAS-4.0.6.CR1 When running Sun's msv XML validator against jboss-web_4_0.dtd that is shipped with 4.0.5.GA, it reports: element "false" is not defined. 521(a)jboss-web_4_0.dtd element "true" is not defined. 521(a)jboss-web_4_0.dtd Reason: The DTD has the following line: <!ELEMENT replication-field-batch-mode (true|false)> I guess that we want an enumerated list. However, DTD only allows attribute to have enumerated list, not element. So, the above line is actually saying that replication-field-batch-mode contains two elements: true and false (not literally). Thus the validator complains about missing the definitions for true and false. Changing the above line into the following fixes the problem: <!ELEMENT replication-field-batch-mode (#PCDATA)> It seems all other validators are OK with it, except Sun msv. -- 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

19 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3820) JaccAuthorizationRealm doesn't support the allRolesMode

by Roland R?z (JIRA)

JaccAuthorizationRealm doesn't support the allRolesMode ------------------------------------------------------- Key: JBAS-3820 URL: http://jira.jboss.com/jira/browse/JBAS-3820 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Reporter: Roland R?z Assigned To: Scott M Stark Priority: Minor The allRolesMode feature is described in http://jira.jboss.com/jira/browse/JBAS-2926. In the server.xml the org.jboss.web.tomcat.security.JaccAuthorizationRealm is documented to provide an attribute named allRolesMode. The attribute is inherited from the parent class JbossSecurityMgrRealm but this attribute has no meaning for JaccAuthorizationRealm. I know it is not easy to provide this features for jacc but at least the xml comment has to be fixed and it has to be mentioned that this feature is not possible with jacc. I have posted in http://jira.jboss.com/jira/browse/JBAS-1824 (JACC: <role-name>*</role-name> in web.xml) a possible solution as a comment. Please take also a look a that when fixing this issue. -- 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

19 years, 6 months

1
0
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 November 2006