Skip to main content

Resolve NullPointerException at weblogic.wsee.jaxws.spi.ClientIdentityRegistry.internalAddClientRuntimeMBean

One of our project running on Solaris Sparc system on production, last week we have deployed newer version of our project which have to integrate with 3rd party webservices. On development platform all the test goes fine on Weblogic 10.3.3, but on production we got the following Nullpointer exception:
05-10-2010 18:48:01.066 ERROR r.f.t.a.service.AuctionAOPLogger - Exception:

java.lang.NullPointerException: null

at weblogic.wsee.jaxws.spi.ClientIdentityRegistry.internalAddClientRuntimeMBean(ClientIdentityRegistry.java:470) ~[weblogic.jar:10.3.3.0]

at weblogic.wsee.jaxws.spi.ClientIdentityRegistry.addClientRuntimeMBean(ClientIdentityRegistry.java:424) ~[weblogic.jar:10.3.3.0]

at weblogic.wsee.jaxws.tubeline.standard.WseeClientTube.register(WseeClientTube.java:54) ~[weblogic.jar:10.3.3.0]

at weblogic.wsee.jaxws.tubeline.standard.WseeClientTube.(WseeClientTube.java:35) ~[weblogic.jar:10.3.3.0]

at weblogic.wsee.jaxws.tubeline.standard.StandardTubelineDeploymentListener$1.createClient(StandardTubelineDeploymentListener.java:52) ~[weblogic.jar:10.3.3.0]

at weblogic.wsee.jaxws.WLSTubelineAssemblerFactory$TubelineAssemblerImpl.createClient(WLSTubelineAssemblerFactory.java:148) ~[weblogic.jar:10.3.3.0]

at com.sun.xml.ws.client.WSServiceDelegate.createPipeline(WSServiceDelegate.java:467) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at com.sun.xml.ws.client.WSServiceDelegate.getStubHandler(WSServiceDelegate.java:689) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at com.sun.xml.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:667) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:362) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:344) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:326) ~[glassfish.jaxws.rt_1.0.0.0_2-1-5.jar:2.1.5]

at javax.xml.ws.Service.getPort(Service.java:92) ~[na:1.6.0_20]

at ru.fors.trade.rosim.ws.client.CheckAuctionServices.getBasicHttpBindingICheckAuctionServices(CheckAuctionServices.java:56) ~[rosim-confirmation-2.0.6.2.jar:na]

at ru.fors.trade.auction.service.RosimServiceImpl.checkAuctionCorrect(RosimServiceImpl.java:47) ~[auction-common-2.0.6.2.jar:na]

at sun.reflect.GeneratedMethodAccessor683.invoke(Unknown Source) ~[na:na]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_20]

at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_20]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) [spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:54) [spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) [spring-aop-2.5.6.jar:2.5.6]

at $Proxy139.checkAuctionCorrect(Unknown Source) [na:na]

at ru.fors.trade.auction.service.AuctionServiceImpl.checkForRosimSendOrUpdate(AuctionServiceImpl.java:1457) [auction-common-2.0.6.2.jar:na]

at sun.reflect.GeneratedMethodAccessor682.invoke(Unknown Source) ~[na:na]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_20]

at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_20]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) [spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:54) [spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) [spring-tx-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) ~[spring-aop-2.5.6.jar:2.5.6]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) [spring-aop-2.5.6.jar:2.5.6]
At first glance it seems, client trying to add client identification on request.
After some googling on web i have just found one forum thread with no answer.


First of all i have check the pom.xml and discover client stub using sun JAX-WS implementation and decided to use Weblogic implementation which resolve the problem. These are the pom.xml dependencies 

<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-rt</artifactId>
<scope>provided</scope>
<version>2.1.4</version>
<exclusions>
<exclusion>
<groupId>com.sun.xml.stream</groupId>
<artifactId>sjsxp</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<scope>provided</scope>
<version>2.1.7</version>
</dependency>

Above fragment of dependencies should exclude followings jar from your applications:
jaxws-api-2.1.jar, jaxb-impl-2.1.7.jar, jaxws-api-2.1.jar и jaxws-rt-2.1.4.jar
Labels:

Comments

Post a Comment

Popular posts from this blog

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title  The Apache Ignite book  has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .
Post a Comment
Read more

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...
Post a Comment
Read more