February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-624) Running on DB2

by Tomaz Cerar (JIRA)

Running on DB2 -------------- Key: JBMESSAGING-624 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-624 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.0.1.GA Environment: jboss messaging 1.0.1GA, windows xp, DB2 8.2 iSeries Reporter: Tomaz Cerar Assigned To: Ovidiu Feodorov To make jboss messaging 1.0.1GA work with DB2 there must be attribute UsingBinaryStream in class JDBCPersistenceManager made configurable from service file. in JDBCPersistenceManager you add methods: /** * Managed attribute. */ public boolean isUsingBinaryStream()throws Exception { return usingBinaryStream; } /** * Managed attribute. */ public void setUsingBinaryStream(boolean usingBinaryStream)throws Exception { this.usingBinaryStream = usingBinaryStream; } and in JDBCPersistenceManager-xmbean.xml you have to add: <attribute access="read-write" getMethod="isUsingBinaryStream" setMethod="setUsingBinaryStream"> <description>Should JDBC read as binary stream be used?</description> <name>UsingBinaryStream</name> <type>boolean</type> </attribute> db2-persistence-service.xml -- 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
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-793) Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of

by Ovidiu Feodorov (JIRA)

Modify testing framework to pick the file containing JGroups stack configurations based on the database tests are currently running in top of --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-793 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-793 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA A place where this is currently hardcoded to use mysql is org.jboss.test.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOfficeTest.createClusteredPostOffice(). -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration

by Ovidiu Feodorov (JIRA)

Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-861 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-861 Project: JBoss Messaging Issue Type: Feature Request Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA Tim: wrt our discussion about OOM errors in HTTP tests, I notice the service container is currently using the BlockingCallbackStore: String params = "/?" + marshallers + "serializationtype=" + serializationType + "&" + dataType + "socket.check_connection=false&" + "clientLeasePeriod=" + clientLeasePeriod + "&" + "callbackStore=org.jboss.remoting.callback.BlockingCallbackStore&" + "clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&" + "serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper&" + "NumberOfRetries=1&" + "NumberOfCallRetries=2&" + "callbackErrorsAllowed=1&" + "onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool"; but the remoting-service.xml is using the standard callback store: <attribute name="leasePeriod">10000</attribute> <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute> <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute> -- 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
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-703) ServerManager.startRemoting should read the configuration from XML

by Clebert Suconic (JIRA)

ServerManager.startRemoting should read the configuration from XML ------------------------------------------------------------------ Key: JBMESSAGING-703 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-703 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Priority: Optional Fix For: 1.2.1 Using the same XML configuration would be a better approach since it would validate the remoting configuration released. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-855) release-admin.xml fails to create a clustered configuration based on a 4.0.5.GA-ejb3 installation

by Ovidiu Feodorov (JIRA)

release-admin.xml fails to create a clustered configuration based on a 4.0.5.GA-ejb3 installation ------------------------------------------------------------------------------------------------- Key: JBMESSAGING-855 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-855 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA release-admin.xml relies on finding ${jboss.home}/docs/examples/binding-manager/sample-bindings.xml. 4.0.5.GA-ejb3 installations seem not to have a "docs" sub-directory, so release-admin.xml fails. I've created an "artificial" one under my jboss-4.0.5.GA-ejb3 so I can get the smoke tests passing, but users will have troubles if they try to use release-admin.xml with 4.0.5.GA-ejb3. Need to coordinate with the AS team to find a proper solution. -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-467) Sort out JBoss AS dependencies

by Ovidiu Feodorov (JIRA)

Sort out JBoss AS dependencies ------------------------------ Key: JBMESSAGING-467 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-467 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 Currently we've imported JBossAS in the lib area of our project to keep the project compiling. This is hardly an acceptable solution. The proper solution involves: 1) Deciding what JBossAS depenencies we need and getting rid of arificially dependencies 2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed in the repository. -- 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

4
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-455) CVS to SVN repository migration

by Ovidiu Feodorov (JIRA)

CVS to SVN repository migration ------------------------------- Key: JBMESSAGING-455 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-455 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-760) Re-enable some bridge recovery tests after JBoss TS bug is fixed

by Tim Fox (JIRA)

Re-enable some bridge recovery tests after JBoss TS bug is fixed ---------------------------------------------------------------- Key: JBMESSAGING-760 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-760 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Renable ReconnectTest::testCrashAndReconnectDestCrashOnCommit_P and ReconnectTest::testCrashAndReconnectDestCrashOnCommit_NP after http://jira.jboss.com/jira/browse/JBTM-192 is complete. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-845) Add xa recovery test that uses XAResourceRecovery instance to interact

by Tim Fox (JIRA)

Add xa recovery test that uses XAResourceRecovery instance to interact ---------------------------------------------------------------------- Key: JBMESSAGING-845 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-845 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.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

19 years

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-771) TransactionManager is not bound error in Embedded EJB

by Tony Hillerson (JIRA)

TransactionManager is not bound error in Embedded EJB ----------------------------------------------------- Key: EJBTHREE-771 URL: http://jira.jboss.com/jira/browse/EJBTHREE-771 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: Embedded with Tomcat on Windows Reporter: Tony Hillerson I'm deploying a fairly simple web app with embedded ejb3 (RC9) to Tomcat 5.5.20. I get These errors: ERROR 06-10 15:53:41,437 (AbstractController.java:incrementState:440) -Error installing to Start: name=UserTransaction state=Create ... Caused by: javax.naming.NameNotFoundException: Name TransactionManager is not bound in this Context The relevent lines from web.xml: <context-param> <param-name>jboss-kernel-deployments</param-name> <param-value>embedded-jboss-beans.xml, jboss-jms-beans.xml</param-value> </context-param> <listener-class>org.jboss.ejb3.embedded.ServletBootstrapListener</listener-class> -- 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
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 February 2007