WLI 8.1 SP2

Hi,
I need to do message sequencing in WLI 8.1 SP 2, is there any nice feature that
WLI provides for managing this or do I have to do it manually? If manual, has
anyone have some examples for me?
Thank you,
Wickes

Hello,
I was wondering if you ever figured out how to do this. I'm trying to work through the same issue. If you figured out a way to do it, could you please tell me how?
Thank you, Matt

Similar Messages

WLI 6.1 SP4 with WLI 2.1 SP2

We would like to install Weblogic 6.1 SP4 with Weblogic Process Integration 2.1
SP2 and we have read on the papers of WLI 2.1 SP2, that it supports WLS 6.1 SP3.
Is it possible to install WLI 2.1 SP2 with WLS 6.1 SP4?
If the answer is "yes", please let me know what kind of problems could happen
with the maps and applications that are already created on WLS 6.1 SP2 and WLI
2.1 SP1.
Tks.
Edy

WLS 6.1 requires JDK 1.3.1
Josh Shi wrote:
I try to run WebLogic 6.1 SP1 with JDK 1.2.2_7a with License exception: license signature validation error. Could it be done ? If so, how ?
Thanks a lot.
Josh

WLI 2.1 sp2 with WLS 6.1 sp3

Hi,
I am unable to start the integration server WLI 2.1 sp2 with WLS 6.1 sp3.
It gives the following errors:
1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error deploying application
wlpi-ejb.jar:
Unable to deploy EJB: Audit from wlpi-ejb.jar:
There is a mismatch between the bean code and generated
code.com.bea.wlpi.Audit . Please rerun ejbc on the bean code.The error was
java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
InfoImpl.java:651)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
DrivenBeanInfoImpl.java:723)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:823)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360) at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy46.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy68.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer> <Failed to
invoke startup class "TimeProcessor", java.lang.Exception: TimeProcessor
startup failed! Check arguments.>
3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception during
invocation from home:
[email protected]ffc94 threw
exception: java.lang.IllegalStateException
java.lang.IllegalStateException
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown Source)
at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
agerCfgBean_gebmxi_EOImpl.java:1428)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
Unknown Source) at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy109.init(Unknown Source)
at com.bea.wlpi.server.initlistener.InitListenerBean.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)
>
Unable to initialize WebLogic Integration - BPM Server:
java.rmi.RemoteException: EJB Exception: ; nested exception is:
java.lang.IllegalStateException
java.lang.IllegalStateException
<<no stack trace available>>
Am I missing something ????? Any help is appreciated.
Thanks in advance.
Sangeetha.

