Just figured it out.

The final release of SMX 3.1 has a new file called servicemix.properties in
the /conf directory.  There are properties for configuring the executor
factory in this file.  I'm used to defining this in the servicemix.xml
itself but this new properties file seemed to override anything specified in
the xml.  When I re-configured the servicemix.properties file more
appropriately, everything went back to normal.  Hope this helps anyone with
a similar problem related to the executor factory configuration.

-los




Anders Hammar wrote:
> 
> For what it's worth, the PollingComponentSupport class hasn't changed for
> three months...
> http://svn.apache.org/viewvc/incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/components/util/PollingComponentSupport.java?view=log
> 
> /Anders
> 
> 
> moraleslos wrote:
>> 
>> I've just upgraded my SMX 3.1 SNAPSHOT release from 12/17/06 to the
>> *final* non-snapshot release version and I'm currently getting issues
>> with my FTPPoller lw component that was never happening on the older
>> version.  Exceptions like:
>> 
>> ************************************************
>>         at java.lang.Thread.run(Thread.java:619)
>> ERROR - PollingComponentSupport        - Caught exception while polling:
>> java.net.SocketException: Socket operation on nonsocket: recv failed
>> java.net.SocketException: Socket operation on nonsocket: recv failed
>>         at java.net.SocketInputStream.socketRead0(Native Method)
>>         at java.net.SocketInputStream.read(SocketInputStream.java:129)
>>         at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
>>         at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
>>         at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
>>         at java.io.InputStreamReader.read(InputStreamReader.java:167)
>>         at java.io.BufferedReader.fill(BufferedReader.java:136)
>>         at java.io.BufferedReader.readLine(BufferedReader.java:299)
>>         at java.io.BufferedReader.readLine(BufferedReader.java:362)
>>         at
>> org.apache.commons.net.ftp.FTPFileEntryParserImpl.readNextEntry(FTPFileEntryParserImpl.java:95)
>>         at
>> org.apache.commons.net.ftp.FTPListParseEngine.readStream(FTPListParseEngine.java:150)
>>         at
>> org.apache.commons.net.ftp.FTPListParseEngine.readServerList(FTPListParseEngine.java:98)
>>         at
>> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2396)
>>         at
>> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
>>         at
>> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>> .....
>> ***********************************************
>> 
>> 
>> and:
>> **********************************************
>> 
>> ERROR - PollingComponentSupport        - Caught exception while polling:
>> java.net.SocketException: Socket operation on nonsocket: getsockname in
>> plain socketBind
>> java.net.SocketException: Socket operation on nonsocket: getsockname in
>> plain socketBind
>>         at java.net.PlainSocketImpl.socketBind(Native Method)
>>         at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
>>         at java.net.ServerSocket.bind(ServerSocket.java:319)
>>         at java.net.ServerSocket.<init>(ServerSocket.java:185)
>>         at
>> org.apache.commons.net.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:155)
>>         at
>> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:475)
>>         at
>> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2390)
>>         at
>> org.apache.commons.net.ftp.FTPClient.initiateListParsing(FTPClient.java:2364)
>>         at
>> org.apache.commons.net.ftp.FTPClient.listFiles(FTPClient.java:2141)
>> .....
>> ************************************************
>> 
>> 
>> Does anyone know of any changes from that snapshot release till this
>> final release that would cause the above exceptions to occur?  I made
>> sure to use the same 3rd party libs, e.g. commons-net-1.4.1 as well as
>> deploying the exact SA in both versions so I think it maybe internal to
>> smx.  Any help would be appreciated.  Thanks in advance!
>> 
>> -los
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/upgrading-3.1-issues-tf3236175s12049.html#a9007488
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to