[JBoss JIRA] Created: (JBAS-4514) CLONE -Deadlock when logging trace
by chris effenberger (JIRA)
CLONE -Deadlock when logging trace
----------------------------------
Key: JBAS-4514
URL: http://jira.jboss.com/jira/browse/JBAS-4514
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: chris effenberger
Assigned To: Scott M Stark
SourceForge Submitter: genman .
This was caused when trace was enabled. I imagine it
was caused by the classloader trying to load a class
while it was being rendered (?) to disk. Probably not
a big issue, unless trace-logging is enabled.
Java stack information for the threads listed above:
===================================================
"SMPP-TIMER-0":
at
com.logica.smpp.util.ByteBuffer.getHexDump(ByteBuffer.java:379)
at
com.logica.smpp.util.ByteBuffer.toString(ByteBuffer.java:387)
at
org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:26)
at
org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:70)
at
org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:288)
at
org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:395)
at
org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:56)
at
org.apache.log4j.PatternLayout.format(PatternLayout.java:495)
at
org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
at
org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
- locked <0x473874c8> (a
org.apache.log4j.ConsoleAppender)
at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
at
org.apache.log4j.Category.callAppenders(Category.java:187)
- locked <0x46829180> (a
org.apache.log4j.spi.RootCategory)
at
org.apache.log4j.Category.forcedLog(Category.java:372)
at
org.apache.log4j.Category.debug(Category.java:241)
at
com.logica.smpp.debug.Log4JDebug.write(Log4JDebug.java:79)
at
com.logica.smpp.TCPIPConnection.send(TCPIPConnection.java:301)
at
com.logica.smpp.Transmitter.send(Transmitter.java:81)
at com.logica.smpp.Session.send(Session.java:983)
at com.logica.smpp.Session.bind(Session.java:452)
at
...
"SMSC-Accept-16910":
at
org.apache.log4j.Category.callAppenders(Category.java:185)
- waiting to lock <0x46829180> (a
org.apache.log4j.spi.RootCategory)
at
org.apache.log4j.Category.forcedLog(Category.java:372)
at org.apache.log4j.Category.log(Category.java:864)
at
org.jboss.logging.Log4jLoggerPlugin.trace(Log4jLoggerPlugin.java:96)
at org.jboss.logging.Logger.trace(Logger.java:113)
at
org.jboss.mx.loading.UnifiedClassLoader3.attempt(UnifiedClassLoader3.java:242)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:126)
- locked <0x472e2f38> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
- locked <0x472e2f38> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
com.proteusmobile.smsgw.server.ServerService.listen(ServerService.java:187)
at
com.proteusmobile.smsgw.server.ServerService.access$3(ServerService.java:46)
at
com.proteusmobile.smsgw.server.ServerService$Listener.run0(ServerService.java:163)
at
com.proteusmobile.smsgw.server.ServerService$Listener.run(ServerService.java:154)
at java.lang.Thread.run(Thread.java:536)
Found 1 deadlock.
--
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
13 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-1152) service-ref in ejb-jar.xml is ignored
by Thomas Diesler (JIRA)
service-ref in ejb-jar.xml is ignored
-------------------------------------
Key: EJBTHREE-1152
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1152
Project: EJB 3.0
Issue Type: Bug
Reporter: Thomas Diesler
Fix For: AS 5.0.0.Beta3
[tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
one-test:
[junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 8.761 sec
[junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
Caused by: javax.naming.NameNotFoundException: service1 not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:776)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.test.ws.jaxws.samples.serviceref.EJBClient.echo(EJBClient.java:52)
<ejb-jar version="3.0"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<enterprise-beans>
<session>
<ejb-name>EJBClient</ejb-name>
<remote>org.jboss.test.ws.jaxws.samples.serviceref.EJBRemote</remote>
<ejb-class>org.jboss.test.ws.jaxws.samples.serviceref.EJBClient</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<service-ref>
<service-ref-name>service1</service-ref-name>
<service-interface>javax.xml.ws.Service</service-interface>
<wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
<service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
</service-ref>
<service-ref>
<service-ref-name>service2</service-ref-name>
<service-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpointService</service-interface>
<wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
<service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
<port-component-ref>
<service-endpoint-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpoint</service-endpoint-interface>
<enable-mtom>true</enable-mtom>
</port-component-ref>
</service-ref>
</session>
</enterprise-beans>
</ejb-jar>
--
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
13 years, 3 months
[JBoss JIRA] Created: (JGRP-619) Change getState semantics
by Vladimir Blagojevic (JIRA)
Change getState semantics
-------------------------
Key: JGRP-619
URL: http://jira.jboss.com/jira/browse/JGRP-619
Project: JGroups
Issue Type: Task
Affects Versions: 2.5, 2.4, 2.3, 2.2.9
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Fix For: 3.0
Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer.
We have to simplify this process! State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener.
This issue is closely related to revamping of channel state transfer callbacks - JGRP-563
--
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
13 years, 3 months