ColdFusion MX 7.0.2 didn’t play nice with RedHat ES4

I have been fighting to get ColdFusion MX 7.0.2 on a RedHat ES4 box. I did a typical install straight from the download (coldfusion-702-lin.bin) to the integration with Apache. Everything seemed fine until I started trying to connect with my Flex 2 applications. I received this error messages, which don’t show up any where on the web, except for a reference to a FDS/ColdFusion installation issue.

[Flex] Exception when invoking service: coldfusion-flashremoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getStatisticsByName
clientId = 34629AE6-CD0E-48A5-BFA8-852FE58DF5AD
destination = ColdFusion
messageId = EA7DE3DE-7499-ACA5-4614-D4564829D4FA
timestamp = 1163203485725
timeToLive = 1163203485725
body = null
hdr(DSEndpoint) = my-cfamf
exception: flex.messaging.MessageException:
flex/messaging/io/amf/UnknownTypeException

[Flex] Error handling message: flex.messaging.MessageException:
flex/messaging/io/amf/UnknownTypeException
incomingMessage: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getStatisticsByName
clientId = 34629AE6-CD0E-48A5-BFA8-852FE58DF5AD
destination = ColdFusion
messageId = EA7DE3DE-7499-ACA5-4614-D4564829D4FA
timestamp = 1163203485725
timeToLive = 1163203485725
body = null
hdr(DSEndpoint) = my-cfamf
errorReply: Flex Message (flex.messaging.messages.ErrorMessage)
clientId = null
correlationId = EA7DE3DE-7499-ACA5-4614-D4564829D4FA
destination = ColdFusion
messageId = 34629AF3-020B-CBF3-29F7-BBB32E69FF55
timestamp = 1163203485730
timeToLive = 0
body = null
code = Server.Processing
message = flex/messaging/io/amf/UnknownTypeException
details = null
rootCause = java.lang.NoClassDefFoundError:
flex/messaging/io/amf/UnknownTypeException
body = null
extendedData = null

After many attempts of uninstalling and re-installing I got it to work. The method to the madness was that I had to:
1. Install ColdFusion MX 7.0.1 (which you can’t download directly, luckily I had a copy on another server)
2. Then install 7.0.1 updater (coldfusion-70-updater-lin.bin)
3. Then install 7.0.2 updater (coldfusion-70-updater2-lin.bin)

When the server came up using the steps above, it all worked like it should have. This is only my third install of ColdFusion MX 7.0.2 on non-development box and I was shocked I had so much trouble with this one. Hopefully this post will stand as a reminder for me, and a help for other people stuck with the same error message above.

10 comments November 10th, 2006

My FMS on RedHat ES4 Installation Experience

Just got a new dedicated box with Redhat ES4 on it. I needed to get Flash Media Server up and running on it and had a little bit of an expereince. Here is my steps with dependencies and quirks when trying to install and then run the server.

1. Downloaded FlashMediaServer2.tar.gz
2. tar -zxvf FlashMediaServer2.tar.gz
3. ./FMS_2_0_3_r68_linux/installFMS
4. This is where I got my first quirk, an error message about not having libstdc++.
5. Using up2date –showall | grep libstdc++

This will list compat-libstdc++-296, compat-libstdc++-33, libstdc++, and libstdc++-devel. The 2 non-compat packages where already installed so I installed the compat packages

6. up2date -i compat-libstdc++-296
7. up2date -i compat-libstdc++-33
8. ./FMS_2_0_3_r68_linux/installFMS (works this time)
9. I did all the deafults, as well as the default to start the fms service after installation
10. I tried to get a sample application to work and nothing.

Checked the /var/log/messages (or /opt/macromedia/fms/logs/admin.00.log) for the presence of text like “1174 _defaultRoot__edge1 1935″. If you do not see 1935 the fmsmaster script is not working properly.

A trip back to my previous post reminded me of the fms not working issue. It pointed

11. /opt/macromedia/fms/fmsmaster

Displays another error message about libnspr4.so. This error I had referenced in my previous post and went looking for nspr packages. The Fedora Core 2 fix was to have the mozilla-nspr package installed, well in ES4 its already installed. Some more searching…

12. up2date –showall | grep nspr

Lists mozilla-nspr and seamonkey-nspr packages

13. up2date -i seamonkey-nspr
14. up2date -i seamonkey-nspr-devel
15. /etc/init.d/fms start

That fixed the problem and got the server running correctly. This is more for my own good to remember how to do this the next time I need to install Flash Media Server, hope it might help somebody else in the process.

4 comments November 10th, 2006