Weblogic 10 NoSuchMethodError: For GenericClassLoader

I try to run a samples class that weblogic provide(http://edocs.bea.com/wls/docs100/wldf_configuring/access_diag_data.html#wp1100898), however I got following error:
Caught exception, weblogic.utils.classloaders.GenericClassLoader.getAugmentableSystemClassLoader()Lweblogic/utils/classloaders/GenericClassLoader;
java.lang.NoSuchMethodError: weblogic.utils.classloaders.GenericClassLoader.getAugmentableSystemClassLoader()Lweblogic/utils/classloaders/GenericClassLoader;
 at weblogic.rmi.internal.ClientRuntimeDescriptor.<clinit>(ClientRuntimeDescriptor.java:51)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFactoryDelegate.java:205)
 at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
 at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
 at weblogic.jndi.Environment.getContext(Environment.java:307)
 at weblogic.jndi.Environment.getContext(Environment.java:277)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:197)
 at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:143)
 at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
 at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
 at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
 at WLAccessor.getRuntimeMBeanServerConnection(WLAccessor.java:178)
 at WLAccessor.getAccessor(WLAccessor.java:56)
 at WLAccessor.queryEventData(WLAccessor.java:78)
 at WLAccessor.main(WLAccessor.java:106)
Where can I find the right jar files? Thanks

You don't need to downgrade.
While WebLogic 10.3 servers runs on a 1.6 JVM, but not a 1.5 JVM, it still supports JEE 5. The JVM version is not the same as the JEE version. For information on JVM and JEE support, see:
[http://edocs.bea.com/wls/docs103/compatibility/compatibility.html]
[http://e-docs.bea.com/platform/suppconfigs/configs103/103_over/overview.html]
[http://www.oracle.com/technology/software/products/ias/files/oracle_wls_certification_10gr3_matrix.xls]
Tom

Similar Messages

Log4j not logging messages out to weblogic console for custom automatplugin

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

"weblogic.utils.classloader.GenericClassLoader" Unable to locate the jar ?

Hi,
I get the exception ClassNotFoundException : weblogic.utils.classloader.GenericClassLoader
I tried searching for the jar having this class everywhere but did not find the jar. Anybody has any idea ?
I am using weblogic version 10.0 MP1
Thanks and Regards,
as

com.bea.core.utils.classloaders*.jar in $ORACLE_HOME/modules directory

Problems Starting Weblogic Server for Tutorials (Fresh install)...

Hi guys, need a little help here.
I'm trying to startup Weblogic Server for Java Control Tutorial application and I get all sorts of errors, mostly seeming to deal with JMS/JNDI network stuff. Here's the error dump I get:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
Starting WLS with line:
C:\bea\JDK142~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:Com
pileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da
:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls
.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.con
figuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.managem
ent.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ign
oreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.log
ErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=C:\bea\WEBL
OG~1\server\lib\weblogic.policy weblogic.Server
<Oct 30, 2005 2:33:31 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Micro
systems Inc.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Configuration Management> <BEA-150016> <Th
is server is being started as the administration server.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877>
<Oct 30, 2005 2:33:32 PM PST> <Notice> <Management> <BEA-140005> <Loading domain
configuration from configuration repository at C:\bea\WEBLOG~1\samples\domains\
workshop\.\config.xml.>
<Oct 30, 2005 2:33:33 PM PST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\weblogic81\samples\domains\workshop\cgServer\cgServer.log is op
ened. All server side log events will be written to this file.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <WebLogicServer> <BEA-000327> <Starting W
ebLogic Admin Server "cgServer" for domain "workshop">
<Oct 30, 2005 2:33:38 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:40 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:42 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:44 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:46 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:47 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgJM
SPool-nonXA" deployment failed with the following error: 0:Could not create pool
connection. The DBMS driver exception was: SQL-server rejected establishment of
SQL-connection. Pointbase Server may not be running on localhost at port 9093..
>
<Oct 30, 2005 2:33:48 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:50 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:52 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:54 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:56 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgPo
ol" deployment failed with the following error: 0:Could not create pool connecti
on. The DBMS driver exception was: SQL-server rejected establishment of SQL-conn
ection. Pointbase Server may not be running on localhost at port 9093..>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce" deployment failed with the following error: DataSource(cgDataSource;cgSamp
leDataSource) can't be created with non-existent Pool (connection or multi) (cgP
ool).>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce-nonXA" deployment failed with the following error: DataSource(cgDataSource-
nonXA;weblogic.jdbc.jts.ebusinessPool) can't be created with non-existent Pool (
connection or multi) (cgJMSPool-nonXA).>
<Oct 30, 2005 2:33:57 PM PST> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer
" store failed to open java.io.IOException: JMS JDBC store, connection pool = <c
gJMSPool-nonXA>, prefix = <weblogic>: connection pool does not exist.
java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JMS> <BEA-040123> <Failed to start JMS Se
rver "cgJMSServer" due to weblogic.jms.common.JMSException: JMS can not open sto
re cgJMSStore.
weblogic.jms.common.JMSException: JMS can not open store cgJMSStore
at weblogic.jms.backend.BEStore.start(BEStore.java:163)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Caused by: java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-non
XA>, prefix = <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
... 29 more
>
<Oct 30, 2005 2:33:57 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090170> <Loading the priv
ate key stored under the alias DemoIdentity from the jks keystore file C:\bea\we
blogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090171> <Loading the iden
tity certificate stored under the alias DemoIdentity from the jks keystore file
C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.j
ks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\JDK142~1\jre\lib\security\cacerts
.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000331> <Started We
bLogic Admin Server "cgServer" for domain "workshop" running in Development Mode
>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
rted in RUNNING mode>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "Li
stenThread.Default" listening on port 7001, ip address *.*>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SS
LListenThread.Default" listening on port 7002, ip address *.*>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 2 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds until
the condition clears.>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 2 attempts. The MDB will attempt to reconnect every
10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 62 attempts. The MDB will attempt to reconnect ever
y 10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 63 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds unti
l the condition clears.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 122 attempts. The MDB will attempt to reconnect eve
ry 10 seconds. This log message will repeat every 600 seconds until the conditio
n clears.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 123 attempts. The MDB will attempt t
o reconnect every 10 seconds. This log message will repeat every 600 seconds unt
il the condition clears.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
THANK YOU for any help you can provide!

