[JBoss JIRA] Created: (EJBTHREE-822) StackOverFlow when enabling log level TRACE to org.jboss.ejb3.mdb.inflow
by Juha Moisio (JIRA)
StackOverFlow when enabling log level TRACE to org.jboss.ejb3.mdb.inflow
-------------------------------------------------------------------------
Key: EJBTHREE-822
URL: http://jira.jboss.com/jira/browse/EJBTHREE-822
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Environment: RHEL 3, Sun JVM 1.5.0_08-b03
Reporter: Juha Moisio
Priority: Minor
When you enable TRACE logging level for package org.jboss.ejb3.mdb.inflow, you get
java.StackOverFlow.
XAResourceWrapper CTOR
2006-12-27 10:10:24,811 TRACE [org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory] createEndpoint org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory$
2006-12-27 10:10:24,838 ERROR [Sonic Resource Adapter for JCA] EXCEPTION: Failure in SonicActivation: java.lang.StackOverflowError
java.lang.StackOverflowError
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:109)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
at $Proxy290.toString(Unknown Source)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:503)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:119)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[JBoss JIRA] Created: (EJBTHREE-821) extend EJB3DeployerMBean attributes regarding JarsIgnoredForScanning
by Avishay Halperen (JIRA)
extend EJB3DeployerMBean attributes regarding JarsIgnoredForScanning
--------------------------------------------------------------------
Key: EJBTHREE-821
URL: http://jira.jboss.com/jira/browse/EJBTHREE-821
Project: EJB 3.0
Issue Type: Feature Request
Environment: JBoss 4.0.4 + EJB3 support
Reporter: Avishay Halperen
instead of just declaring an attribute: JarsIgnoredForScanning,
allow extending this this metadata by setting either a regexp based jarsForScan attribute
or use a better include/exclude attribute.
the problem starts that instead of just declaring the one or two jars in the application that realy needs the EJB3 deployer service,
We need to specify all our application jars (more then a hundred) just to improve the performance of the Jboss's load time, and to maintain this list
cause it is very dynamic (jars are added and removed).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months