[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
[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