Issue with class loader leak tests
by Thomas Diesler
Hi Dominik,
could you pls meet me on IRC #jboss-as7
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
14 years, 1 month
AS7 build error after wiping local .m2/repository
by David Bosschaert
Hi all,
I decided to clean up my local Maven repo and rebuild AS7 after that.
Running mvn install on master fails in the messaging subsystem with:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) on project jboss-as-messaging: Compilation
failure: Compilation failure:
[ERROR]
/Users/david/clones/bosschaert_jboss-as_020512/messaging/src/test/java/org/jboss/as/messaging/test/SubsystemDescriptionsUnitTestCase.java:[31,29]
cannot find symbol
[ERROR] symbol : class MessagingExtension
[ERROR] location: package org.jboss.as.messaging
Anyone an idea why?
Cheers,
David
14 years, 1 month
Jboss eap 6 released?
by Sebastian Otaegui
Hello,
I logged in to the red hat enterprise portal and found a 6.0.0 eap
download, no "beta" in the name, does it mean that is the final release?
Thanks in advance
--
Those who do not understand Unix are condemned to reinvent it, poorly.
Any sufficiently recent Microsoft OS contains an ad hoc,
informally-specified, bug-ridden, slow implementation of half of Unix.
14 years, 1 month
Deploying an ESB project to JBoss server 5.1.0 using Eclipse
by Themba Shezi
Greetings all
I'm using JBoss ESB 4.9 deployed on server 5.1.0 and i configured my server
on eclipse. when i try to deploy any project it gives me the following
error, Can you people please help me find a solution i have been struggling
with this for few days now
17:21:58,775 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of
incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossProject.esb/"
is missing the following dependencies:
Dependency "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossProject.esb/>"
(should be in state "PreInstall", but is actually in state "** UNRESOLVED
Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue'
**")
Dependency "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossProject.esb/>"
(should be in state "PreInstall", but is actually in state "** UNRESOLVED
Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue'
**")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossProject.esb/>"
is in error due to the following reason(s): ** UNRESOLVED Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue'
**, ** UNRESOLVED Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue'
**
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
17:22:18,899 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of
incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossHelloWold.esb/"
is missing the following dependencies:
Dependency "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossHelloWold.esb/>"
(should be in state "PreInstall", but is actually in state "** UNRESOLVED
Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue'
**")
Dependency "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossHelloWold.esb/>"
(should be in state "PreInstall", but is actually in state "** UNRESOLVED
Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue'
**")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN
jboss.esb.vfsfile:/C:/eclipse/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server1339595861867/deploy/JBossHelloWold.esb/>"
is in error due to the following reason(s): ** UNRESOLVED Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue'
**, ** UNRESOLVED Demands
'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue'
**
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at
org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at
org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
--
Name : Mr T. Shezi
NickName : Mthimbanator
Student No : 200702908
Level : Computer Sc Research Student
Institution : University of Zululand
Department : Computer Science
Cell No : 078 706 7208
14 years, 1 month
Limiting Server Thread Usage
by Jason T. Greene
Moving to a new thread.
The big problem we run into with this is that almost every application
of a thread pool that we have needs to be highly tailored to its usage
to get the most optimal performance. So we end up with quite a few
different pools and it becomes difficult to impose a server wide limit.
There however some potential strategies we could take. Although I am
unsure as to how the overall effectiveness would be:
1. Sharing idle threads between pools
2. Force everything to go through a special blocking thread factory via
instrumentation of java.lang.Thread. Any attempt to allocate over the
max would lead to thread reclamation attempts and finally blocking until
a timeout is reached.
3. Some kind of auto-tuning weighting model. If the max total threads is
N, force all thread pools to use a percentage of N, potentially based on
establishing current config value divided by combined total.
One thing I wonder though is if cloud providers are "barking up the
wrong tree"? It seems a better limitation of an application is raw CPU
clock time and max memory usage. How they split that time into threads
doesn't really affect the scalability of the physical server, it's all
virtual process performance (who cares if someone wastes time context
switching?).
On 9/14/11 10:39 AM, Scott Stark wrote:
> The other big cross cutting concern is controlling the total number of
> threads in use by the application server. When running under a
> constrained environment that uses something like pam_limits module to
> control how many process(==java threads) a user can have, it is
> difficult to know what the server max thread usage is right now.
>
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
14 years, 1 month
logger config per deployment / app
by Ales Justin
Can you already configure loggers per deployment?
e.g. I want org.hibernate.search at trace for my app, but not for the whole AS
If yes, how?
I mean, is there a better way than adding the old TCCL filter hack I once helped to write. :)
14 years, 1 month
