[JBoss JIRA] (JASSIST-163) RuntimeSupport.find2Methods a perf hotspot when proxy's methods are called at higher concurrency
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JASSIST-163?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JASSIST-163:
-------------------------------------------------
Brett Meyer <brmeyer(a)redhat.com> made a comment on [bug 900690|https://bugzilla.redhat.com/show_bug.cgi?id=900690]
On hold for:
https://issues.jboss.org/browse/JASSIST-183
https://issues.jboss.org/browse/JASSIST-189
> RuntimeSupport.find2Methods a perf hotspot when proxy's methods are called at higher concurrency
> ------------------------------------------------------------------------------------------------
>
> Key: JASSIST-163
> URL: https://issues.jboss.org/browse/JASSIST-163
> Project: Javassist
> Issue Type: Enhancement
> Affects Versions: 3.15.0-GA, 3.16.1-GA
> Environment: hibernate-core 3.6.10.Final
> Reporter: Nikita Tovstoles
> Assignee: Shigeru Chiba
> Fix For: 3.17.0-GA
>
> Attachments: Bean_$$_bulkaccess_0.txt, Bean_$$_bulkaccess_0_Two.txt, blocked-threads.png, BulkAccessorFactory.java.diff, BulkAccessorFactory.java.diff2, BulkAccessorFactory.patch, find2methods-hotspot.png, jassist-163-fix.patch, monitor-backtraces.png, monitor-backtraces.png, Product.java, Product_$$_javassist_0-post-patch.java, Product_$$_javassist_0.java, Tomcat-2012-03-28(2).zip
>
>
> We've been profiling our Hibernate 3.6.10-based app and noticed a perf bottleneck in javassist.util.proxy.RuntimeSupport.find2methods. Unfortunately, this method, which has a synch. block, is being called on
> every invocation of every proxied entity method (see javassist.util.proxy.ProxyFactory.makeForwarder(), called indirectly by
> ProxyFactory.createClass()).
> In our testing, the result is that our service call's latency increases from 33 to 55, 260, 400ms as concurrency increases
> 1-10-20-30 users on a 4-core CPU. At 20 and 30 users 51% of CPU time is spent contending for a monitor in RuntimeSupport.find2methods:
> {code}
> synchronized (methods) {
> if (methods[index] == null) {
> methods[index + 1] = thisMethod == null ? null
> : findMethod(self, thisMethod, desc);
> methods[index] = findSuperMethod(self, superMethod, desc);
> }
> }
> {code}
> Since find2methods merely interrogates class metadata, seems like its return values should be cached (in a ConcurrentMap?) instead of repeatedly executing the above synchronized statement. Instead, currently, it's being called every time (?) a proxied method is executed - see *Invocation Count* in this screen shot:
> https://issues.jboss.org/secure/attachment/12353025/monitor-backtraces.png
> Full [YourKit profile|http://yourkit.com] is [attached as a ZIP archive|^Tomcat-2012-03-28(2).zip]; key screen shots from the snapshot also attached separately
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6704) build modular AS with Apache Karaf support error
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6704?page=com.atlassian.jira.plugin.s... ]
SBS JIRA Integration updated AS7-6704:
--------------------------------------
Forum Reference: https://community.jboss.org/message/801855, https://community.jboss.org/message/801941#801941 (was: https://community.jboss.org/message/801855)
> build modular AS with Apache Karaf support error
> ------------------------------------------------
>
> Key: AS7-6704
> URL: https://issues.jboss.org/browse/AS7-6704
> Project: Application Server 7
> Issue Type: Bug
> Reporter: Julio Carlos Barrera
> Labels: Karaf, OSGi, build_issue
>
> I followed the instruction of this forum thread https://community.jboss.org/message/801855 and it gave me this error:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build Modular 7.2.0.Final
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ jboss-as-build-modular ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildNumber: 4ed76ceef253c568b7475780a92e49a034f540c5 at timestamp: 1362997311876
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildScmBranch: UNKNOWN
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (modular-config) @ jboss-as-build-modular ---
> [INFO] Executing tasks
> main:
> init:
> init.standalone:
> generate-standalone-configs:
> [echo] Generate subsystems definition for logging:osgi,osgi:karaf,configadmin to /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml
> [echo] Generate module dependencies from /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml to /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /home/logoff/soft/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java
> [java] .io.FileInputStream.<init>(FileInputStream.java:120)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> [echo] Merging standalone configuration/standalone/template-osgi.xml and /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml into /home/logoff/soft/jboss-as/build-modular/target/standalone.xml, using StandaloneMain
> init.domain:
> generate-domain-configs:
> build-standalone-server:
> [mkdir] Created dir: /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Final
> [copy] Copying 241 files to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Final
> [copy] Copied 43 empty directories to 4 empty directories under /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Final
> [copy] Copying 1 file to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-7.2.0.Final/standalone/configuration
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7.356s
> [INFO] Finished at: Mon Mar 11 11:21:54 CET 2013
> [INFO] Final Memory: 13M/118M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (modular-config) on project jboss-as-build-modular: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/logoff/soft/jboss-as/build-modular/build-modular-config.xml:113: Includesfile /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt not found.
> [ERROR] around Ant part ...<ant antfile="build-modular-config.xml" inheritRefs="true">... @ 4:62 in /home/logoff/soft/jboss-as/build-modular/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> It is possible to build JBoss AS 7.2.0.Final-prerelease1 or any version with Apache Karaf support?
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6705) build modular AS with Apache Karaf support error
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6705?page=com.atlassian.jira.plugin.s... ]
SBS JIRA Integration updated AS7-6705:
--------------------------------------
Forum Reference: https://community.jboss.org/message/801855, https://community.jboss.org/message/801941#801941 (was: https://community.jboss.org/message/801855)
> build modular AS with Apache Karaf support error
> ------------------------------------------------
>
> Key: AS7-6705
> URL: https://issues.jboss.org/browse/AS7-6705
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Reporter: Julio Carlos Barrera
> Labels: Karaf, OSGi, build_issue
>
> I followed the instruction of this forum thread https://community.jboss.org/message/801855 and it gave me this error:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build Modular 8.0.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ jboss-as-build-modular ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildNumber: bfeb0721e0a10c630d164a861c01e343b27ee313 at timestamp: 1363002756518
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildScmBranch: UNKNOWN
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (modular-config) @ jboss-as-build-modular ---
> [INFO] Executing tasks
> main:
> init:
> init.standalone:
> generate-standalone-configs:
> [echo] Generate subsystems definition for logging:osgi,osgi:karaf,configadmin to /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml
> [echo] Generate module dependencies from /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml to /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /home/logoff/soft/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> [echo] Merging standalone configuration/standalone/template-osgi.xml and /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml into /home/logoff/soft/jboss-as/build-modular/target/standalone.xml, using StandaloneMain
> init.domain:
> generate-domain-configs:
> build-standalone-server:
> [mkdir] Created dir: /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 240 files to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copied 43 empty directories to 4 empty directories under /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 1 file to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT/standalone/configuration
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.659s
> [INFO] Finished at: Mon Mar 11 12:52:39 CET 2013
> [INFO] Final Memory: 16M/168M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (modular-config) on project jboss-as-build-modular: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/logoff/soft/jboss-as/build-modular/build-modular-config.xml:113: Includesfile /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt not found.
> [ERROR] around Ant part ...<ant antfile="build-modular-config.xml" inheritRefs="true">... @ 4:62 in /home/logoff/soft/jboss-as/build-modular/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> It is possible to build JBoss AS 8.0.0.Alpha1-SNAPSHOT or any version with Apache Karaf support?
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6428) Using Session Scope CDI bean does not work in a HttpSessionListener
by Remy Maucherat (JIRA)
[ https://issues.jboss.org/browse/AS7-6428?page=com.atlassian.jira.plugin.s... ]
Remy Maucherat commented on AS7-6428:
-------------------------------------
If I understand correctly, this is about returning the session object for getSession(false) while getSession(true) has not finished. The "correct" behavior is not really specified, and I don't find it so logical ...
The behavior is the same in Tomcat, and would probably need to be validated by the Servlet EG (personally, I am not convinced).
> Using Session Scope CDI bean does not work in a HttpSessionListener
> -------------------------------------------------------------------
>
> Key: AS7-6428
> URL: https://issues.jboss.org/browse/AS7-6428
> Project: Application Server 7
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 7.1.1.Final
> Environment: linux 64bits, win7 64 bits
> Reporter: nicolas marchais
> Assignee: Remy Maucherat
> Fix For: No Release
>
>
> JBoss AS 7.1.x has a bug with using session bean scope in a HttpSessionListener.
> When i inject a session scope bean in a HttpSessionListener and i try to populate attribute in sessionCreated() method many HttpSession are created by JBoss AS. Is it normal the a web server create many Http session for the same request ?
> Normally, this behaviour should work. See : http://docs.jboss.org/cdi/api/1.1-PRD/javax/enterprise/context/SessionSco...
> I did a light Web Project to explain the problem with 1 JSP, 1 SessionScope bean and 1 HttpSessionListener.
> Here is the code.
> JSP page :
> <%@ page language="java" contentType="text/html; charset=UTF-8"
> pageEncoding="UTF-8"%>
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> SessionScope bean :
> @Named
> @SessionScoped
> public class UserState implements Serializable {
> private int state;
> public int getState() {
> return state;
> }
> public void setState(int state) {
> this.state = state;
> }
> }
> HttpSessionListener :
> @WebListener
> public class SessionListener implements HttpSessionListener {
> @Inject private UserState userState;
>
> @Override
> public void sessionCreated(HttpSessionEvent event) {
> System.out.println("New HTTP Session created : " + event.getSession().getId());
> userState.setState(2);
> }
> @Override
> public void sessionDestroyed(HttpSessionEvent event) {}
> }
> After execution, you can read in the console at least 2 http session creation like this :
> New HTTP Session created : zvlF6vGLP1AaXM-rzFU02wAJ.undefined
> New HTTP Session created : TlrmmA8Eu4v32SHDT0QBBZza.undefined
> The first session seams to be the one which is used by the client. There is one more problem : The polutated attributes of the session scope bean are ignored after HttpSessionListener execution. At the end all session scope attributes are null.
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6706) Move Webservices client-config management into an MSC service
by Paul Robinson (JIRA)
Paul Robinson created AS7-6706:
----------------------------------
Summary: Move Webservices client-config management into an MSC service
Key: AS7-6706
URL: https://issues.jboss.org/browse/AS7-6706
Project: Application Server 7
Issue Type: Enhancement
Components: Web Services
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 8.0.0.Alpha1
Currently the client configuration is managed in 'add' and 'remove' step handlers. This causes two problems:
1) Other services can not depend on this configuration being ready.
2) Injection can't be used to obtain the ServerConfig.
The solution is to have the add and remove step handlers start and stop a service (respectively). This service is dependent on the CONFIG_SERVICE and has the ServerConfig injected. Other services that need the ClientConfig can depend on this service.
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6705) build modular AS with Apache Karaf support error
by Julio Carlos Barrera (JIRA)
[ https://issues.jboss.org/browse/AS7-6705?page=com.atlassian.jira.plugin.s... ]
Julio Carlos Barrera commented on AS7-6705:
-------------------------------------------
I made no changes in any configuration, I tried it with a clean checkout from GitHub. I am going to open an forum thread to clarify it.
> build modular AS with Apache Karaf support error
> ------------------------------------------------
>
> Key: AS7-6705
> URL: https://issues.jboss.org/browse/AS7-6705
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Reporter: Julio Carlos Barrera
> Labels: Karaf, OSGi, build_issue
>
> I followed the instruction of this forum thread https://community.jboss.org/message/801855 and it gave me this error:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build Modular 8.0.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ jboss-as-build-modular ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildNumber: bfeb0721e0a10c630d164a861c01e343b27ee313 at timestamp: 1363002756518
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildScmBranch: UNKNOWN
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (modular-config) @ jboss-as-build-modular ---
> [INFO] Executing tasks
> main:
> init:
> init.standalone:
> generate-standalone-configs:
> [echo] Generate subsystems definition for logging:osgi,osgi:karaf,configadmin to /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml
> [echo] Generate module dependencies from /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml to /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /home/logoff/soft/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> [echo] Merging standalone configuration/standalone/template-osgi.xml and /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml into /home/logoff/soft/jboss-as/build-modular/target/standalone.xml, using StandaloneMain
> init.domain:
> generate-domain-configs:
> build-standalone-server:
> [mkdir] Created dir: /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 240 files to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copied 43 empty directories to 4 empty directories under /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 1 file to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT/standalone/configuration
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.659s
> [INFO] Finished at: Mon Mar 11 12:52:39 CET 2013
> [INFO] Final Memory: 16M/168M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (modular-config) on project jboss-as-build-modular: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/logoff/soft/jboss-as/build-modular/build-modular-config.xml:113: Includesfile /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt not found.
> [ERROR] around Ant part ...<ant antfile="build-modular-config.xml" inheritRefs="true">... @ 4:62 in /home/logoff/soft/jboss-as/build-modular/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> It is possible to build JBoss AS 8.0.0.Alpha1-SNAPSHOT or any version with Apache Karaf support?
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6450) Missing <recovery> element. XA recovery disabled for: java:/JmsXA
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6450?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6450:
----------------------------------------------
Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 907901|https://bugzilla.redhat.com/show_bug.cgi?id=907901]
This issue is fixed. Verified in EAP 6.1.0.ER2. Thanks Jeff!
> Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> -----------------------------------------------------------------
>
> Key: AS7-6450
> URL: https://issues.jboss.org/browse/AS7-6450
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> With latest version of HornetQ and IronJacamar, when AS7 is started with the standalone-full.xml, it logs a WARN message:
> {noformat}
> 11:23:11,152 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingpaging)
> 11:23:11,154 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221008: Waiting to obtain live lock
> 11:23:11,175 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221017: Using NIO Journal
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221039: Waiting to obtain live lock
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221040: Live Server Obtained live lock
> 11:23:11,489 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol
> 11:23:11,490 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221009: Server is now live
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [0ac0dcd4-6f7e-11e2-9c21-f566250843f7]
> 11:23:11,507 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> 11:23:11,508 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 11:23:11,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
> 11:23:11,545 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> 11:23:11,568 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
> 11:23:11,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 11:23:11,570 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> {noformat}
> This WARN was not present in AS7 7.1.2.Final
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6450) Missing <recovery> element. XA recovery disabled for: java:/JmsXA
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6450?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6450:
----------------------------------------------
Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 907901|https://bugzilla.redhat.com/show_bug.cgi?id=907901] from ON_QA to VERIFIED
> Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> -----------------------------------------------------------------
>
> Key: AS7-6450
> URL: https://issues.jboss.org/browse/AS7-6450
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> With latest version of HornetQ and IronJacamar, when AS7 is started with the standalone-full.xml, it logs a WARN message:
> {noformat}
> 11:23:11,152 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221001: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/Users/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/messagingpaging)
> 11:23:11,154 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221008: Waiting to obtain live lock
> 11:23:11,175 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221017: Using NIO Journal
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221039: Waiting to obtain live lock
> 11:23:11,235 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221040: Live Server Obtained live lock
> 11:23:11,489 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol
> 11:23:11,490 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221009: Server is now live
> 11:23:11,492 INFO [org.hornetq.core.server] (MSC service thread 1-5) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [0ac0dcd4-6f7e-11e2-9c21-f566250843f7]
> 11:23:11,507 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
> 11:23:11,508 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 11:23:11,543 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
> 11:23:11,545 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
> 11:23:11,568 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
> 11:23:11,569 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 11:23:11,570 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
> {noformat}
> This WARN was not present in AS7 7.1.2.Final
--
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
13 years, 4 months
[JBoss JIRA] (AS7-6705) build modular AS with Apache Karaf support error
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6705?page=com.atlassian.jira.plugin.s... ]
David Lloyd resolved AS7-6705.
------------------------------
Resolution: Rejected
As was explained in AS7-6704, this is not a bug. This is a problem you are having with a particular configuration. This discussion belongs on the forums, not in the bug tracker.
> build modular AS with Apache Karaf support error
> ------------------------------------------------
>
> Key: AS7-6705
> URL: https://issues.jboss.org/browse/AS7-6705
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Reporter: Julio Carlos Barrera
> Labels: Karaf, OSGi, build_issue
>
> I followed the instruction of this forum thread https://community.jboss.org/message/801855 and it gave me this error:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build Modular 8.0.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create-timestamp (get-build-timestamp) @ jboss-as-build-modular ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @ jboss-as-build-modular ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildNumber: bfeb0721e0a10c630d164a861c01e343b27ee313 at timestamp: 1363002756518
> [INFO] Executing: /bin/sh -c cd /home/logoff/soft/jboss-as/build-modular && git rev-parse --verify HEAD
> [INFO] Working directory: /home/logoff/soft/jboss-as/build-modular
> [INFO] Storing buildScmBranch: UNKNOWN
> [INFO]
> [INFO] --- maven-antrun-plugin:1.7:run (modular-config) @ jboss-as-build-modular ---
> [INFO] Executing tasks
> main:
> init:
> init.standalone:
> generate-standalone-configs:
> [echo] Generate subsystems definition for logging:osgi,osgi:karaf,configadmin to /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml
> [echo] Generate module dependencies from /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml to /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /home/logoff/soft/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> [echo] Merging standalone configuration/standalone/template-osgi.xml and /home/logoff/soft/jboss-as/build-modular/target/standalone-subsystems.xml into /home/logoff/soft/jboss-as/build-modular/target/standalone.xml, using StandaloneMain
> init.domain:
> generate-domain-configs:
> build-standalone-server:
> [mkdir] Created dir: /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 240 files to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copied 43 empty directories to 4 empty directories under /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT
> [copy] Copying 1 file to /home/logoff/soft/jboss-as/build-modular/target/jboss-as-karaf-8.0.0.Alpha1-SNAPSHOT/standalone/configuration
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.659s
> [INFO] Finished at: Mon Mar 11 12:52:39 CET 2013
> [INFO] Final Memory: 16M/168M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (modular-config) on project jboss-as-build-modular: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/logoff/soft/jboss-as/build-modular/build-modular-config.xml:113: Includesfile /home/logoff/soft/jboss-as/build-modular/target/standalone-module-dependencies.txt not found.
> [ERROR] around Ant part ...<ant antfile="build-modular-config.xml" inheritRefs="true">... @ 4:62 in /home/logoff/soft/jboss-as/build-modular/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> It is possible to build JBoss AS 8.0.0.Alpha1-SNAPSHOT or any version with Apache Karaf support?
--
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
13 years, 4 months
[JBoss JIRA] (AS7-5063) AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-5063?page=com.atlassian.jira.plugin.s... ]
Scott Marlow commented on AS7-5063:
-----------------------------------
I'm moving the current AS/jpa {hibernate3, hibernate4, openjpa, spi} code into a separate git repo that can also have the EclipseLink integration code (and other persistence providers.) I'll have more to say in a few days :)
> AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5063
> URL: https://issues.jboss.org/browse/AS7-5063
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Affects Versions: 7.1.1.Final
> Reporter: Craig Ringer
> Assignee: Scott Marlow
> Priority: Minor
> Labels: eclipselink, jpa
> Fix For: 8.0.0.Alpha1
>
>
> For EclipseLink to properly identify the container and set up correct transaction integration, etc, it needs the property "eclipselink.target-server" to be set to "JBoss".
> There's an open issue asking EclipseLink to auto detect the container (https://bugs.eclipse.org/bugs/show_bug.cgi?id=383257) but right now, a simple solution to making EclipseLink work well on AS7 is for AS7 to pass that property to EclipseLink.
> That'll help prevent issues and confusion like this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=365704
> Users can set it as a system property right now as shown on bug 383257, but really it'd be best if JBoss passed it to the persistence unit during creation.
> Time permitting I'll give this a go.
--
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
13 years, 4 months
