|
I've seen this error in three different support request in three days, all using JBoss 3.2.x. So I don't think this would be it.
Peculiar indeed. I did notice that JBoss was copying Jars from one location to another while deploying. Perhaps both to & from locations are in the classpath. Jeff has tested on JBoss 4 with no issues. In my case verything works fine when single instance of JIRA is deployed on JBoss. But when I have tried to deploy a copy of JIRA on the same app server I run into the trouble as described above.
Maybe it is a problem with JNDI when instances tries to bind to the same keys? This appears to be a classloading problem - for some reason JBoss isn't behaving when it comes to classloading.
I think that there was a switch once, which told JBoss to use correct classloading? Does that make a difference here? Question - how does one remove the RPC plug-in without use the GUI? We came across this error after an upgrade and it is preventing Jira from starting.
Tim,
You can remove the RPC plugin by removing the atlassian-jira-rpc-plugin-1.2.jar file in the lib folder. Hope that helps! Cheers Mark C That's what I needed, thanks for the prompt response. ---- [ http://jira.atlassian.com/browse/JRA-5452?page=comments#action_29414 Mark Chaimungkalanont commented on Tim, You can remove the RPC plugin by removing the atlassian-jira-rpc-plugin-1.2.jar file in the lib folder. Hope that helps! Cheers Mark C – Since this issue is not reproducible on JBoss 4.x - we will not be addressing this.
Brian Lane |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Third-party issue
Resolved
Major
RPC Plugin causing problems during upgrade with JBOSS 3.2.x
m