I spent some time on this today with my local version of JBoss-5 Beta4. A bit
of debugging and some modification to the JBoss server code (to print out some
logs) pointed to a file named exposed.beans which is present in the META-INF
folder of
Wow, thanks! I truly appreciate the help.
My next plan for trying to solve this involved building hudson from source. I
may yet do that, but at least I'd now know what the culprit is, and the focus
would be on fixing rather than diagnosing.
You've saved me time from my terribly limited pool.
I tried the hudson build on my local 5.0 Beta4 setup on Windows. I see the same
exceptions. A similar sample war file of my own (irrespective of whether its
deployed as a archive or exploded folder works fine). I wasnt able to spend too
much time on this today. I just used JBoss-4.2.2 (the
jaikiran wrote : I tried the hudson build on my local 5.0 Beta4 setup on
Windows. I see the same exceptions. A similar sample war file of my own
(irrespective of whether its deployed as a archive or exploded folder works
fine). I wasnt able to spend too much time on this today. I just used
On the other hand, this may be indicative of a defect in beta4 :(
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138628#4138628
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138628
Duh, I should have mentioned -- the server root context, jmx console etc. all
comes up okay. There is no hudson war deployed, or findable. This is
definitely a broken configuration somehow.
I tried your suggestion, with removing all hudson paraphenalia, stopping,
starting, and redeploying
Try this. Remove your war file from the deploy folder and start JBoss. Once the
server has started up without any errors, place your war file in the deploy
folder. See if it deploys fine. There have been issues reported about
applications not getting deployed when JBoss5 is booting.
Btw, the
