March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBPM-556) Problems with Exception longer 4000 characters in AtcionLog

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-556?page=all ] Tom Baeyens closed JBPM-556. ---------------------------- Fix Version/s: (was: jBPM jPDL 3.2) Resolution: Rejected i think the previous comment shows how to do what you want. please reopen if you still think this fix won't work for you. > Problems with Exception longer 4000 characters in AtcionLog > ----------------------------------------------------------- > > Key: JBPM-556 > URL: http://jira.jboss.com/jira/browse/JBPM-556 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.2, jBPM 3.1 beta 3 > Reporter: Bernd Ruecker > Assigned To: Tom Baeyens > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > In the ActionLog > public void setException(Throwable exception) { > StringWriter stringWriter = new StringWriter(); > exception.printStackTrace(new PrintWriter(stringWriter)); > this.exception = stringWriter.toString(); > } > a exception is thrown if the exception has more than 4000 characters (at least with Oracle). This code can be fixed easyly: > public void setException(Throwable exception) { > StringWriter stringWriter = new StringWriter(); > exception.printStackTrace(new PrintWriter(stringWriter)); > String st = stringWriter.toString(); > > // perhaps can not write more tha 4000 chars to database field (e.g. Oracle) > if (st.length()>4000) > st = st.substring(0, 4000); > this.exception = st; > } > By the way, this is already done correctly in Timers (Timer.java) :-) Perhaps some refactoring to centralize thi issue would be nice (for example a String getExceptionAsString(Throwble t) helper-method). > if (t!=null) { > log.error("unhandled timer exception", t); > // this means an unhandled exception occurred in this timer > StringWriter sw = new StringWriter(); > actionException.printStackTrace(new PrintWriter(sw)); > exception = sw.toString(); > if (exception.length()>4000) exception = exception.substring(0, 4000); > } -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=all ] Tom Baeyens updated JBPM-165: ----------------------------- Fix Version/s: jBPM jPDL 3.2.1 (was: jBPM jPDL 3.2) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAOP-44) document new ARGS features

by Flavia Rainone (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-44?page=all ] Flavia Rainone reassigned JBAOP-44: ----------------------------------- Assignee: Flavia Rainone (was: Flavia Rainone) > document new ARGS features > -------------------------- > > Key: JBAOP-44 > URL: http://jira.jboss.com/jira/browse/JBAOP-44 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assigned To: Flavia Rainone > Fix For: 2.0.0.alpha4 > > > Document typed argument access within aspects as well as the CurrentInvocation class. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3071) MemoryLeak (redeployment) on EJB3

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3071?page=all ] Carlo de Wolf reassigned JBAS-3071: ----------------------------------- Assignee: Carlo de Wolf (was: Bill Burke) > MemoryLeak (redeployment) on EJB3 > --------------------------------- > > Key: JBAS-3071 > URL: http://jira.jboss.com/jira/browse/JBAS-3071 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.CR2 > Reporter: Clebert Suconic > Assigned To: Carlo de Wolf > Priority: Critical > Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3 > > > This might be caused by JBAS-3016: > But I'm seeing this strong reference: > org.jboss.mx.loading.UnifiedClassLoader3@33411906 > !--- org.jboss.ejb3.stateless.StatelessContainer@29610827 > We should make sure EJB3 packages are not leaking. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-422) UDP UcastReceiver logs spurious error during shutdown

by Brian Stansberry (JIRA)

UDP UcastReceiver logs spurious error during shutdown ----------------------------------------------------- Key: JGRP-422 URL: http://jira.jboss.com/jira/browse/JGRP-422 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor >From Dimitris: some times, when shutting down the 'all config I see something like that. Any ideas? 14:08:03,951 INFO [TomcatDeployer] undeploy, ctxPath=/jbossmq-httpil, warUrl= ./deploy-hasingleton/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 14:08:04,282 INFO [TreeCache] stopService(): closing the channel 14:08:04,352 ERROR [UDP] failed handling data from 192.168.0.22:4864 QueueClosedException at org.jgroups.util.Queue.add(Queue.java:139) at org.jgroups.protocols.TP.receive(TP.java:777) at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:961) at java.lang.Thread.run(Thread.java:595) 14:08:04,352 INFO [TreeCache] stopService(): stopping the dispatcher AFAICT, problem is that UDP.UcastReceiver.stop() does not wait for the receiver thread to terminate it's loop before returning. Therefore the shutdown thread can go on and close the IncomingPacketHandler, leading to the QueueClosedException if UcastReceiver is in the middle of its loop and has read another packet off the wire. Possible solution is to have the shutdown thread join UcastReceiver.thread in UcastReceiver.stop(). Give UcastReceiver.thread time to terminate its loop before continuing on with the shutdown. -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-363) GossipRouter classpath error message is misleading

