February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-402) Consolidate configuration instructions from the Getting Started and Release Notes

by Bruno Georges (JIRA)

Consolidate configuration instructions from the Getting Started and Release Notes --------------------------------------------------------------------------------- Key: JBESB-402 URL: http://jira.jboss.com/jira/browse/JBESB-402 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Reporter: Bruno Georges Assigned To: Mark Little Priority: Minor Fix For: 4.0 Maintenance Pack 1 In http://labs.jboss.com/file-access/default/members/jbossesb/downloads/4.0G... We have: In the server/default/conf directory you will find two config files: jbossesb-listener.xml jbossesb-gateway.xml !!! you can add xml fragments in there and when the controller reload your listeners and gateways come up !!! So try pasting in the Hello World config. and in jbossesb-4.0GA/docs/GettingStarted.pdf We have : They are the :jbossesb-listener.xml and jbossesb-gateway.xml. These represent the configuration as it will be consumed by the esb engine, which where generated from the jbossesb.xml file. There should be no need for you to interact with the generated file. You can add xml fragments in to the jbossesb.xml and when the controller reloads your listeners and gateways come up. -- 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: (JBESB-399) Check document summaries are right

by Mark Little (JIRA)

Check document summaries are right ---------------------------------- Key: JBESB-399 URL: http://jira.jboss.com/jira/browse/JBESB-399 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Maintenance Pack 1 The Message Transformation Guide has "Highlevel Overview of Rosetta". -- 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: (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-795) Bridge tests fail

by Ovidiu Feodorov (JIRA)

Bridge tests fail ----------------- Key: JBMESSAGING-795 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-795 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Tim Fox Fix For: 1.2.0.Beta2 A full HTML report and relevant logs to be found in /home/ovidiu/tmp/testStress_AtMostOnce_P_50.zip on dev03.qa.atl.jboss.com -- 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
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-798) postoffice.cluster RedistributionWithDefaultMessagePullPolicyTest.testConsumeAllPersistentRecoverable() fails

by Ovidiu Feodorov (JIRA)

postoffice.cluster RedistributionWithDefaultMessagePullPolicyTest.testConsumeAllPersistentRecoverable() fails ------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-798 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-798 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Blocker Fix For: 1.2.0.Beta2 expected:<500> but was:<472> junit.framework.AssertionFailedError: expected:<500> but was:<472> at org.jboss.test.messaging.core.plugin.postoffice.cluster.RedistributionWithDefaultMessagePullPolicyTest.consumeAll(RedistributionWithDefaultMessagePullPolicyTest.java:626) at org.jboss.test.messaging.core.plugin.postoffice.cluster.RedistributionWithDefaultMessagePullPolicyTest.testConsumeAllPersistentRecoverable(RedistributionWithDefaultMessagePullPolicyTest.java:100) -- 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: (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: (JBMESSAGING-801) XAOldJBossTxMgrTest.testMultipleSessionsOneTxRollbackSend() error in remoting socket configuration

by Ovidiu Feodorov (JIRA)

XAOldJBossTxMgrTest.testMultipleSessionsOneTxRollbackSend() error in remoting socket configuration -------------------------------------------------------------------------------------------------- Key: JBMESSAGING-801 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-801 Project: JBoss Messaging Issue Type: Bug Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Blocker Fix For: 1.2.0.Beta2 Error Failed to invoke org.jboss.jms.util.MessagingJMSException: Failed to invoke at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:215) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:198) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:154) at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$closing$aop(ClientConnectionDelegate.java:155) at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_4945873952494833124.invokeNext(ClientConnectionDelegate$closing_4945873952494833124.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_4945873952494833124.invokeNext(ClientConnectionDelegate$closing_4945873952494833124.java) at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_4945873952494833124.invokeNext(ClientConnectionDelegate$closing_4945873952494833124.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:97) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_4945873952494833124.invokeNext(ClientConnectionDelegate$closing_4945873952494833124.java) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_4945873952494833124.invokeNext(ClientConnectionDelegate$closing_4945873952494833124.java) at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java) at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:132) at org.jboss.test.messaging.jms.XATestBase.testMultipleSessionsOneTxRollbackSend(XATestBase.java:2438) Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id 5 at org.jboss.jms.wireformat.ClosingRequest.serverInvoke(ClosingRequest.java:63) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:125) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:552) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:378) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:158) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1414) at org.jboss.remoting.Client.invoke(Client.java:511) at org.jboss.remoting.Client.invoke(Client.java:499) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:182) ... 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAS-2865) Move org.jboss.naming package from server module to naming module

by Scott M Stark (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2865?page=all ] Scott M Stark updated JBAS-2865: -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.1.CR1) > Move org.jboss.naming package from server module to naming module > ----------------------------------------------------------------- > > Key: JBAS-2865 > URL: http://jira.jboss.com/jira/browse/JBAS-2865 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2 > > > The existence of the org.jboss.naming classes in the server module are another point for broken module dependencies. There are InitialContextFactory implementations in the security module that should subclass org.jboss.naming implementations (JBAS-2731 for example) but cannot due to server depending on security. Only naming integration services should exist in the server 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
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-808) Failover can't happen if a failure happens on the middle of an ack invocation.

by Clebert Suconic (JIRA)

Failover can't happen if a failure happens on the middle of an ack invocation. ------------------------------------------------------------------------------ Key: JBMESSAGING-808 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-808 Project: JBoss Messaging Issue Type: Bug Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.CR1 When a failure happens right in the middle of a call to ACK, the message can't be found on the new server. I'm adding testFailureRightAfterACK and testFailureRightBeforeACK on FailoverTest -- 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
4
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