VFS3 (in AS trunk) - Non .jar file handling
by Jaikiran Pai
I see a new behaviour with VFS3 in JBoss AS. Earlier in AS-5/6 (with
VFS2) and AS-4 (without any VFS), to try out some quick fixes, i used to
rename existing jar files to end with .bak name and replace them with
the new patched jar file. So for example, if i had a fix in
jboss-ejb3-core.jar, i would:
1) Rename the JBOSS_HOME/common/lib/jboss-ejb3-core.jar to
JBOSS_HOME/common/lib/jboss-ejb3-core.jar.orig.bak
2) Place a patched jboss-ejb3-core.jar in JBOSS_HOME/common/lib
3) Restart the …
[View More]server
The server would then pickup the new patched jar file and ignore the
.bak file. After testing the fix, i would then revert back to the
original jar file by renaming it back to its original name.
However, with the recent upgrade to VFS3 in AS trunk, i notice that even
the .bak is used for classloading (following is the output from
-verbose:class JVM argument):
[Loaded org.jboss.ejb3.EJBContainer from
file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/common/lib/jboss-ejb3-core.jar.orig.bak/]
Looks like VFS3 picks up this non .jar suffix file for classloading. Is
this expected? Shouldn't it be looking for only .jar files (atleast in
this context)?
regards,
-Jaikiran
[View Less]
14 years, 3 months
Small boottime improvement
by Kabir Khan
I have been doing some work on profiling and optimizing the jboss-dependency project [1] for kernel 2.2.0.Alpha6 and it seems to have had a small, but still measurable impact :-)
I did a few startups of AS with jboss kernel 2.2.0.Alpha5 and with a local snapshot. This snapshot contains the work done for Alpha6 with the addition of removing the break in the resolveContexts loop as mentioned in the forum thread.
The startups were done on a freshly rebooted machine with nothing else running. The …
[View More]startup orders are given in brackets, so I started Alpha5 twice, then SNAPSHOT twice and so on.
2.2.0-Alpha5
----------------------
37s:247ms (1)
20s:573ms (2)
20s:275ms (5)
20s:127ms (7)
20s:433ms (9)
20s:329ms (10)
20s:890ms (13)
2.2.0-SNAPSHOT
------------------------
29s:563ms (3)
19s:965ms (4)
19s:821ms (6)
20s:332ms (8)
19s:618ms (10)
19s:905ms (12)
19s:900ms (14)
One strange thing is that the first time I started each server they took loads longer than the other times, does somebody know the reason for that?
Ignoring those initial times leaves me with average start times of:
Alpha5: 20s437ms
SNAPSHOT: 19s923ms
I'm going to have a final look at jboss-dependency to see if there are any other obvious and easy fixes before moving on to have a look at jboss-kernel.
[1] http://community.jboss.org/message/525047#525047
[View Less]
14 years, 9 months
fix AS trunk testing on windows
by Alexey Loubyansky
It currently isn't working (e.g. one-test target) since the classpath is
too long. To work around the issue, a manifest-only jar has to be
created which would reference all the jars and dirs. Can we fix testing
this way?
This is what I am doing on my laptop at the moment.
Thanks,
Alexey
14 years, 11 months
AS trunk status
by Vladimir Blagojevic
Hi,
I cannot get a clean build after initial checkout. I checked out https://svn.jboss.org/repos/jbossas/trunk and started a build. What I am doing wrong?
Regards,
Vladimir
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.jboss.ws.native:jbossws-native-client:jar:3.3.0.CR1.SP2
Try downloading the …
[View More]file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-client -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-client -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-client:jar:3.3.0.CR1.SP2
2) org.jboss.ws.native:jbossws-native-management:war:3.3.0.CR1.SP2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-management -Dversion=3.3.0.CR1.SP2 -Dpackaging=war -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-management -Dversion=3.3.0.CR1.SP2 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-management:war:3.3.0.CR1.SP2
3) org.jboss.ws.native:jbossws-native-core:jar:3.3.0.CR1.SP2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-core -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-core -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-core:jar:3.3.0.CR1.SP2
4) org.jboss.ws.native:jbossws-native-factories:jar:3.3.0.CR1.SP2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-factories -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-factories -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-factories:jar:3.3.0.CR1.SP2
5) org.jboss.ws.native:jbossws-native-resources:jar:3.3.0.CR1.SP2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-resources -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-resources -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-resources:jar:3.3.0.CR1.SP2
6) org.jboss.ws.native:jbossws-native-services:jar:3.3.0.CR1.SP2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-services -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.ws.native -DartifactId=jbossws-native-services -Dversion=3.3.0.CR1.SP2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
2) org.jboss.ws.native:jbossws-native-services:jar:3.3.0.CR1.SP2
----------
6 required artifacts are missing.
for artifact:
org.jboss.jbossas:jboss-as-distribution:pom:6.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
repository.jboss.org (http://repository.jboss.org/maven2),
snapshots.jboss.org (http://snapshots.jboss.org/maven2)
[View Less]
14 years, 12 months
How to bind object to JNDI from jmx-jboss-beans.xml
by Scott Marlow
I'm working on adding a remote JMXConnector to AS trunk via a new
jmx-jboss-beans.xml (see http://pastebin.com/JjsiRrh9). I would like to
bind a string representation of the JMX service URL to JNDI. Any
pointers to doing the bind (from a jboss-beans.xml) are welcome.
If not, I will hack through it but wanted to check first. :)
Thanks,
Scott
14 years, 12 months
Unhelpful exception from HornetQ
by Carlo de Wolf
When my MDB test is done I get:
2010-03-25 19:29:29,378 WARN
[org.hornetq.core.client.impl.DelegatingSession] (Finalizer) I'm closing
a core ClientSession you left open. Please make sure you close all
ClientSessions explicitly before letting them go out of scope! 1073232360
2010-03-25 19:29:29,378 WARN
[org.hornetq.core.client.impl.DelegatingSession] (Finalizer) The
ClientSession you didn't close was created here:: java.lang.Exception
at
org.hornetq.core.client.impl.…
[View More]DelegatingSession.<init>(DelegatingSession.java:93)
at
org.hornetq.core.client.impl.FailoverManagerImpl.createSession(FailoverManagerImpl.java:439)
at
org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:1063)
at
org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:790)
at
org.hornetq.ra.HornetQResourceAdapter.createSession(HornetQResourceAdapter.java:1306)
at
org.hornetq.ra.inflow.HornetQActivation.setupSession(HornetQActivation.java:336)
at
org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:283)
at
org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:496)
at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172)
at
org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:780)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:800)
at java.lang.Thread.run(Thread.java:619)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
This exception isn't telling me what I am(/might be) doing wrong.
Carlo
[View Less]
14 years, 12 months
Fwd: JNDI binding for CDI
by Marius Bogoevici
Posting across to JBoss Dev, as initially intended (but I got the e-mail
address wrong :|)
-------- Original Message --------
Subject: JNDI binding for CDI
Date: Thu, 25 Mar 2010 09:50:09 -0400
From: Marius Bogoevici <marius.bogoevici(a)gmail.com>
To: weld-dev(a)lists.jboss.org, jboss-dev(a)lists.jboss.org
Hi,
I released v. 6.0.0.Beta11 which fixes the JNDI stuff for Weld - thanks Carlo for the support on the EJB side. One change is that BeanManager is now binding to java:comp …
[View More]instead of the previous java:app (which was not conforming to the spec), so we'll need to do a sweep of the Weld and TCK code in order to make sure that the we use the correct namespace.
Marius
[View Less]
15 years
Component Freeze Date Change
by Jason T. Greene
Due to a Weld compatibility issue that is blocking on the new EE
injection work, the component freeze has been moved to April 2. With
this change we should still be able to release within the 2 month cycle
we have been following (April 16th); however, the sooner we can wrap
this up the better.
You can track updates on this and the current schedule via the M3
summary page here:
http://community.jboss.org/wiki/AS600M3StatusExecutiveSummary
--
Jason T. Greene
JBoss, a division of Red Hat
15 years
Reorganizing Javaee Spec Projects
by Paul Gier
Hey Guys,
Shelly and I are reorganizing the javaee spec projects in svn. I'll send out an
update later today after we are finished with some wiki docs about how things
are organized, how to do releases, etc..
Thanks!
15 years
