[JBoss JIRA] (WFLY-3754) EJB StatefulSessionComponentInstance methodMap includes final Object methods
by James Livingston (JIRA)
James Livingston created WFLY-3754:
--------------------------------------
Summary: EJB StatefulSessionComponentInstance methodMap includes final Object methods
Key: WFLY-3754
URL: https://issues.jboss.org/browse/WFLY-3754
Project: WildFly
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 8.1.0.Final
Reporter: James Livingston
Assignee: David Lloyd
StatefulSessionComponentInstance has a methodMap which maintains the ChainedInterceptors for each method. That currently includes final Object methods which are not Business Methods for EJBs (EJB 3.1 4.9.5 "The method must not be declared as final or static"), which results in extra memory overhead for what I believe is the useless interceptors.
The amount of memory a ChainedInterceptor consumes varies between JVMs, but it is between 280 and 400 bytes in some heap dumps I looked at. With 6 final methods (wait, notify*, getClass) on java.lang.Object that adds approximately 2kb of memory use to each instance of each SFSB.
This can affect all BasicComponentInstance subclasses, but it is most noticeable for SFSBs due to the larger number of instances.
The list of methods comes from ComponentConfiguration.getDefinedComponentMethods(), but I'm not sure if filtering the final methods out should be done there or an EJB-specific class since the rule about final methods is from the EJB spec. I'm also not sure if toString, equals and hashCode() should be treated as EJB business methods either.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (WFLY-3745) In domain mode server can not be properly shutdown due to "ServiceNotFoundException: Service service jboss.server.graceful-shutdown-service not found"
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-3745?page=com.atlassian.jira.plugin.... ]
Chao Wang resolved WFLY-3745.
-----------------------------
Resolution: Cannot Reproduce Bug
> In domain mode server can not be properly shutdown due to "ServiceNotFoundException: Service service jboss.server.graceful-shutdown-service not found"
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3745
> URL: https://issues.jboss.org/browse/WFLY-3745
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Chao Wang
> Assignee: Stuart Douglas
>
> With latest Wildfly master(wildfly-core version 1.0.0.Alpha4)
> 1. start wildfly in domain mode
> 2. press Ctrl+C to shutdown
> following error messages is displayed in terminal (100% reproducible):
> {noformat}
> 14:49:54,278 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) WFLYPC0019: Stopping process 'Server:server-two'
> [Server:server-two] 14:49:54,288 ERROR [stderr] (main) org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.graceful-shutdown-service not found
> [Server:server-two] 14:49:54,298 ERROR [stderr] (main) at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668)
> [Server:server-two] 14:49:54,299 ERROR [stderr] (main) at org.jboss.as.server.DomainServerMain.getRequiredService(DomainServerMain.java:168)
> [Server:server-two] 14:49:54,300 ERROR [stderr] (main) at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:157)
> [Server:server-two] 14:49:54,300 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [Server:server-two] 14:49:54,301 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [Server:server-two] 14:49:54,308 ERROR [stderr] (main) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [Server:server-two] 14:49:54,310 ERROR [stderr] (main) at java.lang.reflect.Method.invoke(Method.java:606)
> [Server:server-two] 14:49:54,310 ERROR [stderr] (main) at org.jboss.modules.Module.run(Module.java:312)
> [Server:server-two] 14:49:54,311 ERROR [stderr] (main) at org.jboss.modules.Main.main(Main.java:460)
> 14:49:54,329 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0019: Stopping process 'Server:server-one'
> [Server:server-one] 14:49:54,331 ERROR [stderr] (main) org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.graceful-shutdown-service not found
> [Server:server-one] 14:49:54,331 ERROR [stderr] (main) at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668)
> [Server:server-one] 14:49:54,332 ERROR [stderr] (main) at org.jboss.as.server.DomainServerMain.getRequiredService(DomainServerMain.java:168)
> [Server:server-one] 14:49:54,332 ERROR [stderr] (main) at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:157)
> [Server:server-one] 14:49:54,332 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [Server:server-one] 14:49:54,332 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [Server:server-one] 14:49:54,333 ERROR [stderr] (main) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [Server:server-one] 14:49:54,333 ERROR [stderr] (main) at java.lang.reflect.Method.invoke(Method.java:606)
> [Server:server-one] 14:49:54,333 ERROR [stderr] (main) at org.jboss.modules.Module.run(Module.java:312)
> [Server:server-one] 14:49:54,333 ERROR [stderr] (main) at org.jboss.modules.Main.main(Main.java:460)
> [Server:server-one] 14:49:54,451 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 4) HQ221002: HornetQ Server version 2.5.0.SNAPSHOT (Wild Hornet, 124) [fd957918-276c-11e4-94c9-2722667d8dc0] stopped
> {noformat}
> this does not happen in standalone shutdown.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBLOGGING-109) User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable
by Caron Chen (JIRA)
[ https://issues.jboss.org/browse/JBLOGGING-109?page=com.atlassian.jira.plu... ]
Caron Chen updated JBLOGGING-109:
---------------------------------
Description:
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/Users/****/Documents/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/" is in error due to the following reason(s): org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
Deployment "vfsfile:/Users/****/Documents/jboss-5.1.0.GA/server/default/deploy/admin-console.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/Users/****/Documents/jboss-5.1.0.GA/server/default/tmp/3j001-dt0mv2-hz3cl1b1-1-hz3cl6nh-v/admin-console.war/ deployment failed
This is a Jboss without any modification.
I found that GDAL.framework has added library 'commons-logging' to the JDK. Will this affect? Thanks!
was:
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/" is in error due to the following reason(s): org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
Deployment "vfsfile:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/deploy/admin-console.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/tmp/3j001-dt0mv2-hz3cl1b1-1-hz3cl6nh-v/admin-console.war/ deployment failed
This is a Jboss without any modification.
I found that GDAL.framework has added library 'commons-logging' to the JDK. Will this affect? Thanks!
> User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable
> --------------------------------------------------------------------------------------------------------
>
> Key: JBLOGGING-109
> URL: https://issues.jboss.org/browse/JBLOGGING-109
> Project: JBoss Logging
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Mac OS X 10.9.4, JavaSE-1.7, GDAL.framework, Jboss 5.1.0GA.
> Reporter: Caron Chen
> Assignee: James Perkins
>
> DEPLOYMENTS IN ERROR:
> Deployment "vfszip:/Users/****/Documents/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/" is in error due to the following reason(s): org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
> Deployment "vfsfile:/Users/****/Documents/jboss-5.1.0.GA/server/default/deploy/admin-console.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/Users/****/Documents/jboss-5.1.0.GA/server/default/tmp/3j001-dt0mv2-hz3cl1b1-1-hz3cl6nh-v/admin-console.war/ deployment failed
> This is a Jboss without any modification.
> I found that GDAL.framework has added library 'commons-logging' to the JDK. Will this affect? Thanks!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBLOGGING-109) User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable
by Caron Chen (JIRA)
Caron Chen created JBLOGGING-109:
------------------------------------
Summary: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable
Key: JBLOGGING-109
URL: https://issues.jboss.org/browse/JBLOGGING-109
Project: JBoss Logging
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Mac OS X 10.9.4, JavaSE-1.7, GDAL.framework, Jboss 5.1.0GA.
Reporter: Caron Chen
Assignee: James Perkins
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/" is in error due to the following reason(s): org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
Deployment "vfsfile:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/deploy/admin-console.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/Users/hhchen/Documents/jboss-5.1.0.GA/server/default/tmp/3j001-dt0mv2-hz3cl1b1-1-hz3cl6nh-v/admin-console.war/ deployment failed
This is a Jboss without any modification.
I found that GDAL.framework has added library 'commons-logging' to the JDK. Will this affect? Thanks!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3751) JGroups UNICAST protocol cannot be used due to IAE
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3751?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-3751:
--------------------------------------
While at it, the timeout property is not used anymore in UNICAST either.
> JGroups UNICAST protocol cannot be used due to IAE
> --------------------------------------------------
>
> Key: WFLY-3751
> URL: https://issues.jboss.org/browse/WFLY-3751
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 9.0.0.Beta1
>
>
> Because we provide a nonexistent property in our defaults file.
> {noformat}
> 22:52:37,571 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: clusterbench-ee7.ear
> 22:52:37,661 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.3 (Final)
> 22:52:37,708 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Starting weld service for deployment clusterbench-ee7.ear
> 22:52:38,351 WARN [org.jgroups.stack.Configurator] (MSC service thread 1-4) JGRP000014: UNICAST.setTimeout has been deprecated: not used anymore
> 22:52:38,352 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.jgroups.channel.web: org.jboss.msc.service.StartException in service jboss.jgroups.channel.web: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
> at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:91)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
> at org.jgroups.stack.Configurator.createLayer(Configurator.java:460)
> at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398)
> at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90)
> at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57)
> at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477)
> at org.jgroups.JChannel.init(JChannel.java:849)
> at org.jgroups.JChannel.<init>(JChannel.java:159)
> at org.jboss.as.clustering.jgroups.MuxChannel.<init>(MuxChannel.java:37)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:81)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:85)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3751) UNICAST protocol in JGroups cannot be used due to IAE
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-3751:
------------------------------------
Summary: UNICAST protocol in JGroups cannot be used due to IAE
Key: WFLY-3751
URL: https://issues.jboss.org/browse/WFLY-3751
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 9.0.0.Beta1
Because we provide a nonexistent property in our defaults file.
{noformat}
22:52:37,571 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: clusterbench-ee7.ear
22:52:37,661 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.3 (Final)
22:52:37,708 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Starting weld service for deployment clusterbench-ee7.ear
22:52:38,351 WARN [org.jgroups.stack.Configurator] (MSC service thread 1-4) JGRP000014: UNICAST.setTimeout has been deprecated: not used anymore
22:52:38,352 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.jgroups.channel.web: org.jboss.msc.service.StartException in service jboss.jgroups.channel.web: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
at org.jgroups.stack.Configurator.createLayer(Configurator.java:460)
at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398)
at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90)
at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477)
at org.jgroups.JChannel.init(JChannel.java:849)
at org.jgroups.JChannel.<init>(JChannel.java:159)
at org.jboss.as.clustering.jgroups.MuxChannel.<init>(MuxChannel.java:37)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:81)
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:85)
... 5 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3751) JGroups UNICAST protocol cannot be used due to IAE
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3751?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-3751:
---------------------------------
Summary: JGroups UNICAST protocol cannot be used due to IAE (was: UNICAST protocol in JGroups cannot be used due to IAE)
> JGroups UNICAST protocol cannot be used due to IAE
> --------------------------------------------------
>
> Key: WFLY-3751
> URL: https://issues.jboss.org/browse/WFLY-3751
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 9.0.0.Beta1
>
>
> Because we provide a nonexistent property in our defaults file.
> {noformat}
> 22:52:37,571 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: clusterbench-ee7.ear
> 22:52:37,661 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.3 (Final)
> 22:52:37,708 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Starting weld service for deployment clusterbench-ee7.ear
> 22:52:38,351 WARN [org.jgroups.stack.Configurator] (MSC service thread 1-4) JGRP000014: UNICAST.setTimeout has been deprecated: not used anymore
> 22:52:38,352 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.jgroups.channel.web: org.jboss.msc.service.StartException in service jboss.jgroups.channel.web: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
> at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:91)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: java.lang.IllegalArgumentException: JGRP000001: configuration error: the following properties in org.jgroups.protocols.UNICAST are not recognized: {max_bytes=1m, stable_interval=5000}
> at org.jgroups.stack.Configurator.createLayer(Configurator.java:460)
> at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398)
> at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90)
> at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57)
> at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477)
> at org.jgroups.JChannel.init(JChannel.java:849)
> at org.jgroups.JChannel.<init>(JChannel.java:159)
> at org.jboss.as.clustering.jgroups.MuxChannel.<init>(MuxChannel.java:37)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:81)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:85)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months