December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4434) Create tests of file locking in the deploy dir

by Brian Stansberry (JIRA)

Create tests of file locking in the deploy dir ---------------------------------------------- Key: JBAS-4434 URL: http://jira.jboss.com/jira/browse/JBAS-4434 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Need simple tests where different sorts of deployments are copied to deploy, allowed to deploy, and then deleted. Intent is to prove that the file in the deploy dir can be deleted; i.e. the deployment process doesn't create a file lock. Most AS tests today do deployments via the RMIAdaptor, an approach that doesn't detect file lock issues. See JBAS--4415 and EJBTHREE-969 for an example of where this broke down. The FarmService tests have to use a 'copy file to farm dir' approach, so they detected a file lock issue. But this kind of problem should be directly tested so it's easier to know when problems like EJBTHREE-969 creep in. Also the FarmService test only deploys one jar; if by chance it had been a war instead of an ejb jar, the problem would not have been detected, since the JBossWeb deployer would have handled the war before accepts() was called on the Ejb3Deployer. -- 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

16 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-698) Update Remoting Marshaller/UnMarshallers to implement PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces.

by Ron Sigal (JIRA)

Update Remoting Marshaller/UnMarshallers to implement PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces. ----------------------------------------------------------------------------------------------------------------------- Key: JBREM-698 URL: http://jira.jboss.com/jira/browse/JBREM-698 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta2 (Bluto) In response to JBREM-692 the org.jboss.remoting.marshal.PreferredStreamMarshaller and org.jboss.remoting.marshal.PreferredStreamUnMarshaller interfaces were introduced, and org.jboss.remoting.marshal.serializable.SerializableMarshaller and org.jboss.remoting.marshal.serializable.SerializableUnMarshaller were modified to implement them. In particular, they implement a getMarshallingStream() method which returns an object stream that can be cached and reused by the transport layer. Now, the other Remoting marshallers (http, compressing, encrypting) should also be made to implement those interfaces. -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-764) Wire version should be configurable per client or server

by Ron Sigal (JIRA)

Wire version should be configurable per client or server -------------------------------------------------------- Key: JBREM-764 URL: http://jira.jboss.com/jira/browse/JBREM-764 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently org.jboss.remoting.Version looks to the system property "jboss.remoting.version" to determine the value to return for Version.getDefaultVersion(), and the transports refer to Version.getDefaultVersion(). This means that all clients and servers in a JVM use the same version. It would be preferable to allow the wire version to configurable as a parameter to each client and server. -- 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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-716) Reduce log output from test suite

by Ron Sigal (JIRA)

Reduce log output from test suite --------------------------------- Key: JBREM-716 URL: http://jira.jboss.com/jira/browse/JBREM-716 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Looks like jdk 1.5 test suite on cruisecontrol didn't produce a report. Maybe it ran out of memory. -- 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

16 years, 10 months

1
2
0 / 0

[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

16 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBREM-825) Verify that CoyoteInvoker works with Apache Portable Runtime

by Ron Sigal (JIRA)

Verify that CoyoteInvoker works with Apache Portable Runtime ------------------------------------------------------------ Key: JBREM-825 URL: http://jira.jboss.com/jira/browse/JBREM-825 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Trustin Lee The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars. When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail: 21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker. javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123) at org.jboss.remoting.Client.invoke(Client.java:1632) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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 junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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) Caused by: java.io.EOFException: SSL peer shut down incorrectly at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source) ... 31 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

16 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1204) README.html not displayed properly by firefox on linux

by Daniel Bevenius (JIRA)

README.html not displayed properly by firefox on linux ------------------------------------------------------ Key: JBMESSAGING-1204 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1204 Project: JBoss Messaging Issue Type: Task Components: Documentation and Training Affects Versions: 1.4.0.SP3 Reporter: Daniel Bevenius Assigned To: Tim Fox Priority: Trivial Attachments: README.html The docs/README.html contains <servername> which is causing the rest of the page to be displayed incorrectly with firefox on linux. Just escaping them with "<" and "&gt:" will do. -- 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

16 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-810) coyote.RequestMap not storing all request properties in the Map.Entry set

by Tom Fennelly (JIRA)

coyote.RequestMap not storing all request properties in the Map.Entry set ------------------------------------------------------------------------- Key: JBREM-810 URL: http://jira.jboss.com/jira/browse/JBREM-810 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.1.GA Reporter: Tom Fennelly Assigned To: Trustin Lee Priority: Minor Small thing, but the RequestMap overrides the get method for some of the request properties e.g. "Path" and "HttpVersion". This is fine if the code using the request Map (from InvocationRequest) accesses the properties via the get method. However, if it iterates over the Map.Entry set, these values will come back as null because they're not actually stored in the map entry set. -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1702) Hibernate/JBoss Cache locking issues seem to be occurring in the HA setup

by Sohil Shah (JIRA)

Hibernate/JBoss Cache locking issues seem to be occurring in the HA setup ------------------------------------------------------------------------- Key: JBPORTAL-1702 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1702 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.1 Final, 2.6 Final Reporter: Sohil Shah Assigned To: Sohil Shah When the Portal is run in a clustered environment, I have noticed some locking issues in the Hibernate Cache which is using JBoss Cache as the caching engine. So far, the locks have been detected on the HibernateUserModuleImpl in the Identity Module Steps to Reproduce: 1/ Start up both cluster nodes 2/ Login in to node1 with admin user 3/ Login in to node2 with admin user 4/ Logout of node1 5/ Try to Logout of node2, and you see locking errors on node2 -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5083) Add the transaction active check to the jdbc resource adapter

by Adrian Brock (JIRA)

Add the transaction active check to the jdbc resource adapter ------------------------------------------------------------- Key: JBAS-5083 URL: http://jira.jboss.com/jira/browse/JBAS-5083 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA Add the new transaction active to the jdbc resource adapter. -- 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

16 years, 10 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007