[ http://wso2.org/jira/browse/WSAS-680?page=comments#action_14965 ] Charitha Kankanamge commented on WSAS-680: ------------------------------------------
Closed the bug > Class loading issue when restarting WSAS > ---------------------------------------- > > Key: WSAS-680 > URL: http://wso2.org/jira/browse/WSAS-680 > Project: WSO2 WSAS > Issue Type: Bug > Environment: winxp, jdk15, WSAS-2.2-qabuild5 > Reporter: Charitha Kankanamge > Assigned To: Afkham Azeez > Priority: Blocker > > The jars copied to WSAS_HOME/lib directory while the WSAS instance is running > are not loaded if the instance is restarted either using management console > or JMX managment. > Steps to reproduce: > ================ > 1. Start WSAS > 2. Upload a *.dbs (MySQL data service). Make sure mysqlconnector.jar is not > available in the classpath > 3. The service will be deployed as faulty since the DB driver is not in class > path > 4. Copy the driver jar to WSAS_HOME/lib > 5. Restart WSAS either using Jconsole or management UI > 6. The driver class will not be reloaded > If you stop WSAS instance by pressing Ctrl+C and start again, then the > classes will be loaded correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
