WLI 2.0 Error

Any ideas why this will occur in WLS 6.0 (SP2) WLPI 2.0 (SP4) ...
<Sep 17, 2003 5:21:09 PM CDT> <Info> <EJB> <Exception from ejbStore:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: Protocol violation]
java.sql.SQLException: Protocol violation
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:803)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:549)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1311)
at
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:738)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1313
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1
353)
at
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:1805)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:322)
at weblogic.jdbcbase.jts.Statement.executeUpdate(Statement.java:345)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedState
mentImpl.java:55)
at
weblogic.jdbc.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatem
ent.java:55)
at
com.bea.wlpi.server.template.TemplateDefinitionRWBean_WebLogic_CMP_RDBMS.ejb
Store(TemplateDefinitionRWBean_WebLogic_CMP_RDBMS.java:1842)
at weblogic.ejb20.manager.DBManager.storeBean(DBManager.java:238)
at
weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:356)
at
weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java
:211)
at
weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInf
o.java:511)
at
weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCI
nfo.java:78)
at
weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(
ServerTransactionImpl.java:893)
at
weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerT
ransactionImpl.java:1229)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:168)
at
weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:201)
at
com.bea.wlpi.server.admin.AdminBeanEOImpl.lockTemplate(AdminBeanEOImpl.java:
1073)
at
com.bea.wlpi.server.admin.AdminBeanEOImpl_WLSkel.invoke(AdminBeanEOImpl_WLSk
el.java:1331)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
java:118)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
7)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120

Similar Messages

Error : Running Managed Servers in a cluster

Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick

Hi,
OPTION-A)
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
OPTION-B)
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 10:55 PM

I can't start admin wli wli10gR3MP1_linux32.bin

After installed wli when I tray start admin server I see this error:
<Aug 11, 2012 11:59:09 PM BRT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/wli/user_projects/domains/domain_wli/config/config.xml - Expected element 'password-validator@http://www.bea.com/ns/weblogic/90/security' instead of 'delegate-m-bean-authorization@http://www.bea.com/ns/weblogic/90/security' here in element realm@http://www.bea.com/ns/weblogic/920/domain>
<Aug 11, 2012 11:59:09 PM BRT> <Error> <WLI> <BEA-000000> <Error in startup class com.bea.wli.management.configfile.ConfigFileManager Method: initialize:
java.lang.Error: weblogic.management.provider.EditFailedException:
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.registerAllMBeans(CompatibilityMBeanServerService.java:270)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.access$100(CompatibilityMBeanServerService.java:41)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService$1$1.run(CompatibilityMBeanServerService.java:233)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
Truncated. see log file for complete stacktrace
weblogic.management.provider.EditFailedException:
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1706)
at weblogic.management.provider.internal.EditAccessImpl.getDomainBeanWithoutLock(EditAccessImpl.java:1155)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.registerAllMBeans(CompatibilityMBeanServerService.java:266)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.access$100(CompatibilityMBeanServerService.java:41)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService$1$1.run(CompatibilityMBeanServerService.java:233)
Truncated. see log file for complete stacktrace
java.io.IOException: [Management:141245]Schema Validation Error in /opt/wli/user_projects/domains/domain_wli/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false
at weblogic.management.provider.internal.EditAccessImpl.checkErrors(EditAccessImpl.java:2186)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromActive(EditAccessImpl.java:1725)
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1692)
at weblogic.management.provider.internal.EditAccessImpl.getDomainBeanWithoutLock(EditAccessImpl.java:1155)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.registerAllMBeans(CompatibilityMBeanServerService.java:266)
Truncated. see log file for complete stacktrace
>
<Aug 11, 2012 11:59:09 PM BRT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.lang.Error: weblogic.management.provider.EditFailedException:
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.registerAllMBeans(CompatibilityMBeanServerService.java:270)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.access$100(CompatibilityMBeanServerService.java:41)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService$1$1.run(CompatibilityMBeanServerService.java:233)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService$1.accessed(CompatibilityMBeanServerService.java:230)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.triggerAccessCallback(WLSMBeanServer.java:90)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.queryNames(WLSMBeanServer.java:235)
at weblogic.management.mbeanservers.compatibility.internal.RemoteMBeanServerImpl.queryNames(RemoteMBeanServerImpl.java:197)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.queryMBean(MBeanHomeImpl.java:143)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:167)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:160)
at weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:247)
at weblogic.management.mbeanservers.compatibility.internal.AdminMBeanHomeImpl.getRuntimeMBean(AdminMBeanHomeImpl.java:299)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:95)
at com.bea.wli.management.configfile.AdminRepAgent.<init>(AdminRepAgent.java:35)
at com.bea.wli.management.configfile.AdminConfigFileManager.<init>(AdminConfigFileManager.java:42)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:95)
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.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:280)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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 weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
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)
Caused by: weblogic.management.provider.EditFailedException:
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1706)
at weblogic.management.provider.internal.EditAccessImpl.getDomainBeanWithoutLock(EditAccessImpl.java:1155)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.registerAllMBeans(CompatibilityMBeanServerService.java:266)
... 49 more
Caused by: java.io.IOException: [Management:141245]Schema Validation Error in /opt/wli/user_projects/domains/domain_wli/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false
at weblogic.management.provider.internal.EditAccessImpl.checkErrors(EditAccessImpl.java:2186)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromActive(EditAccessImpl.java:1725)
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1692)
... 51 more
>
what I should do to solve this?

