April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBESB-412) Static transformations

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-412?page=comments#action_12360560 ] Mark Little commented on JBESB-412: ----------------------------------- Prioritise a couple of these and let's try to push the others to 5.0. > Static transformations > ---------------------- > > Key: JBESB-412 > URL: http://jira.jboss.com/jira/browse/JBESB-412 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transformation Service > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.2 > > > Object to XML, DOM to XML, Groovy script, Base64Encode/Decode, UUEncode/Decode,ByteArrayToSerializable,Mail body to String,HTTPRequestBodyToString -- 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

1
0
0 / 0

[JBoss JIRA] Work started: (JBESB-401) During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider]

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-401?page=all ] Work on JBESB-401 started by Kevin Conner. > During Trailblazer DEMO, JMS doesn't reconnect after a restart of the App Server [JMS Provider] > ----------------------------------------------------------------------------------------------- > > Key: JBESB-401 > URL: http://jira.jboss.com/jira/browse/JBESB-401 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Environment: JBoss ESB 4.0 GA + JBoss AS 4.0.5GA - Win 2000 - Fedora Core 6 > Reporter: Bruno Georges > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2 > > > During Trailblazer DEMO, JMS doesn't reconnect when App Server restart: ERROR [JmsCourier] JMS error. Attempting JMS reconnect. > ant runJMSBank > [java] 10:00:01,759 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect > [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) > [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277) > [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > ant runESB > [java] 09:58:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect. > [java] javax.jms.IllegalStateException: The consumer is closed > [java] at org.jboss.mq.SpyMessageConsumer.checkClosed(SpyMessageConsumer.java:963) > [java] at org.jboss.mq.SpyMessageConsumer.receive(SpyMessageConsumer.java:360) > [java] at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:349) > [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:184) > [java] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:166) > [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:246) > [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:228) > [java] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:114) > [java] at java.lang.Thread.run(Thread.java:595) > [java] 09:59:51,775 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect > [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) > [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277) > [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) > [java] at java.lang.Thread.run(Thread.java:595) > [java] Caused by: java.io.IOException: ping timeout. > [java] ... 3 more > [java] 09:59:52,056 ERROR [JmsCourier] JMS error. Attempting JMS reconnect. -- 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

1
0
0 / 0

[JBoss JIRA] Work started: (JBESB-369) WAR deployment

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-369?page=all ] Work on JBESB-369 started by Kevin Conner. > WAR deployment > -------------- > > Key: JBESB-369 > URL: http://jira.jboss.com/jira/browse/JBESB-369 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2 > > > Support for running within a Tomcat container, BEA and IBM. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-510) Unable to transfer a file from ftp server to a local machine

by Faisal Azizullah (JIRA)