These are errors/warning because of incorrect connection pool settings.Either the database parameters were not configured correctly or there were some issues with the configuration itself.
Your server did start up correctly though.
"<Server started in RUNNING mode>"

Coherence integration with oracle weblogic portal for Session management

Could you please let me know how to configure coherence integration with oracle weblogic portal for Session management. Its very urgent. please help.

Please take a look at the following web page -
http://coherence.oracle.com/display/COH35UG/Coherence*Web+Session+Management+Module
-Luk

(Help) system classpath -Vs- the place where weblogic looks for classes

The following is my app's hierarchy.
myapp
|
|__myjsp.jsp
|
|__WEB-INF
|
|__classes
|_ MyClass.class
I am not able to use MyClass within myjsp.jsp
i.e. a scriplet like that shown below gives an error stating that MyClass isnt found
<% MyClass obj; %>
I've tried setting the system classpath, but to no avail.
Is there a difference between the system classpath and the place where weblogic looks for classes?
(I am running my app by creating a myapp.war file and placing it in autodeploy folder)

Try moving your class to a named package and use the appropriate import statement in your JSP. Loading it from WEB-INF/classes/packagename should be fine so you might want to remove the other classpath mods you made to eliminate that uncertainty.
Here's a snippet from http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rweb_jsp_migration.html:
"As of JSP 2.0, referring to any classes from the unnamed or default package is not allowed. This can result in a translation error on some containers, specifically those that run in a JDK 1.4 or greater environment which will also break compatibility with some older JSP applications. However, as of JDK 1.4, importing classes from the unnamed package is not valid. See Java 2 Platform, Standard Edition Version 1.4.2 Compatibility with Previous Releases for details. Therefore, for forwards compatibility, applications must not rely on the unnamed package. This restriction also applies for all other cases where classes are referenced, such as when specifying the class name for a tag in a Tag Library Descriptor (TLD) file."
HTH,
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Looking for a WebLogic Admin for a client in the Miami, FL area