Hi Alex,
Pretty bad... Your installation probably messed with config.xml file...
If you have a backup, time to restore it...
Otherwise you can try and edit config.xml manually to try and start your server again at least... Search for delegate-m-bean-authorization inside the tag realm
Other option is to do what is suggesting on the log... Schema validation can be disabled by starting the server with the command line option:
-Dweblogic.configuration.schemaValidationEnabled=false
Hope this helps...
Cheers,
Vlad

Domain Created: Failed Restarting Managed Servers in a cluster

Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick

Hi Revanth,
The issue seems to be with the JMX URL value defined in the 'server URL' property.
Apparently I ran into the same issue as I was unable to access the Admin Server URL from the SMA.
Changing the Host and Port value properly resolved the issue for me.
Regards,
Anandraj

Error while building WLI application

I have a WLI application. I have a build script to build that project. I am building it using wlwBuild task. When I run the build script, I am getting this following error.
[wlwBuild] Error occurred during initialization of VM
[wlwBuild] java.lang.Error: java.lang.ClassNotFoundException: workshop.core.AppClassLoader
In the serverclasspath, I have the jar ${weblogic.home}/workshop/wlw-ide.jar. Though, I am getting this error. But when I set the classpath through command prompt (set classpath command) to point wlw-ide.jar, the build script is working fine. Its really strange and I could not figure out why it is not picking up the jar when it is in the serverclasspath of the wlwBuild task.
Is this error due to any other issue? Need your help.
Thanks in advance.
Elango

Hi,
Please have a look at this thread,
Re: Error in CompatibilityMode
Regards,
Saravanan K

Error in the worklist control[[WLI-Worklist:493028]Internal error: unexpect

Hi,
The exception bellow is being raised when I call the getTaskInfos from a worklist control.
Caused by: com.bea.control.ControlException: Error in the worklist control[[WLI-Worklist:493028]Internal error: unexpected ejb exception.]
     at com.bea.wli.worklist.control.TaskWorkerControlHelper.invoke(TaskWorkerControlHelper.java:721)
     at com.bea.control.TaskWorkerControlImpl.invoke(TaskWorkerControlImpl.jcs:48)
     at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
     at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
     at $Proxy89.getTaskInfos(Unknown Source)
     at com.orderEntry.status.OrderEntryStatusProcess.orderEntryWorkerGetTaskInfos(OrderEntryStatusProcess.jpd:390)
     at com.orderEntry.status.OrderEntryStatusProcess_wf$ImplControlSend19.invoke(OrderEntryStatusProcess_wf.java:134)
     at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
     ... 77 more
This is how IÂ´m making the call:
log.debub("tskName=" + tskName + " - Order#=" + myOrder);
tskSelector = new TaskSelector();
tskSelector.setTaskName(tskName, false);
tskSelector.setStateTypes(new StateType[]{StateType.ASSIGNED});
tskSelector.addProperty("OrderNumber", myOrder, false);
selectedTasks = orderEntryWorker.getTaskInfos(tskSelector);
where tskName and myOrder has valid values.
thanks.

SOA server installation and/or configuration seems to be the problem. I deployed the same compostie in a different "working" soa-server and it seems to work. But why the soa_server is bad is important to determine. Any suggestions welcome...
Edited by: user9138987 on Apr 8, 2010 10:17 AM

Oracle Error when starting the WLI server (samples domain) on Windows XP

I've installed WLI (SP2) on Windows XP and after Starting the Server (from the
"Start Server and Launch Examples" commands on the start menu) I get the following
Oracle error in the console:
I'm using WLI 7.0 with SP2 and Oracle 9i on Windows XP Home.
ORA-12154: TNS:could not resolve service name
Any ideas?

