[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing
by Stefan Negrea (JIRA)
Stefan Negrea created AS7-4464:
----------------------------------
Summary: EJB3 deployment metrics missing
Key: AS7-4464
URL: https://issues.jboss.org/browse/AS7-4464
Project: Application Server 7
Issue Type: Enhancement
Reporter: Stefan Negrea
The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics:
Stateless Session Bean
Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
Stateful Session Bean
Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
Cache Size - Cache Size
Passivated Count - Passivated Count
Total Size - Total Size
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (AS7-1684) Add configuration setting that allows an extended persistence context to be propagated even if there is no JTA transaction
by Scott Marlow (JIRA)
Add configuration setting that allows an extended persistence context to be propagated even if there is no JTA transaction
---------------------------------------------------------------------------------------------------------------------------
Key: AS7-1684
URL: https://issues.jboss.org/browse/AS7-1684
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.0.Beta2
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
Earlier versions of AS, allowed an extended persistence context (XPC) to propagate, even if no JTA transaction was active during use of the XPC. With the recent fix to AS7-1663, using an XPC outside of a JTA transaction and then invoking a transactional entity manager inside of a JTA transaction, will not propagate the XPC into the new transaction.
Add a domain default setting that allows the (not used in a JTA transaction) XPC to propagate into the new transaction (on behalf of a transactional entity manager). This will only happen if the XPC is active in the call stack.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBWEB-211) Jasper Parser drops exception root cause
by Andrew Sacamano (JIRA)
Jasper Parser drops exception root cause
----------------------------------------
Key: JBWEB-211
URL: https://issues.jboss.org/browse/JBWEB-211
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tomcat
Affects Versions: JBossWeb-2.1.9.GA
Environment: All
Reporter: Andrew Sacamano
Assignee: Remy Maucherat
Priority: Minor
Line 342 in of java/org/apache/jasper/compiler/Parser.java (see below) commits one of the cardinal sins of exception handling - it drops the original stack trace, and original root causes.
This has contributed to the premature grey hair of one of our sysadmins, as he tries to sort out why a particular tag is causing the JSP compiler to puke.
327
328 /*
329 * Invokes parserController to parse the included page
330 */
331 private void processIncludeDirective(String file, Node parent)
332 throws JasperException {
333 if (file == null) {
334 return;
335 }
336
337 try {
338 parserController.parse(file, parent, jarFileUrl);
339 } catch (FileNotFoundException ex) {
340 err.jspError(start, "jsp.error.file.not.found", file);
341 } catch (Exception ex) {
342 err.jspError(start, ex.getMessage());
343 }
344 }
345
It looks like there is a bit of work involved to craft a better response, perhaps adding another jspError variant - but surely the actual exception is important enough to go through the effort.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4777) Use logger instead of [stdout] for JGroups GMS logger
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-4777:
-----------------------------------
Summary: Use logger instead of [stdout] for JGroups GMS logger
Key: AS7-4777
URL: https://issues.jboss.org/browse/AS7-4777
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.2.Final (EAP)
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Trivial
Fix For: 7.2.0.Alpha1
...and possibly remove the unnecessary dash lines on the way.
{noformat}
[JBossINF] 12:11:12,677 INFO [org.jboss.as.osgi] (MSC service thread 1-15) JBAS011907: Register module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-ejb.jar:main" from Service Module Loader
[JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1)
[JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) -------------------------------------------------------------------
[JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200
[JBossINF] 12:11:13,143 INFO [stdout] (ChannelService lifecycle - 1) -------------------------------------------------------------------
[JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1)
[JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) -------------------------------------------------------------------
[JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/ejb, cluster=ejb, physical address=10.16.90.54:55200
[JBossINF] 12:11:13,210 INFO [stdout] (ChannelService lifecycle - 1) -------------------------------------------------------------------
[JBossINF] 12:11:13,441 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3180) Clean shutdown often results in "Problems unmarshalling remote command from byte buffer"
by Radoslav Husar (Created) (JIRA)
Clean shutdown often results in "Problems unmarshalling remote command from byte buffer"
----------------------------------------------------------------------------------------
Key: AS7-3180
URL: https://issues.jboss.org/browse/AS7-3180
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.CR1
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.0.Final
When shutting down a server from a cluster, it often results in
WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Cache manager is either starting up or shutting down but it's not interrupted, so type (id=74) cannot be resolved.
incluing verbose logging which doesnt seem necessary
and jgroups logs
[JBossINF] 12:28:22,392 SEVERE [org.jgroups.protocols.UNICAST2] perf19/web: sender window for perf21/web not found
is this a real problem? if not, can it be handled more cleanly?
{noformat}
[JBossINF] 12:28:21,960 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-7) Pausing Coyote HTTP/1.1 on http-perf19-10.16.90.56-8080
[JBossINF] 12:28:21,961 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-7) Stopping Coyote HTTP/1.1 on http-perf19-10.16.90.56-8080
[JBossINF] 12:28:21,974 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
[JBossINF] 12:28:21,975 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
[JBossINF] 12:28:22,008 INFO [org.jboss.as.clustering] JBAS010302: Stopped org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from sfsb container
[JBossINF] 12:28:22,010 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [be9627f1-362f-11e1-986b-d4856468f854] stopped
[JBossINF] 12:28:22,012 INFO [org.apache.coyote.ajp.AjpAprProtocol] Pausing Coyote AJP/1.3 on ajp-perf19-10.16.90.56-8009
[JBossINF] 12:28:22,012 INFO [org.apache.coyote.ajp.AjpAprProtocol] Stopping Coyote AJP/1.3 on ajp-perf19-10.16.90.56-8009
[JBossINF] 12:28:22,013 INFO [org.jboss.as.clustering] JBAS010302: Stopped org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl cache from sfsb container
[JBossINF] 12:28:22,022 INFO [jacorb.poa] POA RootPOA destroyed
[JBossINF] 12:28:22,029 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000029: Passivating all entries to disk
[JBossINF] 12:28:22,029 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000030: Passivated 0 entries in 0 milliseconds
[JBossINF] 12:28:22,030 INFO [jacorb.orb] prepare ORB for shutdown...
[JBossINF] 12:28:22,030 INFO [jacorb.orb] ORB going down...
[JBossINF] 12:28:22,031 INFO [jacorb.orb] ORB shutdown complete
[JBossINF] 12:28:22,032 INFO [jacorb.orb] ORB run, exit
[JBossINF] 12:28:22,032 INFO [jacorb.orb.iiop] Listener exited
[JBossINF] 12:28:22,036 INFO [org.jboss.weld] Stopping weld service
[JBossINF] 12:28:22,038 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000029: Passivating all entries to disk
[JBossINF] 12:28:22,038 INFO [org.infinispan.eviction.PassivationManagerImpl] ISPN000030: Passivated 0 entries in 0 milliseconds
[JBossINF] 12:28:22,047 INFO [org.jboss.as.server.deployment] Stopped deployment clusterbench-ee6-ejb.jar in 91ms
[JBossINF] 12:28:22,048 INFO [org.jboss.as.server.deployment] Stopped deployment clusterbench-ee6-web.war in 91ms
[JBossINF] 12:28:22,049 INFO [org.jboss.as.server.deployment] Stopped deployment clusterbench-ee6.ear in 97ms
[JBossINF] 12:28:22,057 INFO [org.jboss.as.clustering] JBAS010302: Stopped registry cache from web container
[JBossINF] 12:28:22,063 INFO [org.jboss.as.clustering] JBAS010302: Stopped repl cache from web container
[JBossINF] 12:28:22,069 INFO [org.jboss.as.clustering] JBAS010302: Stopped repl cache from sfsb container
[JBossINF] 12:28:22,336 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
[JBossINF] 12:28:22,392 SEVERE [org.jgroups.protocols.UNICAST2] perf19/web: sender window for perf21/web not found
[JBossINF] 12:28:22,440 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
[JBossINF] 12:28:22,441 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
[JBossINF] 12:28:22,442 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
[JBossINF] 12:28:22,463 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Cache manager is either starting up or shutting down but it's not interrupted, so type (id=74) cannot be resolved.
[JBossINF] at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:257) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351)
[JBossINF] at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
[JBossINF] at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.4.GA.jar:1.3.4.GA]
[JBossINF] at org.infinispan.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:120) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.infinispan.marshall.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:115) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.infinispan.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:79) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromBuffer(MarshallerAdapter.java:50) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:139) [infinispan-core-5.1.0.CR1.jar:5.1.0.CR1]
[JBossINF] at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:447) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:354) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:230) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:556) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler.up(ClassLoaderAwareUpHandler.java:56) [jboss-as-clustering-jgroups-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[JBossINF] at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jboss.as.clustering.jgroups.MuxChannel$ClassLoaderAwareMuxUpHandler.up(MuxChannel.java:64) [jboss-as-clustering-jgroups-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
[JBossINF] at org.jgroups.JChannel.up(JChannel.java:716) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:481) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:178) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:881) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:383) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:733) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:561) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.BARRIER.up(BARRIER.java:126) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:140) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.FD.up(FD.java:273) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:284) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.Discovery.up(Discovery.java:354) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.stack.Protocol.up(Protocol.java:358) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.TP.passMessageUp(TP.java:1174) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1709) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1691) [jgroups-3.0.1.Final.jar:3.0.1.Final]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
[JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
[JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
[JBossINF]
[JBossINF] 12:28:22,809 INFO [org.jboss.as] JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" stopped in 815ms
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4526) CLONE - Setting 'site' attribute of cache-container Transport causes EAP not boot up due to XML parsing error
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/AS7-4526?page=com.atlassian.jira.plugin.s... ]
Jan Martiska closed AS7-4526.
-----------------------------
Verified with EAP ER7.
> CLONE - Setting 'site' attribute of cache-container Transport causes EAP not boot up due to XML parsing error
> -------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4526
> URL: https://issues.jboss.org/browse/AS7-4526
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering, Domain Management
> Affects Versions: 7.1.1.Final
> Reporter: Jan Martiska
> Assignee: Richard Achmatowicz
> Priority: Critical
> Fix For: 7.1.2.Final (EAP)
>
>
> Using CLI or Admin Console - define TRANSPORT for a cache container
> {noformat}
> /subsystem=infinispan/cache-container=hibernate/transport=TRANSPORT/:add
> {noformat}
> .. and define 'site' attribute for it
> {noformat}
> /subsystem=infinispan/cache-container=hibernate/transport=TRANSPORT/:write-attribute(name="site", value="30")
> {noformat}
> This will cause EAP will not be able to boot up because attribute 'site' is unknown to XML parser:
> {noformat}
> ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[153,17]
> Message: JBAS014788: Unexpected attribute 'site' encountered
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months