November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-631) Fix org.jboss.test.remoting.transport.socket.connection.SocketConnectionCheckTestCase and SocketConnectionTestCase failures.

by Ron Sigal (JIRA)

Fix org.jboss.test.remoting.transport.socket.connection.SocketConnectionCheckTestCase and SocketConnectionTestCase failures. ----------------------------------------------------------------------------------------------------------------------------- Key: JBREM-631 URL: http://jira.jboss.com/jira/browse/JBREM-631 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) These tests have been getting about 75% done and then failing. Looks like the System.out.println() in the loop might be causing junit to run out of heap space. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-623) need reset() call added back to JavaSerializationManager.sendObject() method

by Tom Elrod (JIRA)

need reset() call added back to JavaSerializationManager.sendObject() method ---------------------------------------------------------------------------- Key: JBREM-623 URL: http://jira.jboss.com/jira/browse/JBREM-623 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Tom Elrod Assigned To: Ron Sigal Priority: Critical Fix For: 2.2.0.Beta1 (Bluto) Per JBREM-597, code was changed within JavaSerializationManager.sendObject() to not call reset() on the ObjectOutputStream as would cause an error (see below). Although this solution works, it is not optimal as need the reset() to be called to release the references kept internally to the object stream (otherwise could potentially run out of memory if are sending a lot of different object types). Error when reset() method is called: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: java.io.IOException: Can not read data for version 121. Supported versions: 1, 2 at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:408) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125) at org.jboss.remoting.Client.invoke(Client.java:605) at org.jboss.remoting.Client.invoke(Client.java:597) at org.jboss.remoting.Client.invoke(Client.java:582) at org.jboss.test.remoting.transport.socket.connection.SocketTestClient.testInvocations(SocketTestClient.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStarter.java:32) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.io.IOException: Can not read data for version 121. Supported versions: 1, 2 at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:503) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:370) ... 28 more Test case: org.jboss.test.remoting.transport.socket.connection.SocketConnectionTestCase & org.jboss.test.remoting.transport.socket.connection.SocketConnectionCheckTestCase -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3845) JGCacheInvalidationBridge getPartitionName() returns incorrect value

by Brian Stansberry (JIRA)

JGCacheInvalidationBridge getPartitionName() returns incorrect value -------------------------------------------------------------------- Key: JBAS-3845 URL: http://jira.jboss.com/jira/browse/JBAS-3845 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-4.0.5.SP1 Value returned is the node name not the partition name. Only use of this value is as a bit of management information (e.g. displayed in the JMX console). -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-638) Potential memory leak when using 2pc via JCA adapter.

by Tim Fox (JIRA)

Potential memory leak when using 2pc via JCA adapter. ----------------------------------------------------- Key: JBMESSAGING-638 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-638 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.2.CR1 Martin Welss has reported a potential memory leak when using 2pc via the JCA adaptor. It seems that client side TxState instances remain in the resource manager. Need to investigate further. -- 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, 5 months

2
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-773) isLocalInterceptor will invoke local bean when the proxy is remote

by William DeCoste (JIRA)

isLocalInterceptor will invoke local bean when the proxy is remote ------------------------------------------------------------------ Key: EJBTHREE-773 URL: http://jira.jboss.com/jira/browse/EJBTHREE-773 Project: EJB 3.0 Issue Type: Bug Reporter: William DeCoste Assigned To: William DeCoste IsLocalInterceptor checks to see if the container is local based on the OID (e.g. jboss.j2ee:jar=stateless-test.jar,name=CheckedStatelessBean,service=EJB3) via Ejb3Registry.getContainer(oid.toString()). If the bean is deployed identically to the local and remote server and the proxy is remote, the call will still be handled locally. Checking the Ejb3Registry doesn't work in this case. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3784) derby-jdbc2-service.xml not updated to jboss 4.x

by ppc (JIRA)

derby-jdbc2-service.xml not updated to jboss 4.x ------------------------------------------------ Key: JBAS-3784 URL: http://jira.jboss.com/jira/browse/JBAS-3784 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: ppc the file doc/examples/jms/derby-jdbc2-service.xml containt the follow line <depends optional-attribute-name="ConnectionManager">jboss.jca:service=LocalTxCM,name=....</depends> that is applicable to jboss 3.x instead <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=...</depends> according to http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB this errors comes also when form the webstart installer you choose derby as default datasource instead hipersonic. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3785) Syntax Error in derby-jdbc2-service.xml

by ppc (JIRA)

Syntax Error in derby-jdbc2-service.xml --------------------------------------- Key: JBAS-3785 URL: http://jira.jboss.com/jira/browse/JBAS-3785 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: ppc Assigned To: Adrian Brock in the line DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE EXITS (SELECT JMS_TRANSACTIONS.TXID FROM JMS_TRANSACTIONS \ WHERE JMS_TRANSACTIONS.TXID = JMS_MESSAGES.TXID) \ AND JMS_MESSAGES.TXOP = ? there's a syntax error on EXITS istead EXISTS -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-693) TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish.

by Yasar Safkan (JIRA)

TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish. ----------------------------------------------------------------------------------------------- Key: JBCACHE-693 URL: http://jira.jboss.com/jira/browse/JBCACHE-693 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Environment: Tested on Linux, using Resin 3.0.14 with Hibernate 3. Reporter: Yasar Safkan Assigned To: Manik Surtani When the parameters: -Duser.language=tr -Duser.country=TR are passed to the JVM, the AppServer startup bombs when it tires to configure TreeCache using treecache.xml. Seems that it reads the value fine, but thinks the value is invalid for some reason. My best guess is this stems from the way the letters i and I are handled in Turkish. If there is any upper/lowercase conversion code within JBossCache, these letters are handled funny, thus string constants like READ_COMMITED are not recognized. The fix will probably be to use upper/lowercase conversion by specifying a character set in the JBossCache code, and not relying on the JVM defaults. The JVM itself had a similar bug, which prevented encrytion from working under these same conditions. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-125) Installer

by Mark Little (JIRA)

Installer --------- Key: JBESB-125 URL: http://jira.jboss.com/jira/browse/JBESB-125 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.0 -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1031) Update docs with info on the latest installer.

by Alex Pinkin (JIRA)

Update docs with info on the latest installer. ---------------------------------------------- Key: JBPORTAL-1031 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1031 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.4 Final Reporter: Alex Pinkin Assigned To: Roy Russo Fix For: 2.4.1 Final need to mention that latest installer allows to configure datasource. http://labs.jboss.com/portal/jemsinstaller/downloads -- 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, 6 months

3
2
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 November 2006