Hey Jay :-) this is, like Rickard posted, a problem of the JMX implementation, since the reference implementation does not support the relation service. The idea is that jboss *will* have a "real" JMX implementation, rewritten following the JMX specs in toto. For the workaround, search jboss-dev for "startup order", you'll find the solution. Simon > -----Original Message----- > From: Jay Walters [mailto:[EMAIL PROTECTED]] > Sent: luned� 28 agosto 2000 16:30 > To: 'jBoss' > Subject: [jBoss-User] Race condition between Minerva and bean-deployer > on startup? > > > I've recently changed some beans to use the Minerva database > pools for their > database connections, but now I find that sometimes the jar > files don't > deploy because the resources aren't available yet. I've > taken to deleting > the jar files from deploy before starting the server and then > copying them > in once jboss is all up and running along with the XA > connection pools. I > moved the Minerva MLet stuff right up near the top of my > jboss.conf file > (right after JDBC provider) already but that didn't give it > enough time. > Anybody have a better way to get this working? > > Cheers > > -----Original Message----- > From: Justin Forder [mailto:[EMAIL PROTECTED]] > Sent: Saturday, August 26, 2000 9:06 AM > To: jBoss > Subject: Re: [jBoss-User] Anybody know why JDBC + SQL NPE > errors happen > > > Jay > > If you could point me at the exact code, I'll see if I can get it to > produce a meaningful message. > > regards > > Justin > > In message <[EMAIL PROTECTED]>, > Jay Walters <[EMAIL PROTECTED]> writes > >Ha I figured it out. If you have a jaws.xml file with a > <type-mapping> tag > >in it to indicate your default type mapping, move that tag after the > ><type-mappings> tag. Oh so intriguing. There is some code > which processes > >the new mapping when the <type-mapping> tag is hit, and if it hasn't > already > >hit the <type-mappings><type-mapping> which you reference > you get all those > >NPE errors. > > > >Cheers > > > >-----Original Message----- > >From: Justin Forder [mailto:[EMAIL PROTECTED]] > >Sent: Friday, August 25, 2000 7:46 AM > >To: jBoss > >Subject: Re: [jBoss-User] Anybody know why JDBC + SQL NPE > errors happen > > > > > >Jay > > > >I find them pretty annoying too. I don't think they happen > if you have > >the full set of deployment descriptors (ejb-jar.xml, jboss.xml, > >jaws.xml). > > > >They are coming from JAWSCMPField, which is a metadata class that is > >shared between EJX and jBoss, and which currently brings too > much of its > >EJX origins into jBoss. I believe Sebastien Alborini is giving it a > >complete redesign, and I expect the ugliness will disappear > quite soon. > > > >Sebastien - any comments? > > > > Justin > > > >In message > <[EMAIL PROTECTED]>, > >Jay Walters <[EMAIL PROTECTED]> writes > >>Anybody have any insight into the JDBC + SQL NPE errors > printing out from > >>Jaws when I try to deploy the TestBeans jar? It generates > the right SQL > in > >>the end, and passes all the tests from the client - but it > sure doesn't > >look > >>pretty at deploy time. I've done a little bit of digging > and it's the > >>TypeMappings which is null, which is sort of odd since I've > got mapping s > >in > >>both defaultjaws.xml and jaws.xml... > >> > >>Cheers > >> > >> > >>-- > >>-------------------------------------------------------------- > >>To subscribe: [EMAIL PROTECTED] > >>To unsubscribe: [EMAIL PROTECTED] > >>Problems?: [EMAIL PROTECTED] > >> > > > > -- > Justin Forder > > > -- > -------------------------------------------------------------- > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > Problems?: [EMAIL PROTECTED] > > > -- > -------------------------------------------------------------- > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > Problems?: [EMAIL PROTECTED] > -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
