Deployment Warning Message
"Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/sap.com/TestMDBEAR/Test1, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "Test1" does not exist. Possible reasons: the connector in which ConnectionFactory "Test1" is defined is not deployed or not started."
This is the error i got while deployment, actually i am developing a MDB, can any one please help me some good explanatory example on MDBs, and also tell me how to solve the above problem,
Thanks n regards!
It does execute on its own so should be ok
Many thanks
Please remember to accept any solutions and give kudos, Thanks
LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7
Similar Messages
-
Hi,
I have a rather straightforward mapping (but it has over 20 source tables into the Joiner and out to one target table).
I am getting the following 6 warnings when I deploy:
ORA-06550: PACKAGE BODY, line 126, column 36:PL/SQL: ORA-00936: missing expression
ORA-06550: PACKAGE BODY, line 11, column 2:PL/SQL:SQL Statement ignored
ORA-06550: PACKAGE BODY, line 249, column 36:PL/SQL:ORA-00936: missing expression
ORA-06550: PACKAGE BODY, line 134, column 2:PL/SQL:SQL Statement ignored
ORA-06550: PACKAGE BODY, line 679, column 36:PL/SQL:ORA-00936: missing expression
ORA-06550: PACKAGE BODY, line 5577, column 2:PL/SQL:SQL Statement ignored
I have looked at the PL/SQL package, resysnched the tables, even created new mapping from scratch, but still no luck. Any ideas?
I have also looked at other such issues, but had no luck. Also, there are no issues when I validate the mapping and the Join Condition.Does the mapping have any expression . check and validate the expression.
Or
it can be checked form the database directlly
Cheers
Nawneet -
Warning messages in mapping deployment window
Hi all,
After deploying a mapping I got several warning messages but have no clues as to what and where they are referring to. Example of a warning message that I got:
ORA-06550: line 32250, column 11:
PL/SQL: SQL Statement ignored
Do anyone of you know where the line 32250 and column 11 is exactly referring to? I need to see the code in order to know wat's the error. Do I refer to the script in the Script tab? But it seems to refer to nowhere if that is the case...Sutirtha Roy wrote:
Hi ,
The line numbers in the error messages are usually offset from the start of the package body, but the generated code listing has the package spec and body. So for example you got this one:
LINE 671 ,COLUMN 12:
PL/SQL: ORA-00942: table or view does not exist
So you want to find package body line 671. So inside the generated code viewer, find the text "CREATE OR REPLACE PACKAGE BODY". Note the line number where that occurs, then add it to 671, that should be your actual line number.
Thanks,
SutirthaThanks Sutirtha,
I finally made sense of where the warning messages were referring to. But I could not understand why some of these messages were produced. The scenario is like this.
I added a unique key constraint on the attribute suppcode in the supplierwh table, and for all instances of this supplierwh table in my mapping where the loading type is "Update", I set the loading properties for both "match column when updating" and "match column when deleting" to No. Validation has got no errors but upon deployment warning messages were produced. Half of these warning messages were of this type:
Warning
ORA-06550: line 2449, column 41:
PL/SQL: ORA-00936: missing expression
Upon checking where these similar type of warning messages were referring to, all of them were pointing to codes something like below:
"MERGE_SUBQUERY"
ON (
*"T_SUPPLIERWH_T1UPDATE"."SUPPCODE" = AND*
"T_SUPPLIERWH_T1UPDATE"."SUPPKEY" = "MERGE_SUBQUERY"."SUPPKEY_1"
I believe the error codes are the ones in bold because there is nothing after the = sign. But I do not understand why this is so. Can anyone help?
Edit: I think I found the reason to this. Is it because of the "match by constraint" attribute? What does this attribute do when set to "All constraints"?
Edited by: user8915380 on 29-Apr-2010 01:38 -
Warning message when starting Weblogic BPM server in SOA Suite 11G
Hi There,
I understand that most of the warning message we can ignore it but why at first the warning is generated? Anyone can delighted me for this warnings, I don't want this to be show in production mode because of the production policy from most of the clients.
Below are some of the warning message that shows in my Weblogic with BPM.
<Warning> <Connector> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486532106> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566020> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.load(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566036> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.unload(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567018> <BEA-010001> <While deploying EJB 'FacadeFinderBean', class oracle.soa.management.internal.ejb.FacadeFinderBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567034> <BEA-010001> <While deploying EJB 'SOATestBean', class oracle.soa.management.internal.ejb.SOATestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceEx was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.SOADirectInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.Invoker was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567736> <BEA-010001> <While deploying EJB 'ContextAwareBean', class oracle.integration.platform.ejb.ContextAware was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569358> <BEA-015036> <In the EJB MessageDispatcherBean(Application: soa-infra, EJBComponent: sdpmessagingclient-ejb.jar), the value for the activation config property 'connectionFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactory';>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569499> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarter was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTest was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtility was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <J2EE> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486592774> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application BPMComposer is not versioned.>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>Hi There,
I understand that most of the warning message we can ignore it but why at first the warning is generated? Anyone can delighted me for this warnings, I don't want this to be show in production mode because of the production policy from most of the clients.
Below are some of the warning message that shows in my Weblogic with BPM.
<Warning> <Connector> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486532106> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566020> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.load(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566036> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.unload(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567018> <BEA-010001> <While deploying EJB 'FacadeFinderBean', class oracle.soa.management.internal.ejb.FacadeFinderBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567034> <BEA-010001> <While deploying EJB 'SOATestBean', class oracle.soa.management.internal.ejb.SOATestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceEx was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.SOADirectInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.Invoker was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567736> <BEA-010001> <While deploying EJB 'ContextAwareBean', class oracle.integration.platform.ejb.ContextAware was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569358> <BEA-015036> <In the EJB MessageDispatcherBean(Application: soa-infra, EJBComponent: sdpmessagingclient-ejb.jar), the value for the activation config property 'connectionFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactory';>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569499> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarter was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTest was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtility was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <J2EE> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486592774> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application BPMComposer is not versioned.>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra> -
Error during deployment of Message Driven Bean
Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
I am getting some error (or perhaps warning) during deployment of Message
Driven Bean. Any one seen this before?
This error only comes on a machine with Dual Network card.
Thanks.
####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010008> <EJB Deploying file: AppRuntime.jar>
####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
<system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
is of a non-final version of the appropriate specification. It is subject to
change in future releases once the specification becomes finalized. This may
cause application code developed for BEA WebLogic Server 6.1 that uses the
new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
supported in future releases of BEA WebLogic Server.>
####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
unable to connect to the JMS destination: CQM_MessageQueue. The EJB
container will automatically attempt to re-establish the connection with the
JMS server. This warning may occur during WebLogic Cluster start-up if the
JMS destination is located on another server. When the JMS server connection
is re-established, the Message-Driven EJB will again receive JMS messages.
The Error was:
Unable to create a JNDI InitialContext to lookup the JMS destination. The
error was:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
nested exception is:
java.net.ConnectException: Connection refused: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:307)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:211)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
rivenBeanInfoImpl.java:641)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
nPoller.java:474)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
.java:418)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
nectionPoller.java:286)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
foImpl.java:511)
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 $Proxy34.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 $Proxy49.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)
>
####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010009> <EJB Deployed EJB with JNDI name
ASYNCMessageDrivenBean.>
Hi Tom
Yes we do have an URL provided in the descriptor. It's
t3://jms.server.net:7001.
and the jms.server.net is resolved via a hosts file in Win2K
eg,
192.168.100.200 jms.server.net
You are right in saying that the loopback in a dual-net card is a problem.
But our solution
above solves the issue as long as your host file does not use 127.0.0.1 as
the IP.
We need the URL b/c depending on our client's deployment , the JMS Server
may be remote or may be local.
"Tom Barnes" <[email protected]> wrote in message
news:[email protected]...
> Hi x,
>
> Something to do with the loopback and dual-network cards is
> messin' with WLS' mind. I do not know what the problem is,
> but I can guess:
>
> You have specified an URL in the MDB descriptor when there
> is no need for one. If t3://127.0.0.1:7001 is in the same
> cluster the MDB is running in (I suspect this URL is
> actually the same WL server), then don't specify the URL.
> This URL is only useful for connecting an MDB to a JMS
> server that is outside local server and outside the cluster.
> The URL may be working on single-network card systems
> as perhaps then WL has enough info to guess that you
> actually mean the local WL server, and simply converts
> the context to a local context.
>
> Note that the URL option in the MDB descriptor is actually
> a WebLogic extension of J2EE.
>
> Tom
>
>
>
> x wrote:
> > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
> >
> > I am getting some error (or perhaps warning) during deployment of
Message
> > Driven Bean. Any one seen this before?
> > This error only comes on a machine with Dual Network card.
> >
> > Thanks.
> >
> >
> >
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
<main>
> > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
features
> > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
1.2,
> > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
6.1
> > is of a non-final version of the appropriate specification. It is
subject to
> > change in future releases once the specification becomes finalized. This
may
> > cause application code developed for BEA WebLogic Server 6.1 that uses
the
> > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
> > supported in future releases of BEA WebLogic Server.>
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
<main>
> > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
> > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
> > container will automatically attempt to re-establish the connection with
the
> > JMS server. This warning may occur during WebLogic Cluster start-up if
the
> > JMS destination is located on another server. When the JMS server
connection
> > is re-established, the Message-Driven EJB will again receive JMS
messages.
> > The Error was:
> > Unable to create a JNDI InitialContext to lookup the JMS destination.
The
> > error was:
> > javax.naming.CommunicationException. Root exception is
> > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
> > nested exception is:
> > java.net.ConnectException: Connection refused: connect; No available
router
> > to destination
> > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > at
> >
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
> > at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
> > at javax.naming.InitialContext.init(InitialContext.java:217)
> > at javax.naming.InitialContext.<init>(InitialContext.java:193)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
> > rivenBeanInfoImpl.java:641)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
> > nPoller.java:474)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
> > .java:418)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
> > nectionPoller.java:286)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
> > foImpl.java:511)
> > 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 $Proxy34.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 $Proxy49.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)
> >
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010009> <EJB Deployed EJB with JNDI name
> > ASYNCMessageDrivenBean.>
> >
> >
>
-
AnyConnect VPN Warning Message
Hi
I have setup AnyConnect VPN and all works fine apart from the warning messages appearing about the server being Untrusted.
I am not too good with certificates so any help will be much appreciated. When I open anyconnect client and click connect, the warning appears then so I click continue anyway to carry on. Then after entering username//password the warning appears a second time and again i click continue and carry on.
We had a wildcard certificate so I installed in on the asa in the CA certificates section, Now the 2nd warning has gone but the first one still appears.
Any ideas???
ThanksYou can simply accept the self-signed certificate the first time you are presented with that message and direct AnyConnect to always trust such certificates.
If you don't want to do that, you need to make your clients automatically trust this certificate from your ASA. You can do that several ways. You mentioned using a 3rd party vendor - that ends up being the method of using a vendor in the trusted root Certificate Authority (CA) list. If you don't use one of the 3rd party ones, you will need to push out the trust via some software deployment method - e.g. a GPO for Windows clients in a managed AD setup or via pre-deploying with yet another 3rd party tool like LANdesk.
If you don't have an internal CA or AD-managed infrastructure for your clients then just telling users to click "always trust" is the path of least resistance (although the least secure). -
Warning messages thrown while trying to connect to BW Cube
We have Websphere Application Server to deploy our servlets. The problem is when we connect to BW Server through BI Java SDK, it generates the following WARNING messages:
[2/9/06 17:48:14:682 CET] 179cdd40 SystemOut O Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
[2/9/06 17:48:14:682 CET] 179cdd40 SystemOut O Error Message is :com/sap/guid/GUIDGeneratorFactory
[2/9/06 17:48:14:688 CET] 179cdd40 SystemOut O Warning ! Protocol Implementation [com.sap.security.core.client.ws.SecurityProtocol] could not be loaded (ClassNotFound) !
[2/9/06 17:48:14:688 CET] 179cdd40 SystemOut O Error Message is :com.sap.security.core.client.ws.SecurityProtocol
[2/9/06 17:48:20:325 CET] 179cdd40 SystemOut O Warning ! Provider [SecurityProtocol] not found for feature in logical port [MsXmlAnalysisSoap] !
[2/9/06 17:49:25:069 CET] 179cdd40 WebGroup I SRVE0180I: [Shell-CCL] [/Shell-CCL] [Servlet.LOG]: /jsps/cclMyOrderHistory.jsp: init
[2/9/06 17:51:00:564 CET] 179cdd40 WebGroup I SRVE0180I: [Shell-CCL] [/Shell-CCL] [Servlet.LOG]: CCLMyOrderHistoryDownloadServlet: init
[2/9/06 22:08:23:755 CET] 7b749d56 SystemOut O Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
[2/9/06 22:08:23:755 CET] 7b749d56 SystemOut O Error Message is :com/sap/guid/GUIDGeneratorFactory
[2/9/06 22:08:23:762 CET] 7b749d56 SystemOut O Warning ! Protocol Implementation [com.sap.security.core.client.ws.SecurityProtocol] could not be loaded (ClassNotFound) !
[2/9/06 22:08:23:762 CET] 7b749d56 SystemOut O Error Message is :com.sap.security.core.client.ws.SecurityProtocol
[2/9/06 22:08:24:943 CET] 7b749d56 SystemOut O Warning ! Provider [SecurityProtocol] not found for feature in logical port [MsXmlAnalysisSoap] !
Any clues on this one. What causes this and why?
Thanks in advance.http://otn.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#_59_
The thin drivers are classes12.zip/classes111.zip. classes12.zip being the most recent release. You can download it from
http://otn.oracle.com/software/tech/java/sqlj_jdbc/htdocs/winsoft.html
(the general download site is http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html )
Jamie -
Quota warning message not working
I have Quota warning messages turned on to be sent daily to users using over 90% of their limit.
To test it I've had an account filled to 95% for a few days and no message yet.
Anyone else having problems with this? Anyone have any suggestions what might be wrong?Hi Edm Dude
9 days later and no one uses the Quota Warning
feature? I don't believe this. I'm looking for
someone who has it working so I can compare
settings.
You’ve not had a great response have you? This is a pity. I don’t have the Quota Warning enabled and I have never been asked to enable it at various sites where I have deployed Apple Mail Server. I have never been asked to use Virtual Domains either although I can’t see why this would make a difference.
Perhaps no one really does use this feature or has a need for it. It may be that it has been tried by others and they have had the same experience as you?
The user has a limit of 20MB. The quota warning is
set to 90%, and to notify ry 1 days. These have been
configured only via WGM
Don’t quite understand the statment above made from one your earlier posts. Mail Quota limits are defined in WGM. Server Admin is required for notification of Quota excess. Perhaps you already know this and the above statement is a typo.
I know you have configured the user’s account in WGM for POP and IMAP, but is the user’s mail application account configured for POP or IMAP on the client computer? -
Hi I´m facing this problem, I test the queue destination with an external client and everything is ok, but then when I try to deploy the Message - Driver - bean on CE the next error comes out , any help will be appreciated.
--- Deploying file(s):
C:Documents and Settingse100009workspace.jdi xenapjmsEAR xenapjmsEAR.ear
--- Status:
Deploy finished with warnings.
--- Description:
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:C:Documents and Settingse100009workspace.jdi xenapjmsEAR xenapjmsEAR.ear
Name:fxenapjmsEAR
Vendor:com.sap
Location:localhost
Version:2010.02.02.12.47.07
Deploy status:Warning
Version:HIGHER
Description:
1. Warning occurred on server 9111850 during update com.sap/fxenapjmsEAR : SessionsTakerTest: Following tests could not be executed because of failed precondition test "SessionsTakerTest" : Classes Exposure Check, Business Interfaces Check, file: fxenapjms.jar, column -1, line -1, severity: warning
2. Exception has been returned while the [com.sap/fxenapjmsEAR] was starting. Warning/Exception :[
][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 9111850:The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
-> Path to object does not exist at jmsqueues, the whole lookup name is jms_vendor_queues_global/jmsqueues/default/sapDemoQueue.
server ID 9111850:com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean com.sap/fxenapjmsEAR*annotation|fxenapjms.jar*annotation|fxenapmjbBean
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:903)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:435)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:228)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:186)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3432)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3418)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3308)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3280)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean com.sap/fxenapjmsEAR*annotation|fxenapjms.jar*annotation|fxenapmjbBean
at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:94)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:897)
... 35 more
Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:128)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:531)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:155)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:86)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:59)
at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:84)
... 38 more
Caused by: javax.resource.spi.UnavailableException: The destination jmsqueues/default/sapDemoQueue cannot be looked up. Last attempt performed : jms_vendor_queues_global/jmsqueues/default/sapDemoQueue
at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:361)
at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:126)
at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:115)
... 43 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsqueues, the whole lookup name is jms_vendor_queues_global/jmsqueues/default/sapDemoQueue.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:184)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:489)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:321)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:619)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:359)
... 45 moreIt means that bean classes are in the system classpath and therefore
cannot be reloaded. If you do not plan on hot-redeploying your beans
you can ignore this message.
Dragan-Sassler <[email protected]> wrote:
Hi,
i have developed some EJB, that are dependent from each others.
So I set the classpath to a lib-directory with my EJB.
When i try to deploy, i become a warning
<Warning> <EJB> <EJB Deployment: Fnv cannot be redeployed while the server is
running. de.dr_staedtler.extern.audi.fnv.data.ejb.FnvBean is located in the server's
classpath.>
But the EJB's are deployed and the client can connect it.
Why is the warning? It is important or I can ignore it?
Thanks for your time.
dragan-sassler--
Dimitri -
Windows 7 computers show a Valid Trust Anchor warning message when connecting to corporate wireless
We are currently using EAP-TLS Microsoft:Smart Card or certificates" as the Authentication Method on our Radius/NPS server for authenticating domain laptops to be enable to connect to corporate wireless network.
We have a Windows 2003 Root& Issuing CA which has published computer certificates to all the domain laptops/workstations. We have also setup a parallel PKI ( Root and Issuing CA) setup on Windows 2012 OS in the same domain.
This Windows 2012 ISsuing CA has also deployed computer certificates to a cpl of testing domain workstations. So the end result, each of these testing workstations has 2 computer certificates in its PERSONAL Store for client/server auth (1)
One issued by the Windows 2003 CA (2) Other cert issued by the Windows 2012 CA.
We are noticing that windows 7 laptops are throwing a warning message similar to as shown below . I have verified that the ROOT certificate coming from both the CA's described above, is present in the ROOT TRUSTED CERTIFICATION AUTH Store on each of these
Windows 7 laptops. Surprisingly, we don't get this same warning on Windows 8 or 8.1 laptops.
Also, if i hit the CONNECT button, i am able to connect to the wireless,
but then i don't see the "Security " Tab anymore under properties of the wireless profile (SSID). I found on some forums to click on the Security Tab and further click on "SETTINGS" and check if the ROOT CA cert is present
in the Trusted Root Certification Authorities” list, . I dont get these options anymore after connecting.
These options do show up on Windows 8 machines after connecting.in the wireless connection properties, in the dialog authentication properties you need to select root CAs which are eligible to issue RADIUS server certificates:
Vadims Podāns, aka PowerShell CryptoGuy
My weblog: en-us.sysadmins.lv
PowerShell PKI Module: pspki.codeplex.com
PowerShell Cmdlet Help Editor pscmdlethelpeditor.codeplex.com
Check out new: SSL Certificate Verifier
Check out new:
PowerShell File Checksum Integrity Verifier tool. -
Provider ABCS throwing Warning Message
Hi,
I compiled the ProviderABCSImpl, compilation ended with given warning messages.
Kindly let us know
where we can find the WSDL Manager? so that we can define the Binding.
to eliminate these warnings
i.e. 1- Failed to Find Binding "AIAAsyncErrorHandlingBPELProcess":"{http://xmlns.oracle.com/AIAAsyncErrorHandlingBPELProcess}
AIAAsyncErrorHandlingBPELProcess" in WSDL Manager*
2 - Warning: property "bpel.config.oneWayDeliveryPolicy" may not be understood by BPEL component CreateReceiptListEbizProvABCSImplProcess -
it will likely be ignored.
3- Warning(202): Trying to assign incompatible types <from> value type "{http://www.w3.org/2001/XMLSchema}string" is not compatible with <to> value
type "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}CodeType" Make sure that the return value of from-spec query is compatible with the
to-spec query
After Compilation Warning messages
=======================
Project: H:\AIASOAProject\AIAFrameworkProject\CreateReceiptListEbizProvABCSImpl\CreateReceiptListEbizProvABCSImpl.jpr
H:\AIASOAProject\AIAFrameworkProject\CreateReceiptListEbizProvABCSImpl\composite.xml
**Warning(46,189): Failed to Find Binding "AIAAsyncErrorHandlingBPELProcess":"{http://xmlns.oracle.com/AIAAsyncErrorHandlingBPELProcess}AIAAsyncErrorHandlingBPELProcess" in WSDL Manager**
**Warning(58,122): Failed to Find Binding "CreateReceiptListEbizProviderService":"{http://xmlns.baesystems.com.au/InternalServices/Ebiz/ReceiptList/V1}CreateReceiptListEbizProviderService_pt" in WSDL Manager**
H:\AIASOAProject\AIAFrameworkProject\CreateReceiptListEbizProvABCSImpl\CreateReceiptListEbizProvABCSImplProcess.componentType
Warning: property "bpel.config.oneWayDeliveryPolicy" may not be understood by BPEL component CreateReceiptListEbizProvABCSImplProcess - it will likely be ignored.
H:\AIASOAProject\AIAFrameworkProject\CreateReceiptListEbizProvABCSImpl\CreateReceiptListEbizProvABCSImplProcess.bpel
Warning(202): Trying to assign incompatible types
<from> value type "{http://www.w3.org/2001/XMLSchema}string" is not compatible with <to> value type "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}CodeType"
Make sure that the return value of from-spec query is compatible with the to-spec query
Warning(202): Trying to assign incompatible types
<from> value type "{http://www.w3.org/2001/XMLSchema}string" is not compatible with <to> value type "{http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2}TextType"
Make sure that the return value of from-spec query is compatible with the to-spec query
Warning(569): Trying to assign incompatible types
<from> value type "{http://www.w3.org/2001/XMLSchema}string" is not compatible with <to> value type "{http://schemas.xmlsoap.org/ws/2003/03/addressing}AttributedURI"
Make sure that the return value of from-spec query is compatible with the to-spec query
Regards
Manishfor #1, Service Constructor defaults to the abstract WSDL. There are two modes for definition of ABCS. 1. Developer is designing the service but does not have a target system in mind. The service is compilable, but not runnable. When the service is being deployed to a target server, the bindings will have to be added. 2. Developer has a target system (such as dev/test) in mind. The developer would go ahead and specify the concrete WSDL location for the CAVS and error handling runtime.
-
Could anybody explain this warning message regarding Posix Performance Pack
Hi,
I am getting following message on my console :
<Sep 10, 2002 7:12:38 PM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '123' with no corresponding table entry>
<Sep 11, 2002 12:40:48 AM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '151' with no corresponding table entry>
I have deployed the WL server on HP-UX 11.0 and wlserver version is 6.1 sp2. Could
anybody explain the warning message ?
TIA
AnirudhThis is a known issue.
Contact [email protected] and ask for "Combined muxer" patch.
Kumar
Anirudh wrote:
Hi,
I am getting following message on my console :
<Sep 10, 2002 7:12:38 PM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '123' with no corresponding table entry>
<Sep 11, 2002 12:40:48 AM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '151' with no corresponding table entry>
I have deployed the WL server on HP-UX 11.0 and wlserver version is 6.1 sp2. Could
anybody explain the warning message ?
TIA
Anirudh -
Deployment warning -- Compiled by different version of Weblogic Server?
####<Aug 23, 2001 12:17:54 PM PDT> <Warning> <EJB> <alpha> <admin>
<main> <system> <> <010004> <The EJB deployment named: registration
was compiled by a different version of the WebLogic Server.>
I'm using WLS 6.0 SP1.
I'm getting the above warning messages for every jar file within my
EAR file that I try and deploy. I can't figure out the source of this
warning. I get this message in any of the following compilation
cases:
* compiling with BEA's default javac (Sun's JDK version 1.3.0)
* compiling with Sun's javac (Sun's JDK version 1.3.0_02)
* compiling with jikes
The message seems misleading and doesn't make sense to me. Anyone
know why I'm getting this error message? Anyone else getting these
warning messages?
Regards,
JDMihir Kulkarni <[email protected]> wrote in message news:<[email protected]>...
Could you please post this message on the ejb newsgroup.
The message does not seem to mean a different version of the java
compiler, but different version of Weblogic's ejb compiler -
weblogic.ejbc.
Were these EJB's compiled by a previous version of ejbc, say, the one from
51 ?
No, these EJBs were never compiled against a previous version of ejbc.
They were only created and deployed with WLS 6.0 SP1.
Also, please check the generated file inside the build\ejbcgen directory:
WLGENERATED to check which version of WL ejbc was used to compile it.
Here's contents of the WLGENERATED file:
#Wed Aug 29 11:04:33 PDT 2001
WLVERSION=WebLogic Server Build\:\t6.0 Service Pack 1 03/04/2001
22\:05\:05 \#
101616\nWebLogic XML Module\:\tNot installed\n
JD
>
JD Fagan wrote:
####<Aug 23, 2001 12:17:54 PM PDT> <Warning> <EJB> <alpha> <admin>
<main> <system> <> <010004> <The EJB deployment named: registration
was compiled by a different version of the WebLogic Server.>
I'm using WLS 6.0 SP1.
I'm getting the above warning messages for every jar file within my
EAR file that I try and deploy. I can't figure out the source of this
warning. I get this message in any of the following compilation
cases:
* compiling with BEA's default javac (Sun's JDK version 1.3.0)
* compiling with Sun's javac (Sun's JDK version 1.3.0_02)
* compiling with jikes
The message seems misleading and doesn't make sense to me. Anyone
know why I'm getting this error message? Anyone else getting these
warning messages?
Regards,
JD -
Processflow: deployment warning
RPE-02016: The full address of host 101.201.109.1 cannot be obtained. This may be a configuration issue with your Name Lookup Service. Please contact your System Administrator to correct this issue
When deploying the process flow, I am getting this above warning, anybody got an idea, what could be the reason for this warning.
Thanks,
GladWe do get these kind of warnings while deploying the process flows. But treat this as a mere warning which does not hamper the execution of the process flows in anyway.
As for the reason of this error, as long as it is running I have never bothered to find out the reason for this warning message.
regards
-AP -
Can anybody identify this warning message?
It always appear when I'm creating a logical port on my SolMan system. What message should I get from it? Should I do anything to my web service?
Thank you!This is a known issue.
Contact [email protected] and ask for "Combined muxer" patch.
Kumar
Anirudh wrote:
Hi,
I am getting following message on my console :
<Sep 10, 2002 7:12:38 PM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '123' with no corresponding table entry>
<Sep 11, 2002 12:40:48 AM GMT+08:00> <Warning> <Posix Performance Pack> <Got exception
for fd: '151' with no corresponding table entry>
I have deployed the WL server on HP-UX 11.0 and wlserver version is 6.1 sp2. Could
anybody explain the warning message ?
TIA
Anirudh
Maybe you are looking for
-
Hello, I am attempting to use a combination of Vidalia and the Torbutton Firefox extension to access the Tor network. However, every time I do, Firefox refuses to load any pages, stating that it is connected to a proxy that is refusing connections. M
-
What are all the Date pickers available in SAP Netweaver?
I am using Java based SAP Netweaver. I want to enter DATE OF BIRTH in a WebDynPro page. Default date picker shows current month only (refer attachment). Picking date with option to change Year, Month is required. Please help in this regard. With T
-
[SOLVED] Can't get Flash plugin to work.
Hi, all. I have done a fresh install of Arch, but am still using my previous /home partition. I've installed mozplugger, Flash and Firefox, but the Flash plugin doesn't function. Can anyone tell me how I can get around this? Many thanks, Chris. Last
-
In Item groups need to be create subgroups
Hi every one, In Itemgroups need to create a sud groups for example Computers is main group under computers we have to create different sub groups like main Item Group is Computers under this group dell computers is a sub group and under dell there
-
Graphic link isn't shown in the links panel.
Hi there. I'm working on a 550 page catalogue. As many problems with InDesign start, we've converted the file from Quark Xpress into InDesign. This was a manual process and we drag and dropped all the images across, luckily InDesign took the link wit