October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-531) move LEAPS to its own module

by Mark Proctor (JIRA)

move LEAPS to its own module ----------------------------- Key: JBRULES-531 URL: http://jira.jboss.com/jira/browse/JBRULES-531 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Leaps Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 We can't rely on leaps being maintained regularly, so we need to move it to its own module. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1094) ClassCastException when casting SubSession to List in PortalSessionSynchronizationInterceptor

by Poul Bildsoee Moeller (JIRA)

ClassCastException when casting SubSession to List in PortalSessionSynchronizationInterceptor --------------------------------------------------------------------------------------------- Key: JBPORTAL-1094 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1094 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4 Final Environment: Portal Clustered using both Portal-ha-2.4.1CR1 and 2.4.0-ha running on JBoss AS 4.0.4 Reporter: Poul Bildsoee Moeller Assigned To: Julien Viet Priority: Minor In org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor the following code is executed (code partially inserted): HttpSession session = req.getSession(false); if (session != null) { ss = (SubSession)session.getAttribute(key); } // try { // Set the sub session for the portlet synchronization if (ss != null && ss.isActivated()) { invocation.setAttribute("subsession", ss); } // invocation.invokeNext(); } finally { List modifications = (List)invocation.getAttribute("subsession"); The code sets the SubSession as an attribute on invocation and then later tries to fetch this again and at the same time cast to List. This doesn't work since SubSession isn't a List. I am not sure what is meant to happen so I cannot really fix the problem myself. -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-735) Append the cluster name to the TreeCache log category

by Brian Stansberry (JIRA)

Append the cluster name to the TreeCache log category ----------------------------------------------------- Key: JBCACHE-735 URL: http://jira.jboss.com/jira/browse/JBCACHE-735 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.1.0 For the org.jboss.cache.TreeCache class (and PojoCache as well) it would be good to include the cluster name in the log category. This would help a lot in log analysis in situations where there are multiple caches. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-946) Window changes in admin ui not immediate

by Roy Russo (JIRA)

Window changes in admin ui not immediate ---------------------------------------- Key: JBPORTAL-946 URL: http://jira.jboss.com/jira/browse/JBPORTAL-946 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Reporter: Roy Russo Assigned To: Julien Viet Moving windows via the ui do not register immediatley when the page refreshes. You must log in again to see the changes. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3721) Clustered SSO entries not properly cleaned up if a server crashes

by Brian Stansberry (JIRA)

Clustered SSO entries not properly cleaned up if a server crashes ------------------------------------------------------------------ Key: JBAS-3721 URL: http://jira.jboss.com/jira/browse/JBAS-3721 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.6.CR1 If a server crashes, the entries for its sessions in the clustered sso cache will never be removed, and thus the sso may never be removed. TreeCacheSSOManager needs to listen for view changes and discard sessions associated with dead servers. -- 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, 3 months

1
1
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, 3 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, 3 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, 3 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, 3 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, 3 months

2
7
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 October 2006