[
https://jira.jboss.org/jira/browse/JBAS-6595?page=com.atlassian.jira.plug...
]
Scott M Stark commented on JBAS-6595:
-------------------------------------
That is causing the error you show, but that would indicate a clean build issue. The only
problem I'm seeing is that the variable counts are not reliably coming back non-zero
after doing a clean build wth the change to BaseBean to use Hashtable. I don't see any
error retrieving the values so I'll have to look into this.
org.jboss.test.profileservice.test.ServerManagedObjectsTestCase
---------------------------------------------------------------
Key: JBAS-6595
URL:
https://jira.jboss.org/jira/browse/JBAS-6595
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Shelly McGowan
Assignee: Scott M Stark
testWebConnector:
jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor
junit.framework.AssertionFailedError:
jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor
at
org.jboss.test.profileservice.test.ServerManagedObjectsTestCase.testWebConnector(ServerManagedObjectsTestCase.java:227)
testWebConnectorPool:
jboss.web:name=http-127.0.0.1-8080,type=ThreadPool
junit.framework.AssertionFailedError: jboss.web:name=http-127.0.0.1-8080,type=ThreadPool
at
org.jboss.test.profileservice.test.ServerManagedObjectsTestCase.testWebConnectorPool(ServerManagedObjectsTestCase.java:252)
--
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