[JBoss JIRA] (AS7-4090) Opimize organization and management of the Infinispan subsystem
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-4090:
----------------------------------------
Summary: Opimize organization and management of the Infinispan subsystem
Key: AS7-4090
URL: https://issues.jboss.org/browse/AS7-4090
Project: Application Server 7
Issue Type: Task
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Richard Achmatowicz
Assignee: Paul Ferraro
Fix For: 7.1.2.Final
There are a number of areas where the Infinispan subsystem is organizationally deficient:
- does not make use of ResourceDefinitions to (i) simplify the generation of DescriptionProviders and (ii) localize the definition of AttributeDefinitions
- handlers are in some cases written from scratch rather than subclassing helper handlers such as AbstractWriteAttributeHandler, AbstractAddStepHandler, AbstractRemoveStepHandler, etc.
- collections of services are defined monolithically, rather than in distinct units which makes stopping/restarting them error prone (c.f. CacheContainerAdd, CacheAdd install three or four services each with complex processing - stopping and restarting this in another handler is next to impossible)
- ServiceNames are not always easy to reconstruct
These issues make maintenance of the subsystem hard. These matters can be helped by:
- making use of ResourceDefinitions
- defining for each service X a static method installX(context, operation, model) and removeX(context, operation, model) which can be made use of in installServices(context, operation, model) and removeServices(operation, context, model)
- define the static method populate(), used to populate a model from an operation, which can be reused in populateModel(), creating describe operations, as well as other contexts
- define a static method installServices(context, operation, model) which can be used in performRuntime(), and in contexts where all services for a resource need to be stopped and restarted; similarly define removeServices(context, operation, model)
- make sure each ServiceName can be regenerated easily (c.f. regenerating JNDI names can involve model processing)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JBCL-185) BaseClassLoader.loadClass() is slow under load
by Aaron Ogburn (JIRA)
Aaron Ogburn created JBCL-185:
---------------------------------
Summary: BaseClassLoader.loadClass() is slow under load
Key: JBCL-185
URL: https://issues.jboss.org/browse/JBCL-185
Project: JBoss ClassLoader
Issue Type: Enhancement
Components: ClassLoader
Affects Versions: JBossCL.2.0.9.GA
Environment: -JBoss Enterprise Application Platform (EAP) 5.1.2
-JBossCL 2.0.9.GA
Reporter: Aaron Ogburn
Assignee: Ales Justin
Classloader performance dropped from EAP 4.3 to 5. Thread dumps show threads facing contention in the classloader:
java.lang.Thread.State: BLOCKED (on object monitor)
at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:495)
- waiting to lock <0x80e22960> (a org.jboss.classloader.spi.base.BaseClassLoader)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:87)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:97)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
These are repeat lookups. The thread and classloader trace logging show that these look ups are not returning cached values from checkCacheAndBlackList() and so they are having to go progress through doLoadClass() and the baseclassloderdomain to finally return the class from another classloaders cache. This is bad as threads are forced to synchronize to return a cached class from elsewhere whereas the cached value return could all happen concurrently.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-5133) "Once a process is reloaded, always reloaded" exception when reloading AS7
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-5133:
-------------------------------------
Summary: "Once a process is reloaded, always reloaded" exception when reloading AS7
Key: AS7-5133
URL: https://issues.jboss.org/browse/AS7-5133
Project: Application Server 7
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Brian Stansberry
In a master build, once an server started in admin mode is reloaded, it throws:
{code}16:52:31,576 ERROR [org.jboss.msc.service] MSC00002: Invocation of listener "org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1@16e3a921" failed: java.lang.AssertionError: Once a process is reloaded, always reloaded!
at org.jboss.as.controller.RunningModeControl.setReloaded(RunningModeControl.java:53) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432]
at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:72)
at org.jboss.as.server.operations.ServerProcessReloadHandler$1.doReload(ServerProcessReloadHandler.java:63)
at org.jboss.as.controller.operations.common.ProcessReloadHandler$1$1.transition(ProcessReloadHandler.java:95) [jboss-as-controller-7.x.incremental.432.jar:7.x.incremental.432]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31]{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4963) HTTPS configuration throws errors in when running domain.sh and no errors in case of standalone.sh
by Andriy Kalashnykov (JIRA)
Andriy Kalashnykov created AS7-4963:
---------------------------------------
Summary: HTTPS configuration throws errors in when running domain.sh and no errors in case of standalone.sh
Key: AS7-4963
URL: https://issues.jboss.org/browse/AS7-4963
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.1.1.Final
Environment: Red Hat Linux x64 (virtual via VMWare)
Reporter: Andriy Kalashnykov
Assignee: Anil Saldhana
Configuring SSL in "ha" profile of domain.xml:
<connector name="https" protocol="HTTP/1.1" socket-binding="https" scheme="https" secure="true" enable-lookups="false">
<ssl cipher-suite="ALL" protocol="TLSv1" verify-client="false" name="https" key-alias="jboss" password="jbossjboss" certificate-key-file="/opt/jboss/jboss-as-7.1.1.Final/standalone/configuration/keystore.jks"/>
</connector>
Executing ./domain.sh, and in the JBoss logs there is an error:
[Server:web-server-group-001] 13:55:24,152 ERROR [stderr] (pool-6-thread-1) Exception in thread "pool-6-thread-1" java.lang.IllegalStateException: java.io.IOException: Keystore was tampered with, or password was incorrect
[Server:web-server-group-001] 13:55:24,157 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:113)
[Server:web-server-group-001] 13:55:24,160 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.<init>(DefaultMCMPHandler.java:747)
[Server:web-server-group-001] 13:55:24,165 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.add(DefaultMCMPHandler.java:183)
[Server:web-server-group-001] 13:55:24,166 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.addProxy(DefaultMCMPHandler.java:179)
[Server:web-server-group-001] 13:55:24,171 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl$AdvertiseListenerWorker.run(AdvertiseListenerImpl.java:443)
[Server:web-server-group-001] 13:55:24,171 ERROR [stderr] (pool-6-thread-1) at java.lang.Thread.run(Thread.java:662)
[Server:web-server-group-001] 13:55:24,177 ERROR [stderr] (pool-6-thread-1) Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
[Server:web-server-group-001] 13:55:24,177 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771)
[Server:web-server-group-001] 13:55:24,178 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
[Server:web-server-group-001] 13:55:24,190 ERROR [stderr] (pool-6-thread-1) at java.security.KeyStore.load(KeyStore.java:1185)
[Server:web-server-group-001] 13:55:24,190 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getStore(JSSESocketFactory.java:259)
[Server:web-server-group-001] 13:55:24,191 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeystore(JSSESocketFactory.java:208)
[Server:web-server-group-001] 13:55:24,191 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:280)
[Server:web-server-group-001] 13:55:24,202 ERROR [stderr] (pool-6-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98)
[Server:web-server-group-001] 13:55:24,202 ERROR [stderr] (pool-6-thread-1) ... 5 more
[Server:web-server-group-001] 13:55:24,203 ERROR [stderr] (pool-6-thread-1) Caused by: java.security.UnrecoverableKeyException: Password verification failed
[Server:web-server-group-001] 13:55:24,205 ERROR [stderr] (pool-6-thread-1) at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769)
[Server:web-server-group-001] 13:55:24,206 ERROR [stderr] (pool-6-thread-1) ... 11 more
If mentioned above configuraion parameters copied to standalone.xml and ./standalone.sh executed - there will be no errors reported.
Interestingly, as result HTTPS will be available on port 8443 in both cases...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months