Jim,
I tried the new upgrade installer (in Windows this time),
I din't get problem no 3.
But 2 which seemed to work before after changing the configuration file
fails. The server automatically shuts down with the following message:
<Aug 6, 2002 4:33:33 PM EDT> <Emergency> <WebLogicServer> <Server shutdown
due to fatal exception: w
eblogic.t3.srvr.FatalStartupException: Can't start server due to startup
class failure TimeProcessor
- with nested exception:
[java.lang.Exception: TimeProcessor startup failed! Check arguments.]>
<Aug 6, 2002 4:33:33 PM EDT> <Info> <WebLogicServer> <Shutdown has
completed.>
Problem no 1 still persists.
I am also attaching my configuration file.
Any help is much appreciated.
Thanks,
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
The Upgrade Installer should be available now on the support downloads.
-Jim
Sangeetha Raghavan wrote:
Hi David,
I am unable to download the file thru' the ftpserver.
The download got cancelled with a message like
'connection closed by the remote server'.
Please let me know when it is available at the support downloads.
Thanks.
Sangeetha.
"R J David Burke" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha
My apologies for the inconvenience you are experiencing. We havediscovered
a problem with the website for the WLI 2.1 SP2 upgrade installer,providing
an incorrect file.
We are working to correct this immediately. In the mean time, the
proper
file can be accessed from our FTP server. The details are:
server: ftpsupport.bea.com
user: support
password: xuquoov (expires on Sunday)
path: /pub/wli21sp2
files: wlintegration21sp2_upgrade_win.exe - upgrade installer for
Windows
wlintegration21sp2_upgrade_unix.zip - upgrade installerfor
Unix-based platforms
For security purposes, directory listings are not enabled, so you willneed
to specify the file by name.
Regards, David
"Sangeetha Raghavan" <[email protected]> wrote in message
news:[email protected]...
Hi Jim,
I upgraded from WLI 2.1 sp1 to WLI 2.1 sp2.
I am not running in a clustered environment.
Attached is my configutaion file.
Thanks.
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
Just a few questions...
Did you upgrade or migrate? From which version did you
upgrade/migrate?
Are
you running in a clustered environment? Can you send your
config.xml?
>>>>>
Thanks,
Jim
"Sangeetha.R" wrote:
Hi Jim,
I am using Linux and Oracle 8i
I made the changes in the config.xml and it did solve problem 2.
Problem 1 and 3 still persists.
Thanks in Advance.
Sangeetha.
"Jim Hinkey" <[email protected]> wrote in message
news:[email protected]...
Hi Sangeetha,
Can you tell me what OS and DB you are using? Also, have you
implemented
the
changes talked about in Release Notes section "Time Services
Changes
in
BPM"? I
think that is causing problem 2.
Thanks,
Jim
"Sangeetha.R" wrote:
Hi,
I am unable to start the integration server WLI 2.1 sp2 with
WLS
6.1
sp3.
It gives the following errors:
1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error
deploying
application
wlpi-ejb.jar:
Unable to deploy EJB: Audit from wlpi-ejb.jar:
There is a mismatch between the bean code and generated
code.com.bea.wlpi.Audit . Please rerun ejbc on the bean
code.The
error
was
java.lang.NoSuchFieldException
at java.lang.Class.getField0(Native Method)
at java.lang.Class.getDeclaredField(Class.java:1113)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
InfoImpl.java:651)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
>>>>
DrivenBeanInfoImpl.java:723)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:823)
atweblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at
weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
atweblogic.j2ee.Application.addComponent(Application.java:170)
atweblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360) at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
>>>>>>>>
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy46.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360) at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy68.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer>
<Failed
to
invoke startup class "TimeProcessor", java.lang.Exception:TimeProcessor
startup failed! Check arguments.>
>
3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception
during
invocation from home:
[email protected]ffc94
threw
exception: java.lang.IllegalStateException
java.lang.IllegalStateException
at
com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown
Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown
Source)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
agerCfgBean_gebmxi_EOImpl.java:1428)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
Unknown Source) at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
at
weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
atweblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:262)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
atweblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy109.init(Unknown Source)
atcom.bea.wlpi.server.initlistener.InitListenerBean.onMessage(Unknown
Source)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
atweblogic.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)
atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>>>>>>>>>
Unable to initialize WebLogic Integration - BPM Server:
java.rmi.RemoteException: EJB Exception: ; nested exceptionis:
java.lang.IllegalStateException
java.lang.IllegalStateException
<<no stack trace available>>--------------------------------------------------------------------------
>
Am I missing something ????? Any help is appreciated.
Thanks in advance.
Sangeetha.
[config.xml]

WLI 7.0 SP2 on Windows XP

Hi
I am trying to create a new domain and a DB on windows XP with Weblogic Integration
7.0 SP2.
The domain creation goes fine , but when I try to create a DB , I get the following
error in switchDB.cmd
Please respond.
Thanks
Manish
-------------------------------------- begin log -------------------------------------------
Buildfile: d:\bea\user_projects\ABCSys\scripts\SwitchDB.xml
java.io.IOException: CreateProcess: command.com /c set error=3
     at java.lang.Win32Process.create(Native Method)
     at java.lang.Win32Process.<init>(Win32Process.java:61)
     at java.lang.Runtime.execInternal(Native Method)
     at java.lang.Runtime.exec(Runtime.java:546)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:564)
     at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:384)
     at org.apache.tools.ant.taskdefs.Execute.getProcEnvironment(Execute.java:162)
     at org.apache.tools.ant.taskdefs.Property.loadEnvironment(Property.java:250)
     at org.apache.tools.ant.taskdefs.Property.execute(Property.java:183)
     at org.apache.tools.ant.ProjectHelper$TaskHandler.finished(ProjectHelper.java:489)
     at org.apache.tools.ant.ProjectHelper$AbstractHandler.endElement(ProjectHelper.java:204)
     at org.xml.sax.helpers.XMLReaderAdapter.endElement(XMLReaderAdapter.java:347)
     at weblogic.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1411)
     at weblogic.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1613)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1841)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1207)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
     at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
     at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
     at weblogic.xml.jaxp.WebLogicParser.parse(WebLogicParser.java:67)
     at weblogic.xml.jaxp.RegistryParser.parse(RegistryParser.java:144)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:326)
     at org.apache.tools.ant.ProjectHelper.parse(ProjectHelper.java:117)
     at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:85)
     at org.apache.tools.ant.Main.runBuild(Main.java:439)
     at org.apache.tools.ant.Main.start(Main.java:153)
     at org.apache.tools.ant.Main.main(Main.java:176)