by Jerry Gauthier (JIRA)

GossipRouter classpath error message is misleading -------------------------------------------------- Key: JGRP-363 URL: http://jira.jboss.com/jira/browse/JGRP-363 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Jerry Gauthier Assigned To: Bela Ban Priority: Minor If you start the GossipRouter without concurrent.jar on the classpath, a NoClassDefFoundError exception will occur. However this information is hidden by GossipRouter error handing and the user is presented with the cryptic message: "failed reading the magic number mapping file." I think there are severl ways to improve this situation. 1) Update the GossipRouter example in the JGroups documentation to show what jars need to be on the classpath. 2) Modify the GossipRouter or ClassConfigurator to reveal the underlying problem. Note that this error occurs when you start the GossipRouter per the doc without adding concurrent.jar to the classpath. -- 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

19 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-887) how can i use my custom tags in the task.jsp page

by Ana Velez (JIRA)

how can i use my custom tags in the task.jsp page ------------------------------------------------- Key: JBPM-887 URL: http://jira.jboss.com/jira/browse/JBPM-887 Project: JBoss jBPM Issue Type: Feature Request Reporter: Ana Velez Assigned To: Tom Baeyens hi, i tried to use my custom tags in the task page, at the first i had errors with the uri and classes ,but now i dont have any error, however when i display the page there isnt nothing of my tags., where i cant to find documentation about that o something that can help me. Thanks -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Updated: (JGRP-253) List officially supported classes/API for JGroups

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-253?page=all ] Bela Ban updated JGRP-253: -------------------------- Fix Version/s: 3.0 (was: 2.5) > List officially supported classes/API for JGroups > ------------------------------------------------- > > Key: JGRP-253 > URL: http://jira.jboss.com/jira/browse/JGRP-253 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assigned To: Bela Ban > Priority: Minor > Fix For: 3.0 > > > List of APIs which are supported by JBoss, e.g. DistributedHashtable won't be supported -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3550) JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.classloader.test.CircularityUnitTestCase (testRecursiveLoadMT)

by Vivek Lakshmanan (JIRA)

JBAS 4.0.4GA Test suite Error on Java 1.5 - org.jboss.test.classloader.test.CircularityUnitTestCase (testRecursiveLoadMT) ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3550 URL: http://jira.jboss.com/jira/browse/JBAS-3550 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.5.0_08, Java VM Version 1.5.0_08-b03 OS: Linux RHEL 4 U3 2.6.9-34.EL Arch: i386 Reporter: Vivek Lakshmanan The above test case seems to produce an error frequently on Sun 1.5 JVM. From a cursory search through JIRA, it seems this could be related to JIRA issue JBAS-760. The stacktrace produced in the test reports follows: javax.management.MBeanException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.Exception: Thread1 failed to load HARMIServerImpl_Stub, class=null at org.jboss.test.classloader.circularity.test.RecursiveCCETests.testRecursiveLoadMT(RecursiveCCETests.java:99) at org.jboss.test.classloader.circularity.Starter.testRecursiveLoadMT(Starter.java:154) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) ... 40 more -- 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

19 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4029) Endorsed directory not working but works with 4.0.5GA

by tony anecito (JIRA)

Endorsed directory not working but works with 4.0.5GA ----------------------------------------------------- Key: JBAS-4029 URL: http://jira.jboss.com/jira/browse/JBAS-4029 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 2000 Professional JDK 1.6 JAXWS-2.1 Reporter: tony anecito When adding jars to the endorsed directory for JAXWS-2.1 seems servlet runner (TomCat) reports it is using JAXWS-2.0. I want to overide this with the JAXWS-2.1 and that works with 4.0.5GA. Following is clip from command console using beta1 21:10:44,781 INFO [ServiceEndpointManager] WebServices: jbossws-2.0.0.CR2.DEV date=200611171751) -- 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

19 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007