Weblogic 9.1: Error in Dispatcher

Hi,
I have an application (.ear) which contains and ejb jar.
I call the ejb from a swing application. It works fine
using weblogic 8.1. But when I use weblogic 9.1, I get
the following error, although the application went as
expected. What do I miss?
Any information would be appreciated. Thanks in advance.
>>>>>>
####<Feb 23, 2006 4:52:18 PM EST> <Notice> <WebLogicServer> <hp2> <AdminServer> <main> <<WLS Kernel>> <> <> <1140731538521> <BEA-000360> <Server started in RUNNING mode>
####<Feb 23, 2006 4:52:52 PM EST> <Error> <RMI> <hp2> <AdminServer> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1140731572802> <BEA-080001> <Error in Dispatcher
java.lang.AssertionError: Assertion violated.
java.lang.AssertionError: Assertion violated
     at weblogic.utils.Debug.assertion(Debug.java:57)
     at weblogic.rmi.internal.MethodDescriptor.getWorkManager(MethodDescriptor.java:248)
     at weblogic.rmi.internal.BasicServerRef.getWorkManager(BasicServerRef.java:333)
     at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:276)
     at weblogic.rmi.cluster.ClusterableServerRef.dispatch(ClusterableServerRef.java:236)
     at weblogic.iiop.EndPointImpl.handleIncomingRequest(EndPointImpl.java:834)
     at weblogic.iiop.EndPointImpl.processMessage(EndPointImpl.java:504)
     at weblogic.iiop.EndPointImpl.handleMessage(EndPointImpl.java:496)
     at weblogic.iiop.EndPointImpl.dispatch(EndPointImpl.java:320)
     at weblogic.iiop.ConnectionManager.dispatch(ConnectionManager.java:121)
     at weblogic.iiop.MuxableSocketIIOP.dispatch(MuxableSocketIIOP.java:295)
     at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:359)
     at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:167)
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