all:
Config.xml:
BUILD FAILED
d:\bea\user_projects\ABCSys\scripts\SwitchDB.xml:23: java.io.FileNotFoundException:
D:\bea\user_projects\ABCSys\scripts\${env.WLI_HOME}\lib\scripts\SwitchDB.xml (The
system cannot find the path specified)
Total time: 1 second
------------------------------------------- end log----------------------------------------------------

Is Weblogic 7.0 supported on Windows XP ? Is it reliable, etc. ? I was          planning to use it on a laptop running windows XP.
          If you're just developing, then I think you'll be fine.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Amit Pradhan" <[email protected]> wrote in message
          news:3d93920d$[email protected]..
          >

Exception in WLPI after upgrading to WLI 2.0 SP4 from SP2

Environment is :
WLS 6.0 SP2 and WLI 2.0 SP4 on Solaris 2.8.
We get the following exception when the server starts up and tries to deploy
wlpi-mdb-ejb.jar. This started only after upgrading to WLI 2.0 SP4 from WLI
2.0 SP2.
Any help will be highly appreciated.
####<Feb 12, 2002 6:08:49 PM PST> <Info> <J2EE> <spruce> <edevServer31>
<main> <system> <> <160003> <Deployed : wlpi-master-ej
b.jar>
####<Feb 12, 2002 6:08:49 PM PST> <Info> <EJB> <spruce> <edevServer31>
<main> <system> <> <010008> <EJB Deploying file: wlpi-m
db-ejb.jar>
####<Feb 12, 2002 6:08:50 PM PST> <Info> <EJB> <spruce> <edevServer31>
<main> <system> <> <010052> <An exception occurred whil
e creating the freepool.>
java.rmi.RemoteException: Error in the bean's constructor : ; nested
exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException:
java.lang.ExceptionInInitializerError:
weblogic.ejb20.internal.MethodPermissionEx
ception: Security violation: insufficient permission to access method
at
weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:91)
at
weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
:55)
at
com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.getState(PluginManager
CfgBeanEOImpl.java:1411)
at
com.bea.wlpi.server.plugin.PluginManagerImpl.refreshState(PluginManagerImpl.
java:187)
at
com.bea.wlpi.server.plugin.PluginManagerImpl.<init>(PluginManagerImpl.java:1
72)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.<clinit>(EventProcessor.ja
va:37)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.ejbCreate(EventListenerB
ean.java:47)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDrivenEJBHome
.java:297)
at
weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:98)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:100)
at weblogic.ejb20.pool.Pool.<init>(Pool.java:74)
at weblogic.ejb20.pool.EntityPool.<init>(EntityPool.java:34)
at
weblogic.ejb20.pool.MessageDrivenPool.<init>(MessageDrivenPool.java:43)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getPool(MessageDrivenBeanI
nfoImpl.java:336)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
foImpl.java:403)
at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:133)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:327)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:277)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:232)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:192)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy0.updateDeployments(Unknown Source)
Regards,
Adarsh

