Configuration of statistics gathering
by Brian Stansberry
I'd like to get some info from the component leads responsible for WF
subsystems.
1) What statistical data does your subsystem capture (including the
underlying libraries it integrates).
2) What configuration options do you support for enabling/disabling
statistics gathering. What's the resource address and attribute name of
the config option?
3) Is the statistic gathering enabled by default?
Paul Ferraro's pull request [1] fixing JIRA [2] prompts this question,
although it's long overdue. WF should be consistent about how we handle
configuration of statistics gathering, so I'd like to take the
opportunity of Paul's PR to move in that direction.
Thanks for your help.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
[1] https://github.com/wildfly/wildfly/pull/5415
[2] https://issues.jboss.org/browse/WFLY-2415
10 years, 11 months
Servlet Samples on Beta2 snapshot
by Arun Gupta
I tried Servlet samples from:
https://github.com/arun-gupta/javaee7-samples/tree/master/servlet
and encountered the following issues:
1). An HttpOnly cookie is set as:
cookie = new Cookie("myHttpOnlyCookieKey", "myHttpOnlyCookieValue");
cookie.setHttpOnly(true);
cookie.setMaxAge(60);
response.addCookie(cookie);
and
document.write(document.cookie);
displays the cookie and its value.
2). event-listeners sample is not getting deployed and throwing the
following exception:
Caused by: java.lang.IllegalArgumentException: UT010012: Listener
class class org.javaee7.servlet.event.listeners.MyHttpSessionBindingListener
must implement at least one listener interface
even though the class is defined as:
@WebListener
public class MyHttpSessionBindingListener implements
HttpSessionBindingListener {
...
}
3). file-upload sample allows to upload a file and writes it to /tmp
directory as:
for (Part part : request.getParts()) {
fileName = part.getSubmittedFileName();
part.write(fileName);
}
part.write() is not throwing any exception but not even writing the file.
4). In order to try servlet-security sample, I was trying to add a new
user in application realm as:
./bin/add-user.sh -g g1-u u1 -p p1 -r ApplicationRealm
but getting:
* Error *
JBAS015281: The user supplied realm name 'ApplicationRealm' does not
match the realm name discovered from the property file(s)
'ManagementRealm'.
Adding a user in the default realm, as expected, did not pass
authentication for the secure page. How should the user be added such
that the credentials can be used in an application ?
Thanks,
Arun
--
Blog: http://blog.arungupta.me
Twitter: http://twitter.com/arungupta
10 years, 11 months
Invalid use of BasicClientConnManager for JAX-RS Client API
by Arun Gupta
Tests for JAX-RS Client API sample at:
https://github.com/arun-gupta/javaee7-samples/tree/master/jaxrs/jaxrs-client
is failing with:
Caused by: java.lang.IllegalStateException: Invalid use of
BasicClientConnManager: connection still allocated.
Make sure to release the connection before allocating another one.
at org.apache.http.impl.conn.BasicClientConnectionManager.getConnection(BasicClientConnectionManager.java:161)
at org.apache.http.impl.conn.BasicClientConnectionManager$1.getConnection(BasicClientConnectionManager.java:138)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:455)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:245)
... 33 more
The instructions to run the test are described at:
https://github.com/arun-gupta/javaee7-samples
Any suggestions ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
10 years, 12 months
Surprising logging configuration: enable just some logs?
by Baptiste Mathus
Hi guys,
[[I crawled the archive a bit, and wrote here as jboss-as-dev seems
inactive. If it's the wrong list here to talk about an old version of
jboss/wildfly, just let me know.]]
I was recently trying to customize the output of JBoss 7 (EAP6.1) in our
development environment.
We're currently seeing what IMO is far too many logs at the beginning of
the server (about 3.5k lines, and too many logs kills the logs :-)).
We'd like to configure the root-logger at ERROR level, and redefine our
root package at just WARN.
Then, we particularly want to keep two INFO logs from JBoss:
starting/finished starting[error or not].
15:47:29,652 INFO [org.jboss.as.server.ApplicationServerService] [-][]
(MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.1.GA <http://6.1.1.ga/> (AS
7.2.1.Final-redhat-10) démarre
15:48:00,789 INFO [org.jboss.as.server.BootstrapListener] [-][]
(Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA <http://6.1.1.ga/> (AS
7.2.1.Final-redhat-10) a démarré en 32035ms - 5898 sur 6139 services ont
démarré (229 services sont passifs ou à la demande)
To achieve that, someone previously configured org.jboss.as logger at the
INFO level. BUT, as this is a parent package of almost anything in the
server, this seems to activate a lot of other logs (some from
org.jboss.as.clustering.foo, org.jboss.as.naming.bar to name a few).
So, I naively first tried configuring the FQN being displayed
org.jboss.as.server.ApplicationServerService and
org.jboss.as.server.BootstrapListener, and realized this did not change
anything.
After a quick look in the code, I saw that loggers in jboss/wildfly
actually don't seem to use the class the logs are being emitted from as
often elsewhere, but some specially Logger instances defined in some
central class (like
https://github.com/wildfly/wildfly/blob/7.1/server/src/main/java/org/jbos...
example).
ApplicationServerService [1] and BootstrapListener[2], for instance,
actually log the server through the ServerLogger.AS_ROOT_LOGGER[3] instance.
And AS_ROOT_LOGGER is "bound" to org.jboss.as... I'm stuck. I have to
activate org.jboss.as to see the starting logs, but at the same time
enabling other logs.
Btw, why do those logs get sent through ServerLogger.AS_ROOT_LOGGER (
org.jboss.as) instead of ServerLogger.ROOT_LOGGER (org.jboss.as.server)?
Was it actually made on purpose?
A possible solution I see might be to redefine some org.jboss.as.foo
package at a higher level than INFO in my standalone.xml, but this seems a
bit cumbersome.
Did I understand how logging inside as/wildfly work correctly? Do you see
another way to achieve what I say above?
Thanks a lot for any hint.
[1]
https://github.com/wildfly/wildfly/blob/7.1/server/src/main/java/org/jbos...
[2]
https://github.com/wildfly/wildfly/blob/7.1/server/src/main/java/org/jbos...
[3]
https://github.com/wildfly/wildfly/blob/7.1/server/src/main/java/org/jbos...
-- Baptiste
10 years, 12 months
CR1 Update
by Jason Greene
Hello Everyone,
We have made great progress on the TCK but still have a few EE7 TCK tests failing, and achieving 100% passing is an important goal for CR1. I have pushed the date until mid next week to allow for more time.
I'll provide weekly updates until we have met this critical goal.
It goes without saying but if your area is one of the affected please let me know ASAP if you expect any additional delays or need help.
Thanks!
10 years, 12 months
Weird behaviour if a new profile is added via cli, the subsystem=batch can not be added successfully
by Wolf-Dieter Fink
I use a batch script to configure a domain (
https://github.com/wfink/quickstart/blob/ejb-multi-server-transfer/ejb-mu...
)
You can run that script with "jboss-cli.sh -c --file=install-domain.cli"
against a fresh copy of wildfly Beta2 (upstream)
The batch is running without messages, but the domain.xml looks like this
<subsystem xmlns="urn:jboss:domain:batch:1.0">
<job-repository>
<in-memory/>
</job-repository>
</subsystem>
The used commands are:
/profile=default-web/subsystem=batch:add()
/profile=default-web/subsystem=batch/thread-pool=batch:add(keepalive-time={time=100,unit=milliseconds},
max-threads=10)
So the thread-pool is missing in the domain.xml.
But if I try to tun the second command again (after the script) I get this:
[domain@localhost:9990 /]
/profile=default-web/subsystem=batch/thread-pool=batch:add(keepalive-time={time=100,unit=milliseconds},
max-threads=10)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"JBAS014803: Duplicate resource [
(\"profile\" => \"default-web\"),
(\"subsystem\" => \"batch\"),
(\"thread-pool\" => \"batch\")
]"},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
After the domain is restarted the same command will run successfully.
I wonder whether this is a bug or do I something wrong (I did not suppose)
cheers
Wolf
10 years, 12 months
Problem with deployment - current upstream
by Wolf-Dieter Fink
HI,
I try to deploy a quickstart to WF 8.0.0.Beta2 upstream.
With an older build (B2 from 11-07) it works.
Is there something changed and I need to change the deployment?
I did not expect that.
Find CLI install script and deployments attached. Use a fresh copy of
WF8 and run the install batch file
this is the deploy order:
deploy app-one/ear/target/jboss-ejb-multi-server-app-one.ear
--server-groups=quickstart-ejb-multi-appOne-server
deploy app-two/ear/target/jboss-ejb-multi-server-app-two.ear
--server-groups=quickstart-ejb-multi-appTwo-server
deploy app-main/ear/target/jboss-ejb-multi-server-app-main.ear
--server-groups=quickstart-ejb-multi-main-server
deploy app-web/target/jboss-ejb-multi-server-app-web.war
--server-groups=quickstart-ejb-multi-appWeb-server
Also if the deploy-domain.cli script is used the deployment may fail.
Wolf
[Server:app-main] 18:21:06,435 INFO [org.jboss.weld.deployer] (MSC
service thread 1-11) JBAS016008: Starting weld service for deployment
jboss-ejb-multi-server-app-main.ear
[Server:app-main] 18:21:06,462 ERROR
[org.jboss.as.controller.management-operation]
(host-controller-connection-threads - 3) JBAS014613: Operation
("deploy") failed - address: ([("deployment" =>
"jboss-ejb-multi-server-app-main.ear")]) - failure description:
{"JBAS014771: Services with missing/unavailable dependencies" => [
[Server:app-main]
"jboss.deployment.unit.\"jboss-ejb-multi-server-app-main.ear\".WeldStartService
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".jndiDependencyService]",
[Server:app-main]
"jboss.deployment.unit.\"jboss-ejb-multi-server-app-main.ear\".deploymentCompleteService
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".deploymentCompleteService]",
[Server:app-main]
"jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".weld.weldClassIntrospector
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".beanmanager]"
[Server:app-main] ]}
[Server:app-main] 18:21:06,464 ERROR [org.jboss.as.server]
(host-controller-connection-threads - 3) JBAS015870: Deploy of
deployment "jboss-ejb-multi-server-app-main.ear" was rolled back with
the following failure message:
[Server:app-main] {"JBAS014771: Services with missing/unavailable
dependencies" => [
[Server:app-main]
"jboss.deployment.unit.\"jboss-ejb-multi-server-app-main.ear\".WeldStartService
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".jndiDependencyService]",
[Server:app-main]
"jboss.deployment.unit.\"jboss-ejb-multi-server-app-main.ear\".deploymentCompleteService
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".deploymentCompleteService]",
[Server:app-main]
"jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".weld.weldClassIntrospector
is missing
[jboss.deployment.subunit.\"jboss-ejb-multi-server-app-main.ear\".\"jsf.war\".beanmanager]"
[Server:app-main] ]}
[Server:app-main] 18:21:06,466 INFO [org.jboss.weld.deployer] (MSC
service thread 1-15) JBAS016009: Stopping weld service for deployment
jboss-ejb-multi-server-app-main.ear
10 years, 12 months
HornetQException[errorType=NATIVE_ERROR_CANT_OPEN_CLOSE_FILE message=Can't open file]
by Arun Gupta
Trying to run Java EE 7 unit tests and the complete log is at:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
HornetQ throws the following error:
[0m[0m10:51:36,892 INFO [org.jboss.ws.common.management] (MSC
service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack
CXF Server 4.2.3.Final
[0m[33m10:51:37,031 WARN [org.hornetq.core.server] (ServerService
Thread Pool -- 58) HQ222010: Critical IO Error, shutting down the
server. file=AIOSequentialFile:/scratch/jenkins/workspace/Java EE 7
Samples on WildFly-cb/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/data/messagingjournal/hornetq-data-1.hq.tmp,
message=Can't open file:
HornetQException[errorType=NATIVE_ERROR_CANT_OPEN_CLOSE_FILE
message=Can't open file]
at org.hornetq.core.asyncio.impl.AsynchronousFileImpl.init(Native
Method) [hornetq-journal-2.4.0.Beta2.jar:]
at org.hornetq.core.asyncio.impl.AsynchronousFileImpl.open(AsynchronousFileImpl.java:220)
[hornetq-journal-2.4.0.Beta2.jar:]
at org.hornetq.core.journal.impl.AIOSequentialFile.open(AIOSequentialFile.java:190)
[hornetq-journal-2.4.0.Beta2.jar:]
Several test deployments are failing with the following reason:
Caused by: java.lang.Exception: {"JBAS014771: Services with
missing/unavailable dependencies" =>
["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory
is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]}
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
If I run in the default Web profile then this error does not occur as shown at:
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
But JMS tests fail.
I can't reproduce this issue with the latest workspace on my machine.
Any suggestions ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
11 years