It looks like you hit a bug. Please contact [email protected]
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Similar Messages

  • Getting this Error Reason=weblogic.ejb20.InternalException: Error writing f

    I am using a weblogic 8.1 sp4 and is getting the following error
    =====
    java.sql.SQLException: Transaction BEA1-00A0C7390CDF3A289F82 not active anymore. tx status = Marked rollback. [Reason=weblogic.ejb20.InternalException: Error writing from flushModified]
    at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:430)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
    =====
    Is this a bug in Weblogic ?
    This happens when the the the container managed entity bean has the following element.
    <cache-strategy>read-write</cache-strategy>
    This does not happend if the following value is set
    <cache-strategy>read-only</cache-strategy>
    Any clues on a resolution to this problem ?
    Thanks in advance.

    I have similar problem with my application. I'm using Weblogic 8.1 sp4 and MS SQL 2000 sp 3 and Hibernate 2.8 to connect to DB. Table causing exception is replicated bidirectional with transactional replication. I get trace of SQL transactions made during user logging process and noticed update querry which is rolled back. There are only select querries before. I wonder if synchronizing triggers used by replication could be the problem. Can it somehow reset the session?
    Stack Trace lools like this below:
    30328 [Thread-5] ERROR pl.computerland.snu.repo.remote.external.RemoteRepoFactoryWrapper - operation():
    pl.computerland.snu.repo.remote.RemoteRepoException: java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
    Detail:
    <detail>
    EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException] </detail>; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactory.login(RemoteRepoFactory.java:116)
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactoryWrapper$ExternConnection.operation(RemoteRepoFactoryWrapper.java:301)
         at pl.computerland.snu.rfi.services.TaskService$1.run(TaskService.java:51)
         at java.lang.Thread.run(Unknown Source)
    Caused by: java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
    Detail:
    <detail>
    EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException] </detail>; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:241)
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:258)
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactory.login(RemoteRepoFactory.java:114)
         ... 3 more
    Caused by: javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
         at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:236)
         ... 5 more

  • JMSException Error finding dispatcher

    I have a JMS thin-client (linux) trying to connect to a remote JMS connection factory. The program works on any WebLogic server (8.1.SP6), but not on others. So it would seem to be an IIOP problem. I've gone through the IIOP setup doc's but nothing helps (Listener address set, using bidir iiop, and hosts know each others dns). Here's the stack trace:
              gov.va.med.logservice.appender.EELSDException: Error finding dispatcher
              at gov.va.med.logservice.appender.LogServiceDelegate_POJO.logException(LogServiceDelegate_POJO.java:140)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:324)
              at gov.va.med.caip.client.factory.DelegateProxy.invoke(DelegateProxy.java:116)
              at gov.va.med.caip.client.factory.DelegateProxy.invoke(DelegateProxy.java:80)
              at $Proxy0.logException(Unknown Source)
              at gov.va.med.logservice.oemhandler.LogEvent.main(LogEvent.java:236)
              Caused by: weblogic.jms.common.JMSException: Error finding dispatcher
              at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FEConnectionFactory.java:427)
              at weblogic.jms.frontend.FEConnectionFactory.connectionCreateRequest(FEConnectionFactory.java:386)
              at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
              at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:120)
              at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
              Caused by: weblogic.jms.dispatcher.DispatcherException: Could not register a HeartbeatMonitorListener for [Delegate(9041582) [weblogic.iiop.IOR@d7bc7554 RMI:weblogic.jms.dispatcher.DispatcherImpl:0000000000000000 @sms-agent-dev:25747, class weblogic.jms.dispatcher.DispatcherImpl]] for weblogic.jms.C:sms-oracle2-dev:ydz:-b
              at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(DispatcherWrapperState.java:580)
              at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FEConnectionFactory.java:421)
              ... 11 more
              Caused by: weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException: Could not register a HeartbeatMonitorListener for [Delegate(9041582) [weblogic.iiop.IOR@d7bc7554 RMI:weblogic.jms.dispatcher.DispatcherImpl:0000000000000000 @sms-agent-dev:25747, class weblogic.jms.dispatcher.DispatcherImpl]]
              at weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
              at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(DispatcherWrapperState.java:576)
              ... 12 more

    The program works on any WebLogic server (8.1.SP6), but not on others.                     What are these others?
              Does the standard "weblogic.jar" thick client work instead? (with "t3" URLs)

  • How to get rid of the weblogic.kernel.Default errors and warning?

    Hi there,
    When i'm running my application deployed on WLS8.1 SP3 and the application is running fine, but the following error and warnings were thrown.
    2004-08-05 11:26:30,453 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] ERROR com.bea.wlw.runtime.core.util.Config - Failed to obtain connection to datasource=cgDataSource, using generic DB properties
    <Aug 5, 2004 11:26:30 AM SGT> <Error> <WLW> <000000> <Failed to obtain connection to datasource=cgDataSource, using generic DB properties>
    2004-08-05 11:27:12,281 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.default.elementattributes
    2004-08-05 11:27:12,282 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.default.elementattributes', using defaults.
    2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.system.groupIdCache.elementattributes
    2004-08-05 11:27:12,308 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.system.groupIdCache.elementattributes', using defaults.
    2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.config.OptionConverter - Could not find value for key jcs.region.CodeTableCache.elementattributes
    2004-08-05 11:27:12,386 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN org.apache.jcs.engine.control.CompositeCacheConfigurator - Could not instantiate eAttr named 'jcs.region.CodeTableCache.elementattributes', using defaults.
    2004-08-05 11:27:13,527 [ExecuteThread: '13' for queue: 'weblogic.kernel.Default'] WARN com.bea.wlw.netui.script.el.NetUIReadVariableResolver - Could not create a ContextFactory for type "com.bea.netuix.servlets.script.PortalVariableResolver$PortalContextFactory" because the ContextFactory implementation class could not be found.
    May i know why this is so? How to get rid of these error and warnings?
    Thanks
    Derek
    Message was edited by derekchan at Aug 4, 2004 8:41 PM
    Message was edited by derekchan at Aug 4, 2004 8:42 PM

    you didnt seem to have configured the datasource / connection pool / database control with proper db properties
    you should check your configuration to see if you have done it right and then you should check your application and the properties settings in the controls to ensure they are right.

  • Weblogic 9.2 Error in poll for fd=60, revents=32

    hello,
    Glad to talk with you。
    When my web application running on weblogic 9.2,it often happens a problem, as follows:
    <2010-7-14 下午01时15分26秒 CST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
    weblogic.utils.NestedError: Error adding FD to epoll.
    weblogic.utils.NestedError: Error adding FD to epoll
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:86)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1353)
    Truncated. see log file for complete stacktrace
    java.io.IOException: epoll_ctl failed: Bad file descriptor
    at jrockit.ext.epoll.EPoll.epollEnableOneshot(II)V(Unknown Source)
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:72)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    Truncated. see log file for complete stacktrace
    and another problem:
    <Error> <HTTP> <BEA-101083> <Connection failure.
    java.net.SocketException: Error in poll for fd=60, revents=32
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:133)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    thanks
    regards,
    lijun

    Hi,
    For WLS version 9.2 there is a Fix Available for the same issue : CR309671 Please contact Oracle support to get the Patch (CR309671).
    After BEA/Oracle integration the Patch Naming convention is changed so to get the TAR version of the Patch Number u need to contact Oracle Support.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/ (WebLogic Wonders Are Here)

  • Getting weblogic server startup error

    getting the following erro while starting weblogic server
    An error has occurred. The following chain of information is available:
    error 1: /Arg/Arg/Tag/
    message: Tag not found in dictionary.
    argument position: 50979500
    tag: "vnum"
    issue is coming when we configure the application.

    Has the server ever started prior to deployment of services?

  • BEA-000802   weblogic.utils.NestedError: Error adding FD to epoll.

    hello,everyone,
    My weblogic have a problem.it often happens.
    <2010-7-14 下午01时15分26秒 CST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
    weblogic.utils.NestedError: Error adding FD to epoll.
    weblogic.utils.NestedError: Error adding FD to epoll
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:86)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1353)
    Truncated. see log file for complete stacktrace
    java.io.IOException: epoll_ctl failed: Bad file descriptor
    at jrockit.ext.epoll.EPoll.epollEnableOneshot(II)V(Unknown Source)
    at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:72)
    at weblogic.servlet.internal.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java:211)
    at weblogic.servlet.internal.VirtualConnection.requeue(VirtualConnection.java:323)
    at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1267)
    Truncated. see log file for complete stacktrace
    who can help me?
    thanks
    lijun

    hi everyone,
    i am waiting for you answers. is anyone here?
    thanks,
    lijun

  • Weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for ServletContext

    Hi,
         We have Installed Weblogic Server 10.3.5, applied the ADF Runtime 11.1.1.6 and applied the patch 11.1.2.4.0.
         All the Deployment libraries are appearing in the server.
    When we try to deploy a simple application, we are getting below error.
    [05:07:29 PM] Deploying Application...
    [05:07:30 PM] [Deployer:149193]Operation 'deploy' on application 'JSFPageTest_Project1_JSFPageTest' has failed on 'AdminServer'
    [05:07:30 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application JSFPageTest_Project1_JSFPageTest on AdminServer.: Failed to load webapp: 'JSFPageTest-ViewController-context-root'.
    [05:07:30 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'JSFPageTest-ViewController-context-root'
    [05:07:30 PM] Caused by: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@68993675[app:JSFPageTest_Project1_JSFPageTest module:JSFPageTest-ViewController-context-root path:/JSFPageTest-ViewController-context-root spec-version:2.5]", defined in weblogic.xml [Extension-Name: jsf, Specification-Version: 2, exact-match: false]
    [05:07:30 PM]   See server logs or server console for more details.
    [05:07:30 PM] weblogic.application.ModuleException: Failed to load webapp: 'JSFPageTest-ViewController-context-root'
    [05:07:30 PM] Deployment cancelled.
    [05:07:30 PM] ----  Deployment incomplete  ----.
    [05:07:30 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Regards,
    Lakshmi

    looks like you didn't install the application development runtime on WLS, or if you did, you either forgot to extend your domain with the JRF or installed the wrong version of the application development runtime.

  • Idoc, error during dispatch

    Hi,
    How can we correct idocs in staus 11 ie error during dispatch. What can be the reason behind the error? How can i check that?
    Thanks in advance.

    Hi,
    ALEFailureCode 11
    An IDoc that is not successfully sent to the endpoint is considered a failure and the IDoc status is updated by the adapter to 11
    try to reprocess the idoc in BD87.
    Prabhudas

  • Weblogic/Java Transaction error...

    Hi,
    have you ever seen an error like this?
    <Dec 15, 2001 2:08:05 AM PST> <Error> <JTA> <Resource weblogic.jdbc.jts.Connection was not assigned to any of these servers: wladm >
    <Dec 15, 2001 2:08:05 AM PST> <Error> <EJB> <Exception during commit of transaction transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Rolled back. [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1325,seconds left=9,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=none),SCInfo[wladm]=(state=rolledback),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})): weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))
         at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1026)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:388)
         at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:791)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:357)
         at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:757)
         at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1261)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:218)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:201)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl.updateUser(UserManagerEjbEOImpl.java:247)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLSkel.invoke(UserManagerEjbEOImpl_WLSkel.java:575)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:115)
         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:88)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLStub.updateUser(UserManagerEjbEOImpl_WLStub.java:700)
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1022)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    EXCEPTIONadmin2001/12/15;02:08:05.137UserCtrl.updateUser(1035)
    UserCtrl.service(1561)
    WebRequestDispatcher.dispatch(246)
    WebMain.service(48)
    --- exception
    com.corrtech.web.util.WebInternalException: weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))
         at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1026)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:388)
         at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:791)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:357)
         at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:757)
         at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1261)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:218)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:201)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl.updateUser(UserManagerEjbEOImpl.java:247)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLSkel.invoke(UserManagerEjbEOImpl_WLSkel.java:575)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:115)
         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:88)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLStub.updateUser(UserManagerEjbEOImpl_WLStub.java:700)
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1022)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ; nested exception is:
         weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1036)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    EXCEPTIONadmin2001/12/15;02:08:05.150WebMain.service(53)
    We're using Weblogic 6.1 with Oracle 8.1.6.
    This happens whenever we want to update a record in the database
    represented by our Entity User Ejb object. The weird part is that
    this is the only situacion that causes the problem. We can create
    users without trouble and we can create/update any information in the
    database represented by any of our other beans but update for User is not
    possible.
    I tried to look for information in the bea web site but I could not find
    anything related to it. I couldn't even find the weblogic.jdbc.jts package?
    Do you have any idea about it?
    Thanks in advance.

    Hi Alberto,
    As you can see from the exception the transaction was rolled-back due to timeout. As to your question of why it is happening in the particular method, the reason might be the time that is being taken in this particular operation. You can increase the timeout seconds for the transaction by changing the value in weblogic-ejb-jar.xml file. The default value is 30 secs. Use the tag <trans-timeout-seconds> to change this value. This is the child tag of
    <weblogic-enterprise-bean>
         <transaction-descriptor>
    You can find reference for the tags at http://edocs.beasys.com/wls/docs61/ejb/reference.html#1072610.
    Hope this helps.
    Vikram.

  • Cannot run PAPI in Weblogic Server 10g - Error 500--Internal Server Error

    I use Jdev 11g to create an ADF (PAPI) and deploy it to Weblogic 10g.
    The code is copied from Jdev 10g. The PAPI works fine in when running in Jdev 10g
    However, after I deploy the ADF (PAPI) created using Jdev 11g to the Weblogic server. The following error appears.
    How to modify the code? Should I add the fuego lib to the weblogic domain?
    I try to add the fuegopapi-client.jar to Weblogic Server. But it shows error: Unable to access the selected application. java.lang.NullPointerException
    BPM is running in BPM standalone. I do not use PAPI webservice
    Sincerely
    Error 500--Internal Server Error
    javax.faces.el.EvaluationException: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
         at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:51)
         at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
         at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:458)
         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:763)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:640)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:275)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:61)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:279)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:239)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:196)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:139)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
         at fuego.directory.exception.DirectoryNotAvailableException.wrapDNAException(DirectoryNotAvailableException.java:33)
         at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:81)
         at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:34)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:437)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:91)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:242)
         at fuego.directory.provider.Factory.startSession(Factory.java:405)
         at fuego.directory.Directory.startAnonymousSession(Directory.java:214)
         at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
         at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
         at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
         at fuego.papi.ProcessService.create(ProcessService.java:335)
         at hypapai2.view.backing.P1.commandButton1_action(P1.java:54)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
         at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
         at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
         ... 32 more
    Caused by: fuego.connector.ConnectorException: External resource [fuego] of type [SQL] is not initialized.
    Detail:External resource [fuego] cannot be used because it failed to initialize correctly at service startup.
    That failure generated a warning in the server log.
    Check the logs for the details on the failure.
         at fuego.connector.ConnectorException.connectorNotInitialized(ConnectorException.java:60)
         at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:527)
         at fuego.connector.CompositeConnectorService.getDirectoryConnectorInterface(CompositeConnectorService.java:446)
         at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:293)
         at fuego.connector.ConnectorTransaction.registerConnectorInterfaceCoordinator(ConnectorTransaction.java:656)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:315)
         at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:68)
         ... 50 more

    While still using PAPI, try also adding b1oracle.jar, b1base.jar and b1util.jar to your ADF project.
    These jars could be found from your BPM Studio installation.
    HTH

  • Weblogic.jspc outofmemory error while compiling jsps using ant in eclipse

    Hi all,
    I am trying to execute this target in my ant build:
         <target name="jspc">
              <java classname="weblogic.jspc" fork="yes">
                   <arg line="-verbose -verboseJavac -compileAll -webapp ${project.jsp.dir} -d ${project.jsp.class.dir}" />
                   <classpath>
                        <pathelement path="${classpath}" />
                   </classpath>
         </java>
         </target>
    I am getting the following error:
    [java] Error: [jspc]: 0 file(s) failed:
    [java] [Compilation errors : ]
    [java] The system is out of resources.
    [java] Consult the following stack trace for details.
    [java] java.lang.OutOfMemoryError
    [java] at weblogic.jspc.doCompile(jspc.java:861)
    [java] at weblogic.jspc.runJspc(jspc.java:654)
    [java] at weblogic.jspc.runBodyInternal(jspc.java:412)
    [java] at weblogic.jspc.runBody(jspc.java:319)
    [java] at weblogic.utils.compiler.Tool.run(Tool.java:192)
    I am using weblogic 8.1, eclipse3.1, java1.4.1.
    Can some one please help me with this issue?
    thanks in advance.

    --> some error on posting please refer to the next post...
    From the error logs we can trace it out to the web project's Build.xml file ....I was getting a similar error and by commenting out the following lines in the web project's Build.xml I am able to run the build script correctly and get a EAR file. The lines are
    <!--
    <assemble
    moduleDir="${generated.module.root}"
    moduleName="${project.name}"
    srcOutputDir="${assembly.src}"
    appRootDir="${ear.root}">
    <assemblyContext factory="org.apache.beehive.controls.runtime.assembly.WebAppAssemblyContext$Factory" />
    <assemblyContext factory="org.apache.beehive.controls.runtime.assembly.AppAssemblyContext$Factory" />
    <classpath refid="assembly.classpath" />
    <fileset dir="${project.dir}">
    <include name="**/*.controls.properties" />
    </fileset>
    </assemble>
         -->
    Please check it now, also if any one can let us know the function or role played by the above lines it would be great. Also if there would be any future or unseen problems by commenting out these lines please do let us know...
    Thanks
    -MiM
    Edited by prodigymonish83 at 10/22/2007 5:56 AM

  • Oim 9.1.0.1 installation over WebLogic App server Error

    Please Fix this Error
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:591)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:64)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:174)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:235)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:131)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:510)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:782)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:591)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:64)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:174)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:235)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:131)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:510)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:782)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >

    I have the same problem at :redhat5.3-x64 ,database:11.1.0.7 weblogic 10.3 jdk:1.6.0.10
    can anyone have solveit?

  • Weblogic Server - Timeout error in AdminServer Diagnostic logs

    Hi,
    We have deployed our application (OAM 11g) on Weblogic 10.3.5. The application was working fine until thursday. After that we have only restarted the machine and the application start responding very slow. We can see the following errors in weblogic Admin Server Diagnostic logs.
    +[2012-06-18T17:23:00.481+05:30] [AdminServer] [ERROR] [] [] [tid: PoolWatcher] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-0000000000000011,0] java.net.SocketTimeoutException: Read timed out+
    +[2012-06-18T17:24:01.000+05:30] [AdminServer] [ERROR] [] [] [tid: PoolWatcher] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-0000000000000011,0] java.net.SocketTimeoutException: Read timed out+
    +[2012-06-18T17:25:01.536+05:30] [AdminServer] [ERROR] [] [] [tid: PoolWatcher] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-0000000000000011,0] java.net.SocketTimeoutException: Read timed out+
    +[2012-06-18T17:26:02.071+05:30] [AdminServer] [ERROR] [] [] [tid: PoolWatcher] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-0000000000000011,0] java.net.SocketTimeoutException: Read timed out++2012-06-18T17:27:00.496+05:30] [AdminServer] [ERROR] [] [] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] java.net.SocketTimeoutException: Read timed out+
    +[2012-06-18T17:27:00.496+05:30] [AdminServer] [ERROR] [] [] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] Failed to communicate with any of configured Access Server, ensure that it is up and running.+
    +[2012-06-18T17:27:00.700+05:30] [AdminServer] [NOTIFICATION] [OAMSSA-22005] [oracle.oam.diagnostic] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] Number of collectors registered: "3".+
    +[2012-06-18T17:27:00.700+05:30] [AdminServer] [NOTIFICATION] [OAMSSA-20032] [oracle.oam.user.identity.provider] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] Finished constructing mediator.+
    +[2012-06-18T17:27:00.700+05:30] [AdminServer] [NOTIFICATION] [OAMSSA-20002] [oracle.oam.user.identity.provider] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] Diagnostic Engine Initialized.+
    +[2012-06-18T17:27:00.715+05:30] [AdminServer] [NOTIFICATION] [] [oracle.oam.user.identity.provider] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b8352126b8c9e0f:1ec8524a:137ff4bc247:-8000-000000000000005b,0] [APP: oam_admin#11.1.1.3.0] resolved id store name : UserIdentityStore1+
    Anybody have any clue where is the issue and what is the fix required. Thanks for all your help.

    Hi,
    It seems there are some sort of communication laps try to enable Http tunneling on there for every individual server.
    You will find them under following option.
    Server >> <server name > >> Protocol >> General
    There you will find check box enable Tunneling.
    Regards,
    Kal

  • Weblogic admin server error.

    Hi Team,
    I am trying to started weblogic admin server from windows i am getting below error from admin server logs.
    but I am able to start weblogic from the command prompt.
    I verified classpath are same in command prompt and windows services and Node Manager also working fine from windows services.
    Please help me on this.it is urgent for me .
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000436> <Allocating 2 reader threads.>
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000446> <Native IO Enabled.>
    ####<Nov 14, 2012 8:31:27 PM GMT+05:30> <Info> <IIOP> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905287039> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288695> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288898> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090511> <The following exception has occurred:
    com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Error> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Notice> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Critical> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289023> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FAILED>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Error> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Info> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000236> <Stopping execute threads.>
    Thanks in advance.
    Regards,
    Ravi.

    Hi,
    Check this link :
    Re: myrealm error when start through node manager

Maybe you are looking for