Hi Feng,
In 2.0.10, we strictly evualuate the xpath queries:
1. According to bpel spec 1.1 section 14.3, xpath queries should be absolute queries. you need to change query="//sessionID" to /cstaPrefix:iRequest/cstaPrefix:sessionID.
2.If your xml documents are namespace aware then you must use qualified xpath queries. in your case you have to add prefix to your query like "/tns:disconnect_cstaRequest/tns:input. So please change the unqualified query //sessionId to qualified one by just prefixing. (Same rule goes for /xmlMessage query, please change all your queries to have prefix.)
Here is the link to xpath spec which explains this in more detail.
http://www.w3.org/TR/xpath#node-tests
A QName in the node test is expanded into an expanded-name using the namespace
declarations from the expression context. This is the same way expansion is
done for element type names in start and end-tags except that the default
namespace declared with xmlns is not used: if the QName does not have a
prefix, then the namespace URI is null (this is the same way attribute names
are expanded). It is an error if the QName has a prefix for which there is no
namespace declaration in the expression context.

How to achieve process rework in WLI 8.1?

Hi,
I am using WLI 8.1 SP2. I am trying to model a workflow application using WLI.
My workflow requires to have rework functionality i.e at any step in the workflow,
the user might like to rework the process starting from any of the completed steps.
For e.g, lets say my process has 5 tasks T1,T2,T3,T4 and T5. Currently lets say
T1,T2,T3 are complete and T4 has started. Now the user wants to re-enter the process
again from T2. So now T2, T3 will be reworked and completed, after which T4 will
be created again. I would like to stay within the same process instance rather
than starting a new process instance. Is there any way of designing this as a
generic solution?( i.e you can re-enter at any step). Can we modify/move the execution
point within WLI process by any way?

You should design the model itself the way that it can move back to another
step. That essentially means that you have to make a loop of some kind to be
able to return to an earlier point in the process flow. The most versatile
solution in my opinion is to make a loop, and make an event-choice inside
the loop. Make control receives for each task completion (and possibly other
task termination callbacks as well) as a separate branch in the
event-choice, and maintain the actual state you are in the process flow in a
variable in the workflow.
You should check at each control receive that you are in the correct state
to get that control receive, if you are then carry out the appropriate
operations including possibly creating new worklist entries, and change the
actual state variable in which you keep track of the actual state to reflect
the new state of the process flow.
Regards,
Robert varga
"Arun" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am using WLI 8.1 SP2. I am trying to model a workflow application usingWLI.
My workflow requires to have rework functionality i.e at any step in theworkflow,
the user might like to rework the process starting from any of thecompleted steps.
For e.g, lets say my process has 5 tasks T1,T2,T3,T4 and T5. Currentlylets say
T1,T2,T3 are complete and T4 has started. Now the user wants to re-enterthe process
again from T2. So now T2, T3 will be reworked and completed, after whichT4 will
be created again. I would like to stay within the same process instancerather
than starting a new process instance. Is there any way of designing thisas a
generic solution?( i.e you can re-enter at any step). Can we modify/movethe execution
point within WLI process by any way?

How to extend mfl type in wli 8.1.5

in the older version it is possible to provide new datatype ifor MFL data transformation.
I am looking to do the same thing in wli 8.1.5 but was unable to find in the documentation the accurate way to do it.
Any help
<b>thanks a lot</b>

You should design the model itself the way that it can move back to another
step. That essentially means that you have to make a loop of some kind to be
able to return to an earlier point in the process flow. The most versatile
solution in my opinion is to make a loop, and make an event-choice inside
the loop. Make control receives for each task completion (and possibly other
task termination callbacks as well) as a separate branch in the
event-choice, and maintain the actual state you are in the process flow in a
variable in the workflow.
You should check at each control receive that you are in the correct state
to get that control receive, if you are then carry out the appropriate
operations including possibly creating new worklist entries, and change the
actual state variable in which you keep track of the actual state to reflect
the new state of the process flow.
Regards,
Robert varga
"Arun" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am using WLI 8.1 SP2. I am trying to model a workflow application usingWLI.
My workflow requires to have rework functionality i.e at any step in theworkflow,
the user might like to rework the process starting from any of thecompleted steps.
For e.g, lets say my process has 5 tasks T1,T2,T3,T4 and T5. Currentlylets say
T1,T2,T3 are complete and T4 has started. Now the user wants to re-enterthe process
again from T2. So now T2, T3 will be reworked and completed, after whichT4 will
be created again. I would like to stay within the same process instancerather
than starting a new process instance. Is there any way of designing thisas a
generic solution?( i.e you can re-enter at any step). Can we modify/movethe execution
point within WLI process by any way?

