[JBoss JIRA] (AS7-3681) JBoss crashes when run with AspectJ java agent
by dpocock (JIRA)
[ https://issues.jboss.org/browse/AS7-3681?page=com.atlassian.jira.plugin.s... ]
dpocock commented on AS7-3681:
------------------------------
I can confirm for JBoss 7.1.0.Final
a) I've observed exactly the same problem with the jmxetric agent for Ganglia
b) the same workaround appears to solve the problem
I've created a blog entry describing how I run jmxetric with a fresh install of 7.1.0.Final, including the workaround:
http://danielpocock.com/monitoring-jboss-tomcat-and-application-servers-w...
> JBoss crashes when run with AspectJ java agent
> ----------------------------------------------
>
> Key: AS7-3681
> URL: https://issues.jboss.org/browse/AS7-3681
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.0.2.Final, 7.1.0.CR1b
> Environment: OS X 10.7.2, Ubuntu 11.10
> Reporter: Jack Lund
> Assignee: David Lloyd
> Labels: aspectj, load_time_weaving
>
> When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs:
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b
> JAVA: java
> JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> WARNING: Failed to load the specified logmodule org.jboss.logmanager:main
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at org.jboss.as.server.Main.main(Main.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.jboss.modules.Module.run(Module.java:248)
> at org.jboss.modules.Main.main(Main.java:313)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
> at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
> ... 7 more
--
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-6010) After redeploy an application to a domain the old content is not removed at slave host
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6010?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-6010:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901200
> After redeploy an application to a domain the old content is not removed at slave host
> --------------------------------------------------------------------------------------
>
> Key: AS7-6010
> URL: https://issues.jboss.org/browse/AS7-6010
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.2.0.Alpha1
> Environment: OS Fedora17
> Two instances in domain mode.
> DC without server
> HC with one server
> Reporter: Wolf-Dieter Fink
> Assignee: Emanuel Muckenhuber
> Labels: deployment, domain, host-controller
> Fix For: 7.3.0.Alpha1
>
>
> If an application deployed on a domain slave HC the content is not removed if a new version of the application is deployed with 'deploy xxx --force'
> The logfile looks correct and shows:
> JBAS018565: Replaced deployment "appone.ear" with deployment "appone.ear"
> JBAS014901: Content removed from location /.../domain/servers/server-one/data/content/5e/c06cd5b58b1b6578188d822b351a14f974804c/content
> If the folder is checked the file still exists.
> An undeploy remove the files correct with the same log messages.
--
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-6010) After redeploy an application to a domain the old content is not removed at slave host
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6010?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6010:
----------------------------------
Assignee: Emanuel Muckenhuber
> After redeploy an application to a domain the old content is not removed at slave host
> --------------------------------------------------------------------------------------
>
> Key: AS7-6010
> URL: https://issues.jboss.org/browse/AS7-6010
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.2.0.Alpha1
> Environment: OS Fedora17
> Two instances in domain mode.
> DC without server
> HC with one server
> Reporter: Wolf-Dieter Fink
> Assignee: Emanuel Muckenhuber
> Labels: deployment, domain, host-controller
> Fix For: 7.3.0.Alpha1
>
>
> If an application deployed on a domain slave HC the content is not removed if a new version of the application is deployed with 'deploy xxx --force'
> The logfile looks correct and shows:
> JBAS018565: Replaced deployment "appone.ear" with deployment "appone.ear"
> JBAS014901: Content removed from location /.../domain/servers/server-one/data/content/5e/c06cd5b58b1b6578188d822b351a14f974804c/content
> If the folder is checked the file still exists.
> An undeploy remove the files correct with the same log messages.
--
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-6564) JSR-322 Java EE Connector Architecture 1.7
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6564?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen reassigned AS7-6564:
------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
> JSR-322 Java EE Connector Architecture 1.7
> ------------------------------------------
>
> Key: AS7-6564
> URL: https://issues.jboss.org/browse/AS7-6564
> Project: Application Server 7
> Issue Type: Sub-task
> Components: JCA
> Reporter: Jesper Pedersen
> Assignee: Stefano Maestri
> Fix For: 8.0.0.Alpha1
>
>
> * Integrate IronJacamar 1.1
> * Update :jca: to support DistributedWorkManager
> * Update :resource-adapters: to support new IronJacamar features
> * Update :datasources: to support new IronJacamar features
> * Deployer chain for new deployment annotations (minimum implementation - developer mode only)
--
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-4932) CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4932?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4932:
----------------------------------------------
Jitka Kudrnacova <jkudrnac(a)redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]
Affects 6.1.0.ER1:
Seen in majority of our tests.
For example here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Clus...
> CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
> -------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4932
> URL: https://issues.jboss.org/browse/AS7-4932
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: as713tracking
> Fix For: 7.1.3.Final (EAP)
>
>
> NPE is thrown in roughly 0.36% of HTTP session request processing in the test.
> This results in response code 503 returned to the client with the exception.
> The test is using passivation-enabled WAR of clusterbench
> https://github.com/rhusar/clusterbench
> Here is a shorter soak test run that uncovered the issue
> https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Clustering-Soak/jo...
> {noformat}
> [JBossINF] 19:52:10,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-2570) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:972) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1377) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:673) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:84) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
--
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