Unable to transfer a file from ftp server to a local machine ------------------------------------------------------------ Key: JBESB-510 URL: http://jira.jboss.com/jira/browse/JBESB-510 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Environment: Jboss 4.05 GA, java version "1.5.0_05" and jbossesb -4.0 GA Reporter: Faisal Azizullah Assigned To: Mark Little Fix For: 4.0 I am trying to move a file from a ftp server to a local machine and I am getting some error. My Jbossesb.xml looks like following <?xml version = "1.0" encoding = "UTF-8"?> <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." parameterReloadSecs="50"> <providers>  <ftp-provider name="Chase" hostname="f0test.bankone.com" > <ftp-bus busid="ChaseFTPChannel" > <ftp-message-filter username="@username@" password="@password@" passive="true" directory="/outbound" input-suffix=".txt" work-suffix=".esbWorking" post-delete="false" post-directory="C:/IDDTest" post-suffix=".COMPLETE" /> </ftp-bus> </ftp-provider> <jms-provider name="JBossMQ" connection-factory="ConnectionFactory" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-URL="localhost" > <jms-bus busid="IDDJMSBus"> <jms-message-filter dest-type="QUEUE" dest-name="queue/A" selector="source='fromIDDFTPAction'" /> </jms-bus> </jms-provider>  </providers> <services>  <service category="myCategory" name="TheFileGateway" description="IDD file gateway" > <listeners> <ftp-listener name="IddFtpGateway" busidref="ChaseFTPChannel" maxThreads="1" is-gateway="true"> <property name="pollLatencySeconds" value="60"/> </ftp-listener> <jms-listener name="IDDListener" busidref="IDDJMSBus" maxThreads="1" /> </listeners> </service>  </services> </jbossesb> The error I am getting is as follows 07:51:39,656 ERROR [STDERR] java.lang.reflect.InvocationTargetException 07:51:39,656 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0( Native Method) 07:51:39,656 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(N ativeMethodAccessorImpl.java:39) 07:51:39,656 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invo ke(DelegatingMethodAccessorImpl.java:25) 07:51:39,656 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:5 85) 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.AbstractF ileGateway.doRun(AbstractFileGateway.java:150) 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.lifecycle.Abstrac tThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:114) 07:51:39,656 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 07:51:39,656 ERROR [STDERR] Caused by: org.jboss.soa.esb.listeners.gateway.Gatew ayException: java.io.IOException: The system cannot find the path specified 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.RemoteGat ewayListener.getFileContents(RemoteGatewayListener.java:145) 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.FileGatew ayListener$PackageFileContents.getFileContent(FileGatewayListener.java:224) 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.FileGatew ayListener$PackageFileContents.process(FileGatewayListener.java:218) 07:51:39,656 ERROR [STDERR] ... 7 more 07:51:39,656 ERROR [STDERR] Caused by: java.io.IOException: The system cannot fi nd the path specified 07:51:39,656 ERROR [STDERR] at java.io.WinNTFileSystem.createFileExclusively (Native Method) 07:51:39,656 ERROR [STDERR] at java.io.File.checkAndCreate(File.java:1345) 07:51:39,656 ERROR [STDERR] at java.io.File.createTempFile(File.java:1434) 07:51:39,656 ERROR [STDERR] at org.jboss.internal.soa.esb.util.EdtFtpImpl.do wnloadFile(EdtFtpImpl.java:299) 07:51:39,656 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.RemoteGat ewayListener.getFileContents(RemoteGatewayListener.java:135) 07:51:39,656 ERROR [STDERR] ... 9 more 07:51:39,656 ERROR [AbstractFileGateway] Problems invoking method <process> java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.doRun(Abstrac tFileGateway.java:150) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycl e.run(AbstractThreadedManagedLifecycle.java:114) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.soa.esb.listeners.gateway.GatewayException: java.io.IOExcep tion: The system cannot find the path specified at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.getFileCont ents(RemoteGatewayListener.java:145) at org.jboss.soa.esb.listeners.gateway.FileGatewayListener$PackageFileCo ntents.getFileContent(FileGatewayListener.java:224) at org.jboss.soa.esb.listeners.gateway.FileGatewayListener$PackageFileCo ntents.process(FileGatewayListener.java:218) ... 7 more Caused by: java.io.IOException: The system cannot find the path specified at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1345) at java.io.File.createTempFile(File.java:1434) at org.jboss.internal.soa.esb.util.EdtFtpImpl.downloadFile(EdtFtpImpl.ja va:299) at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.getFileCont ents(RemoteGatewayListener.java:135) ... 9 more 07:51:40,437 ERROR [AbstractFileGateway] Problems renaming file log.txt.esbWorki ng to \outbound\log.txt.esbError org.jboss.soa.esb.listeners.gateway.GatewayException: org.jboss.soa.esb.util.Rem oteFileSystemException: com.enterprisedt.net.ftp.FTPException: /outbound/log.txt .esbError: No such file or directory. at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.deleteFile( RemoteGatewayListener.java:115) at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.doRun(Abstrac tFileGateway.java:289) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycl e.run(AbstractThreadedManagedLifecycle.java:114) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: com.enterprisedt.ne t.ftp.FTPException: /outbound/log.txt.esbError: No such file or directory. at org.jboss.internal.soa.esb.util.EdtFtpImpl.deleteRemoteFile(EdtFtpImp l.java:285) at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.deleteFile( RemoteGatewayListener.java:107) ... 3 more Caused by: com.enterprisedt.net.ftp.FTPException: /outbound/log.txt.esbError: No such file or directory. at com.enterprisedt.net.ftp.FTPControlSocket.validateReply(FTPControlSoc ket.java:800) at com.enterprisedt.net.ftp.FTPClient.delete(FTPClient.java:2208) at org.jboss.internal.soa.esb.util.EdtFtpImpl.deleteRemoteFile(EdtFtpImp The ftp directory listing is as follows ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. log.txt tre_410000066_04032007121539.txt.esbWorking.esbWorking 226 Transfer complete. ftp: 65 bytes received in 0.00Seconds 65000.00Kbytes/sec. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. log.txt.esbWorking tre_410000066_04032007121539.txt.esbWorking.esbWorking 226 Transfer complete. ftp: 76 bytes received in 0.00Seconds 76000.00Kbytes/sec. -- 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

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-525) FTPGatewayListener: refactor extract rename functionality.

