[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
12 years
[JBoss JIRA] (AS7-5835) CLONE - application.xml does not support property replacement
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/AS7-5835?page=com.atlassian.jira.plugin.s... ]
Brad Maxwell commented on AS7-5835:
-----------------------------------
I tested again, in AS 7.2.0 Alpha 1 and system property substitution is not working for env-entries, it does appear to be working for context-params.
./standalone.sh -DsysProp=test
standalone.xml
----------------------------
<subsystem xmlns="urn:jboss:domain:ee:1.1">
<spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>
<jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
</subsystem>
web.xml:
----------------------------
<context-param>
<param-name>webtest</param-name>
<param-value>${sysProp:'web-test'}</param-value>
</context-param>
<env-entry>
<env-entry-name>test</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>${sysProp:'web-test-env'}</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>test2</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>test2</env-entry-value>
</env-entry>
index.jsp:
----------------------------
<body>
${initParam['webtest']}<br/><br/>
<%=new InitialContext().lookup("java:app/env/test") %><br/><br/>
<%=new InitialContext().lookup("java:comp/env/test") %><br/><br/>
<%=new InitialContext().lookup("java:comp/env/test2") %><br/>
</body>
Output:
----------------------------
test
${sysProp:'app-test'}
${sysProp:'web-test-env'}
test2
> CLONE - application.xml does not support property replacement
> -------------------------------------------------------------
>
> Key: AS7-5835
> URL: https://issues.jboss.org/browse/AS7-5835
> Project: Application Server 7
> Issue Type: Bug
> Components: EE
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Tom Fonteyne
> Assignee: Stuart Douglas
> Priority: Minor
> Attachments: PropertyTest.ear, PropertyTest.ear
>
>
> Property substitution in application.xml does not work
--
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] (JBRULES-3656) java.lang.ClassCastException: org.drools.reteoo.AlphaNode$AlphaMemory cannot be cast to org.drools.reteoo.BetaMemory
by Mariano De Maio (JIRA)
Mariano De Maio created JBRULES-3656:
----------------------------------------
Summary: java.lang.ClassCastException: org.drools.reteoo.AlphaNode$AlphaMemory cannot be cast to org.drools.reteoo.BetaMemory
Key: JBRULES-3656
URL: https://issues.jboss.org/browse/JBRULES-3656
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.5.0.Beta1, 5.4.1.Final
Reporter: Mariano De Maio
Assignee: Mark Proctor
Attachments: P8.tar.gz
When trying to add a rule package to a knowledge base I previously removed a used knowledge session from, the following error occurrs:
java.lang.ClassCastException: org.drools.reteoo.AlphaNode$AlphaMemory cannot be cast to org.drools.reteoo.BetaMemory
at org.drools.reteoo.NotNode.updateSink(NotNode.java:461)
at org.drools.reteoo.RuleTerminalNode.attach(RuleTerminalNode.java:347)
at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:174)
at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:134)
at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:113)
at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:445)
at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:952)
at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:629)
at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:472)
at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:150)
...
This issue doesn't seem to happen on 5.4.0.Final but it does appear on 5.5.0.Beta1 and on branch 5.4.x
I attached a project (P8.tar.gz) that allows you to test this issue. Any help would be appreciated
--
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] (AS7-5829) JBoss AS7 and Log4j2
by Amarkanth Ranganamayna (JIRA)
Amarkanth Ranganamayna created AS7-5829:
-------------------------------------------
Summary: JBoss AS7 and Log4j2
Key: AS7-5829
URL: https://issues.jboss.org/browse/AS7-5829
Project: Application Server 7
Issue Type: Clarification
Components: Logging
Affects Versions: 7.1.1.Final
Environment: Spring 3, Hibernate, Wicket, JBoss AS7
Reporter: Amarkanth Ranganamayna
Assignee: James Perkins
I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2.
Looks like Jboss AS7 by default use log4j 1.x
Are you guys already working on using log4j2 ?
If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging.
Thanks,
Amar
--
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] (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
12 years