[JBoss JIRA] (WFLY-3285) Domain directory properties only work on specific operating systems
by Dennis Reed (JIRA)
Dennis Reed created WFLY-3285:
---------------------------------
Summary: Domain directory properties only work on specific operating systems
Key: WFLY-3285
URL: https://issues.jboss.org/browse/WFLY-3285
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Scripts
Affects Versions: 8.1.0.CR1
Reporter: Dennis Reed
Assignee: Tomaz Cerar
domain.sh only parses -Djboss.domain.base.dir, -Djboss.domain.log.dir, and -Djboss.domain.config.dir (used to set -Dlogging.configuration and -Dorg.jboss.boot.log.file) on Linux, Solaris, and OS X.
It does not attempt to parse these (and therefore does not set the logging properties correctly) on any other OS, including AIX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (WFLY-3226) Add test cases to verify LDAP caching on security realms.
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3226?page=com.atlassian.jira.plugin.... ]
Martin Choma edited comment on WFLY-3226 at 4/25/14 2:35 AM:
-------------------------------------------------------------
Hi,
I have solved the problem. In documentation there is missing initialization part. Now I can proceed to writing tests.
I wonder is there any info regarding LDAP caching of security realms? In particular i am interested when is record cached. When is record invalidated from cache?
Can you please describe closer your opinion of solution. Should I created new test suite, let say LDAPCachingTestSuite or use some existing one. Should I register interceptor only for Caching tests or can it be there for other tests as well.
Thanx,
Martin
was (Author: friler):
Hi,
I have solved the problem. In documentation there is missing initialization part. Now I can proceed to writing tests.
I wonder is there any info regarding LDAP caching of security realms? In particular i am interested when is record cached. When is record invalidated from cache?
Thanx,
Martin
> Add test cases to verify LDAP caching on security realms.
> ---------------------------------------------------------
>
> Key: WFLY-3226
> URL: https://issues.jboss.org/browse/WFLY-3226
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management, Test Suite
> Reporter: Darran Lofthouse
> Fix For: Awaiting Volunteers
>
>
> The existing test cases are based on a statically defined set of LDIFs, testing of caching could consider a couple of options: -
> 1 - Interceptors within ApacheDS to verify if calls hit the directory.
> 2 - Updates to the directory that would affect the outcome of tests if there is a cache hit, tests can then be repeated with and without clearing the cache.
> Note: It would be beneficial for this to use different users and groups and maybe even different partitions so that test ordering does not affect the outcome if changes are made to the directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (WFLY-3226) Add test cases to verify LDAP caching on security realms.
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3226?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-3226:
------------------------------------
Hi,
I have solved the problem. In documentation there is missing initialization part. Now I can proceed to writing tests.
I wonder is there any info regarding LDAP caching of security realms? In particular i am interested when is record cached. When is record invalidated from cache?
Thanx,
Martin
> Add test cases to verify LDAP caching on security realms.
> ---------------------------------------------------------
>
> Key: WFLY-3226
> URL: https://issues.jboss.org/browse/WFLY-3226
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management, Test Suite
> Reporter: Darran Lofthouse
> Fix For: Awaiting Volunteers
>
>
> The existing test cases are based on a statically defined set of LDIFs, testing of caching could consider a couple of options: -
> 1 - Interceptors within ApacheDS to verify if calls hit the directory.
> 2 - Updates to the directory that would affect the outcome of tests if there is a cache hit, tests can then be repeated with and without clearing the cache.
> Note: It would be beneficial for this to use different users and groups and maybe even different partitions so that test ordering does not affect the outcome if changes are made to the directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-3274?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-3274:
------------------------------------
requestCount , maxTime, bytesReceived all sound like runtime metrics/attributes. Have you checked the listener resource with include-runtime=true? I haven't.
> connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3274
> URL: https://issues.jboss.org/browse/WFLY-3274
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Rituraj Sinha
> Assignee: Tomaz Cerar
>
> while using jboss 7.2.0 we were able to fetch above values from the cli command as
> {noformat}
> [domain@test.com:9999 subsystem=web] ls
> configuration valve default-virtual-server=default-host native=false
> connector virtual-server instance-id=${jboss.node.name}
> [domain@test.com:9999 connector] ls
> ajp http
> [domain@test.com:9999 connector] cd http
> [domain@test.com:9999 connector] pwd
> /profile=ha/subsystem=web/connector=http
> [domain@test.com:9999 connector=http] ls
> configuration max-connections=undefined proxy-port=undefined
> ssl max-post-size=2097152 redirect-port=443
> bytesReceived= max-save-post-size=4096 requestCount=
> bytesSent= maxTime= scheme=http
> enable-lookups=false name=http secure=false
> enabled=true processingTime= socket-binding=http
> errorCount= protocol=HTTP/1.1 virtual-server=undefined
> executor=undefined proxy-name=undefined
> {noformat}
>
> Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8)
> as below
> {noformat}
> [domain@test2.com:9990 subsystem=undertow] ls
> buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 )
> configuration servlet-container default-virtual-host=default-host
> error-page default-server=default-server instance-id=${jboss.node.name}
> {noformat}
>
> but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
> {noformat}
> [domain@test2.com:9990 server=default-server] ls
> ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
> {noformat}
> after getting into http-listener we get the below
> {noformat}
> [domain@test2.com:9990 http-listener=default] ls
> allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http
> always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8
> buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default
> buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https
> {noformat}
>
> Can someone please look into it ..?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
by Rituraj Sinha (JIRA)
[ https://issues.jboss.org/browse/WFLY-3274?page=com.atlassian.jira.plugin.... ]
Rituraj Sinha commented on WFLY-3274:
-------------------------------------
can anyone please guide us on how to proceed here ..this is the last thing in our migration from jboss 7 to wildfly 8...everything else is working as expected ...
> connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3274
> URL: https://issues.jboss.org/browse/WFLY-3274
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Rituraj Sinha
> Assignee: Tomaz Cerar
>
> while using jboss 7.2.0 we were able to fetch above values from the cli command as
> {noformat}
> [domain@test.com:9999 subsystem=web] ls
> configuration valve default-virtual-server=default-host native=false
> connector virtual-server instance-id=${jboss.node.name}
> [domain@test.com:9999 connector] ls
> ajp http
> [domain@test.com:9999 connector] cd http
> [domain@test.com:9999 connector] pwd
> /profile=ha/subsystem=web/connector=http
> [domain@test.com:9999 connector=http] ls
> configuration max-connections=undefined proxy-port=undefined
> ssl max-post-size=2097152 redirect-port=443
> bytesReceived= max-save-post-size=4096 requestCount=
> bytesSent= maxTime= scheme=http
> enable-lookups=false name=http secure=false
> enabled=true processingTime= socket-binding=http
> errorCount= protocol=HTTP/1.1 virtual-server=undefined
> executor=undefined proxy-name=undefined
> {noformat}
>
> Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8)
> as below
> {noformat}
> [domain@test2.com:9990 subsystem=undertow] ls
> buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 )
> configuration servlet-container default-virtual-host=default-host
> error-page default-server=default-server instance-id=${jboss.node.name}
> {noformat}
>
> but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
> {noformat}
> [domain@test2.com:9990 server=default-server] ls
> ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
> {noformat}
> after getting into http-listener we get the below
> {noformat}
> [domain@test2.com:9990 http-listener=default] ls
> allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http
> always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8
> buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default
> buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https
> {noformat}
>
> Can someone please look into it ..?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years