by Daniel Bevenius (JIRA)

FTPGatewayListener: refactor extract rename functionality. ----------------------------------------------------------- Key: JBESB-525 URL: http://jira.jboss.com/jira/browse/JBESB-525 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor Extract the renaming of files to a method in AbstractFileGateway, primarily so that a subclass like RemoteGatewayListener can override it. I need this for my current project where the ftp server is running on a mainframe where read, write permissions are given for the specific file and not a folder. This mean that I can't delete or rename the file. I also need to solve the problem where a different listener takes the same file. If I can do this in a generall way I'll try to add another JIRA. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-521) Added message properties

by Mark Little (JIRA)

Added message properties ------------------------ Key: JBESB-521 URL: http://jira.jboss.com/jira/browse/JBESB-521 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 1 Reporter: Mark Little Assigned To: Mark Little Priority: Optional >From Burr: I do like the concept of having things like: - name of file before it was sucked in - the file ext - the hostname/ip address it came from - the directory it came from - the date/time it was sucked in - the size of the file in bytes (perhaps that is easy to calculate since it is in an array) -- 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

1
4
0 / 0

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

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=all ] Kevin Conner closed JBESB-438. ------------------------------ Fix Version/s: (was: 5.0 Milestone Release 1) Resolution: Out of Date The lifecycle processing should be taking care of this. I'll open another issue for 5.0 so that it can be tracked separately. > 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 > > > 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

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-496) JMS Endpoints not being unregistered from registry

by Tom Fennelly (JIRA)

JMS Endpoints not being unregistered from registry -------------------------------------------------- Key: JBESB-496 URL: http://jira.jboss.com/jira/browse/JBESB-496 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-513) SqlTableGatewayListener keeps the transaction open over successive polls

by Kevin Conner (JIRA)

SqlTableGatewayListener keeps the transaction open over successive polls ------------------------------------------------------------------------ Key: JBESB-513 URL: http://jira.jboss.com/jira/browse/JBESB-513 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Kevin Conner Assigned To: Mark Little An examination of the SqlTableGatewayListener shows that the polling loop does not terminate the current transaction at the end of the loop. As the isolation layer is currently set to serializable this will result in a full table lock on the database for the duration of the transaction. Further, having created a prepared statement to execute the query this does not appear to be used by the polling loop resulting in the JDBC driver parsing the scan statement for each invocation. There is also a possibility of a connection leak if the prepared statement creation fails in the initialise. -- 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
4
0 / 0

[JBoss JIRA] Assigned: (JBESB-287) Add in HTTP support for new listeners

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-287?page=all ] Mark Little reassigned JBESB-287: --------------------------------- Assignee: Tom Cunningham (was: Mark Little) > Add in HTTP support for new listeners > ------------------------------------- > > Key: JBESB-287 > URL: http://jira.jboss.com/jira/browse/JBESB-287 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Cunningham > Fix For: 4.2 > > -- 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

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