WLI 2.1 for Solaris

Will WLI 2.1 for Solaris work on Linux systems (specifically Red Hat Linux
7.2) ? Apparently there is no Linux Certified version in the downloads
page.
Regards,
Adarsh

I found WLI sp2.
Thanks.
Sangeetha
"Sangeetha.R" <[email protected]> wrote in message
news:[email protected]..
Thanks Chris.
But, I couldn't find this in the support downloads too.
Could you let me know, from where can I download this?
Thanks,
Sangeetha
"Chris Stead" <[email protected]> wrote in message
news:[email protected]..
Sangeetha,
WLI 2.1 SP2 will go live tomorrow (7/31) and is compatible with WLS 6.1SP3.
Cheers,
Chris
Sangeetha.R wrote:
Is there a service pack for WLI 2.1 that is compatible with WLS 6.1
sp3
Thanks in advance.
Sangeetha

WLI 2.1 setting all workflows to Suspended Mode

Hi,
Twice now I have seen WLI set all instantiated workflows to a suspended state. Worse,
I can continue to create workflows (via JMS Events), but they are also set to a suspended
state. This normally occurs when a database exception has been raised on a WLI table
or when someone was dynamically changing the active workflow template while one was
being instantiated.
Has anyone seen this happen? If so, what needs to be done to get WLI out of this
mode of creating workflows in a suspended state?
We are using WLI 2.1 SP1 and WLS 6.1 SP2.
Thanks.
--Todd

BEA has provided a fix for this problem with WLI 2.1 SP1 rolling patch 3. You will
need to contact BEA to get this patch.
--Todd
"Todd Dolan" <[email protected]> wrote:
>
After contacting BEA, they have confirmed that the suspended workflow problem
is a
bug and something that will be fixed with WLI 2.1 SP2. However, they did
not have
a date as to the release of that service pack.
Louise -- Thanks for pointing me in the right direction.
--Todd
"Louise Scully" <[email protected]> wrote:
Hi Todd,
We were getting the suspended workflows problem a couple of months ago.
We recieved
a fix for this in a service patch, but we were running WLPI 2.0, so I would
assume
that the fix we received would be part of the service pack for 2.1
To get WLPI out of this behaviour once it happens, try removing all the
instances
which are suspended by running this SQL:
delete from eventwatch where instanceid in (select instanceid from instance
where
state=0);
delete from instance where state=0;
Hope this helps,
Louise
"Todd Dolan" <[email protected]> wrote:
Hi,
Twice now I have seen WLI set all instantiated workflows to a suspended
state. Worse,
I can continue to create workflows (via JMS Events), but they are alsoset
to a suspended
state. This normally occurs when a database exception has been raisedon
a WLI table
or when someone was dynamically changing the active workflow template
while
one was
being instantiated.
Has anyone seen this happen? If so, what needs to be done to get WLIout
of this
mode of creating workflows in a suspended state?
We are using WLI 2.1 SP1 and WLS 6.1 SP2.
Thanks.
--Todd

WLI Login

I've just installed WLI 2.1 SP2. No issues in the install, but when I start Studio and try to log in, I get:
"Failed to logon to WebLogic integrations because of error below:
please make sure your username,password and server URL are all correct"
I am sure I am using the correct info.
Thanks

You can register to log into EIM server by following the URI : https://try.contivo.net/cws/Cws?html_template=userLogin.html&bundler_name=BEA&offering_type=EVALUATION&companyName=null
Cole <[email protected]> wrote:
I downloaded the Contivo "analyst.exe" program in "e-docs.bea.com" site.
As I remembered the information of id and password through this web
site, but I can't remember it now. So I can't login the EIM Server to
access WLI repository.
Contivo EIM Server Login information
- Hostname : try.contivo.net
- Organization : BEA Corporate
- ID : ?
- PWD : ?
I hope someone help me.
Thanks for your answers in advance.
Cole

