Logging Subsystem Operation Names
by James Perkins
Feeding off a previous short discussion about removing operations from
subsystems, I was thinking of removing a few of the operations from the
logging subsystem. We are giving the root-logger a proper address type
of /subsystem=logging/root-logger=ROOT. This moves the
change-root-log-level operation to that path. I was thinking about
removing that operation as it should probably be handled via the
write-attribute operation.
Along with the change-root-log-level, I'd like to rename the
"root-logger-assign-handler" and "root-logger-unassign-handler" to
remove the "root-logger" prefix.
Also, I'd like to remove the change-log-level in the
/subsystem=logging/logger=name path.
Anyone have any thoughts or concerns about this?
--
James R. Perkins
JBoss by Red Hat
14 years, 2 months
Build JAXR Subsystem failed
by Pavel Janousek
Steps:
1. git clone git@github.com:jbossas/jboss-as.git
2. cd jboss-as
3. ./build.sh install
Got this result:
<snip>
[ERROR] Failed to execute goal on project jboss-as-jaxr: Could not resolve dependencies for project org.jboss.as:jboss-as-jaxr:jar:7.1.0.Alpha2-SNAPSHOT: Failed to collect dependencies for [org.jboss.as:jboss-as-controller:jar:7.1.0.Alpha2-SNAPSHOT (compile), org.jboss.as:jboss-as-naming:jar:7.1.0.Alpha2-SNAPSHOT (compile), org.jboss.as:jboss-as-server:jar:7.1.0.Alpha2-SNAPSHOT (compile), org.jboss.as:jboss-as-web:jar:7.1.0.Alpha2-SNAPSHOT (compile), org.jboss.spec.javax.xml.registry:jboss-jaxr-api_1.0_spec:jar:1.0.0.Final (compile), org.jboss:jboss-common-core:jar:2.2.17.GA (compile), juddi:juddi:jar:2.0.1 (compile), org.apache.ws.scout:scout:jar:1.1.1 (compile), org.jboss.as:jboss-as-subsystem-test:jar:7.1.0.Alpha2-SNAPSHOT (test), junit:junit:jar:4.10 (test), org.jboss.as:jboss-as-build-config:jar:7.1.0.Alpha2-SNAPSHOT (compile)]: Failed to read artifact descriptor for juddi:juddi:jar:2.0.1: Could not find artifact juddi:juddi-parent:pom:2.0.1 in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
Although also my local Maven repo (~/.m2/repository/juddi/juddi/2.0.1) contains:
[pjanouse@pjanouse 2.0.1]$ ls -l
total 860
-rw-rw-r--. 1 pjanouse pjanouse 856048 Aug 1 16:03 juddi-2.0.1.jar
-rw-rw-r--. 1 pjanouse pjanouse 40 Aug 1 16:03 juddi-2.0.1.jar.sha1
-rw-rw-r--. 1 pjanouse pjanouse 8385 Aug 1 16:02 juddi-2.0.1.pom
-rw-rw-r--. 1 pjanouse pjanouse 40 Aug 1 16:02 juddi-2.0.1.pom.sha1
-rw-rw-r--. 1 pjanouse pjanouse 261 Nov 9 15:09 _maven.repositories
What I've done wrong or how can I fix this?
--
Pavel Janousek
Senior JBoss QA Engineer
14 years, 2 months
Re: [jboss-as7-dev] [hibernate-dev] Which JBoss Logging version to use in AS and Hibernate Core
by Strong Liu
if jboss-logging 3.1.0 final would compatible with 3.1.0.Beta3, then i would vote for releasing 4.0 Final today
hope AS7 could cut off a CR release with jboss-logging 3.1.0.Beta3 or Final soon
|-------------------------------------------------------
or we wait for jboss-logging goes final and --`
shade plugin is not always a good choice and i don't know if there is an alternative can be used in gradle
On Nov 8, 2011, at 6:12 PM, Hardy Ferentschik wrote:
> On Tue, 08 Nov 2011 00:33:23 +0100, David M. Lloyd
> <david.lloyd(a)redhat.com> wrote:
>
>>> I don't think the shade approach is the way to go; it wouldn't work in
>>> AS 7.1, which is our final goal.
>>
>> Yeah, it would actually. It would just put a copy of that base class in
>> your JAR somewhere, and then your generated classes would extend that
>> class instead of the one which is missing in 3.0, thus your program
>> would function normally.
>
> Even though this solution seems of the table, I just thought that the
> productization
> team cannot use the shade plugin (don't ask me why). For that reasons they
> actually
> have to remove the shade plugin from the pom and patch the build in other
> ways.
>
> --Hardy
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
14 years, 2 months
Testsuite config for AS location gone wrong?
by Jaikiran Pai
It looks like some recent commit in AS7 upstream in testsuite module
might have introduced an issue where the server logs get written to a
wrong location (and maybe even which AS instance the tests use). I was
in the testsuite/integration folder and ran the following:
mvn clean test -Dtest=org.jboss.as.test.integration.<sometestname>
Although the test was run, there was no log folder under
testsuite/integration/target/jbossas/standalone. It turns out that it
got written in testsuite/*smoke*/target/jbossas/standalone
I even suspect that the server being used to run the tests is from
testsuite/smoke/target/jbossas instead of
testsuite/integration/target/jbossas.
I haven't had the time to look into details as I'm heading out now.
Could someone please take a look at what went wrong? If not, I'll check
later tomorrow.
-Jaikiran
14 years, 2 months
Classpath problems in EAR project
by Diego Keller Silva
Hi!
I am migrating a project from JAS 6 Final to JAS 7.0.2 Final.
Here is the structure of my application:
EJB-MainEAR.ear
JPA-Main.jar (JPA Project)
EJB-MainClient.jar (EJB Interfaces Project)
EJB-Main.jar (EJB Session Beans Project)
GWT-Main.war (Web Project)
I read the article
https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7 and i am
aware of the property ear-subdeployments-isolated.
I tried to add this property to the file
C:\jboss7\standalone\configuration\standalone.xml setting it to FALSE.
<subsystem xmlns="urn:jboss:domain:ee:1.0">
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
</subsystem>
But i get this error message whe starting JBoss.
"SistemaSession" is the EJB interface inside EJB-MainClient.jar.
10:39:03,356 WARN [org.jboss.modules] (MSC service thread 1-4) Failed to
define class com.framework.business.ejb.session.SistemaSessionBean in
Module "deployment.EJB-MainEAR.ear.EJB-Main.jar:main" from Service Module
Loader: java.lang.LinkageError: Failed to link
com/framework/business/ejb/session/SistemaSessionBean (Module
"deployment.EJB-MainEAR.ear.EJB-Main.jar:main" from Service Module Loader)
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:401)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
[jboss-modules.jar:1.0.2.GA]
at org.jboss.modules.Module.loadModuleClass(Module.java:590)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:201)
at
org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:83)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
[jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.7.0_01]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.7.0_01]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_01]
Caused by: java.lang.NoClassDefFoundError:
com/framework/business/client/intf/SistemaSession
at java.lang.ClassLoader.defineClass1(Native Method) [:1.7.0_01]
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
[:1.7.0_01]
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[:1.7.0_01]
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:397)
[jboss-modules.jar:1.0.2.GA]
... 15 more
Caused by: java.lang.ClassNotFoundException:
com.framework.business.client.intf.SistemaSession from [Module
"deployment.EJB-MainEAR.ear.EJB-Main.jar:main" from Service Module Loader]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
[jboss-modules.jar:1.0.2.GA]
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
[jboss-modules.jar:1.0.2.GA]
... 19 more
Then i tried to add a jboss-deployment-structure.xml file to the EAR,
defining all the dependencies.
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<dependencies>
<module name="com.keyworks.k3" />
</dependencies>
</deployment>
<sub-deployment name="JPA-Main.jar">
</sub-deployment>
<sub-deployment name="EJB-MainClient.jar">
<dependencies>
<module name="deployment.EJB-MainEAR.ear.JPA-Main.jar:main" />
</dependencies>
</sub-deployment>
<sub-deployment name="EJB-Main.jar">
<dependencies>
<module name="deployment.EJB-MainEAR.ear.JPA-Main.jar:main" />
<module
name="deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main" />
</dependencies>
</sub-deployment>
<sub-deployment name="GWT-Main.war">
<dependencies>
<module name="deployment.EJB-MainEAR.ear.JPA-Main.jar:main" />
<module
name="deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main" />
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
And the error message when starting JBoss was:
10:43:37,194 INFO [org.jboss.as.server.controller]
(DeploymentScanner-threads - 2) Deployment of "EJB-MainEAR.ear" was rolled
back with failure message {"Services with missing/unavailable
dependencies" =>
["jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"GWT-Website.war\".CONFIGURE_MODULE
missing [
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar:main\".main,
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main\".main
]","jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"EJB-Main.jar\".CONFIGURE_MODULE
missing [
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar:main\".main,
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main\".main
]","jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"JPA-Main.jar\".POST_MODULE
missing [
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-Main.jar\".main
]","jboss.module.service.\"deployment.EJB-MainEAR.ear\".main missing [
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-Main.jar\".main
]","jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"EJB-MainClient.jar\".CONFIGURE_MODULE
missing [
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar:main\".main
]","jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"TST-Main.war\".CONFIGURE_MODULE
missing [
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar:main\".main,
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main\".main
]","jboss.deployment.unit.\"EJB-MainEAR.ear\".POST_MODULE missing [
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.GWT-Website.war\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-Main.jar\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.TST-Main.war\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.GWT-Main.war\".main
]","jboss.deployment.subunit.\"EJB-MainEAR.ear\".\"GWT-Main.war\".CONFIGURE_MODULE
missing [
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar:main\".main,
jboss.module.information.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar:main\".main
]","jboss.module.service.\"deployment.EJB-MainEAR.ear.JPA-Main.jar\".main
missing [
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-MainClient.jar\".main,
jboss.module.spec.service.\"deployment.EJB-MainEAR.ear.EJB-Main.jar\".main
]"]}
What i need to do for my modules (JAR and WAR) to see each other and get
this working?
Diego Keller
diego.keller(a)keyworks.com.br
(54) 3534-8980
http://www.keyworks.com.br
Keyworks TI ® - Tailor Made Software
14 years, 2 months
Datasource operation - test-connection-in-pool is failing
by Vimal Kansal
Hi,
I have configured a PostGreSQL 8.4 datasource on the latest build using
the admin console, which writes the following configuration to
standalone.xml :
<datasource jndi-name="java:jboss/datasources/MyDS"
pool-name="MyDS_Pool" enabled="false" jta="false" use-ccm="false">
<connection-url>
jdbc:postgresql://localhost:5432/testdb
</connection-url>
<driver-class>
org.postgresql.Driver
</driver-class>
<driver>
postgresql-8.4-702.jdbc4.jar
</driver>
<security>
<user-name>
postgres
</user-name>
<password>
postgres
</password>
</security>
. . .
When I click the "Test" button on admin console or invoke the
"test-connection-in-pool" operation (which is what is invoked by admin
cosnole) using CLI, it fails with following error :
14:28:34,187 ERROR [org.jboss.as.controller]
(HttpManagementService-threads - 4) Operation
("test-connection-in-pool") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "java:jboss/datasources/MyDS")
]) - failure description: "failed to invoke operation: failed to match
pool. Check JndiName: java:jboss/datasources/MyDS"
Besdies this error, there is no other log message. This used to work
earlier ( I still have an instance - one month old build, on which same
definition is working.) I think possibly it is a bug.
Thx
Vimal
14 years, 2 months
Core Logging and Messages
by James Perkins
Hello All,
I've add the base support for subsystems to use the JBoss Logging i18n
tools for log messages and messages. I have not gone through and
converted all the messages in every subsystem/module, though there are a
number of them that have been converted.
When you are working in the subsystems/modules please use the
@MessageLogger for all logging and the @MessageBundle for all text that
needs to be translated as well as exceptions. If you have the time,
please feel free to convert any older log messages or exceptions that
need to be converted. This is a fairly time consuming task to do all in
one shot.
Here are some general guidelines on how the i18n work should be done
http://community.jboss.org/wiki/LoggingInCoreJBossApplicationServer7.
There is a listing of some of the subsystems/modules and there progress
here http://community.jboss.org/wiki/LoggingIds.
If you have any questions feel free to contact me.
--
James R. Perkins
JBoss by Red Hat
14 years, 2 months
Re: [jboss-as7-dev] [hibernate-dev] Which JBoss Logging version to use in AS and Hibernate Core
by David M. Lloyd
I can look into it tonight. Have you tested with the latest 3.1.0
release to verify there are no problems?
On 11/07/2011 09:51 AM, Steve Ebersole wrote:
> Specifically, is there anyway to get org.jboss.logging:jboss-logging to
> Final/GA in the next few days? The generator/processor is irrelevant as
> far as we are concerned for a Hibernate release.
>
> On Mon 07 Nov 2011 09:47:08 AM CST, Steve Ebersole wrote:
>> Which really sucks since 4.0 Final is slated for 2 days.
>>
>> Ugh.
>>
>> On Fri 04 Nov 2011 10:59:24 AM CDT, Emmanuel Bernard wrote:
>>> Do you know when JBoss Logging 3.1.0.GA will hit the road. I can't
>>> really release Hibernate Commons Annotations nor Core etc until we
>>> have the final version. I mean we could but we might have to redo it.
>>>
>>> Emmanuel
>>>
>>> On 4 nov. 2011, at 16:05, David M. Lloyd wrote:
>>>
>>>> Yeah let's target 3.1.0.GA for everything. The final 1.0.0.GA release
>>>> of the i18n logging tool will require 3.1.0.GA.
>>>>
>>>> On 11/04/2011 09:42 AM, Scott Marlow wrote:
>>>>> Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
>>>>> Hibernate (Core) module. The "org.jboss.logging" module happens to be
>>>>> "3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
>>>>> sync with the AS7 version of JBoss Logging.
>>>>>
>>>>> https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
>>>>>
>>>>>
>>>>> I think that AS7 needs to stay in sync with what integrated
>>>>> projects are
>>>>> using (using the 3.1.0.* versions of JBoss logging for AS 7.1).
>>>>>
>>>>>
>>>>> On 11/04/2011 07:30 AM, Emmanuel Bernard wrote:
>>>>>> JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
>>>>>> Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
>>>>>>
>>>>>> // logging
>>>>>> logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
>>>>>> logging_generator:
>>>>>> 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
>>>>>> logging_processor:
>>>>>> 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
>>>>>>
>>>>>> So which one we should go to? Once we have decided, I will align
>>>>>> Search, OGM and Commons Annotations.
>>>>>>
>>>>>> Emmanuel
>>>>>> _______________________________________________
>>>>>> hibernate-dev mailing list
>>>>>> hibernate-dev(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>
>>>> --
>>>> - DML
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
--
- DML
14 years, 2 months
