Ok, no need for a JIRA -- it was operator failure that caused the problem (that would be me, BTW).
The InstanceAlreadyExistsException was caused by having 2 copies of the wicket-jmx-1.3.5.jar file in the app's WEB-INF/lib directory. The 2nd copy was in a subdirectory -- I had put it there while experimenting with Wicket version 1.4. Solution: remove the 2nd copy. Now the issue with the "WicketRuntimeException: signin is already mounted for BookmarkablePageEncoder" issue I think may have something to with WebSphere. Once I removed the wicket.mbean.server.agentid=WebSphere JVM setting from the app server then the problem went away. -- View this message in context: http://www.nabble.com/InstanceAlreadyExistsException-when-Redeploying-in-Websphere-tp15617038p22310588.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