Building /deploying sample plugin in WLI 2.1 and WLS 6.1

I'm running WLI 2.1 (service pack 1) and WLS 6.1. I'm trying to build and deploy
the sample plugin (sampleplugin-ejb.jar) but have had numerous problems.
Specifically, though there are no errors and the WLS admin console tells me the
plugin is deployed I cannot actually see any of the plugin actions etc. on the
WLI Studio and am told that the plugin is not loaded when I open the template
definitions.
I've even resorted to deploying the version of the plugin bundled in WLI_HOME\lib\sampleplugin-ejb.jar
i.e. one I didn't build myself but again, although there are no errors, the plugin
does not seem to be correctly loaded.
In order to get this far I've had to include the plugin jar file in the server
CLASSPATH. Otherwise I get an 'java.lang.NoClassDefFoundError: com/bea/wlpi/common/plugin/PluginObject'
error. I know I shouldn't have to include the EJB in the CLASSPATH but it seems
to resolve this error. Perhaps this is contributing to the other problem ????
Any help gratefully appreciated. Has anyone successfully built and deployed the
sample plugin to WLI 2.1/ WLS 6.1 ?

I found WLI sp2.
Thanks.
Sangeetha
"Sangeetha.R" <[email protected]> wrote in message
news:[email protected]..
Thanks Chris.
But, I couldn't find this in the support downloads too.
Could you let me know, from where can I download this?
Thanks,
Sangeetha
"Chris Stead" <[email protected]> wrote in message
news:[email protected]..
Sangeetha,
WLI 2.1 SP2 will go live tomorrow (7/31) and is compatible with WLS 6.1SP3.
Cheers,
Chris
Sangeetha.R wrote:
Is there a service pack for WLI 2.1 that is compatible with WLS 6.1
sp3
Thanks in advance.
Sangeetha

WLI 2.1 for WLS 6.1 sp3

Is there a service pack for WLI 2.1 that is compatible with WLS 6.1 sp3 ?
Thanks in advance.
Sangeetha

Sangeetha,
Did you ever get a reply to this question? I can't upgrade
WLS 6.1 SP3 or SP4 because of WLI 2.1 SP2
--Todd Dolan
"Sangeetha.R" <[email protected]> wrote:
Is there a service pack for WLI 2.1 that is compatible with WLS 6.1
sp3 ?
Thanks in advance.
Sangeetha

Migration from WLI2.0 to WLI2.1 - problems and solutions

We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
     -v (No such file or directory)
     null
     java.lang.NullPointerException
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:120)
     at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
     at com.bea.eci.migration.Migrate.main(Migrate.java:73)
     java.lang.NullPointerException
     at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
     ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete

Pete,
Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
Pete Edwards wrote:
We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
-v (No such file or directory)
null
java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
at com.bea.eci.migration.Migrate.main(Migrate.java:73)
java.lang.NullPointerException
at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
". $WLI_HOME/bin/checkdomain" # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete--
Developer Relations Engineer
BEA Support

Problem creating user in RDBMS realm Using com.bea.wlpi.rdbmsrealm.RDBMSRealm

Hi,
I am currently using WLI 2.0 SP2 installation. Here is a very unusual thing I
noticed. Can somebody tell me what is going on ???
1 : I have set up the security realm as indicated in the config.xml file. As far
as I understand, the caching realm entry has attribute pointing to the wlpiRDBMSRealm,
which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
2: I start the server, open the WLS console, and create a new user through the
console. I get no error message and it seems to work fine. ( I also click on the
save it to database link, and it returns with msg that cache is refreshed ).
3: I see an entry in the fileRealm.properties file, but no record is inserted
in the WLSUSER table in the database.
Since the RDBMS realm (from WLI distribution) is defined as basic
realm implementation, should it not insert entry into the database, instead of
the file realm.
Is this a general problem ( any RDBMS realm ) or is it specific to the WLI ?
Is there anything that I have not configured here that is causing this behavior
Is it just refreshing the cache instead of inserting record in DB ?
Why should it insert entry into fileRealm.properties ?
Thanks,
Girish
[noaa1.zip]

