Weblogic 10 spring bean intialisation problem

I am having 2 ear file deployed in one weblogic 10 server. Each ear file contains same spring bean(e.g "fsiAuthService" bean) definition under applicationContext.xml file belongs to each ear. But while deploying both the ear file in weblogic 10, I am getting exception with bean initialisation failure. It seems, once bean initialisation done for first ear file, we are not able to intialise same bean for second ear file. But I am able to deploy both the ear file successfully in weblogic 9.1, 9.2 version. It seems, there is some issue with weblogic 10. Can anyone explain why this problem is occuring with weblogic 10? Please find below the exception detail getting for weblogic 10:
<HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'fsiAuthService' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is java.lang.ExceptionInInitializerError.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'fsiAuthService' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is java.lang.ExceptionInInitializerError
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     Truncated. see log file for complete stacktrace
java.lang.ExceptionInInitializerError
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
     at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
     Truncated. see log file for complete stacktrace

It's likely that the stack trace in the server log will provide the "root cause" of the exception (whether that's really the root cause or not). That might be helpful.

Similar Messages

  • Using Spring beans from EJB MDB

    I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
    it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message.
    The problem is I cannot get the spring context to load properly, since the MDBean it self is initialized(constructor called) only when it receives the first message from the broker, thus It's "too late" to initialize the spring context. What I want to do is load the spring context when the EJB is deployed in the Java EE container. So, is there a way I can call a some method, class, anything when the EJB is deployed in the container. Can I do something with a deployment descriptor?
    I am using glassfish V2 UR1, EJB 3.0, Spring 2.0.7 The project is deployed as a jar.

    Miku wrote:
    I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
    it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message. Why not make it a real service? Spring's contract first web services are a very nice way to go. It hides the fact that you're using a message-driven component for processing, too.
    %

  • Weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND

    I have a deploy application on the server [Weblogic 10], but when I try to assign a VirtualHost handing me the following error:
              weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
              problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
              problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
              at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
              at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
              at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
              at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
              at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
              Truncated. see log file for complete stacktrace

    <?xml version="1.0" encoding="UTF-8"?>
              <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
              <display-name>portalUchileWeb</display-name>
              <welcome-file-list>
              <welcome-file>index.html</welcome-file>
              <welcome-file>index.htm</welcome-file>
              <welcome-file>index.jsp</welcome-file>
              <welcome-file>default.html</welcome-file>
              <welcome-file>default.htm</welcome-file>
              <welcome-file>default.jsp</welcome-file>
              </welcome-file-list>
              <filter>
              <filter-name>PageFlowJspFilter</filter-name>
              <filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
              </filter>
              <filter>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
              <init-param>
              <param-name>response-code</param-name>
              <param-value>404</param-value>
              </init-param>
              </filter>
              <filter-mapping>
              <filter-name>PageFlowJspFilter</filter-name>
              <url-pattern>*.jsp</url-pattern>
              <dispatcher>FORWARD</dispatcher>
              <dispatcher>REQUEST</dispatcher>
              <dispatcher>INCLUDE</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowJspFilter</filter-name>
              <url-pattern>*.jspx</url-pattern>
              <dispatcher>FORWARD</dispatcher>
              <dispatcher>REQUEST</dispatcher>
              <dispatcher>INCLUDE</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.java</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.jsfb</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <filter-mapping>
              <filter-name>PageFlowForbiddenFilter</filter-name>
              <url-pattern>*.jpfs</url-pattern>
              <dispatcher>REQUEST</dispatcher>
              </filter-mapping>
              <listener>
              <listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
              </listener>
              <listener>
              <listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
              </listener>
              <servlet>
              <servlet-name>action</servlet-name>
              <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
              <init-param>
              <param-name>config</param-name>
              <param-value>/_pageflow/struts-config.xml</param-value>
              </init-param>
              <init-param>
              <param-name>debug</param-name>
              <param-value>2</param-value>
              </init-param>
              <init-param>
              <param-name>detail</param-name>
              <param-value>2</param-value>
              </init-param>
              <load-on-startup>2</load-on-startup>
              </servlet>
              <servlet>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>action</servlet-name>
              <url-pattern>*.jpf</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>action</servlet-name>
              <url-pattern>*.do</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <url-pattern>*.xhr</url-pattern>
              </servlet-mapping>
              <servlet-mapping>
              <servlet-name>XmlHttpRequestServlet</servlet-name>
              <url-pattern>*.render</url-pattern>
              </servlet-mapping>
                   <jsp-config>
              <taglib>
              <taglib-uri>render.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/render_taglib.jar</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/exesite.tld</taglib-uri>
              <taglib-location>/WEB-INF/exesite.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>netui-tags-template.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
              </taglib>
                   <taglib>
              <taglib-uri>netui-tags-databinding.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>netui-tags-html.tld</taglib-uri>
              <taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/struts-adapter-html.tld</taglib-location>
              </taglib>
              <taglib>
              <taglib-uri>um.tld</taglib-uri>
              <taglib-location>/WEB-INF/lib/um_taglib.jar</taglib-location>
              </taglib>
              </jsp-config>
              </web-app>

  • DelegatingVariableResolver not resolving Spring beans

    I'm developing an application using ADF UI + Spring using Jdveloper11g and deploying it to Weblogic 10.3. I'm creating beans in Spring and injecting them into ADF as managed beans(via faces-config.xml). My faces-config.xml looks like:
    -------------snip-----------------------
    <?xml version="1.0" encoding="windows-1252"?>
    <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
    <application>
    <default-render-kit-id>oracle.adf.rich</default-render-kit-id>
    <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
    </application>
    <managed-bean>
    <managed-bean-name>engineAspect</managed-bean-name>
    <managed-bean-class>com.x.EngineAspect</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    <managed-property>
    <property-name>engineAspect</property-name>
    <value>#{engineAspect}</value>
    </managed-property>
    </managed-bean>
    </faces-config>
    -------------snip-----------------------
    I'm using a backing bean to call a method on the engineAspect bean when some action happens in the UI. But, the line System.out.println(engineAspect); in the backing bean always prints a null. The backing bean has getter and setter for this field. Yet, the bean is not resolved from Spring. Any ideas what may be missing from the configuration?

    Miku wrote:
    I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
    it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message. Why not make it a real service? Spring's contract first web services are a very nice way to go. It hides the fact that you're using a message-driven component for processing, too.
    %

  • Weblogic, Spring, EAR, EE container, how to start spring container?

    Hi, I'm a bit stuck and although googled for quite a while, haven't found any hint on how to achieve the following. (If someone notice, yeah, I've posted same question on spring forums :) )
    I have some jar which contains spring beans which so far operated as
    standalone app by simply starting spring context. Spring context config is within jar, but it could be moved out if required.
    Now, I'm trying to embed it into EAR and to deploy to EE container (it is WebLogic server, thus I am posting here)...and it is fine, I've embedded it as javaModule and deployed it,
    but of course it doesn't do anything as spring context is not started.
    That is my question, does someone has experience with this? All I need is to on EAR start, to start spring context and on EAR stop to stop it...
    This does not have any gui or anything so I don't need it to be webapp. Also there are no EJBs as I don't need them, this app actually occasionally calls some system command to process some files.
    I am aware that maybe I'd need to extend ApplicationLifecycleListener but if so, what would be good approach to start context and keep it alive until EAR is stopped?
    I am aware that I could convert it to web-app and use ContextListener on web-app, but before that I'd like to check, is this achievable,
    and what is the best approach to start spring context if I only need container to be started, nothing else?
    Furthermore, if I implement singleton service (as I don't need this to be spread throughout cluster) what would be the best approach to start spring context from it?
    Any help/tip/info/suggestion is very appreciated.
    Thanks.

    Well, I've actually solved it meanwhile without webapp stuff.
    Perhaps if you are experienced with weblogic could evaluate my solution.
    I've implemented application lifecycle listener and in post start I start spring
    with ClassPathApplicationContext.start (by giving it config location) and stop it in pre stop.
    Not sure if this is the best solution but it works quite fine.
    Thanks,
    Edited by: rssole on Apr 7, 2012 4:17 PM

  • When to use Custom Adapter, Event Beans and Spring beans

    Hi,
    I have basic question on when or on what basis/scenario the Custom Adapter, Event Beans or Spring beans should be used.
    All three has same implementation methods.
    Please help me in understanding when to use Custom Adapters, Event Beans or Spring beans.
    Thanks,
    Sri
    Edited by: 897694 on Mar 7, 2012 8:12 AM

    custom adapters:
    you have to use a custom adapter when you don't find any adapter in ocep which will serve your purpose.
    Most of the times you use an adapter to connect the application with external things like http server, etc It can be both to listen the events or to send the events outside.
    Event Beans:
    This type of beans does most of the work that an adapter code does but in convention beans are not used to connect the application with external stuff
    You can use Beans as event sink etc In this case using an using an adapter is not suggestable.
    If you implement Interfaces like Initializing Bean for an adapter code it won't work properly, you have to use an event Bean in that case.
    Spring beans:
    Spring beans are used when the bean code doesn't implement EventSink or EventSender.
    These beans are used to enable something (eg: make ${wlevs_dev_home}/abc/a/b.java this path is not understandable by java code unless you override the path using a spring bean)
    Most of the things which doesn't need a connection between components in the application (eg cache loader: you can do this using spring beans and event beans both but spring beans doesn't need a connection with cache)
    Hope this small writeup helps you :)
    Edited by: Patha on Mar 8, 2012 9:10 AM

  • I want to use an XMLCollection in a Spring bean

    From within a mxml I make a HttpSession call that generates
    an XMLCollection (e4x). I then use the XML with in the mxml. I also
    want to use the XML in an Spring bean. Any idea how I can id the
    XML in the HttpSession?
    Thanks for the help

    Have a look at this Flex Cookbook Article:
    http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&productId=2&postI d=3401

  • Jelly Bean Update Problems on Xperia S Tablet

    I think we need a new topic for Jelly Bean update problems and fixes.
    Solved!
    Go to Solution.

    small fonts and icons blurry pixelated in notification or google agenda widget
    browser crashes a lot.
    Missing jelly bean home launcher
    Wifi disconnecting for no reason.
    Animations aren't smooth tough tablet is more responsive then android 4.0.3 release6b

  • EJB calling Spring Bean with non XA Datasources causing Rollback Exception

    We have an EJB CMT with Required calling a spring bean (@Transactional Propagation.NOT_SUPPORTED). This is causing an Rollback Exception saying 2 phase commit must be enabled. The EJB has to write to datasource 1, but the Spring Bean is ready only on Data Source 2. The Data Sources are set to use Non XA Driver with Support Global Transaction enabled for One phase commit. Any help is appreciated.

    We have an EJB CMT with Required calling a spring bean (@Transactional Propagation.NOT_SUPPORTED). This is causing an Rollback Exception saying 2 phase commit must be enabled. The EJB has to write to datasource 1, but the Spring Bean is ready only on Data Source 2. The Data Sources are set to use Non XA Driver with Support Global Transaction enabled for One phase commit. Any help is appreciated.

  • Spring Bean not loading in Coherence 3.5

    Hi,
    I am upgrading my application from Coherence 3.4 to 3.5. But when I put jar files for 3.5 on application start Coherence is not able to find the spring bean. I checked the spring application context. The bean which I am reffering s present in context. The spring config is loaded before the coherence config file is loaded.
    Below mentioned is the error which I am getting
    (Wrapped: Failed to instantiate class "spring-bean:eventCacheStore" using sun.misc.Launcher$AppClassLoader@757aef
    <class-scheme>
    <class-name>spring-bean:eventCacheStore</class-name>
    </class-scheme>) java.lang.ClassNotFoundException: spring-bean:eventCacheStore
         at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
         at com.tangosol.run.xml.XmlHelper.createInstance(XmlHelper.java:2307)
         at com.tangosol.net.DefaultConfigurableCacheFactory.instantiateAny(DefaultConfigurableCacheFactory.java:2959)
         at com.tangosol.net.DefaultConfigurableCacheFactory.instantiateCacheStore(DefaultConfigurableCacheFactory.java:2822)
         at com.tangosol.net.DefaultConfigurableCacheFactory.instantiateReadWriteBackingMap(DefaultConfigurableCacheFactory.java:1458)
         at com.tangosol.net.DefaultConfigurableCacheFactory.configureBackingMap(DefaultConfigurableCacheFactory.java:1223)
         at com.tangosol.net.DefaultConfigurableCacheFactory$Manager.instantiateBackingMap(DefaultConfigurableCacheFactory.java:3457)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.instantiateResourceMap(DistributedCache.CDB:22)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.setCacheName(DistributedCache.CDB:27)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ConfigListener.entryInserted(DistributedCache.CDB:15)
         at com.tangosol.util.MapEvent.dispatch(MapEvent.java:206)
         at com.tangosol.util.MapEvent.dispatch(MapEvent.java:166)
         at com.tangosol.util.MapListenerSupport.fireEvent(MapListenerSupport.java:556)
         at com.tangosol.util.ObservableHashMap.dispatchEvent(ObservableHashMap.java:229)
         at com.tangosol.util.ObservableHashMap$Entry.onAdd(ObservableHashMap.java:270)
         at com.tangosol.util.SafeHashMap.put(SafeHashMap.java:244)
         at com.tangosol.coherence.component.util.collections.WrapperMap.put(WrapperMap.CDB:1)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$ServiceConfigMap.put(Grid.CDB:31)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$StorageIdRequest.onReceived(DistributedCache.CDB:45)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:9)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:136)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
         at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
         at java.lang.Thread.run(Thread.java:619)
    Thariq

    Hi Paul,
    Thanks for the reply.
    I am doing that programmatically. Below mentioned is the code.
    loadSystemProperties(connectionProps);
    InputStream is = Thread.currentThread().getContextClassLoader().getResourceAsStream(fileName); //coherence cache config file.
    XmlDocument xmlDocument = XmlHelper.loadXml(is);
    SpringAwareCacheFactory defaultConfigurableCacheFactory = new SpringAwareCacheFactory();
    defaultConfigurableCacheFactory.setBeanFactory(currrentContext); //Spring injected context
    defaultConfigurableCacheFactory.setConfig(xmlDocument);
    CacheFactory.setConfigurableCacheFactory(defaultConfigurableCacheFactory);
    CacheFactory.ensureCluster();
    When I put jar files of Coherence 3.4 its loading spring beans properly. But when I put Coherence 3.5.1 everything breaks.
    Thanks,
    Thariq

  • Oracle 8i & weblogic Entity bean problem

    I have a bean named AccountEJB,and in home interface,I have findByprimaryKey(Sting id).I allocated an Account(remote interface) object by call findByPrimaryKey.The program found it.But when I call busness method using this object,(sunch as account.getUserType()),I got remoteException.In server window,I got following message:
    <Jul 10, 2001 1:04:21 PM EDT> <Error> <EJB> <Exception during commit of transa
    ion transaction=(IdHash=5169777,Name = [EJB AccountEJBImpl.getDetails()],Xid=3
    a33593394cd3b17,Status=Rolled back. [Reason = java.lang.NullPointerException],
    mRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=30,
    Info[myserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
    countEJBImpl.getDetails()], LOCAL_ENTITY_TX=true})): java.lang.NullPointerExce
    ion
    at com.nmt.account.ejb.AccountADO.store(AccountADO.java:228)
    at com.nmt.account.ejb.AccountEJB.ejbStore(AccountEJB.java:109)
    at com.nmt.account.ejb.AccountEJBImpl.ejbStore(AccountEJBImpl.java:125
    at weblogic.ejb20.manager.DBManager.storeBean(DBManager.java:231)
    at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:33
    at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxMan
    er.java:159)
    at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Se
    erSCInfo.java:500)
    at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(
    rverSCInfo.java:70)
    at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepare
    dChain(ServerTransactionImpl.java:877)
    at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepar
    ServerTransactionImpl.java:1203)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTr
    sactionImpl.java:158)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java
    03)
    at com.nmt.account.ejb.AccountEJBEOImpl.getDetails(AccountEJBEOImpl.ja
    :344)
    at com.nmt.account.ejb.AccountEJBEOImpl_WLSkel.invoke(AccountEJBEOImpl
    LSkel.java:118)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.
    va:373)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.
    va:237)
    at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicReques
    andler.java:103)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReque
    .java:17)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected exception in beforeCompleti
    : sync = weblogic.ejb20.internal.TxManager$TxListener@3 - with nested exceptio
    [java.lang.NullPointerException]
    at weblogic.transaction.internal.TransactionImpl.throwRollbackExceptio
    TransactionImpl.java:1248)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTr
    sactionImpl.java:208)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java
    03)
    at com.nmt.account.ejb.AccountEJBEOImpl.getDetails(AccountEJBEOImpl.ja
    :344)
    at com.nmt.account.ejb.AccountEJBEOImpl_WLSkel.invoke(AccountEJBEOImpl
    LSkel.java:118)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.
    va:373)
    at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.
    va:237)
    at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicReques
    andler.java:103)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteReque
    .java:17)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    I am sorry,I still have more to say.This is urgent.Please help me.
    Thanks
    I have a bean named AccountEJB,and in home interface,I
    have findByprimaryKey(Sting id).I allocated an
    Account(remote interface) object by call
    findByPrimaryKey.The program found it.But when I call
    busness method using this object,(sunch as
    account.getUserType()),I got remoteException.In server
    window,I got following message:
    <Jul 10, 2001 1:04:21 PM EDT> <Error> <EJB> <Exception
    during commit of transa
    ion transaction=(IdHash=5169777,Name = [EJB
    AccountEJBImpl.getDetails()],Xid=3
    a33593394cd3b17,Status=Rolled back. [Reason =
    java.lang.NullPointerException],
    mRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
    begin=0,seconds left=30,
    Info[myserver]=(state=rolledback),properties=({weblogic
    transaction.name=[EJB
    countEJBImpl.getDetails()], LOCAL_ENTITY_TX=true})):
    java.lang.NullPointerExce
    ion
    at
    at
    at
    t
    com.nmt.account.ejb.AccountADO.store(AccountADO.java:22
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJB.ejbStore(AccountEJB.java
    109)
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJBImpl.ejbStore(AccountEJBI
    pl.java:125
    at
    at
    at
    t
    weblogic.ejb20.manager.DBManager.storeBean(DBManager.ja
    a:231)
    at
    at
    at
    t
    weblogic.ejb20.manager.DBManager.beforeCompletion(DBMan
    ger.java:33
    at
    at
    at
    t
    weblogic.ejb20.internal.TxManager$TxListener.beforeComp
    etion(TxMan
    er.java:159)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerSCInfo.callBeforeCo
    pletions(Se
    erSCInfo.java:500)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerSCInfo.startPrePrep
    reAndChain(
    rverSCInfo.java:70)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerTransactionImpl.loc
    lPrePrepare
    dChain(ServerTransactionImpl.java:877)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerTransactionImpl.glo
    alPrePrepar
    ServerTransactionImpl.java:1203)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerTransactionImpl.com
    it(ServerTr
    sactionImpl.java:158)
    at
    at
    at
    t
    weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJ
    Object.java
    03)
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJBEOImpl.getDetails(Account
    JBEOImpl.ja
    :344)
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJBEOImpl_WLSkel.invoke(Acco
    ntEJBEOImpl
    LSkel.java:118)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicSe
    verAdapter.
    va:373)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicSe
    verAdapter.
    va:237)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicRequestHandler.handleRequest
    BasicReques
    andler.java:103)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicExecuteRequest.execute(Basic
    xecuteReque
    .java:17)
    at
    at
    at
    t
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.jav
    :137)
    at
    at
    at
    t
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:12
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected
    exception in beforeCompleti
    : sync =
    weblogic.ejb20.internal.TxManager$TxListener@3 - with
    nested exceptio
    [java.lang.NullPointerException]
    at
    at
    at
    t
    weblogic.transaction.internal.TransactionImpl.throwRoll
    ackExceptio
    TransactionImpl.java:1248)
    at
    at
    at
    t
    weblogic.transaction.internal.ServerTransactionImpl.com
    it(ServerTr
    sactionImpl.java:208)
    at
    at
    at
    t
    weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJ
    Object.java
    03)
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJBEOImpl.getDetails(Account
    JBEOImpl.ja
    :344)
    at
    at
    at
    t
    com.nmt.account.ejb.AccountEJBEOImpl_WLSkel.invoke(Acco
    ntEJBEOImpl
    LSkel.java:118)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicSe
    verAdapter.
    va:373)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicSe
    verAdapter.
    va:237)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicRequestHandler.handleRequest
    BasicReques
    andler.java:103)
    at
    at
    at
    t
    weblogic.rmi.internal.BasicExecuteRequest.execute(Basic
    xecuteReque
    .java:17)
    at
    at
    at
    t
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.jav
    :137)
    at
    at
    at
    t
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:12

  • Weblogic 5.1 SP9 problems with MAC OS 9 w/ MRJ 2.2.5 [InterruptedIOException]

    Hello all,
    We're having a problem with one of the beans running on our WebLogic server.
    A quick summary:
    The application is a standalone java application that
    interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
    The clients are a mix of Windows machines and Mac OS 9 (with OS X
    coming down the line, but that is not feasible at this time
    to consider a massive upgrade). Due to the limitations
    of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
    Mac and JRE 1.1.9 on the Windows machines.
    The general flow of data is a request is made from the client app
    to the WebLogic bean. The bean calls another class method which
    retrieves data from the the backend database (Sybase or SQL Server 2000).
    We've verified that the data comes back from the query, is placed
    in an array, and is in the same state when the EJB prepares to 'return'
    the data to the client. This works as expected on the Windows machines,
    however, every so often, the Macs will give an
    InterruptedIOException: send timed out error. Once the server times
    out (after 240 seconds), the client can continue until the next
    error.
    A few additional pieces of info.
    The data returned is an array, but there isn't any consistancy to the
    size of the data set. Some will be single element arrays while others
    will have 8-10 elements. The amount of data in each element is only
    a string of a couple hundred characters, so it is not a large data
    stream. Systems on the same network segment can go for a while (sometimes
    going on 10 minutes) before getting this error, while remote offices
    going over slower links will get an immediate InteruptedIOException.
    We have a process in place that if it catches an InterruptedIOException
    it loops and tries the procedure again, however a 4 minute wait
    between loops just isn't acceptable. We tried lowering this by
    placing the following lines into our weblogic.properties file:
    weblogic.system.periodLength=15
    weblogic.system.idlePeriodsUntilTimeout=4
    However, this has had zero impact on the timeout. Are there programatic
    ways of changings these values? Or to force a blocking connection that
    will force the data pipe to stay open? Has anyone had any insight into
    any similar problems? Unfortunately, due to the size of the company,
    the environment is fixed, and no mass upgrades are a vaiable option.
    Thanks all!
    Cliff

    Hi Cliff,
    it seems as if we have a similar problem within WLS51sp13 and a Java
    Client (Servlet within Tomcat). We found that an EJB Stub within the
    Client App has a 180s timeout, if the server socket didn't close
    (Network problem or similar). I friend gave me a hint setting this
    parameter on both sides, client and Server: It works. It seems as if the
    server takes the bigger value of both values set.
    Greetings,
    schnaggy:-)
    Cliff Wagner wrote:
    Hello all,
    We're having a problem with one of the beans running on our WebLogic server.
    A quick summary:
    The application is a standalone java application that
    interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
    The clients are a mix of Windows machines and Mac OS 9 (with OS X
    coming down the line, but that is not feasible at this time
    to consider a massive upgrade). Due to the limitations
    of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
    Mac and JRE 1.1.9 on the Windows machines.
    The general flow of data is a request is made from the client app
    to the WebLogic bean. The bean calls another class method which
    retrieves data from the the backend database (Sybase or SQL Server 2000).
    We've verified that the data comes back from the query, is placed
    in an array, and is in the same state when the EJB prepares to 'return'
    the data to the client. This works as expected on the Windows machines,
    however, every so often, the Macs will give an
    InterruptedIOException: send timed out error. Once the server times
    out (after 240 seconds), the client can continue until the next
    error.
    A few additional pieces of info.
    The data returned is an array, but there isn't any consistancy to the
    size of the data set. Some will be single element arrays while others
    will have 8-10 elements. The amount of data in each element is only
    a string of a couple hundred characters, so it is not a large data
    stream. Systems on the same network segment can go for a while (sometimes
    going on 10 minutes) before getting this error, while remote offices
    going over slower links will get an immediate InteruptedIOException.
    We have a process in place that if it catches an InterruptedIOException
    it loops and tries the procedure again, however a 4 minute wait
    between loops just isn't acceptable. We tried lowering this by
    placing the following lines into our weblogic.properties file:
    weblogic.system.periodLength=15
    weblogic.system.idlePeriodsUntilTimeout=4
    However, this has had zero impact on the timeout. Are there programatic
    ways of changings these values? Or to force a blocking connection that
    will force the data pipe to stay open? Has anyone had any insight into
    any similar problems? Unfortunately, due to the size of the company,
    the environment is fixed, and no mass upgrades are a vaiable option.
    Thanks all!
    Cliff

  • Message Driven Bean Reference Problem

    Hi,
    I have problems a MDB referencing other beans, I am getting Class Cast
    exception whenever my MDB tries to use narrow operation after the lookup
    is done.
    The Code is as follows:
    public void ejbCreate () throws CreateException {
    log("ejbCreate called");
    try {
    InitialContext ctx = new InitialContext();
    Object ref = ctx.lookup("java:comp/env/ejb/LoggerCache");
    log("Lookup of Cache done");
    LoggerCacheHome loggerCacheHome = (LoggerCacheHome)
    PortableRemoteObject.narrow(ref, LoggerCacheHome.class);
    } catch(Exception ex) {
    ex.printStackTrace();
    The lookup is successful but when I try to use the narrow..... I get the
    following exception stackk Trace.
    Any help will be appreciated.
    TIA,
    Vikas
    Stack Trace
    java.lang.ClassCastException
    at
    weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteO
    bjectDelegateImpl.java:90)
    at
    javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
    at
    examples.ejb20.message.MessageTraderBean.ejbCreate(MessageTraderBean.
    java:90)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDriven
    EJBHome.java:290)
    at
    weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.ja
    va:98)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:100)
    at weblogic.ejb20.pool.Pool.<init>(Pool.java:74)
    at weblogic.ejb20.pool.EntityPool.<init>(EntityPool.java:34)
    at
    weblogic.ejb20.pool.MessageDrivenPool.<init>(MessageDrivenPool.java:4
    3)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getPool(MessageDriv
    enBeanInfoImpl.java:336)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrive
    nBeanInfoImpl.java:403)
    at
    weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    at weblogic.j2ee.Application.deploy(Application.java:167)
    at
    weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
    at
    weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
    ation.java:217)
    at
    weblogic.management.mbeans.custom.Application.setDeployed(Application
    .java:187)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
    anImpl.java:1136)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
    anImpl.java:773)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
    anImpl.java:750)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
    igurationMBeanImpl.java:256)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1331)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
    s(ConfigurationMBeanImpl.java:318)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
    igurationMBeanImpl.java:259)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1331)
    at
    weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:
    291)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:173)
    at $Proxy91.setDeployed(Unknown Source)
    at
    weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
    cationManager.java:494)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(Application
    Manager.java:465)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(Application
    Manager.java:380)
    at
    weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
    onManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:562)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:548)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:285)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
    at $Proxy2.update(Unknown Source)
    at
    weblogic.management.console.pages._domain._upload_app._jspService(_up
    load_app.java:172)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:213)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:1265)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:1622)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Print the class info for the castee and the cast-to classes. They are
    incompatible, and hence the exception. It could be a bug in your code, or
    it could be a classloader issue (resulting from how you
    packaged/deployed/how your app works) or something like that.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "Vikas" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I have problems a MDB referencing other beans, I am getting Class Cast
    exception whenever my MDB tries to use narrow operation after the lookup
    is done.
    The Code is as follows:
    public void ejbCreate () throws CreateException {
    log("ejbCreate called");
    try {
    InitialContext ctx = new InitialContext();
    Object ref = ctx.lookup("java:comp/env/ejb/LoggerCache");
    log("Lookup of Cache done");
    LoggerCacheHome loggerCacheHome = (LoggerCacheHome)
    PortableRemoteObject.narrow(ref, LoggerCacheHome.class);
    } catch(Exception ex) {
    ex.printStackTrace();
    The lookup is successful but when I try to use the narrow..... I get the
    following exception stackk Trace.
    Any help will be appreciated.
    TIA,
    Vikas
    Stack Trace
    java.lang.ClassCastException
    at
    weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteO
    bjectDelegateImpl.java:90)
    at
    javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
    at
    examples.ejb20.message.MessageTraderBean.ejbCreate(MessageTraderBean.
    java:90)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDriven
    EJBHome.java:290)
    at
    weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.ja
    va:98)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:100)
    at weblogic.ejb20.pool.Pool.<init>(Pool.java:74)
    at weblogic.ejb20.pool.EntityPool.<init>(EntityPool.java:34)
    at
    weblogic.ejb20.pool.MessageDrivenPool.<init>(MessageDrivenPool.java:4
    3)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getPool(MessageDriv
    enBeanInfoImpl.java:336)
    at
    weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrive
    nBeanInfoImpl.java:403)
    at
    weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    at weblogic.j2ee.Application.deploy(Application.java:167)
    at
    weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
    at
    weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
    ation.java:217)
    at
    weblogic.management.mbeans.custom.Application.setDeployed(Application
    .java:187)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
    anImpl.java:1136)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
    anImpl.java:773)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
    anImpl.java:750)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
    igurationMBeanImpl.java:256)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1331)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
    s(ConfigurationMBeanImpl.java:318)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
    igurationMBeanImpl.java:259)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1356)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
    ava:1331)
    at
    weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:
    291)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:173)
    at $Proxy91.setDeployed(Unknown Source)
    at
    weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
    cationManager.java:494)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(Application
    Manager.java:465)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(Application
    Manager.java:380)
    at
    weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
    onManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:562)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:548)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:285)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
    at $Proxy2.update(Unknown Source)
    at
    weblogic.management.console.pages._domain._upload_app._jspService(_up
    load_app.java:172)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:213)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:1265)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:1622)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Spring bean creation fails when statefull ejb created in other component

    Hi All,
    We have two components A and B. A creates stateful ejb as well calls B.
    B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
    Error creating bean with name 'dataSource' defined in file ....
    Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
    This happens only when A is using stateful beans.
    when the flow uses A's stateless beans this is working fine.
    For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
    Env: Weblogic 10.3.2
    Thanks and Regards
    Veeramani

    Hi All,
    We have two components A and B. A creates stateful ejb as well calls B.
    B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
    Error creating bean with name 'dataSource' defined in file ....
    Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
    This happens only when A is using stateful beans.
    when the flow uses A's stateless beans this is working fine.
    For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
    Env: Weblogic 10.3.2
    Thanks and Regards
    Veeramani

  • WebLogic RMI UNIX Performance problem

    Hi.
    I'm experiencing problems with the performance of RMI calls from within session
    beans to external RMI services. I have a system running 4 RMI services in separate
    JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+ Gb of RAM.
    The system was developed on NT and deployed to UNIX. A typical request is serviced
    in 70-90 ms on the NT development box (Desktop 512Mb RAM) but when deployed to
    the UNIX box takes anywhere between 500-4000 ms. Performance metrics in the code
    indicate that 'crunch' times are similar but remote RMI calls are orders of magnitude
    greater.
    Has anybody had similar problems? I have checked the tuning guides wrt TCP/IP
    configurations but would not expect such a large difference using the default
    Solaris configuration. Memory and CPU utilisation on the SPARC are low as are
    I/O and other metrics available from vmstat.
    Cheers
    Pete

    Hi.
    The JVMs are running on the same machine thus should be looking in /etc/hosts
    and not going via DNS.
    I have read there is a performance gain by tying WL to a single CPU, any insight?
    Pete
    Andy Piper <[email protected]> wrote:
    "Pete Harris" <[email protected]> writes:
    I'm experiencing problems with the performance of RMI calls from withinsession
    beans to external RMI services. I have a system running 4 RMI servicesin separate
    JVMs to weblogic 6.1 instance on Solaris 2.6 on SPARC boxes with 1+Gb of RAM.
    The system was developed on NT and deployed to UNIX. A typical requestis serviced
    in 70-90 ms on the NT development box (Desktop 512Mb RAM) but whendeployed to
    the UNIX box takes anywhere between 500-4000 ms. Performance metricsin the code
    indicate that 'crunch' times are similar but remote RMI calls are ordersof magnitude
    greater.
    Has anybody had similar problems? I have checked the tuning guideswrt TCP/IP
    configurations but would not expect such a large difference using thedefault
    Solaris configuration. Memory and CPU utilisation on the SPARC arelow as are
    I/O and other metrics available from vmstat.Its possible that you are getting a DNS lookup for each request or
    worse a reverse lookup. You might want to try using IP addresses in
    your config to see if that helps.
    andy

Maybe you are looking for