Leonardo, I happened to noticed that your using the new DB Console we have added to this release. Appreciate if you can provide feedback/blog/tweet about it.
/sumedha On Thu, Jun 9, 2011 at 8:08 PM, Leonardo <vy...@maneh.org> wrote: > I tryed with JTDS and SQLJDBC, but I receiving new errors. > > I rewrote service with only one method (with store procedure > existing), using wizard of Data Services Server 2.6.0 (RC7), but > didn't have success. > > I attachment the log files, screenshots and dbs files with JTDS and > SQLJDBC drivers. > > I'll perform more tests and return with more information. > > []s > Leonardo > www.wso2brasil.com.br > > On Thu, Jun 9, 2011 at 12:08 AM, Anjana Fernando <anj...@wso2.com> wrote: > > Hi Leonardo, > > > > On Thu, Jun 9, 2011 at 8:05 AM, Leonardo <vy...@maneh.org> wrote: > >> > >> On Wed, Jun 8, 2011 at 11:18 PM, Prabath Abeysekera <praba...@wso2.com> > >> wrote: > >> > >> > In the meantime, Could you please send us the details of the > stacktrace > >> > if you get anything such > >> > printed on the server console? > >> > >> In console nothing is printed. I don't see anything error in console. > >> > >> I tried restarting the server, but server stopped in deploy of > >> services (and nothing is printed after this). So, server is locked and > >> I had to manually kill the process (kill -9 NUM_PID). > > > > I suspect this may be a problem with the JTDS driver, is it possible for > you > > to use the official MSSQL driver and see? .. Because at the service > > deployment time, we do not check the SQL in the query sections. So the > same > > problem should be there even if you point it to a valid store procedure. > At > > deployment time we simply test the connection by creating a new JDBC > > connection from the data source and see. So this must be the step that is > > stopping the deployment. > > > > Cheers, > > Anjana. > > > >> > >> > >> > >> On Wed, Jun 8, 2011 at 11:19 PM, Charitha Kankanamge <chari...@wso2.com > > > >> wrote: > >> > >> > We did exactly the same steps with mysql in recent RCs but did not > face > >> > this issuse. may be MSSQL specific? > >> > >> The MSSQL is 2005 and JDBC driver is JTDS. > >> > >> -- > >> Att, > >> Leonardo Saraiva > >> > >> ........__Ô "chuva-ou-sol, > >> ....._ \ >_ peda-lã-moi-gual" > >> ....(_) / (_) (Tássia Arouche) > >> _______________________________________________ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > > Anjana Fernando > > Senior Software Engineer > > WSO2 Inc. | http://wso2.com > > lean . enterprise . middleware > > > > _______________________________________________ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > Att, > Leonardo Saraiva > > ........__Ô "chuva-ou-sol, > ....._ \ >_ peda-lã-moi-gual" > ....(_) / (_) (Tássia Arouche) > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