We are currently looking for a WebLogic Admin for a client in the Miami, FL area (Permanent position)
This right candidate must have experience with the following technical skill sets:
· Extensive experience with WebLogic and SQL Server
· Solid expertise as WebLogic Administrator | Web Administrator | Java Developer
· Strong experience in Web hosting infrastructure
· Experience in WebLogic installation, configuration, and tuning;
· Performed application deployments and diagnosing performance related issues with WebLogic;
· Worked with BEA/Oracle WebLogic Technical Support in resolving the critical issues by analyzing the logs and config files and follow up on the open incidents;
· Extensive experience in WebLogic Administration, monitoring and troubleshooting;
· Ability to analyze the results of monitoring systems to identify problem areas;
· Experience in writing WLST scripts for deployment, start and stop servers;
· Solid experience using Java, doing systems maintenance or new functionality development
· Worked closely with development and testing teams to implement fixes in Production under strict time constraints;
· Involved in troubleshooting for production issues and escalating as per the requirement;
· Experience in writing scripts to handle complex automation / administration;
Some Preferred Experience:

· Past experience in the financial sector would be preferred


If you are interested, know anyone or have any questions please feel free to call or email me at (561) 745-6945 or [email protected]


Thanks in advance,
Bob Kelly


FYI. Forums abuse has been reported.
:Rob:

SimpleCallbackHandler no longer in weblogic.jar for WebLogic 10.3g

