[Concern-users] RE: server.log and jmx-console output

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Quoting Raoul Zon <rao...@to...>: 

> Holger, 
>  
> There's no bigint datatype in MaxDB, the only relevant types are 
> integer, long, char and varchar. 
> I have it running now (I can log in), but there are some servlet errors 
> when trying to access EngagementWorker and ApplicationWorker. 

Try to restart jboss. It seems like you have loaded some classes several times 
from different class loaders. This can happen, when the process or controller 
is redeployed after the war has been accessed. Alternatively you could redploy 
the jars in the correct order: 

  touch Allication*.jar Engagement*.jar engagement/WEB-INF/web.xml 

This could be avoided, if you put all deployables into an ear and thus always 
reload the whole ear. However this takes longer and I don't like long 
roundtrips. If I keep the deployables separate and don't deploy them in mixed 
order, it is working without the ear. 

> Can I check in the altered sapdb.xsl? 

If you tell me your sf account, I can add you to the project. You will have to 
modify your CVS/Root files or get a fresh checkout with your account: 

for f in `find -name Root` 
do  
  echo ":ext:you...@cv...:/cvsroot/concern" > $f 
done 

> By the way, is this your daily job developing con:cern or is it a 
> hobbyproject you're running? 

It started as a hobby project, when I was a freelancer. Now, I'm employed in a 
company, that is integrating con:cern with their ERP suite, shop, etc. From 
beginning of next month on, it will be my daily job. 

You're welcome! 

Holger 

> -----Oorspronkelijk bericht----- 
> Van: Holger Engels [mailto:he...@me...]  
> Verzonden: woensdag 12 mei 2004 13:18 
> Aan: Raoul Zon 
> CC: con...@li... 
> Onderwerp: RE: server.log and jmx-console output 
>  
>  
> Quoting Raoul Zon <rao...@to...>:  
>   
> > Holger, 
> >   
> > I changed timeout to "varchar(256)" and currently it runs without 
> > errors!!!  
>   
> .. hm, maybe something like bigint instead of varchar?  
>   
> It would be great, if you could correct the xsl according to your 
> findings  
> with sapdb ..  
>   
> > BUT....as the never ending story continues, logging in seems to be a 
> > problem. I provide an arbitrary user and pass (which are the same) but 
>  
> > get a authentication failed.  
>   
> Sorry, I forgot to mention that in the documentation. You have to tell 
> jboss,  
> how to authenticate by editing the 
> jboss/server/default/conf/login-config.xml.  
> Add the following lines:  
>   
>     <application-policy name = "concern">  
>        <authentication>  
>           <login-module  
> code="org.jboss.security.auth.spi.SimpleServerLoginModule"  
>              flag = "required" />  
>        </authentication>  
>     </application-policy>  
>   
>   
> Regards,  
>   
> Holger  
>   
>   
> > -----Oorspronkelijk bericht----- 
> > Van: Holger Engels [mailto:he...@me...]   
> > Verzonden: woensdag 12 mei 2004 12:11  
> > Aan: Raoul Zon  
> > Onderwerp: RE: server.log and jmx-console output  
> >   
> >   
> > Quoting Raoul Zon <rao...@to...>: 
> >    
> > > Holger, 
> > >    
> > > What did you fix....I did a complete "Replace with latest from  
> > > HEAD", 
> > > but still get the conversion error after the build. Anything  
> > particular 
> > > you changed or haven't you checked in the fix yet? 
> >    
> > The ddls are generated from xsl templates located in 
> > devel/src/res/xsl/ddl.   
> > You have to run   
> >    
> > cd devel 
> > ant dist   
> > cd ..   
> > cd j2ee-demo   
> > ant concern   
> >    
> > then you should have ddls with an integer typed timeout field in the 
> > timer   
> > table.   
> >    
> > Holger 
> >    
> > > Raoul 
> > >    
> > > -----Oorspronkelijk bericht-----  
> > > Van: Holger Engels [mailto:he...@me...]    
> > > Verzonden: woensdag 12 mei 2004 11:45 
> > > Aan: Raoul Zon   
> > > Onderwerp: Re: server.log and jmx-console output   
> > >    
> > >    
> > > Quoting Raoul Zon <rao...@to...>: 
> > >     
> > > > Holger, 
> > > >      
> > > > Here are my server.log containing the errors and the jmx-console 
> > > > output   
> > > > in textfile.    
> > >     
> > > Thanks, 
> > >     
> > > it's looking quite ok. Only the column type of field timeout in the  
> > > *_timer    
> > > tables is wrong. The error occurs periodically, because the 
> scheduler   
> > > service    
> > > polls these tables. I fixed it in cvs.    
> > >     
> > > Regards, 
> > >     
> > > Holger Engels  
> > > (Dipl Inf Med)    
> > >     
> > > --  
> > > Consultant, Architect, Developer    
> > > Mobile: +49 176 20119752    
> > >    
> > > ------------------------------------------------- 
> > > This mail sent through IMP: http://horde.org/imp/   
> > >    
> > >    
> >    
> >    
> > Holger Engels 
> > (Dipl Inf Med)   
> >    
> > -- 
> > Consultant, Architect, Developer   
> > Mobile: +49 176 20119752   
> >   
> > ------------------------------------------------- 
> > This mail sent through IMP: http://horde.org/imp/  
> >   
> >   
>   
>   
> Holger Engels  
> (Dipl Inf Med)  
>   
> --  
> Consultant, Architect, Developer  
> Mobile: +49 176 20119752  
>  
> ------------------------------------------------- 
> This mail sent through IMP: http://horde.org/imp/ 
>  

Holger Engels 
(Dipl Inf Med) 

-- 
Consultant, Architect, Developer 
Mobile: +49 176 20119752 

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/