January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4021) Distinct system properties for mcast_port in each config file

by Brian Stansberry (JIRA)

Distinct system properties for mcast_port in each config file ------------------------------------------------------------- Key: JBAS-4021 URL: http://jira.jboss.com/jira/browse/JBAS-4021 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Optional Fix For: JBossAS-4.2.0.CR1 Using a startup switch for the JGroups UDP mcast_port is not possible in a non-multiplexer environment, because every channel should use a separate port. But, we can add some properties to the standard config files to make it easier for users to set the ports via -D. cluster-service.xml -- ${jboss.hapartition.mcast_port:45566} jboss-web-cluster.sar/META-INF/jboss-service.xml -- ${jboss.webpartition.mcast_port:45577} ejb3-entity-cache-service.xml -- ${jboss.ejb3entitypartition.mcast_port:43333} ejb3-clustered-sfsbcache-service.xml -- ${jboss.ejb3sfsbpartition.mcast_port:45551} -- 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: (JBFORUMS-159) Forums doesn't work with Portal 2.6-Alpha1 - org.jboss.portal.identity.User has changed.

by Ian White (JIRA)

Forums doesn't work with Portal 2.6-Alpha1 - org.jboss.portal.identity.User has changed. ---------------------------------------------------------------------------------------- Key: JBFORUMS-159 URL: http://jira.jboss.com/jira/browse/JBFORUMS-159 Project: JBoss Forums Issue Type: Bug Components: Portlet Productization Affects Versions: 1.0.0 Alpha Environment: AS 4.0.5.GA, Portal 2.6 Alpha1, Forums 1.0.0 AlphaP2.6DR Reporter: Ian White Assigned To: Ryszard Kozmik I realise that the latest distribution of Forums for Portal 2.6DR is meant for 2.6DR, but I'm trying to get it working with 2.6 Alpha1. Simple one: org.jboss.portal.portlet.Parameters is renamed PortletParameters. But I could really do with some help with the change to org.jboss.identity.User. Should I now use HibernateUserImpl ? This change would ripple through several interfaces and classes. Any help much appreciated. 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-636) assets to be "versioned" when parent is versioned, not copied (CND change)

by Michael Neale (JIRA)

assets to be "versioned" when parent is versioned, not copied (CND change) -------------------------------------------------------------------------- Key: JBRULES-636 URL: http://jira.jboss.com/jira/browse/JBRULES-636 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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: (JBESB-394) property manager silenly fails

by Kurt Stam (JIRA)

property manager silenly fails ------------------------------ Key: JBESB-394 URL: http://jira.jboss.com/jira/browse/JBESB-394 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.0 If the jbossts-common.jar is not in your classpath, and something like the Registry need to look something up in the jbossesb-properties.xml the run will fail in 'Class not Found'. Nothing more. It would be nice if the error is a bit more specific! -- 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
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-738) Make sure all functional and stress tests pass

by Ovidiu Feodorov (JIRA)

Make sure all functional and stress tests pass ---------------------------------------------- Key: JBMESSAGING-738 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-738 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Beta2 -- 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: (JBAS-4013) Add ability to use multiplexer to ClusterPartition

by Brian Stansberry (JIRA)

Add ability to use multiplexer to ClusterPartition -------------------------------------------------- Key: JBAS-4013 URL: http://jira.jboss.com/jira/browse/JBAS-4013 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Inject the JChannelFactoryMBean and a stack name; if present use them to construct the channel. Even if we do not deploy the multiplexer in 4.2.0, we want these hooks to leave a path for upgrading. -- 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-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, 3 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, 3 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-776) Specify one way thread pool on the server side too

by Tim Fox (JIRA)

Specify one way thread pool on the server side too -------------------------------------------------- Key: JBMESSAGING-776 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-776 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Fix For: 1.2.0.Beta2 We are currently not specifying metadata.put(ServerInvoker.ONEWAY_THREAD_POOL_CLASS_KEY, "org.jboss.jms.server.remoting.DirectThreadPool"); On the server side, only on the client side. Need to do this on the server side too, otherwise any one way invocations (e.g. changeRate) will unnecessarily be invoked via a thread pool. -- 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
5
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 January 2007