I wasn't sure which forum to submit this to, since it covers a variety of
topics -- hibernate, JNDI, clustering, etc. So I'm picking this forum; if you
can suggest a better one, I'll repost there.
Here's the situation. We've had a web app that's been running fine on JBoss
4.0.5.GA, as the server-side for a Flex app. I built an MDB, added it to the
deploy dir, and it worked somewhat with our web app, but the MDB couldn't find
the FlexSession stuff. So we thought we'd build an .ear, to include the .war
of the web app and the .jar of the MDB.
The problem I'm getting on start-up is anonymous wrote : ...
| 17:59:02 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext
properties:{}
| 17:59:02 FATAL [org.hibernate.connection.DatasourceConnectionProvider]
Could not find datasource: jdbc/PlanITDataSource
| javax.naming.CommunicationException: Failed to retrieve stub from server
192.168.1.18:1100 [Root exception is java.io.StreamCorruptedException:
unexpected block data]
| ...
Now, I never had this problem before, so something is not configured right, I
guess. That IP address belongs to my colleague, who is running a clustered
JBoss setup; I'm running non-clustered. He's also running Linux, whereas I'm
running Windows XP Pro. He was able to get the app up and running, after
wading through some configuration issues. We're on the same LAN, as are
several other developers, who are only using the .war, not the .ear or .jar
(MDB), and they don't experience any errors.
Can you please tell me what's wrong with our set-up? Is there a way to make
sure the clustered JBoss installation doesn't interfere with the non-clustered
ones? I'm hoping that will solve my issue. Or maybe there's another solution.
Thanks
Pauly T.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055434#4055434
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055434
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