Hi Peter,
Based on the error messages it looks like this might be a Windows 7 security issue, which would be why it doesn't occur on XP since security is handled differently in that OS. Have you gone into dcomcnfg.exe and checked the DCOM permissions as described in the error message?

Error while starting WLI server on Solaris Machine

Hi
While starting WLI server using startWLI.sh command I am getting following error.
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Server:-(
Please help me for rectifying this error.
Thanking you.
Amol

Hi
While starting WLI server using startWLI.sh command I am getting following error.
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Server:-(
Please help me for rectifying this error.
Thanking you.
Amol

Error: Error WLI-Worklist

FOllowing error is logged in weblogic server( 8.1 workshop).
<Feb 17, 2004 10:53:16 AM GMT+05:30> <Error> <WLI-Worklist> <BEA-610066> <You
mu
st be in the worklist admin role or task owner or the task claimant or in the
as
signee list to perform this operation.>
It does not specify task. it logs this error frequently. even when there is no
request from browser.
Pls help.
Thanks in advance.

Karen
Please ensure that wlpi-worklist.jar is in your classpath when you start
weblogic
Tony
"Karen Law" <[email protected]> wrote in message
news:[email protected]..
I am using Weblogic 6.1 with WLI 2.1. I have just deployed worklist.war
which is a JSP worklist client. I can access the first login page. But
when I insert username, password and submit, an error comes out as
shown:
C:\bea61\wlintegration2.1\config\samples\applications\.wlnotdelete\WEB-INF\_
tmp_war_myserver_myserver_worklist\jsp_servlet\_worklist\__worklist.java:24:
package com.bea.wlpi.server.worklist does not exist
probably occurred due to an error in /worklist/worklist.jsp line 11:
" session="true" %>
C:\bea61\wlintegration2.1\config\samples\applications\.wlnotdelete\WEB-INF\_
tmp_war_myserver_myserver_worklist\jsp_servlet\_worklist\__worklist.java:25:
package com.bea.wlpi.server.principal does not exist
probably occurred due to an error in /worklist/worklist.jsp line 11:
" session="true" %>
I use the default "samples" domain. And I don't know why it can't
include com.bea.wlpi.server.worklist and com.bea.wlpi.server.principal.
Anyone can help? Thx!
Regards,
Karen

WLI-Core:489214: jpd not found error on bea weblogic 8.1 sp4

Hi,
I am developing a website using BEA Workshow 8.1 SP4 deployed on Integration single managed server cluster domain. I have some stateless jpd to process the stuff in asynchronized mode.
one in a week I am geting the following error:
[WLI-Core:489214]ProcessControl invocation failed[Service at /easWeb/com/pfizer/eas/marketing/processes/CreateDocCopies.jpd not found]
caused by: : com.bea.wlw.runtime.core.dispatcher.ServiceHandleException: Service at /easWeb/com/pfizer/eas/marketing/processes/CreateDocCopies.jpd not found
If I restart the managed server then this problem is resolved.
How can I fix this problem. Everything like queues, jsm server, connection pool is configured properly.
I can provide info about domain configuration if somebody needs.
Thanks,
Utkarsh

Hello
I'm getting the same error using BEA Workshop 8.1 SP6. Could you resolve this issue?
please answer me by email. [email protected]
Thank you
Leandro

WLI V2.1 install error: WebLogic Server 6.1 SP1 is not installed.

Hi,
FYI
I installed WLS 6.1 and then Service Pack 1 (separately).
I then installed WLI V2.1 and got the error.
WebLogic Server 6.1 SP1 is not installed.
This is on Windows NT.
The problem was due to the registry.xml file being empty of content. Thus the
install did not know where the WLS 6.1 SP1 was. The Service Pack 1 for WLS 6.1
emptied this file, incorrectly.
I think if you download and install WLS 6.1 Service Pack 1 in one install and
not separately the emptying of the registry.xml does not occur.
To get around the problem, I got BEa Support to send me a registry.xml and I edited
it to be my own machine and BEA_HOME directory. The WLI V2.1 install then worked.(Not
the safest solution but it worked!)
Regards,
Kathryn

Hi ,
Installed OBIA & related components in the following Order
OS: Windows-2008 R2
OBIA: 11.1.17.1
1. Oracle Database 11gR2
1.2 Installed OBIEE 11g(11.1.1.7.0)
2. Oracle Fusion Middleware RCU11g(11.1.1.7.0)
3. ODI 11g(11.1.1.7.0) Using JDK 7 Update 21 for 64 Bits(ie jdk-7u21-windows-x64)
4. Applied RCU for Oracle BI Application 11.1.1.7.1)
### Till now No Error, all the stages completed Successful.
5. Installing Oracle BI Application(11.1.1.7.1) using JDK 7 Update 21 for 64 Bits(ie jdk-7u21-windows-x64)
The installer running for all most 3 Hours, No Progress in the (Showing 0% Progress) and Copying.....
We have doubted JDK/JRE version, So Cancelled installation.
Without uninstalling the JDK7, We installed JDK 6 with 45 Updates(ie.jdk-6u45-windows-i586) into different folder.
Attempted to re-install the OBA 11g by specifying the JDK6 update 45 Path._
We get the error error INST-07515: oracle.bi.bishiphome is not found.
Right now, we are struck, no idea how to proceed further.
Forum support is required to resolve this hurdle.
Thanks in advance.
Regards,
Basavanagowda M
Edited by: BG on May 29, 2013 5:00 AM

Build Errors for Imported WLI 10.3.0 projects

I've upgraded WLI 10.3.0 to WLI 10.3.1 using the upgrade installer on my Windows machine. I then created a new domain using the current WL Server 10.3.0 and WLI 10.3.1. I then imported Oracle's Tutorial Worklist application projects into a new workspace. This WLI application was originally developed with WLI 10.3.0 and was builiding/working correctly in the old WLS 10.3.0/WLI 10.3.0 environment. I get the following build errors now:
- The project was not built since its build path is incomplete. Cannot find the class file for java.io.Serializable. Fix the build path then try building this project          Loan_Web
- The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project          LoanUtil
- The type java.io.Serializable cannot be resolved. It is indirectly referenced from required .class files     Loan_Web/src/process     MyControl.java     line 1
- CHKJ3010W: Welcome Files cannot begin or end with a /.     Loan_Web/WebContent/WEB-INF     web.xml     org.eclipse.jst.j2ee.webapplication.internal.impl.WelcomeFileImpl@5b5bec (welcomeFile: /user.portal)
The source files don't even appear under the projects in the workspace now. How can I fix this? Shouldn't importing the WLI 10.3.0 application into WLI 10.3.1 be transparent?
Thanks.

Hi,
Does you check for the build path for this issue.
Might this would be the problem with default JRE internal.
Please check build java path and correct the JRE subsystem it will solve your issue.
Regards,
Kal.

Error marking transaction for rollback: java.lang.IllegalStateException in WLI 6.1 SP3

Hi,
The following exception occurs, when the workflow was waiting after it has made
a synchronous call to an external system through WTC Interface.
I had read Rob's comments earlier for WLI 6.1 SP1 on this exception that there
would be a fix available for it in the next minor release. For your information,
I had got this exception in WLI 6.1 SP3. Is still EJB Container's timeout excels
the JTA's timeout? Can anybody help me out to find a fix for this problem?
Thanks in Advance,
Regards
Jegadeesan.
The Stack Trace is given below :
<Error marking transaction for rollback: java.lang.IllegalStateException: Cannot
mark the transaction for rollback. xid=4362:5b4c62b47adcc632, status=Rolled back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 31 seconds
Xid=4362:5b4c62b47adcc632(6932052),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[ecwli001+admin_ecwli001]=(state=active),properties=({weblogic.jdbc=t3://147.149.116.70:50101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+,
Resources={})],CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+)]>
java.lang.IllegalStateException: Cannot mark the transaction for rollback. xid=4362:5b4c62b47adcc632,
status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed out after 31 seconds
Xid=4362:5b4c62b47adcc632(6932052),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[ecwli001+admin_ecwli001]=(state=active),properties=({weblogic.jdbc=t3://147.149.116.70:50101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+,
Resources={})],CoordinatorURL=admin_ecwli001+147.149.116.70:50101+ecwli001+)]
 at weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(TransactionImpl.java:1492)
 at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:466)
 at weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.java:255)
 at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:215)
 at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
 at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
 at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
 at com.bea.wlpi.server.principal.WLPIPrincipalBean_u7lmf4_EOImpl.getOrganizationInfo(WLPIPrincipalBean_u7lmf4_EOImpl.java:463)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getBusinessCalendarProcessor(Unknown
Source)
 at com.bea.wlpi.server.workflow.Timer.dateAdd(Unknown Source)
 at com.bea.wlpi.server.workflow.action.ActionTimedEvent.getScheduleTimestamp(Unknown
Source)
 at com.bea.wlpi.server.workflow.action.ActionTimedEvent.execute(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
 at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Decision.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Decision.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
 at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
 at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
 at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
 at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
 at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
 at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
 at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
 at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
 at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
 at com.bea.wlpi.server.workflow.Start.activate(Unknown Source)
 at com.bea.wlpi.server.workflow.Workflow.start(Unknown Source)
 at com.bea.wlpi.server.workflow.Workflow.instantiate(Unknown Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Unknown
Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithErrorHandling(Unknown
Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Unknown
Source)
 at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.instantiate(WorkflowProcessorBean_h7kt4j_EOImpl.java:692)
 at com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(Unknown Source)
 at com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(Unknown Source)
 at com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(Unknown Source)
 at weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
 at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
 at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
 at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

You could change the transaction timeout value, but I'd re-examine the
application and see if the transaction times could be reduced some.
29 seconds seems like a long time.

Catch Error message from WLI Process

Hi,
I have a big application developed with WLI and I wanna know if there is a way to recive error messagem from this application throught the ALSB. The ALSB call a WLI jpd procces by BussinesProxy.
For example, when occurs a database error into JPD proccess, I want to receive this error and log it or pass it to another application to nofify error and so one.
All the procces in my WLI application were developed with ClientRequestWithReturn and I am thinking in put in this return one tag called <ERROR>ORACLE-0002 - JDBC ERROR bla bla</ERROR> in case off error and <ERROR>FALSE</ERROR> when everythig went OK at the WLI Application.
Is there another way to do this?
Thanks!
Edited by denimar at 05/12/2008 2:33 PM

Hi,
Try throwing an RPC SoapFaultException from your JPD. That should make it back to ALSB as an error and does not count as "Unhandled Exception" by WLI. Although SoapFaultExceptions are a pain to create.
Otherwise passing an error element back in the body has worked fine for me in the past.

WLI error for SSL

Hi,
I am trying to confgure SSL for WLS. In Admin console, I chose custom keystores
entred my keystore names, passphrases, etc in the form. When I restart WLS, it
gives the following error in WLI section.
[java.lang.RuntimeException: java.io.FileNotFoundException: C:\BE632A~1\domains\ABCPLA~1\ABCDevTrustKeyStore
(The system can
not find the file specified)]]
This error is not letting WLS start. How do I get around this?
John

You can replace the config.xml with the last config.xml.booted, start the server,
and fix the configuration, or modify the config.xml by hand: find the reference
to the ABCDevTrustKeyStore and replace it with the correct file name.
Pavel.
"John Hryn" <[email protected]> wrote:
>
Hi,
I am trying to confgure SSL for WLS. In Admin console, I chose custom
keystores
entred my keystore names, passphrases, etc in the form. When I restart
WLS, it
gives the following error in WLI section.
[java.lang.RuntimeException: java.io.FileNotFoundException: C:\BE632A~1\domains\ABCPLA~1\ABCDevTrustKeyStore
(The system can
not find the file specified)]]
This error is not letting WLS start. How do I get around this?
John

WLI 2.0 Error

Similar Messages

Maybe you are looking for