Hi,
I turned on the caching realm through the WLS Console, (Security).
After this I get a very unusual error, which seems to be comming
from the RDBMS implementation class (from WLI 2.0 SP2 distribution).
Here is the msg that I get while WLS server boots (the WLS server boots ok, but
WLPI does not initialize) ....
Unable to initialize WebLogic Process Integrator:
SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
autocommit is OFF.
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.j_(Unknown Source)
at c8e.k.n.checkIfClosed(Unknown Source)
at c8e.k.n.movePosition(Unknown Source)
at c8e.k.n.movePosition(Unknown Source)
at c8e.k.n.next(Unknown Source)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.getGroup(RDBMSDelegate.java:425)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:235)
at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.Kernel.execute(Kernel.java:250)
at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
<Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <WebLogic Server started>
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
com.bea.wlpi.rdbmsrealm.RDBMSException: caught SQL exception - with nested exception:
[SQL Exception: ResultSet not open, operation 'next' not permitted. Verify that
autocommit is OFF.]
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getGroup(RDBMSRealm.java:242)
<Aug 22, 2001 11:56:01 AM MDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7101>
at weblogic.security.acl.CachingRealm.getGroup(CachingRealm.java:1120)
at weblogic.ejb20.deployer.SecurityRoleMapping.lookupPrincipal(SecurityRoleMapping.java:243)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:96)
at weblogic.ejb20.deployer.SecurityRoleMapping.getSecurityRolePrincipals(SecurityRoleMapping.java:128)
at weblogic.ejb20.deployer.SecurityRoleMapping.isPrincipalInAnyRole(SecurityRoleMapping.java:174)
at weblogic.ejb20.deployer.MethodInfoImpl.checkAccess(MethodInfoImpl.java:214)
at weblogic.ejb20.internal.MethodDescriptor.checkAccess(MethodDescriptor.java:285)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:90)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:55)
at com.bea.wlpi.server.plugin.PluginManagerCfgBeanEOImpl.init(PluginManagerCfgBeanEOImpl.java:1301)
at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(InitListenerBean.java:151)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:221)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:175)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1933)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1892)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.Kernel.execute(Kernel.java:250)
at weblogic.jms.client.JMSSession.pushEnvelope(JMSSession.java:1779)
at weblogic.jms.client.JMSCallback.pushEnvelope(JMSCallback.java:69)
at weblogic.jms.frontend.FESession.execute(FESession.java:1972)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"Girish Gupte" <[email protected]> wrote:
>
>
>
Hi,
I am currently using WLI 2.0 SP2 installation. Here is a very unusual
thing I
noticed. Can somebody tell me what is going on ???
1 : I have set up the security realm as indicated in the config.xml file.
As far
as I understand, the caching realm entry has attribute pointing to the
wlpiRDBMSRealm,
which is a RDBMS implementation from the WLI 2.0 SP2 distribution.
2: I start the server, open the WLS console, and create a new user through
the
console. I get no error message and it seems to work fine. ( I also click
on the
save it to database link, and it returns with msg that cache is refreshed
3: I see an entry in the fileRealm.properties file, but no record is
inserted
in the WLSUSER table in the database.
Since the RDBMS realm (from WLI distribution) is defined as basic
realm implementation, should it not insert entry into the database, instead
of
the file realm.
Is this a general problem ( any RDBMS realm ) or is it specific to the
WLI ?
Is there anything that I have not configured here that is causing this
behavior
Is it just refreshing the cache instead of inserting record in DB ?
Why should it insert entry into fileRealm.properties ?
Thanks,
Girish

WLS Container Threads LOCKED

Apologize for this cross-post but I posted in in probably wrong group
Found several WLS Jrockit Threads LOCKED. We are using jrockit81sp2rp1_141_06
System got HUNG
All MUXERS are LOCKED show SocketResetException that seems funny ?
Thanks
Harish
[enablersthreaddump.txt]

Hi,
I'm also facing the same problem, but my server is WLI 8.1 SP2. When we restarted the server for couple of times, it started working fine. but why it is coming? also restarting production server is not a possible solution.
Any one has answers?
Thanks,
Chandra. T

WLI 8.1 SP2

Similar Messages

Maybe you are looking for