instance jaxbcontext

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

instance jaxbcontext

Baohong Wu
I am using WebLogic 1212 with java 7
 
in servlet init(), I call to instance jaxbcontext via singleton, it took 1 hour to finish. My jaxb class contains 680 class files.
 
but, if I put call in a standalone java main, it comes out result right away.
 
any help are appreciated.


Reply | Threaded
Open this post in threaded view
|

Re: instance jaxbcontext

Mirko Klemm
Hi Baohong,
The delay is likely to be caused by the classloader(s) WebLogic installs for your application.
As I'm not familiar with WebLogic, my only suggestion is to look for an option to configure class loading in a way such that no network URLs are in the class path of your application. It seems as if WebLogic tries to resolve classes from network locations, which can be very slow.
Your issue is most likely better answered in a WebLogic-specific forum or by WebLogic support.
Regards,
Mirko

Mirko Klemm
Hermannstädter Str. 10
53119 Bonn

[hidden email]
T +49 228 2493636
M +49 151 22646381
F +49 721 509663752

> Am 31.03.2015 um 14:43 schrieb Baohong Wu <[hidden email]>:
>
> I am using WebLogic 1212 with java 7
>  
> in servlet init(), I call to instance jaxbcontext via singleton, it took 1 hour to finish. My jaxb class contains 680 class files.
>  
> but, if I put call in a standalone java main, it comes out result right away.
>  
> any help are appreciated.
>
>

smime.p7s (8K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: instance jaxbcontext

Iaroslav Savytskyi
Hi,

One more thing. WLS also contains another JAXB impl - MOXy.
So you can try to use that one and compare results.


Yarda

> On 31 Mar 2015, at 17:39, Mirko Klemm <[hidden email]> wrote:
>
> Hi Baohong,
> The delay is likely to be caused by the classloader(s) WebLogic installs for your application.
> As I'm not familiar with WebLogic, my only suggestion is to look for an option to configure class loading in a way such that no network URLs are in the class path of your application. It seems as if WebLogic tries to resolve classes from network locations, which can be very slow.
> Your issue is most likely better answered in a WebLogic-specific forum or by WebLogic support.
> Regards,
> Mirko
>
> Mirko Klemm
> Hermannstädter Str. 10
> 53119 Bonn
>
> [hidden email]
> T +49 228 2493636
> M +49 151 22646381
> F +49 721 509663752
>
>> Am 31.03.2015 um 14:43 schrieb Baohong Wu <[hidden email]>:
>>
>> I am using WebLogic 1212 with java 7
>>
>> in servlet init(), I call to instance jaxbcontext via singleton, it took 1 hour to finish. My jaxb class contains 680 class files.
>>
>> but, if I put call in a standalone java main, it comes out result right away.
>>
>> any help are appreciated.
>>
>>