BPM for WebLogic 10.3 JMS listener problem: SecurityException
Hi!
I have a BPM 10.3 engine running on WebLogic 10.3 and a BPM process that uses JMS listener global automatic activity. The JMS queue is located in a WebLogic 8.1 server.
The global activity receives a message and tries to create a new process instance. At runtime a strange error occurs (see below). If I just log the message and comment the process creation out, the message is successfully consumed, but with the creation part it is not. The process creation itself is not the problem because other message listeners that call other process activities fail with similar errors.
Btw, it's working in Studio, but not in WL10.
Could someone explain me what happens and how to fix it?
Have I misconfigured something?
Thanks in advance,
Jaanus
The BPM engine log:
The task could not be successfully executed.
Reason: 'fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
Caused by: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
Caused by: Process execution engine execution error.
Caused by: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Caused by: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
fuego.lang.ComponentExecutionException: The task could not be successfully executed.
Reason: 'fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1094)
at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:3023)
at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)
at fuego.ejbengine.EJBProcessBean.executeTask(EJBProcessBean.java:147)
at fuego.server.execution.GlobalJMSExecutor.execute(GlobalJMSExecutor.java:105)
at fuego.ejbengine.EJBGlobalJMSExecutor.access$400(EJBGlobalJMSExecutor.java:43)
at fuego.ejbengine.EJBGlobalJMSExecutor$JMSExecutorWorker.run(EJBGlobalJMSExecutor.java:213)
at java.lang.Thread.run(Thread.java:619)
Caused by: fuego.papi.exception.ActivityFailedException: Activity '/MyProcess#Default-1.0/Begin[Begin]' task 'BeginIn' could not execute successfully.
Detail:Method: 'BeginIn', Exception: 'Process execution engine execution error.'
at fuego.papi.exception.ActivityFailedException.create(ActivityFailedException.java:66)
at fuego.server.AbstractProcessBean.createActivityFailedException(AbstractProcessBean.java:3690)
at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4326)
at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
at fuego.components.Process.createInstance(Process.java:106)
at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
... 16 more
Caused by: fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
... 27 more
Caused by: class fuego.lang.RuntimeExceptionShell ->> fuego.connector.ConnectorException: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
at fuego.server.service.EngineConnectorService.getConnection(EngineConnectorService.java:581)
at fuego.server.service.EngineConnectorService.getEngineConnection(EngineConnectorService.java:300)
at fuego.transaction.TransactionAction.getEngineHandle(TransactionAction.java:179)
at fuego.server.execution.EngineExecutionContext.getEngineHandle(EngineExecutionContext.java:443)
at fuego.server.AbstractInstanceService.create(AbstractInstanceService.java:302)
at fuego.server.execution.microactivity.BeginMicroActivity.createInstance(BeginMicroActivity.java:95)
at fuego.server.AbstractProcessBean$53.execute(AbstractProcessBean.java:3642)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:125)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
at fuego.components.Process.createInstance(Process.java:106)
at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:472)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:125)
... 8 more
Caused by: fuego.connector.ConnectorException: Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [TrinityEngine_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:95)
at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:324)
at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:298)
at fuego.connector.JDBCHelper.getConnection(JDBCHelper.java:41)
at fuego.server.service.EngineConnectorService.getConnection(EngineConnectorService.java:578)
at fuego.server.service.EngineConnectorService.getEngineConnection(EngineConnectorService.java:300)
at fuego.transaction.TransactionAction.getEngineHandle(TransactionAction.java:179)
at fuego.server.execution.EngineExecutionContext.getEngineHandle(EngineExecutionContext.java:443)
at fuego.server.AbstractInstanceService.create(AbstractInstanceService.java:302)
at fuego.server.execution.microactivity.BeginMicroActivity.createInstance(BeginMicroActivity.java:91)
at fuego.server.AbstractProcessBean$53.execute(AbstractProcessBean.java:3642)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.internalCreateInstance(AbstractProcessBean.java:4320)
at fuego.server.AbstractProcessBean._doCreateInstance(AbstractProcessBean.java:3650)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:665)
at fuego.server.AbstractProcessBean.createInstance(AbstractProcessBean.java:736)
at fuego.components.Process.createInstance(Process.java:106)
at fuego.components.ProcessInstance.create(ProcessInstance.java:392)
at fuego.components.ProcessInstance.create(ProcessInstance.java:503)
at oracle.MyProcess.Default_1_0.Instance.CIL_ootaJMSSonumit(Instance.xcdl:12)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1085)
at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1280)
at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:94)
at fuego.server.AbstractProcessBean$45.execute(AbstractProcessBean.java:3017)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
... 8 more
Caused by: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
at weblogic.security.service.SecurityServiceManager.seal(Unknown Source)
at weblogic.security.service.IdentityUtility.authenticatedSubjectToIdentity(Unknown Source)
at weblogic.security.service.RoleManager.getRoles(Unknown Source)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(Unknown Source)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:442)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:423)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:180)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at fuego.connector.impl.BaseRemoteConnector.getReferencedObject(BaseRemoteConnector.java:116)
at fuego.connector.impl.BaseRemoteConnector.getReferencedObject(BaseRemoteConnector.java:107)
at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:75)
at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:64)
at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:147)
at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:319)
... 43 more
I managed to solve the problem by configuring the domain's security settings on both WebLogic servers as follows:
*) checked "Anonymous Admin Lookup Enabled",
*) entered the same value to Advanced->Credential on both WLs.
Similar Messages
-
BPM for Weblogic configuration is failed
1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) 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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) 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.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?Hi,
Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
-------------------log message-------------------------------
TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
TO_MSG
TO_MSG Your environment has been set.
TO_MSG
TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
TO_MSG
TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
TO_MSG
TO_MSG Welcome to WebLogic Server Administration Scripting Shell
TO_MSG
TO_MSG Type help() for help on available commands
TO_MSG
TO_MSG Starting server BPMServer
TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
TO_MSG Starting weblogic server ...
TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ26￥ﾈﾆ58ﾧﾒ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00ﾧﾒ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00ﾧﾒ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ12ﾧﾒ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ13ﾧﾒ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15ﾧﾒ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ16ﾧﾒ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ24ﾧﾒ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
TO_MSG Server started successfully.
TO_MSG Started Server. Trying to connect to the server ...
TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
TO_MSG
TO_MSG Warning: An insecure protocol was used to connect to the
TO_MSG server. To ensure on-the-wire security, the SSL port or
TO_MSG Admin port should be used instead.
TO_MSG
TO_MSG Location changed to edit tree. This is a writable tree with
TO_MSG DomainMBean as the root. To make changes you will need to start
TO_MSG an edit session via startEdit().
TO_MSG
TO_MSG For more help, use help(edit)
TO_MSG
TO_MSG Starting an edit session ...
TO_MSG Started edit session, please be sure to save and activate your
TO_MSG changes once you are done.
TO_MSG creating mbean of type JMSServer ...
TO_MSG creating mbean of type JMSSystemResource ...
TO_MSG creating mbean of type SubDeployment ...
TO_MSG creating mbean of type Queue ...
TO_MSG creating mbean of type Topic ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type Server ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Realm ...
TO_MSG creating mbean of type RoleMapper ...
TO_MSG creating mbean of type CredentialMapper ...
TO_MSG creating mbean of type CertPathProvider ...
TO_MSG creating mbean of type Authorizer ...
TO_MSG creating mbean of type Adjudicator ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG setting attributes for mbean type JMSServer
TO_MSG setting attributes for mbean type JMSSystemResource
TO_MSG setting attributes for mbean type SubDeployment
TO_MSG setting attributes for mbean type Queue
TO_MSG setting attributes for mbean type Topic
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type Server
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type DefaultIdentityAsserter
TO_MSG setting attributes for mbean type SecurityConfiguration
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type EmbeddedLDAP
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type Domain
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type JDBCXAParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG Saving all your changes ...
TO_MSG Saved all your changes successfully.
TO_MSG Your edit session is not stopped, you can continue your edits.
TO_MSG Activating all your changes, this may take a while ...
TO_MSG The edit lock associated with this edit session is released
TO_MSG once the activation is completed.
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG
TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
TO_MSG that require server re-start:
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
TO_MSG Attributes changed : ListenAddress
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG Activation completed
TO_MSG Creating a user ...
TO_MSG
TO_MSG Created user successfully
TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ01ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ08ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
TO_MSG .................Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ29￥ﾈﾆ48ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ30￥ﾈﾆ45ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ00ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ31ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48ﾧﾒ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48ﾧﾒ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
TO_MSG WLST-WLS-1249792014056: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:117)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:133)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: >
TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.Fil -
Configuration is failed - BPM for Weblogic 10.3.1
1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear], to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 [archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear], to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) 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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) 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.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?Hi Ye,
I noticed this afternoon that Oracle's refering to Oracle WebLogic 10.3.1 as "Oracle WebLogic 11g".
Know this comes as no surprise to you, but when I tried to install Oracle BPM 10gR3 Enterprise on WebLogic 11g (WebLogic 10.3.1) this afternoon it failed. A friend pointed out to me that Oracle WebLogic 11g does not support the DataDirect JDBC driver. Since Oracle BPM Enterprise 10gR3 uses this driver to connect to both its Engine database and Directory Service databases, he's thinking this might be the cause of our problem.
It would be worth verifying this with Support. Here's what I think they'll point you to. The Oracle BPM 10gR3 release notes(http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/relnotes/release_notes_OracleBPM10gR3.htm#N65589) indicate that the only WebLogic application servers supported are Oracle WebLogic 10.3 (10gR3), Oracle WebLogic 10.0 MP1.
Again, talk to Support, but I don't think there's a workaround. The only thing I think you can do is to uninstall WebLogic 10.3.1 and then install WebLogic 10.3 if you want to install Oracle BPM 10gR3 Enterprise on it.
Dan -
Mule, Weblogic and MQ JMS : deadlock problem
Dear Oracle community,
We are hosting our Mule ESB (3.1) application on a Weblogic 10.3 (11g) server and are using IBM Websphere MQ's JMS solution (with libraries version 7.0.1.7).
The problem we are facing is that JMS connections are created by one of Weblogic's worker (thread) and the close() method for those connections are not necessarily called by the same thread.
This is bad because from what I know this behavior is undefined from JMS specification
(see http://docs.oracle.com/cd/E15051_01/wls/docs103/jms/design_best_practices.html#wp1061413 ) and it is a blocker issue in our case because this lead to a deadlock.
Do someone has any idea how to enforce the fact that the same thread do create and close the connection through Weblogic and/or Mule configuration (without re-implementing the connector) ?
Thanks in advance for your help,
Best regards,
Y.
PS : I've already posted this question on Mule ESB's forum : http://forum.mulesoft.org/mulesoft/topics/mule_weblogic_and_mq_jms_deadlock_problem
Edited by: user7428803 on May 14, 2012 2:26 PMI hope you found a solution by now, but as an FYI:
* The JMS specification specifically requires that JMS providers support the ability to call connection.close() and session.close() from an arbitrary thread even when another thread is making calls on these objects. It furthermore goes into some detail about the expected behavior of these calls. The best practices link you cited alludes to this: "The JMS Specification states that multi-threading a session, producer, consumer, or message method results in undefined behavior +except when calling close().+"
* Depending on your use case, you may not need to use Mule to integrate MQ with WebLogic. WebLogic supports a variety of options for integrating MQ directly without the use of third party tooling. See http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm .
Tom -
Configuration of Password Sync & JMS Listener in fail over in SUN IDM 7.1
HI All,
We are having a set up with IDM running on two Sun application servers pointed to single repository. Sun webserver Reverse Proxy has configured for load balancing.
We have configured JMS Listener adapter for Password Sync and JMS Listener Sync is running on Instance1*
and I copied a copy of .bindings file from Instance1 to Instance2 (I doubt whether this is correct or not) by keeping in mind about load balancing with Reverse Proxy.
Issue
Some times the JMS Listener Sync running on Instance1 is hanging (no polling is happening) and password changes are not happening. To make password changes happen, we are restarting Application server of Instance1 and with this some password are failing to synchronize.
I want to configure High availability or Failover to overcome the above issue.
[http://docs.sun.com/source/819-6123/IDM_admin_passwordsync.html#wp25192] not having any detailed steps to configure failover.
Please provide valuable suggestions
Thanks In Advance
MadhuThe problem appears to be machine account password changes that pass null or corrupted values. Machine accounts are like users, but the password change occur automatically between machine and DC so that the client can be a member of the domain.
We turned up the Password Sync logging were able to see the machine name that occurred before each event, and then researching those machines identified them as NT 4.0 workstations. It turns out that NT 4.0 machines cycle their password every 7 days, down to the second. To say that we were surprised to find these machines still on the network was an understatement.
Contact support for this issue. They have been working on a patch for this.
Jason -
Integrating Oracle BPM with WebLogic Portal
Can I integrate Oracle BPM standalone 10g with Weblogic Protal?
Must I use the BPM for Weblogic to integrate with Weblogic Protal or OSB.
According to the Configuration Guide, I cannot find the <ORABPM_standalone_HOME>/j2ee/weblogic/deployerHi All,
I am able to configure Oracle with Weblogic.
Thx. -
Deadlock in TopLink when using JMS listener on WebLogic
I am experiencing a deadlock in TopLink 10.1.3 on WebLogic 9 in code that previously worked on TopLink 9.0.4 with WebLogic 8.1. As such, I'm not sure if it's due to the TopLink change, the WebLogic change or both. Anyway, we have a JMS listener (note, NOT a MessageDrivenBean) that is updating an existing TopLink cached domaing object. The JMS listener thread gets stuck when attempting to commit the transaction. The thread-dump shows that there is another thread which is blocked in the ConcurrencyManager waiting to obtain the lock on an object which is being updated by the listener thread. It appears to me that the root cause is that the Synchronization.afterCompletion() listener is running on a different thread than the one which owns the locks which were obtained beforeCompletion.
See stack traces.
First, the message listener thread which is waiting for participants in the transaction to commit:
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=9 tid=0x3a4a4728 nid=0xa48 in Object.wait() [0x3a0cf000..0x3a0cfbec]
at java.lang.Object.wait(Native Method)
- waiting on <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2665)
- locked <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2570)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:277)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:539)
at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
at com.avinamart.BusinessLogic.Bean.JobService.JobService_u1ylwo_EOImpl.submitJobAndRun(JobService_u1ylwo_EOImpl.java:1388)
at com.avinamart.Framework.Event.Task.OptimizationTaskListener._submitAsAJob(OptimizationTaskListener.java:253)
at com.avinamart.Framework.Event.Task.OptimizationTaskListener._submitAsAJob(OptimizationTaskListener.java:217)
at com.avinamart.Framework.Event.Task.OptimizationTaskListener.processMessage(OptimizationTaskListener.java:344)
at com.emptoris.base.event.EPASSMessageBaseListener.onMessage(EPASSMessageBaseListener.java:722)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:3253)
at weblogic.jms.client.JMSSession.invoke(JMSSession.java:4195)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:674)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:262)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:134)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:36)
at weblogic.messaging.dispatcher.DispatcherServerRef$1.run(DispatcherServerRef.java:105)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Next, the other thread which is participating in the transaction which is stuck:
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=5 tid=0x3adb80a0 nid=0xb30 in Object.wait() [0x3c7af000..0x3c7afd6c]
at java.lang.Object.wait(Native Method)
- waiting on <0x0c7a0000> (a oracle.toplink.internal.helper.ConcurrencyManager)
at java.lang.Object.wait(Object.java:474)
at oracle.toplink.internal.helper.ConcurrencyManager.acquire(ConcurrencyManager.java:76)
- locked <0x0c7a0000> (a oracle.toplink.internal.helper.ConcurrencyManager)
at oracle.toplink.internal.identitymaps.CacheKey.acquire(CacheKey.java:80)
at oracle.toplink.internal.identitymaps.FullIdentityMap.remove(FullIdentityMap.java:164)
at oracle.toplink.internal.identitymaps.HardCacheWeakIdentityMap.remove(HardCacheWeakIdentityMap.java:82)
at oracle.toplink.internal.helper.WriteLockManager.releaseAllAcquiredLocks(WriteLockManager.java:363)
at oracle.toplink.publicinterface.UnitOfWork.afterTransaction(UnitOfWork.java:2123)
at oracle.toplink.transaction.AbstractSynchronizationListener.afterCompletion(AbstractSynchronizationListener.java:135)
at oracle.toplink.transaction.JTASynchronizationListener.afterCompletion(JTASynchronizationListener.java:66)
at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:862)
at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2913)
at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2806)
at weblogic.transaction.internal.ServerTransactionImpl.setCommittedUnsync(ServerTransactionImpl.java:2857)
at weblogic.transaction.internal.ServerTransactionImpl.ackCommit(ServerTransactionImpl.java:1097)
- locked <0x0c7a0908> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.CoordinatorImpl.ackCommit(CoordinatorImpl.java:211)
at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Is this the same concurrency bug which was fixed in 10.1.3.1??? As I am writing this, I am attempting to build the application with the updated TopLink jar to test for myself. Has anyone else seen this scenario with WebLogic? I should also point out that the problem only occurs when the listener is running on a separate server than the one hosting the JMS queue it reads from. It may be that when the listener runs on the same server, it does not use multiple threads in the transaction.
Any ideas are greatly appreciated.
- BrunoWe've got the same kind of issue with toplink 10.1.3.0.0 and bea weblogic 8.1 SP5.
I 've not tried with 10.1.3.1.0, did you?
Do you have a new status for this issue.
Chris -
Weblogic jms connection problem
Hi All,
My jms bpel process listening on jms Queue. If I deploy bpel process first time I am not getting any jms connection problem with weblogic , but if redploy I am getting jms conneciton problem. saying
Adapter_start: Jms Adapter started
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound> Error whil
e creating managed connection:
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor BP
ELJMS neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnection
FactoryFactory.java:156)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConne
ctionFactoryFactory.java:95)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:143)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:102)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:355)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConn
ectionFactory.java:346)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:309)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConn
ectionFactory.java:99)
at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(Applic
ationConnectionManager.java:564)
at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnection(ConnectionPoolImpl.java:
Work around is I need to restart the BPEL server.
Is there any permanant solution for this, Please suggest.
Thanks,
Srinisrini,
see this thread
JMS Connection
thanks,
-Ng. -
When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card. I have tested with both 1.0.3 and 1.0.5 clients with RabbitMQ 3.1.5.
I was wondering if the community was aware of this problem and if there are any workarounds? If not what is the proper channel to file a bug report. An example code snippet is below. The test fails because the TextMessageMatcher expects the destination passed in on construction (second parameter) to equal the desination on the message received (aquired from getJMSDestination).
Mockery context = new Mockery();
final MessageListener messageListener = context.mock(MessageListener.class);
final Latch latch = new LatchImpl();
final String prefix = "test" + System.currentTimeMillis();
context.checking(new Expectations() {
oneOf(messageListener).onMessage(with(new TextMessageMatcher("MSG1", prefix + ".1234")));
will(new CustomAction("release latch") {
@Override
public Object invoke(Invocation invocation) throws Throwable {
latch.unlatch();
return null;
final Connection connection = createConnection(null, null);
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
connection.start();
Topic wildcardTopic = (Topic) getInitialContext().lookup(prefix + "." + "#");
Topic destination = (Topic) getInitialContext().lookup(prefix + ".1234");
final MessageConsumer consumer = session.createConsumer(wildcardTopic);
consumer.setMessageListener(messageListener);
MessageProducer producer = session.createProducer(null);
producer.send(destination, session.createTextMessage("MSG1"));
latch.await(5000);
connection.close();
Thread.sleep(5);
context.assertIsSatisfied();Check where your MDB sends the [response] messages to.
-
WLST Failed in Oracle BPM Enterprise for Weblogic Server
Hi,
I am not getting any clue of resolving the following issue. We are using Oracle BPM Enterprise for Weblogic # 100141. Error details:-
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
t3://192.68.1.3:
Connecting to t3://192.168.1.3: with userid weblogic ...
This Exception occurred at Tue Jul 3 :56: IST .
weblogic.utils.NestedError: Local host not known?!
at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:9)
at weblogic.rjvm.JVMID.localID(JVMID.java:8)
at weblogic.protocol.LocalServerIdentity$SingletonMaker.<clinit>(LocalServerIdentity.java:3)
at weblogic.protocol.LocalServerIdentity.getIdentity(LocalServerIdentity.java:)
at weblogic.server.channels.ServerChannelImpl.createDefaultServerChannel(ServerChannelImpl.java:3)
at weblogic.rjvm.t3.ProtocolHandlerT3$ChannelInitializer.<clinit>(ProtocolHandlerT3.java:3)
at weblogic.rjvm.t3.ProtocolHandlerT3.getDefaultServerChannel(ProtocolHandlerT3.java:4)
at weblogic.protocol.ServerChannelManager$SingletonMaker$.getOutboundServerChannel(ServerChannelManager.java:339)
at weblogic.protocol.ServerChannelManager.findOutboundServerChannel(ServerChannelManager.java:43)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:3)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:94)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:5)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:88)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:53)
at weblogic.jndi.WLInitialContextFactoryDelegate$.run(WLInitialContextFactoryDelegate.java:344)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
at weblogic.jndi.Environment.getContext(Environment.java:35)
at weblogic.jndi.Environment.getContext(Environment.java:85)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:88)
at javax.naming.InitialContext.init(InitialContext.java:3)
at javax.naming.InitialContext.<init>(InitialContext.java:9)
at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:5)
at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:35)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:3)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:6)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:5)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
at java.lang.reflect.Method.invoke(Method.java:59)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:6)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:48)
at org.python.core.PyObject.invoke(PyObject.java:6)
at org.python.pycode._pyx4.connect$(<iostream>:6)
at org.python.pycode._pyx4.call_function(<iostream>)
at org.python.core.PyTableCode.call(PyTableCode.java:8)
at org.python.core.PyTableCode.call(PyTableCode.java:44)
at org.python.core.PyTableCode.call(PyTableCode.java:8)
at org.python.core.PyFunction.__call__(PyFunction.java:9)
at org.python.pycode._pyx6.initConfigToScriptRun$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:5)
at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
at org.python.core.PyTableCode.call(PyTableCode.java:8)
at org.python.core.PyTableCode.call(PyTableCode.java:56)
at org.python.core.PyFunction.__call__(PyFunction.java:69)
at org.python.pycode._pyx6.f$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:66)
at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
at org.python.core.PyTableCode.call(PyTableCode.java:8)
at org.python.core.PyCode.call(PyCode.java:4)
at org.python.core.Py.runCode(Py.java:35)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:6)
at weblogic.management.scripting.WLST.main(WLST.java:9)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
at java.lang.reflect.Method.invoke(Method.java:59)
at weblogic.WLST.main(WLST.java:9)
Caused by: java.net.UnknownHostException: HOME-MITTAL: HOME-MITTAL
at java.net.InetAddress.getLocalHost(InetAddress.java:353)
at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:5)
... 6 more
No server running at t3://192.168.1.3: or the user/password is wrong
Exiting WebLogic Scripting Tool.
Even I tried using hostname as "localhost" but still I am facing the same issue.
Please suggest what is the resolution for the same.
Thanks,
AbhishekHi,
I was getting same excepction when tried to configure weblogic server (10.3.3 and 10gR3) through BPM Configuration Wizard, so I end up doing everything manually, like setting up JDBC data sources, JMS Server, JMS Modules and created DB (Directory & Engine).
Now, I am stuck at the last step of deploying the EAR files generated using BPM Process Administrator, they EAR's are generated fine but while deploying them to Weblogic server (through BPM Process Administrator), getting following exception (for "01-eng-bpmengine.ear")
<Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpmengine".
fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: Invalid column type].
at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1423)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy246.authenticateHumanParticipant(Unknown Source)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy243.connect(Unknown Source)
at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
at fuego.directory.provider.Factory.startSession(Factory.java:405)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
at fuego.directory.Directory.startSession(Directory.java:268)
at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
at fuego.ejbengine.Engine.start(Engine.java:122)
at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLException: Invalid column type
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7975)
at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8028)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:238)
at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:324)
at fuego.jdbc.FaultTolerantPreparedStatement.setString(FaultTolerantPreparedStatement.java:436)
at fuego.directory.provider.jdbc.JDBCPersistenceManager.setStringAttribute(JDBCPersistenceManager.java:896)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1417)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy246.authenticateHumanParticipant(Unknown Source)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy243.connect(Unknown Source)
at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
at fuego.directory.provider.Factory.startSession(Factory.java:405)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
at fuego.directory.Directory.startSession(Directory.java:268)
at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
at fuego.ejbengine.Engine.start(Engine.java:122)
at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
my assumption is JDBC Data Sources or the Directory/Engine database have some column name mismatch.
Let me know if somebody has a solution for this, or if I am doing something wrong.
NOTE: just found out that this happens only on Windows 2003 server, but not on OEL5 (Oracle Enterprise Linux 5).
Thanks !! -
JMS Listener configuration problem
I am installing IDM6.0 and trying to use the password synch feature with Active Directory. Below are my environment details
tomcat 5.0.28 on linux
Sun Message Queue 3.6 for JMS
When I am configuring the JMS Listener adapter I am getting the below error. I have installed the Sun Message Queue and storing the administered objects in a file.
Test connection failed for resource(s):
JMS Listener: javax.naming.NameNotFoundException
If anyone has ever done that earlier it will be very helpful for me.
Thanks in advanceJust an update on my last comment
I had tested this on the windows box. The problem may not be there in the Linux -
BPM Enterprise for weblogic and clusters
good morning every body
what is the best practice for High Avalibilty Clustered environement for BPM enterprise for weblogic ?
i know that clustering is done on the Weblogic server side but is there is any constraints regarding to ALBPM clustering
if some one would direct me to a diagram of the clustring best practice it would be appreciated!Hi,
Event I am facing the similar problem but its irrregular(but most of the time). I get following as a log while shutting down the server.
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'atg
_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Shutting down the server AdminServer with force=false while connected to AdminSe
rver ...
And it countinues...
Regards,
Kevin Chheda -
How to configure a error queue for weblogic jms topic
Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
MingzhuangMingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj -
How to setup the cluster environment for BPM using weblogic
want to setup the cluster environment for BPM using weblogic....
i have installed the oracle weblogic server 10gr3 and oracle BPM enterprise for weblogic 10gR3
i have used the Admin tools from the "oracle BPM enterprise for weblogic" to setup the configuration and create the weblogic domain servers.
i can launch the process administrator and import the project exp file to domain server.
but what should i do to setup cluster environment using weblogic?
what i want to do is :
setup one admin machine..
setup two product machine..
enable the cluster so the admin machine can monitor the status of the product machine..
thanks a lot ...The install guide at http://download-llnw.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html gives a reasonable amount of info on how to do this.
Personally I have not used the OBPM option to configure WebLogic instead I've used the information in the above install guide to create the weblogic domain in advance of configuring OBPM.
Once you've setup WebLogic configure OBPM using the values I mention in the following thread: How to set the JMX Engine parameter in Process Administation?
Let me know any specific config questions and I'll do my best to answer them for you.
Thanks,
Mike -
Workspace of BPM Enterprise 10.3.1 for Weblogic
I just install BPM Enterprise 10.3.1 for weblogic. I configure it using default setting.
In the BPM admin center, it has 5 options:
Start
Stop
Start process administrator
configuration
exit
Where is the workspace?Hi YE,
If you are deploying BPM on a Weblogic Server you'll find your workspace on the following url
http://localhost:7001/workspace
This is because the all the jar services are deployed to the WLS. You can monitor if it is installed by going into the Process administrator -> Engines -> J2EE jar deployment (or something)
There you'll find all the jars that are/can be deployed. If you make any changes using the BPM admin center configuration don't forget to recreate and redeploy the jar file.
Hope this helps.
Kind regards
Nils
Maybe you are looking for
-
I purchased a movie from the itunes store, it had errors (25) in the down load, and it does not allow me to down load again. I just get directed to the Store, and Check for available downloads, which when selected again informes me that 25 errors occ
-
Can any body tell me about the multithreaded nature of servlet?
-
How to run shell script using External Process in Process Flow?
Hi, We can run external process using Process flow. I would like to run shell script as external process in Process flow. Could any one please explain it? Thanks and regards Gowtham Sen.
-
Does wowslider work with dreamweaver
DDoes wowslider work in dreamweaver?
-
We are using Class.forName("driver class") statement for registering the driver class. But after writing this statement we are not using any refernce to that Class.forName, why it is needed actually.