June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-665) Need better error reporting of response marshalling errors

by Scott M Stark (JIRA)

Need better error reporting of response marshalling errors ---------------------------------------------------------- Key: JBREM-665 URL: http://jira.jboss.com/jira/browse/JBREM-665 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha4 Reporter: Scott M Stark Assigned To: Tom Elrod A failure to write a response on the server such as: 21:03:32,935 ERROR [ServerThread] failed to process invocation. java.io.NotSerializableException: java.util.HashMap$KeySet at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.aop.joinpoint.InvocationResponse.writeExternal(InvocationResponse.java:101) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:85) at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:84) at org.jboss.invocation.unified.marshall.InvocationMarshaller.write(InvocationMarshaller.java:66) at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:491) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:470) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) results in this uninformative exception on the client: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: ... Caused by: java.net.SocketException at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:352) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125) at org.jboss.remoting.Client.invoke(Client.java:589) at org.jboss.remoting.Client.invoke(Client.java:581) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPProxy$1.getTemplateNames(AOPProxy$1.java) at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) ... 23 more Need to look at how this can be improved. -- 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

18 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBRULES-479) Wizard for autopopulating a decision table

by Michael Neale (JIRA)

Wizard for autopopulating a decision table ------------------------------------------ Key: JBRULES-479 URL: http://jira.jboss.com/jira/browse/JBRULES-479 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor This could be done quite easily by a contributor. Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates it). -- 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-753) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-753 URL: http://jira.jboss.com/jira/browse/JBREM-753 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.CR1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Critical Fix For: 2.4.0.CR1 (Pinto) Each version of Remoting must be API and wire compatible with earlier versions, at least as far back as 1.4.3.GA, which is used in JBossAS 4.0.4.GA and 4.0.5.GA. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-703) allow for total configuration of socket via socket invoker

by Tom Elrod (JIRA)

allow for total configuration of socket via socket invoker ---------------------------------------------------------- Key: JBREM-703 URL: http://jira.jboss.com/jira/browse/JBREM-703 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Currently remoting does not expose all the configuration properties for a socket for the socket invokers. Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize) -- 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

18 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-739) Fix java serialization leak.

by Ron Sigal (JIRA)

Fix java serialization leak. ---------------------------- Key: JBREM-739 URL: http://jira.jboss.com/jira/browse/JBREM-739 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP2 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP2 Bug was reported in JBAS-4359. -- 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

18 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAS-4446) JGroups file in lib should be named jgroups-all.jar

by Brian Stansberry (JIRA)

JGroups file in lib should be named jgroups-all.jar --------------------------------------------------- Key: JBAS-4446 URL: http://jira.jboss.com/jira/browse/JBAS-4446 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Name the file jgroups-all.jar, which is what it's named in the JGroups dist. Using a different name makes it too easy to end up with duplicate jars when upgrading, a mistake I've made several times and which we hear about on support from time to time. -- 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

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-128) ClassInfo should be serialzable

by Adrian Brock (JIRA)

ClassInfo should be serialzable ------------------------------- Key: JBMICROCONT-128 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-128 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The ClassInfo objects should be serializable, this is currently not the case because they hold references back to their factory to support lazy initialization. -- 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

18 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-4389) nestedjarXXXX.temp files remain in the User's Temp directory on Windows after AS shutdown.

by Mark Spritzler (JIRA)

nestedjarXXXX.temp files remain in the User's Temp directory on Windows after AS shutdown. ------------------------------------------------------------------------------------------ Key: JBAS-4389 URL: http://jira.jboss.com/jira/browse/JBAS-4389 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Mark Spritzler When you startup the App Server some temp jar files are created in "C:\Documents and Settings\Username\Local Settings\Temp" directory. After you shutdown the App Server, a lot of them are deleted, but not all of them. After restarting the server many times those files that remain are all still there, causing your hard drive to run out of space. I had had 15 gigs used up by these remaining files. Here are the statistics of restarting the server about 4 times after cleaning everything out of the Temp folder before the first startup. Start 386 Files 73.5 MB Shutdown 224 Files 33.7 Megabytes Second start 546 Files 97.6 MB Second Shutdown 576 Files 86.9 MB Third start // This tells me I didn't refresh(F5) Windows Explorer to get all the new files. 576 Files 86.9 MB Third Shutdown 1024 Files 154 MB Fourth start 1410 Files 228 MB Fourth Shutdown 1280 Files 193 MB Format of files remaining in temp nestedjarNNNN.temp -- 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

18 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-3996) Web Console AppletBrowser hangs browser because of missing Logger

by teej TJ (JIRA)

Web Console AppletBrowser hangs browser because of missing Logger ----------------------------------------------------------------- Key: JBAS-3996 URL: http://jira.jboss.com/jira/browse/JBAS-3996 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-5.0.0.Beta1 Environment: Ubuntu Edgy Eft 6.10 Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux Firefox 2.0.0.1 Sun Java 1.5.0_08 Reporter: teej TJ Assigned To: Darran Lofthouse Firefox hangs and has to be killed when the JBoss Web Console link is followed on the JBoss Management service (http://localhost:8080/). The hang is caused by a NoClassDefFoundError exception whilst attempting to load AppletBrowser in applet.jar. This appears to be another instance of the use of Logger where it has been removed (as in the shutdown.sh script bugs JBAS-3560). org.jboss.console.remote.Util: private static org.jboss.logging.Logger log = org.jboss.logging.Logger.getLogger(Util.class); --- Java Console Report --- basic: Loading applet ... basic: Initializing applet ... basic: Starting applet ... network: Connecting http://10.254.251.2:8080/web-console/applet.jar with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/applet.jar with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" basic: Loading http://10.254.251.2:8080/web-console/applet.jar from cache basic: No certificate info, this is unsigned JAR file. http://10.254.251.2:8080/web-console/Invoker network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) basic: Exception: java.lang.NoClassDefFoundError: org/jboss/logging/Logger java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) -- 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

18 years, 4 months

6
5
0 / 0

[JBoss JIRA] Created: (JBAS-3857) shutdown.sh does not work

by Ovidiu Feodorov (JIRA)

shutdown.sh does not work ------------------------- Key: JBAS-3857 URL: http://jira.jboss.com/jira/browse/JBAS-3857 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Ovidiu Feodorov $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/system/server/ServerImplMBean at org.jboss.Shutdown.main(Shutdown.java:116) -- 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

18 years, 4 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 June 2007