August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (BPEL-186) Write a blog entry about the 1.1 release

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-186?page=comments#action_12342363 ] Thomas Diesler commented on BPEL-186: ------------------------------------- Please post the link > Write a blog entry about the 1.1 release > ---------------------------------------- > > Key: BPEL-186 > URL: http://jira.jboss.com/jira/browse/BPEL-186 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-629) need to get remote binding uri from Connector for default

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-629?page=comments#action_12342361 ] Bill Burke commented on EJBTHREE-629: ------------------------------------- i cannot reproduce this in HEAD > need to get remote binding uri from Connector for default > --------------------------------------------------------- > > Key: EJBTHREE-629 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-629 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC8 - FD > Reporter: Andrea Luciano > Assigned To: Bill Burke > Fix For: EJB 3.0 RC2, EJB 3.0 RC9 - FD > > > The issue http://jira.jboss.com/jira/browse/EJBTHREE-204 reopen. > I downloaded jboss 4.0.4 GA and jboss-EJB-3.0_RC8-FD. > I installed jboss and ejb3 support than I tryed to modify the standard port 3873 so I changed the file deploy/ejb3.deployer/META-INF/jboss-service.xml: > <mbean code="org.jboss.remoting.transport.Connector" > xmbean-dd="org/jboss/remoting/transport/Connector.xml" > name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"> > <depends>jboss.aop:service=AspectDeployer</depends> > <attribute name="InvokerLocator">socket://${jboss.bind.address}:10009</attribute> > <attribute name="Configuration"> > <handlers> > <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> > </handlers> > </attribute> > </mbean> > While the server listens correctly on new port the client has no way to contact the bean I deployed. > Using strace I figured out that the client ignores the new port and tries to contact port 3873 as before RC3 of ejb3 support (while another installation with ejb3 rc3 works without problems). > Is this a regression? > Regards. > Andrea -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3435) Get the 4.0.5.CR1 testsuite passing

by Dimitris Andreadis (JIRA)

Get the 4.0.5.CR1 testsuite passing ----------------------------------- Key: JBAS-3435 URL: http://jira.jboss.com/jira/browse/JBAS-3435 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Priority: Critical Fix For: JBossAS-4.0.5.CR1 Task to hold testsuite related issues -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-423) Change test to use a single repository- for speed

by Michael Neale (JIRA)

Change test to use a single repository- for speed ------------------------------------------------- Key: JBRULES-423 URL: http://jira.jboss.com/jira/browse/JBRULES-423 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale rather then blowing it away with each single test 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-457) DSLs to have an add method just like rules/functions

by Michael Neale (JIRA)

DSLs to have an add method just like rules/functions ---------------------------------------------------- Key: JBRULES-457 URL: http://jira.jboss.com/jira/browse/JBRULES-457 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-755) `Potential bug when using (async) replication queue and region based marshalling

by Manik Surtani (JIRA)

`Potential bug when using (async) replication queue and region based marshalling -------------------------------------------------------------------------------- Key: JBCACHE-755 URL: http://jira.jboss.com/jira/browse/JBCACHE-755 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.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, 11 months

1
3
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov closed JBMESSAGING-150. --------------------------------------- Resolution: Done Done. http://jira.jboss.org/jira/browse/JBCTS-325 The src/cts subdirectory is not relevant anymore, it has been incorporated in tck-mods, so it can be removed. > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Priority: Minor > Fix For: 1.2.0.CR1 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov updated JBMESSAGING-150: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.2.1) > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Priority: Minor > Fix For: 1.2.0.CR1 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-538) The MessageCount property on the queue appears to climb to the FullSize value, then stop

by Ovidiu Feodorov (JIRA)

The MessageCount property on the queue appears to climb to the FullSize value, then stop ---------------------------------------------------------------------------------------- Key: JBMESSAGING-538 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-538 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 The MessageCount property on the queue appears to climb to the FullSize value, then stop. Investigate this. Case 10646. https://na1.salesforce.com/50030000002Urdd -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-537) Test with remoting 2.0.0.GA

by Ovidiu Feodorov (JIRA)

Test with remoting 2.0.0.GA --------------------------- Key: JBMESSAGING-537 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-537 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 -- 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, 11 months

1
1
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 August 2006