For some reason SQL Server is always problematic. Let's proceed in the following way.
When any problem happens before you even get to run a process, wipe out the database and the JMS queues. You are dealing with stateful components here, and stale data is a real problem. Old Microsoft SQL Server drivers used to suck. The new ones are far better. Make sure you get the latest. The schema creation seems to run fine. I googled around for these 5701 and 5703 warnings and found the following information. 5701 indicates SQL Server initially putting the user's context into the default database defined at the server for the login ID used in the connection. 5703 indicates the language being used on the server None of them seems harmful. However, before proceeding, open your management console and verify that the jBPM BPEL tables have been created and they contain columns, just to be sure. Hot deployment does not seem to work well right now. When you change something in the configuration, you should bring JBoss down and apply your changes in the cold. The previous point does not apply to individual processes; you can freely bring them up and down on the flight. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941351#3941351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941351 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