I was using the weblogic.security.SimpleCallbackHandler in WebLogic 9.2 to authenticate users. I looked at the documentation for 10.3g and it still mentions this class is available, however it is not in the weblogic.jar file nor in the javadocs. Here is the URL where I was looking. http://e-docs.bea.com/wls/docs103/security/thin_client.html#wp1035574.
The only CallbackHandler in the 10.3g release seems to be the weblogic.security.URLCallbackHandler class. I tried replacing the SimpleCallbackHandler with this class. When I put the weblogic.jar in my classpath and build, I get the following error.
class file for weblogic.security.acl.internal.AuthenticatedSubject not found
ServletAuthentication.runAs(mySubject, request);
Indeed, this class is not in the weblogic.jar file. Both SimpleCallbackHandler and AuthenticatedSubject were in the weblogic.jar for WebLogic 9.2
<code>
import javax.security.auth.Subject;
import weblogic.security.SimpleCallbackHandler;
import weblogic.security.services.Authentication;
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws Exception {
LoginForm loginForm = (LoginForm) form;
Subject subject = Authentication.login(new SimpleCallbackHandler(loginForm.getUsername(), loginForm.getPassword().getBytes()));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
<./code>
Why were these removed and not deprecated???

SimpleCallbackHandler does not exist in weblogic.jar. Used the following code to get around this. WebLogic documentation offers this as an alternative to using SimpleCallbackHandler.
Subject subject = Authentication.login(new URLCallbackHandler(uid, pwd));
weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
This code agrees with the snippet provided in WebLogic documentation
Project does not compile with the following error:
Project: C:\apps\11g\PrismMainApp\ViewController\ViewController.jpr
C:\apps\11g\PrismMainApp\ViewController\src\adr\prismmain\view\managed\PrismLogin.java
Error(70,28): cannot access weblogic.security.acl.internal.AuthenticatedSubject

Weblogic plugin for Apache 2.2

Where should I download the weblogic plugin for Apache 2.2?
I'm running WL 10.3 on windows xp.
Please provide the link .
Thanks,
sripos

Hi
On this link, click Accept license and go all the way to bottom and click on All Versions link named next to "Oracle WebLogic Server Web Server Plugins 1.1"
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
That click should open this below link. Accept the license and Download the zip file. Then follow the instructions.
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html
Thanks
Ravi Jegga

What is the default password for weblogic 11G for EPM 11.1.2

HI All,
Just need to know the default user name and password for weblogic 11G for EPM 11.1.2.
At the time of installation I have kept the default user name epm_admin and a password... but its not accepting that user name and password.
Any help on the above?

On my painfully new 11.1.2 install, and per the install instructions, the username and password are as follows:
epm_admin
whatever you set up -- (As I only ever use one of three different ones when I do installs, it wasn't too hard to go through all of the possibilities)
See: http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_install/frameset.htm?webLogicDomainName.html
Regards,
Cameron Lackpour
Edited by: CL on Aug 3, 2010 11:14 AM

Weblogic server for Windows 7 64 bit operating system

Hi,
I have installed Personal Oracle 11g on my laptop. Next, I would like to install the weblogic server and then the Fusion middle ware. My goal is to have Oracle Forms, reports and discoverer running on the laptop. I dont see Weblogic server 64 bit for windows in the oracle product matrix. Can anyone suggest where I can get weblogic server for Winfows 7 64 bit machine?
Thanks,
RV

Hi,
Oracle WebLogic Server Downloads can be found at http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
I believe Oracle WebLogic Server is not certified yet on Windows 7 64-bit, and this explains why you cannot find installation files to download. More details about the product certification can be found at:
Oracle Certification Matrix
http://www.oracle.com/technology/support/metalink/index.html
Regards,
Hussein

Exception occurred when tried to install Weblogic Adapter for SAP 7.0

Hi,
 I tried to install current available Weblogic Adapters for SAP 7.0 into weblogic platform 8.1 sp3, I got the following exceptions. Those exceptions can be reproduced when to deploy BEA_SAP_1_0_70.ear into a weblogic integration domain. Based on BEA Weblogic Adapter for SAP installation guide, there should be a new version of adapter for SAP, such as BEA_SAP_8_1.ear, but for some reason, I couldn't find it. The following are error messages, please help.
 Thanks,
 pg
 ------------- error message ------------------
 <Jul 28, 2004 3:01:41 AM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating Deploy task for application BEA_SAP_1_0_70.>
 <Jul 28, 2004 3:01:41 AM EDT> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 2 for the application BEA_SAP_1_0_70.
 weblogic.management.ApplicationException:
 Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 2
 Module: BEA_SAP_1_0.rar Error: Error parsing file at line: 36 column: 27. weblogic.xml.process.XMLParsingException: Error parsing file at line: 36 column: 27. The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)". - with nested exception:
 [org.xml.sax.SAXParseException: The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)".]
 org.xml.sax.SAXParseException: The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)".
 at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1189)
 at weblogic.xml.jaxp.WebLogicParser.parse(WebLogicParser.java:67)
 at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:154)
 at weblogic.connector.deploy.dd.xml.WeblogicRarLoader_Connector10.process(WeblogicRarLoader_Connector10.java:170)
 at weblogic.connector.deploy.dd.xml.DDUtil.processDDFile(DDUtil.java:380)
 at weblogic.connector.deploy.dd.xml.DDUtil.processWeblogicRaDD(DDUtil.java:218)
 at weblogic.connector.deploy.dd.xml.DDUtil.processDDFiles(DDUtil.java:126)
 at weblogic.connector.deploy.dd.xml.DDUtil.getConnectorDescriptor(DDUtil.java:602)
 at weblogic.connector.deploy.dd.xml.DDUtil.getConnectorDescriptor(DDUtil.java:577)
 at weblogic.connector.deploy.ConnectorModule.loadConnectorDescriptors(ConnectorModule.java:693)
 at weblogic.connector.deploy.ConnectorModule.loadDescriptor(ConnectorModule.java:202)
 at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1379)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1204)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Hello,
 You may have a lot of greif if this is the wrong version of adaptor for 8.1. I too was directed to this EAR file when looking for the 8.1 adaptor. The problem looks like it is in the weblogic-ra.xml file in BEA_SAP_1_0.rar. The some of the xml entries for <map-config-properties> loo incomplete:
 <map-config-property>
 <map-config-property-name>bselocation</map-config-property-name>
 </map-config-property>
 <map-config-property>
 <map-config-property-name>bseeis</map-config-property-name>
 </map-config-property>
 Are missing a value tags.
 You can try adding some dummy ones in order to get passed the SAX exception but you may run into more problems. (I was going to install this my self but never got round to it in the end).
 Good Luck

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

Need WebLogic.jar for download

I need WebLogic.jar for development .Kindly let me no from where can i get?

Go to support.oracle.com
Search for document id 763603.1
OR
edelivery.oracle.com and use the BEA WebLogic Media Pack
Did you try creating a wlfullclient.jar?
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/jarbuilder.htm#BABCGHFH

BEA WebLogic jDriver for Microsoft SQL Server

Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
Thank you for your attention regarding this matter.

Actually, this driver is already documented as deprecated. We intended to remove it from a future
release (most likely, the release after WLS 8.1).
The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
for features, quality, and performance. We are pushing very hard to have this replacement
driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
ship in July). The most likely candidate is already in testing both at the WLS level and
with the layered products. It also did quite well in an internal performance comparison.
"Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
>
>
Peter Foskaris wrote:
Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
product development direction.
>>
Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
our next major release (8), but may not be in future ones.
Joe Weinstein at BEA

Weblogic 10 NoSuchMethodError: For GenericClassLoader

Similar Messages

Maybe you are looking for