April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBESB-284) Increase DB support matrix for listeners

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-284?page=all ] Mark Little closed JBESB-284. ----------------------------- Resolution: Done We added more support in 4.0 and 4.2 MR1. > Increase DB support matrix for listeners > ---------------------------------------- > > Key: JBESB-284 > URL: http://jira.jboss.com/jira/browse/JBESB-284 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > > Qualify against MySQL, Oracle and HSQL (if possible). -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-339) Add HTTP Gateway Listener

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-339?page=all ] Mark Little updated JBESB-339: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) > Add HTTP Gateway Listener > ------------------------- > > Key: JBESB-339 > URL: http://jira.jboss.com/jira/browse/JBESB-339 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 2 > > > We have a Message Aware listener for HTTP, but it would appear as though there is no Gateway equivalent. > I'm sorry if the Gateway equivalent is there, just close this then. I JIRA'd just in case it wasn't and to make sure it wasn't missed. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-438) Controlled shutdown

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=comments#action_12359699 ] Kevin Conner commented on JBESB-438: ------------------------------------ The listeners/gateways should be checking their state between processing iterations (however they define that) and should therefore complete current processing before stopping. If they call external services, ejb, JMS etc. then we would have no way of controlling their undeployment other than through the normal AS dependency mechanisms. > Controlled shutdown > ------------------- > > Key: JBESB-438 > URL: http://jira.jboss.com/jira/browse/JBESB-438 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2, 5.0 Milestone Release 1 > > > During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359696 ] Kevin Conner commented on JBESB-417: ------------------------------------ With the current AS setup it is possible to share these deployments between multiple ESBs providing they have access to the same deployment locations. Taking down one ESB should unregister all the services deployed in that ESB but I am unsure whether failover will work in all circumstances. Do you have specific scenarios that you would like us to check? > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359692 ] Mark Little commented on JBESB-417: ----------------------------------- I think this is a very coarse grained task. Some of it is not specific to ESB and is much more about project management. Whereas I can see that some stuff is s/w related. If you have specific targets then let's add them as individual tasks so it's easier to track. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-438) Controlled shutdown

by Burr Sutter (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=comments#action_12359691 ] Burr Sutter commented on JBESB-438: ----------------------------------- This may actually work already. Let's say 5 files hit an FTP server or 5 messages hit a particular queue, if the listener/action chain is presently processing one of those messages and an "undeploy" occurs, what happens to the current "in-process" message and/or what happens to the remaining messages? An action chain may consist invoke other services, transform the message, invoke business logic in an EJB, POJO or WS, etc. > Controlled shutdown > ------------------- > > Key: JBESB-438 > URL: http://jira.jboss.com/jira/browse/JBESB-438 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2, 5.0 Milestone Release 1 > > > During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Burr Sutter (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359689 ] Burr Sutter commented on JBESB-417: ----------------------------------- Concerning the dev, test, staging, production item... That is more a matter of making sure the steps involved in moving a "project" out of dev and into production are at least tested/well documented. In the future there might be a central repository that is responsible for this type of thing. For instance, if I need to update 2 ESBs with the same services/archives together, can I simply have a shared file system between the 2 servers? Can I ask one ESB server and all its associated services to "stand down" in which case it no longer consume messages and all new messages would be routed to other ESB servers that hosted those same services (matched by category and name)? There may be more questions like this. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-508) "Unexpected null reply received" using edtftpj.jar version 1.5.2

by Rafael Codina Tormo (JIRA)

"Unexpected null reply received" using edtftpj.jar version 1.5.2 ----------------------------------------------------------------- Key: JBESB-508 URL: http://jira.jboss.com/jira/browse/JBESB-508 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Rafael Codina Tormo Assigned To: Mark Little Priority: Critical Hi, I am taking part in a project where the JbossEsb is being used to retrieve data from files via FTP connection. We have also developed a class which allows placing a file into a folder through FTP connection. To perform this, we have been based in the "org.jboss.soa.esb.util.FtpClientUtil" class, which defines a method "uploadFile" that uploads a specified file from a local directory localDirURI) to a remote directory (remoteDirURI). When trying to execute this method, we get an exception caused by the following reason: Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: java.io.IOException: Unexpected null reply received at org.jboss.soa.esb.util.FtpClientUtil.uploadFile(FtpClientUtil.java:361) at com.axione.service.clientftp.PousseurFichierImpl.pousserFichier(PousseurFichierImpl.java:218) ... 63 more Caused by: java.io.IOException: Unexpected null reply received at com.enterprisedt.net.ftp.FTPControlSocket.readReply(FTPControlSocket.java:686) at com.enterprisedt.net.ftp.FTPControlSocket.sendCommand(FTPControlSocket.java:649) at com.enterprisedt.net.ftp.FTPClient.setType(FTPClient.java:2190) at org.jboss.soa.esb.util.FtpClientUtil.uploadFile(FtpClientUtil.java:351) ... 64 more After having verified the reason of the exception, we have concluded that the line of code which causes the problem is: "m_oConn.put(fileToFtpString(p_oFile), sRemoteTmp);" this line is using the "com.enterprisedt.net.ftp.FTPClient.put" method, defined in the edtftpj.jar and contained in the jbossesb-dependencies.sar. The version that is being used by the esb is the 1.5.2, version that doesn't fix this bug, whereas the last version of this jar (1.5.4) does it. We have tried to replace the edtftpj.jar 1.5.2 by the 1.5.4 version but the definition of the" com.enterprisedt.net.ftp.FTPClient.put" method has been changed. In the 1.5.2 version it was defined as a void, but in the 1.5.4 it returns a String. My question is that wether this last release of the edtftpj.jar could be somehow included in your prospect release of the JbossEsb product in order to achieve the proper functionality of our development. Thank you in advance, Rafaël Codina -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359686 ] Kevin Conner commented on JBESB-417: ------------------------------------ The current deployer architecture, as it is based on the AS, can be used to provide different profiles for deployments in the same way. Would this suffice for 4.2? If so then we can drop the 4.2 requirement and keep this open for 5. BTW The OSGi development should include supporting repositories for bundles, this could also help in this requirement. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-417) Service lifecycle

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359678 ] Mark Little commented on JBESB-417: ----------------------------------- Without fundamental changes to the codebase, is there anything more we can do? The answer may be: no. > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007